App Embed
In the Shopify theme editor this appears under App embeds as 3D Bits - Auto 3D on product pages. It is the recommended way to run 3D Bits and the only thing most stores need.
Switching it on lets 3D Bits render on your storefront. On each product page it checks whether that product has a published 3D Bits project, and if it does, it draws the configurator. Products without one are left alone.
If you have not turned it on yet, Enable 3D on Your Store walks through it.
The embed applies to your whole store, and presentation usually needs to differ between products, so nearly everything is set per project in the 3D Bits admin instead. Only Placement (CSS selector) and Runner CDN Link are read from the theme editor. The other settings you can see there are carried by each published project and the project's value wins, so changing them here has no effect on a product you have published from the app.
Placement
Default: form[action*="/cart/add"]
A CSS selector saying where on the product page the 3D viewer goes. The viewer becomes the first thing inside the element it matches.
The default targets your add to cart form, which every Shopify theme has, and that is why the embed works on any theme without setup. The form gets special treatment: the viewer is never put inside it, but at the top of the theme section that holds it. That is the top of your product section, above the gallery.
To put the viewer somewhere else, enter that element's selector instead. A common choice is the product gallery or media area, for example div.product__media-wrapper. The exact selector depends on your theme, and your theme developer or your browser's inspector will tell you what it is.
If the selector matches nothing, 3D Bits falls straight back to your add to cart form - it does not wait first. It only keeps retrying, for about ten seconds, if it cannot find that form either, which is what happens on a theme that renders the product page late. So a typo does not usually leave the page blank, it leaves the viewer in the default place. Check on a real product page after changing it rather than trusting the theme editor preview.
The Split layout builds around the same element: 3D Bits finds what you named, then lays the canvas out beside the column that holds it. A selector that points at your gallery therefore affects that layout as much as the plain inline one.
Runner CDN Link
Pins which version of the Bitbybit runner, the 3D engine that draws the scene, your storefront loads. The options panel, pricing and cart code come with the app and do not follow this link. Leave it as it comes unless we have asked you to change it, or unless you are hosting the runner files yourself. A configurator you updated from its project page loads the version set there in place of this link - see Runner versions.
Fuller explanation in Runner CDN Link.
When the embed stays out of the way
There are two situations where the embed deliberately does nothing, both to avoid drawing a second viewer on top of one that is already there.
The first is a project whose Placement on the product page is set to Theme template blocks. You have told us you want to position things yourself, so the embed leaves those products to your blocks. See Switching a project to blocks.
The second is a product configured before the app embed existed, using a BITBYBIT VIEWER or RUNNER block placed into a template with the product's metafields filled in by hand. Those keep working as they always did, and the embed recognises them and leaves them alone.
In your cart
The embed also loads a script for the cart, and it has two jobs.
The first is drawing the configuration summary. When you charge configured amounts as product lines, the row your theme draws has a price with nothing on it explaining the price. The script fetches the product's published scene and rebuilds the summary from the shopper's own configuration, using the same row builder the PDF report uses, so the cart, the PDF and the order cannot disagree about what was ordered. You control how that summary looks, and where in the row it sits, from Composer's Cart overview tab.
The second is tidying up. A configured item is accompanied by helper product lines that carry its option amounts. If a shopper removes the configured item itself, those lines would be left behind on their own, and checkout would refuse them. The script spots lines whose configured item has gone and removes them, so the cart adds up again without the shopper having to work it out.
This runs on every page, not just /cart, once the cart holds something configured. That is deliberate: a cart drawer is the same cart opened on a collection or home page, and if the script only ran on the cart page a drawer opened anywhere else would show a bare row with no summary.
Settings that live in the app instead
Canvas height on desktop and mobile, maximum width, side offset, top and bottom margins, the storefront layout, which side the options panel sits on and how wide it is are all set per project, in the 3D Bits admin, under a project's Storefront settings. Saving there applies them to your published products straight away, without a republish. Canvas and layout sizing covers them.
Pausing a configurator is also a per-project action, but it is not in Storefront settings either. You pause it from the project's own page, with Pause this configurator, and Resume selling puts it back. See Projects.
The settings below are still shown in the theme editor, but a project published by the app always carries its own value and that value wins. The explanations are in Settings the Project Overrides and under each setting's own heading in Common Settings.
| In the theme editor | Set per project as |
|---|---|
| Show Fullscreen Button | Show fullscreen button |
| Show Spinner | Show loading spinner |
| Receive Input Names As Variants | Receive input names as variants |
| Input Collection Mode | Input collection mode |
The two input settings only matter when the configurator reads your theme's own inputs, such as its variant pickers or a third-party options app, rather than a panel you built in Composer.
Enable OCCT, Enable JSCAD, Enable Manifold
These load geometry engines used by parametric configurators built with scripts. Each one adds to what the page has to download, so only what a script actually uses should be switched on.
A project built in Composer chooses its own engines in the Scripting section and boots nothing else, so these three do not apply to it. Scripting covers that. A script project sets them in the CAD kernels card on its own page.
The individual settings are explained under Enable OCCT, Enable JSCAD and Enable Manifold.
Verified against the product in November 2026