A forty-clip assembly exports for the same charge as a two-clip trim
Editor credits are 0 × previews + export_price × final_exports; timeline complexity is not a term.
Editor credits are 0 × previews + export_price × final_exports; timeline complexity is not a term.
A forty-clip assembly with music and captions exports for the same single charge as a two-clip trim. The billed variable is how many times you asked for a finished file, not how many sources sit on the timeline and not how many times you moved a cut. Editor previews and final export is the cost page for that formula. This post is the constraint the formula encodes: complexity is not a coefficient.
A count, not a rate
Most pages on the cost hub are about a rate — per second, per 1,000 characters, per megapixel. This one is about a count.
credits = (0 × preview_renders) + (export_price × final_exports)
preview_renders are 480p passes used while you iterate. They cost nothing. A short per-user cooldown sits between them so the pipeline is not hammered. export_price is one editor export charge, quoted before you confirm — a single charge for the whole render, however many clips, overlays and caption tracks the timeline holds. final_exports is how many times you render for real. It is the only term with a coefficient.
Twenty revisions and one export is one charge. One revision and three exports is three. A six-clip edit with music, captions and a title card that takes eight preview passes and one final export is one export charge. Spot a typo after that export and export again, and you have paid twice. The eight previews still cost nothing.
Free 480p previews walk the preview: true switch on edit_video. This page is the arithmetic underneath: the forty-clip timeline and the two-clip trim are the same export_price because clip count is not in the expression.
What a preview can tell you
Previews render at 480p by design — that is what makes them free. Timing, pacing and cut points are visible. Caption wording and placement are visible. Whether the crop loses the subject is visible. Audio mix and levels are visible. Fine detail, grain and compression artefacts are not. Those need the full-resolution export.
The discipline that saves credits is unglamorous: preview until it is right, then export once. A typo caught in the preview is free. The same typo caught after the export costs a second export. Not using the free passes is the most common avoidable charge on this meter.
The video editing hub is the task list that sits on this formula — trim, merge, reframe, assemble with music and captions. Each of those tasks can preview. Each of them bills on export count when you ask for the finished file.
Do not export "just to see it." That instinct is correct on a system that charges per render. It is the wrong instinct here.
One assembly versus a chain
Assembling in one pass is cheaper than assembling in steps. Cutting, attaching audio and burning captions as three separate operations is three charges. Describing the same result as one editor render is one. The output is the same video.
That is why edit a video with music and captions exists as a named job: one EDL, one export. Trim a video on its own is also one export — the two-clip trim in the title. The forty-clip version is not a different price. It is a different timeline on the same charge.
A worked comparison, every row the same edit:
| How you worked | Previews | Charged renders | Charges |
|---|---|---|---|
| Previewed until right, exported once | 8 | 1 | 1 |
| Exported to check, fixed it, exported again | 0 | 2 | 2 |
| Exported after every change | 0 | 5 | 5 |
| Cut, attached audio and captioned as separate steps | 0 | 1 export + 2 operations | 3 |
The fourth row is the common one. Chaining single-purpose operations feels tidier and costs more than describing the finished result in a single render.
Captions and titles are burned into the pixels. A wording change after export means paying for the export twice. Lock the copy in preview.
What the export charge does not cover
The export charge is the editor render. It is not:
- The generation cost of any clip on the timeline — those were charged when they were made.
- Captioning as its own job with its own preset multiplier, if you run that job separately instead of burning type in the assembly.
- Model-backed operations like upscaling or background removal, priced per the model that performs them.
Halving your exports halves this line item. Using previews at all is the lever the formula was written to expose. One render instead of a chain is the other. Plan this one by counting exports rather than credits: one export per finished video is the discipline that matters, and previews are free however many you run.
Clips on the timeline still have to be real HTTPS URLs. file:// paths are rejected. That failure is not a charge, but it is not a preview either. Host the asset, then iterate.
FAQ
Are preview renders really free?
Yes. Preview passes render at 480p at no credit cost, with a short per-user cooldown between them. The final export is the charged render.
Does a longer or more complex edit cost more to export?
No. The export is billed as a single charge for the render rather than by clip count, so a forty-clip assembly and a two-clip trim both resolve to one export.
Is it cheaper to do everything in one editor render?
Yes. Chaining trim, then attach audio, then caption bills each step. Describing the finished result as one assembly bills once.
What if the export comes out wrong?
A completed export is charged. That is exactly what the free previews are for: check timing, wording and framing at 480p, then export once.