From one image to your entire catalog
The same API becomes the rendering backend for your application. No migration needed when you scale.
From one render to your entire product catalog
The same Three.js application that renders one image for one customer can generate every variant, from every camera, for every SKU.
Start with a button
await render()Then render multiple cameras
One capture and one upload, a picture from each camera in your scene.
await render({
cameras: ['hero', 'front', 'detail']
})Then generate every product variant
Your own code puts the scene in each state. One variant is in memory at a time, so one browser tab can make six thousand pictures without running out of memory.
await renderVariants({
key: 'fall-2026',
variants: products,
apply: (product) => configurator.show(product),
cameras: ['hero', 'front', 'detail'],
maxCost: 600
})Or render the catalog from your server
Models that already sit on a CDN need no browser. Name the URLs and the shots from Node; we fetch each model once, frame every angle from its own size, and the run goes on overnight without your process. On the Production and Scale plans.
await api.renderBatch({
key: 'fall-2026',
products: [{ id: 'chair-aria', url: 'https://cdn.shop.com/chair-aria.glb' }],
shots: ['three-quarter', 'front', { kind: 'video', from: 'front', to: 'back' }],
room: { preset: 'loft_golden' },
maxCost: 600
})Set one spending limit for the whole run. Pictures that would go over it are refused, never charged.
Run it again after a crash or a change. Pictures from the last 30 days are reused at no cost.
Test first. One call renders three products from every camera, small and fast, before the full run is paid for.
Customer downloads
Give configurator users a studio-quality image of the exact product they created.
Product imagery
Generate product page, catalog and marketplace images from the 3D product data you already have.
Quotes and proposals
Attach photoreal renders to customer configurations automatically.
Marketing
Make campaign images in every color, material and camera angle.
Batch rendering
Turn thousands of configurations into production assets without maintaining a separate render pipeline.
Thumbnails
Render every SKU and finish again whenever the model changes.
Your configurator can become your content pipeline
Interactive 3D and offline rendering have traditionally been separate workflows, with two material libraries and an offline scene somebody has to keep in sync by hand. Bakery3 connects them.
No second material library.
No manually synchronized offline scene.
No separate rendering pipeline.
Rendering gets cheaper the second time
Large configurator scenes shouldn’t be uploaded again for every image. Bakery3 hashes your assets and only uploads what changed.
First render
148 MB
uploaded
Change the camera
2 KB
uploaded
Change one texture
6 MB
uploaded
Geometry, textures and environments are reused automatically, and the exact same render again within 30 days costs nothing.
Built to go into production
The API you try for free is the one that becomes the rendering backend for your application. You don’t migrate to a different product when you scale.
- Async jobs and signed webhooks
- Batch rendering
- Persistent asset caching
- More renders at once on a plan
- Project budgets and spend limits
- Teams and roles
- Reserved GPUs, by contract
For agencies: one integration across every client
Agency workspace ├── Furniture client ├── Kitchen client ├── Bicycle client ├── Jewelry client └── Automotive client
Separate projects, credentials, budgets and usage. One rendering workflow across all of your Three.js work.
For high-volume configurators: thousands of product images without running your own render servers
- Large batches with many renders at once
- GPUs reserved for you
- Usage commitments and invoice billing
- Priority support and custom retention
- Enterprise security review
Keep your product logic in Three.js. We’ll operate the rendering infrastructure.