Webflow has no server you control, so the integration happens beside the site rather than inside it. Resolve vehicles in an automation, write the URLs into a CMS collection, and bind the field in the Designer like any other image.
An embed that calls an API puts your key in the page source and makes every visitor wait for a third party. A CMS field costs nothing at render time and is editable by whoever runs the site.
One CMS field per angle, one automation, and the Designer does the rest.
A plain text field per angle on your vehicle collection, next to the VIN or the spec you already store.
Make, Zapier or a small script calls the API and writes the URLs back through the Webflow CMS API.
Point an image element at the field. Webflow renders it as a normal image with your own styling.
Re-run the automation when a collection item is added or its vehicle data changes, then publish.
Bring vehicle imagery into your product without the heavy lifting. Clear docs, open SDKs and ready-made plugins connect to your stack in minutes, and our status page shows you live how the API is doing.
Webflow sites are usually built by designers who care that a grid lines up. Identical framing and lighting across every vehicle means the collection list looks intentional without anyone retouching anything.
Webflow projects hit vehicle imagery at the point where the design is finished and the content is not. The collection has forty vehicles, the grid looks perfect with placeholder art, and the real photos arrive at six different crops with backgrounds that fight the section colour.
Because Webflow has no server, the fix has to live in an automation, and that turns out to be an advantage. Resolution runs once per item rather than once per visitor, the site itself stays a static export with no third party call in it, and the Designer keeps treating the image as a field it can style freely.
You should not. The key would be visible in the page source and every visitor would pay for the request. Resolve in an automation instead.
Make and Zapier both work, and so does a small script on a schedule. The only requirement is somewhere safe to keep the key.
No. Store the URL in a plain text field and bind an image element to it. The file stays on our CDN and your asset limits stay untouched.
Unaffected. You are adding fields to items you already have, not new items.
Yes. The URLs are absolute, so an exported site keeps rendering them without any Webflow runtime.
The response tells you when a fallback was used, so the automation can leave the field empty and your Designer conditional can hide the element.
Tell us how your vehicle collection is structured and which angles the design uses. We come back with URLs and an automation outline.
