Layer images and bulk upload

The preview is a stack of transparent images. Each selected answer adds its layer for the current view, and layers stack by question order (z). There is no 3D model to build: if you can export layers from your design tool, you can build a customizer.

Preparing layers

• Use one canvas size per view, for example 1200 × 1200 px, and export every layer at that size with a transparent background.
• Keep each part in exactly the same position it has on the assembled product. The builder only stacks images; it does not move them.
• PNG, JPEG or WebP, up to 20 MB each. The app stores everything as WebP, so file size on the storefront stays small.
• Add a base layer (a shadow or outline) to an answer that is always selected, such as the main body color.

Bulk upload

Open Images in the editor and choose Bulk upload and match. Name each file:

view__question__answer.png

For example front__face-shell__halo.png or side__upper__forest.webp.

• view is the view id.
• question is the question id, its order key, or its English label.
• answer is the answer id, its order value, or its English label.

Case, spaces and punctuation do not matter, so Front__Face Shell__Halo.PNG matches too. Drop a whole folder; the editor shows what matched and lists files it could not place (unknown view, question or answer, or a duplicate) so you can rename and try again.

The asset library

The Library tab shows every image uploaded for your store, with its size and whether it is in use. Uploading the same file twice reuses the existing image.

You cannot delete an image that a customizer still uses; the library tells you which customizer uses it. Remove it from the answers first.

Performance

The builder keeps the old picture until all new layers have loaded, so swapping a part never shows a gap. Layers for other views load in the background. Even so, smaller files load faster on phones: crop empty space consistently across a view and avoid photographic noise in flat-color parts.