Changelog
Improved

Render compose videos faster, priced by length

Long compose videos finish in less than half the time on a new engine, and you pay for the seconds of video you get back, at $0.04 a minute.

API Dashboard SDK MCP

compose jobs now render on a new engine. You send the same JSON to the same endpoint and get the same output format back. Videos come back faster, and the price follows the length of the video you get, billed by the second.

Faster renders. Lower prices. Compose runs on a new engine: long timelines render in under half the time, $0.04 a minute billed per second on every plan, 4K and 60 fps on Studio, and animated text and 3D turns up to 1080p.
Send the same JSON and get the video back faster, billed by the second of video you receive.
  • Speed. A 21-minute customer timeline took 837 seconds to render before and 373 seconds now. Short videos of 6 to 20 seconds finish in 17 to 24 seconds.
  • Price. $0.04 per minute of output video, the same on every plan and for every video your plan can render. Billing is per second, with a 15-second minimum per render, which is 1 cent.
  • What each plan renders. The Free plan renders up to 1080p at 30 fps. Pro renders a plain edit up to 1440p. Studio renders a plain edit up to 4K at 60 fps. Animated graphics above 1080p or 30 fps need an enterprise plan.
  • Plan check before the render. A video above your plan is refused at submit with PLAN_LIMIT, and the message names the plan that renders it. POST /compose/validate and the validate_compose MCP tool run the same check for free and return the price.
  • Animated graphics. Titles can arrive and leave a letter, word or line at a time, and clips can turn in 3D. They render at the same rate, up to 1080p at 30 fps. Every feature is shown rendered on the Compose features page.
  • Failed renders. A render that fails on our side costs nothing. A render that fails where your input may be the cause, such as a source file that will not decode, is charged twice the compute it used. A job that never starts is free.
  • What you change. Nothing for a video up to 1080p at 30 fps. A Free account that renders above that moves to Pro for 1440p or to Studio for 4K and 60 fps, and so does a Pro account that renders 4K or 60 fps today. The timeline schema, the endpoint and the output format stay the same.

What the same customer jobs cost, before and after:

Video lengthBeforeNow
21 minutes$0.855$0.85
20 seconds$0.021$0.013
10 seconds$0.037$0.010
6 seconds$0.047$0.010

Short videos cost less because the price follows the length of the video, not the render time. A long video costs about the same as before and arrives in less than half the time.

New accounts still start with $5 of credit and no card, which covers 125 minutes of compose video. Pro costs $9 a month. It includes $5 of credit each month and adds 25% to every credit purchase. Studio, at $29 a month, includes $20 of credit, adds the same 25% and runs up to 50 jobs at once. ffmpeg jobs keep their per-second compute pricing.

The compose docs list every timeline option, and the pricing page has the full rates.

Share