Block Settings
Every setting on the BITBYBIT VIEWER block, which you find in the theme editor after adding the block to a template. The "BITBYBIT VIEWER" Block explains what the block is for and how to place it.
On a product with a published project you leave the model and scene settings empty, as the project provides them, together with its pricing, option availability and pause. What is left is where the canvas goes and how the block reads your page, and only the block's own settings decide that: the project's Show fullscreen button, Show loading spinner, Receive input names as variants, Input collection mode and Debug mode do not reach this block.

Text settings can each be linked to a product metafield, so that one template shows a different value per product. Dynamic vs. Global Settings explains when that is worth doing, and How to Link Settings to Metafields how to do it. A product set up by hand usually links Model URL and the camera settings, and leaves the rest global. Scene JSON Configuration needs no link: left empty, it reads the product's 3D Bits Scene Config metafield by itself.
Model URL
Loads a single 3D model file. This is the simplest way to put 3D content on a page, and it takes no scene at all.
Give it a public address that starts with http:
https://example.com/models/my-product.glb
It reads glb, gltf, ply, splat, obj and stl. Supported Formats compares them. To host a file on Shopify, upload it under Content then Files, or to the app's Assets, and copy its address.
For more than one model, or for models that respond to what a shopper picks, use a scene configuration below. If you fill in both, the model at this address loads as well as the ones in the scene.
Scene JSON Configuration
Everything a Composer project is, written down: its models, camera, lighting, background, option panel, rules and pricing. Leave this setting empty and the block uses the scene the product's published project provides.
You only fill it in to show something else. It accepts either of two things, and 3D Bits tells them apart by whether the text starts with http:// or https://.
A URL to a JSON file:
https://example.com/scene-config.json
The file has to be public, return valid JSON, and carry CORS headers if it is on another domain. The address of a configurator published from 3D Bits, from Use on any page (homepage, blog, landing) on its project page or Copy URL in Composer, keeps showing that configurator's latest publish, so you paste it once. On a page that is not a product, such as your homepage, it shows the configurator for shoppers to explore. They buy on the product page, so give your page a link to it. A URL also keeps your theme settings cleaner than a long block of text.
The JSON itself:
{
"models": [
{
"url": "https://example.com/model1.glb",
"position": [0, 0, 0],
"scaling": [1, 1, 1]
}
],
"arcRotateCamera": {
"position": [3, 1, 3],
"target": [0, 0, 0]
},
"backgroundColor": "#ffffff"
}
You rarely write this by hand. Composer writes it for you: Copy scene config to clipboard and Download scene config (.json) give you the configuration as it stands. If a part has a SKU, Composer asks first: choose Remove them before you paste the configuration into a product metafield or into this setting, since every visitor to the page downloads it. Pasting it is not publishing, though: computed pricing, option availability and pausing reach a product only through a publish from the app, so sell a product whose price depends on the shopper's choices through a published project. What a scene can hold depends on your plan, as Features by plan shows, and it follows a JSON schema that lists every option.
A camera set in the scene wins over Camera position and Camera target, and Background Color is ignored as soon as there is a scene.
Theme buy buttons
Default: Auto (recommended)
What happens to your theme's own add-to-cart and accelerated checkout buttons when the block renders. Theme buy buttons lists the four choices and why accelerated checkout is treated separately.
Leave this on Auto (recommended) unless you want a different result: Always hide hides the theme's buttons whatever your configuration does, Hide all product option controls also hides the theme's variant pickers, for a page where 3D Bits owns every choice, and Never hide leaves the theme alone. All four act on the same theme elements, so a button your theme builds its own way is not hidden by any of them. The cart form stays in the page in every case.
Settings shared with other blocks
Each of these is documented once, in Common Settings. This is what is particular to the VIEWER block.
| Setting | On this block |
|---|---|
| Runner CDN Link | Picks the lighter viewer runner by itself when the block shows the product's published configurator. |
| Camera position | Defaults to [3, 1, 3], a close view suited to prepared models. |
| Camera target | Defaults to [0, 0, 0], the origin, where models are usually centred. |
| Background Color | Defaults to #ffffff. |
| Show Spinner | Runs until the scene's loading screen takes over, or until the model is ready when there is no scene. |
| Receive Input Names As Variants | Decides the names you match against when a scene reads your theme's own inputs. |
| Input Collection Mode | Standard Inputs is usually enough. Use All Inputs only for hidden fields or an unusual input type. |
| Enable Debug Mode | Shows which names to use in Composer, with the Live and GUI Setup tabs. |
| Try to Prepend, Prepend With Query Selector, Remove Children Before Prepend | Commonly used to put the canvas in the product media gallery, beside or in place of the photos. |
| Show Fullscreen Button | Keep it on unless your theme has fullscreen of its own. |
Verified against the product in November 2026