How to Make a Product Video With Creatomate (2026 Guide)

November 11, 2026

Creatomate renders video from templates programmatically — you design a template once, then fill it with data via API or CSV and get an MP4 per row. A single 15-second render takes roughly 10 to 30 seconds.

It’s a developer tool with a visual editor attached, which is the reverse of most video makers. If you need one hand-edited video, this is the wrong product. If you need 500 variants of the same 15-second template for a product catalog, Creatomate is designed exactly for that.

What makes Creatomate different from a video editor?

Templates are JSON. Every element — text, image, video, audio, shape — is a key you override. That means your backend, a spreadsheet, or a form can produce a video without anyone opening an editor.

It also has a browser editor for building the template, plus a REST API, a Node/Python SDK, and integrations with Zapier and Make.com.

How do you build your first template?

  1. Sign in and create a template from one of the starter compositions or start blank.
  2. Set the canvas: 1080×1920 for vertical, 1920×1080 for horizontal, 1080×1080 for square.
  3. Add elements — a background image placeholder, a headline text layer, a subhead, a logo.
  4. Mark each element you’ll override with a name (e.g. headline, product_image). Names are the API contract; change them later and every render breaks.
  5. Add a short fade or slide animation at 0-0.4s so the layers don’t pop in.
  6. Save and copy the template ID.

Step 4 is the one that matters. Name elements by function, not appearance.

How do you render from the API?

The render endpoint takes a template ID and an array of modifications. You send the modifications as key-value pairs matching your element names, plus the output format and dimensions.

A minimal request needs: the template ID, the modification list, and output_format set to mp4. The response returns a render ID you poll, or you provide a webhook URL and the render status is pushed when it finishes.

Use webhooks for batches. Polling a 500-video batch at 1-second intervals will get you rate limited, and the webhook route is simpler once it’s wired.

How fast does a batch render, and what does it cost?

Batch Render time Notes
1 video, 15s 10-30s Includes queue wait
50 videos 8-15 min Parallel workers
500 videos 1.5-3 hours Depends on concurrency on your plan

Pricing is per rendered minute of output. A 15-second video is a quarter of a minute of render time. Plans start with a monthly render-minute allowance and scale up; volume tiers drop the per-minute rate.

The cost trap: re-rendering after a template edit. If you edit the template, every previously rendered video is stale. Design the template properly once, run a 10-video test batch, then render the rest.

Where does Creatomate get in the way?

The editor is functional, not pleasant. Complex compositions with layered animations are fiddly to build visually, and debugging a template that renders wrong usually means inspecting the JSON rather than the canvas.

Font handling causes real problems. Custom fonts need to be uploaded to your project and referenced by name; if the font isn’t registered, renders fall back silently to a default and you don’t notice until you watch one.

It also doesn’t do generative content. No AI scripting, no AI B-roll. You supply the assets.

Who should use it?

Ecommerce teams with large catalogs, SaaS companies generating personalized onboarding videos, real estate and automotive listings, and agencies producing localized variants at scale.

Don’t use it for a one-off brand film — a real editor plus a freelancer is faster and cheaper there. Don’t use it if your video needs story-level variation between pieces; templates are templates.

Quick Summary

  • Creatomate builds videos from named-element templates filled with JSON data via API.
  • A 15-second render takes 10-30 seconds; 500 videos take 1.5-3 hours.
  • Pricing is per rendered output minute, with volume tiers lowering the rate.
  • Name template elements by function and upload custom fonts or they fall back silently.
  • Built for catalog-scale variants, not for one-off editing.