Visuals

Show a render on your product page

A composite render is one image URL. No SDK, no client-side compositing.

Updated 27 August 2026

You request a render the way you request any picture: one GET, one image back.

/photo/{slug}.png

The slug names the model and every chosen option:

{model}__{parameter}-{option}_{parameter}-{option}
  • __ separates the model from the choices
  • _ separates one choice from the next
  • - separates a parameter from its option

So a page only has to build a string and drop it into src. The whole configuration survives being pasted into an email or a spreadsheet cell.

/photo/demo-sofa__fabric-linen01_wood-oak.png
__ model, then the choices _ one choice from the next - parameter from its option
<img src="/photo/demo-sofa__fabric-linen01_wood-oak.png">
Linen 01, oak
<img src="/photo/demo-sofa__fabric-boucle03_wood-oak.png">
Bouclé 03, oak
One string decides the whole picture: change the fabric in the slug and the src returns a different render.

What to reuse

Troubleshooting

The URL returns a 404

Usually the identifier rather than the shape of the slug. See Pick the right identifier.

One option renders and its neighbour does not

That is a missing layer image, not a URL problem. Check coverage on the model.

On this page
  1. What to reuse
  2. Troubleshooting
  3. The URL returns a 404
  4. One option renders and its neighbour does not

If they can't see it, they won't buy it. Let's show them.

Leave your details and we arrange a free consultation with the people who have spent years helping brands sell customised products. You bring the catalogue and the questions. We bring what has worked, what has not, and what it would take for you.

1Mvariants from one source
Same dayprice changes live in the shop
No-codeconfigurators the client runs
No demo booking, no sales sequence. We reply by email and take it from there.