The background of a vehicle image used to be a fact about where the car was parked. With rendered imagery it becomes a design token: the car arrives as a clean cutout, and what it sits on is your call, made in CSS or in a compositing step you control. Teams underuse this because they think of it as an image-editing problem. It is a parameter.
The building blocks
Requests combine a handful of options: transparency for a pure cutout, shadow for a grounded studio look, ground and mirroring for a showroom-floor reflection, plus color, format and sizing. Every combination is a URL, which means every look below is a template you define once and apply to the entire catalogue.
Four recipes
1. Brand colour, everywhere
A transparent WebP over your brand background colour is the cheapest complete redesign available: one CSS rule, and the whole inventory sits on your identity instead of on forty different forecourts. Works equally in email, where the background is a table cell fill.
2. The grounded studio
A shadow variant on a neutral field reads as a professional studio shoot without any compositing at all. This is the safe default for listings and detail pages. The car sits on something, and every car sits on the same thing. The variants are shown side by side on shadows, reflections and transparency.

3. The showroom floor
Ground reflection with mirroring produces the premium-configurator look, with the car on a polished dark floor. Pair it with a dark page theme for launch pages and flagship placements where you want deliberate drama rather than catalogue neutrality.
4. The campaign composite
For seasonal or campaign creative, a transparent cutout drops into any scene your design team builds: gradient fields, photography, illustration. The cutout's consistent framing is what makes this scale: one template, every vehicle, no masking work per car.
Rules that keep it looking deliberate
- Pick one recipe per surface: grids and galleries in one look, campaign surfaces in another
- Never mix grounded and floating cars in the same grid, it reads as a bug
- Keep contrast honest: dark cars on dark backgrounds need the reflection or shadow to separate
- Let the template own the background; the request should only carry transparency and size
Where each recipe fits in the funnel
The recipes are not interchangeable, and picking by funnel stage keeps the system coherent. Listing grids and search results want the grounded studio, because comparison needs neutrality. Detail pages can afford the showroom floor, because one car has the stage to itself. Campaign surfaces, from paid social to seasonal email, are where the composite earns its keep, since those formats are designed around attention rather than comparison.
Email deserves its own sentence, because it is the surface where teams give up first. A transparent cutout over a table cell fill survives dark mode, renders identically across clients, and needs no image editing when the campaign colour changes. The background is a hex value in the template, so a rebrand touches one variable instead of a thousand images.
The other half of the branding story, what the images deliberately do not carry, is on trim and colour accuracy.




