Skip to main content

Block Settings

Every setting on the BITBYBIT PREVIEW block, which you find in the theme editor after adding the block to a template. The "BITBYBIT PREVIEW" Block explains what the block is for and walks through setting it up.

The block has five settings, and only one is its own. The others it shares with the blocks that draw a canvas.

Model Preview URL​

Which bitbybit.dev script to embed. Give it the script's preview address, which is the address of the script with /preview in place of the editor:

https://bitbybit.dev/app/your-name/project-id/script-id/preview

Using Script Preview Mode shows where to find it.

The block only accepts addresses that start with https://bitbybit.dev/. With any other address it shows The url provided does not point to https://bitbybit.dev. Please provide a valid url. instead of the iframe. Left empty, it draws an empty frame.

Different products usually show different scripts, so this is the one setting worth linking to a product metafield. Use the 3D Bits Model Url metafield the app provides, or one of your own. See How to Link Settings to Metafields.

Settings shared with other blocks​

Each of these is documented once, in Common Settings. PREVIEW runs none of the code the other blocks run, so here they behave a little differently.

SettingOn this block
Show Fullscreen ButtonWorth keeping, as an iframe can feel small at its default size. It relies on the browser's Fullscreen API, with no fallback.
Try to PrependMoves the iframe, commonly into the product media gallery. It looks for the selector once, as the page loads, with no retries and no fallback.
Prepend With Query SelectorWhere to move it. The first match wins.
Remove Children Before PrependRemoves content from the page rather than hiding it, as described on that setting.

What the iframe can and cannot do​

The script runs in a sandboxed iframe, on bitbybit.dev rather than in your theme, and nothing connects the two:

  • It cannot read product variants, form fields or anything else on the page, and it cannot respond to what a shopper picks.
  • It cannot add anything to the cart.
  • Everything a shopper does happens inside the script, so anything interactive has to be built into it, along with whatever the script needs at the sizes your theme gives it.

An iframe loads a whole page of its own, so it is heavier than a canvas in your theme. Keep the script fast, and try the product page on a phone before going live.

For a product that has to respond to choices, use Composer.

Verified against the product in November 2026