RenderDrama

What a second of AI video costs, channel by channel

The price ledger as a file you can compute with

The ledger is published as one file so that the arithmetic on this site can be repeated somewhere else. Each row is one figure with its source and its reading date. As of 2026-09-12.

Which rows carry a rate and which carry an absenceRows split into three kinds: a rate published directly per second, a rate derived from a credit price using the vendor's own conversion, and a record that no computable rate is published. All three are exported, and the third is the one most often missing from comparisons elsewhere.What the pricing page publishesA per-second rateRecorded directlyThe figure, the tier itbelongs to and the page itwas read from.Credits onlyDerivedConverted with thevendor's own publishedrate; the credit pricestays beside it.NeitherRecorded as absentA row saying no computablerate is published. Itcounts.Three kinds of row, all exported
Fig. 1 Dropping the third kind would make the file tidier and make any budget built from it quietly optimistic.

Cost comparisons age badly, and a table in a blog post ages worst of all. A file lets someone rebuild the comparison next quarter against the same sources rather than trusting a screenshot from this one.

Only published figures are exported. Where a channel prices in credits, the conversion used is the vendor's own and the credit price sits beside the derived rate, so a reader who disagrees with the conversion can redo it.

The rows most worth having are the ones that say nothing is published. A budget built only from channels with clean rate cards is a budget that quietly excludes the products hardest to price.

Reuse is governed by the licence named below. Keeping the source column intact is the whole point: a per-second figure without the page it came from is a number nobody can defend in a planning meeting.

1What each column holds

The seven columns in the exported ledger, in file order. Recorded 2026-09-12.
ColumnWhat it holds
fact_idThe line's permanent reference, kept across price changes.
valueThe published figure, in the currency and unit the vendor prints.
applies_toThe model, resolution or tier the figure belongs to.
source_urlThe price page it was taken from.
source_nameThe vendor's title for that page.
value_sinceWhen the figure is first known to have applied.
verifiedThe date the price page was last read.

Inclusion rule. Every recorded figure is exported, including the rows that record an absence of published pricing. Order. File order follows the order figures were recorded, grouping them by channel.

The file is at /datasets/durations.csv, licensed CC BY-SA 4.0. Cite the ledger and the reading date rather than this page.

Elsewhere on the ledger: Channels, Ratings, Unpriced, Price shapes, What each channel publishes, One model, several sellers, Single ratings, Questions, Terms, Learn. How a figure earns a line is set out on the method page.

2What the seconds buy

Price aside, what goes into the seconds behind “Data” is described in SceneMixer's guides:

On a segment’s storyboard card, next to Edit, press AI edit.

SceneMixer, AI Edit: Rewrite a Storyboard Segment by Saying What to Change (read 2026-10-13)

It is the reference every later segment points at, which is what keeps a character's face and a location consistent across an episode.

SceneMixer, Glossary — “What is a setup image for?” (read 2026-10-13)