RenderDrama

What a second of AI video costs, channel by channel

What Segmind publishes about price

Segmind (segmind.com) does print a per-second figure, and it is not a second of video: $0.00310 a second for a dedicated H100 endpoint, alongside $9.00 an hour for the same machine. Per-model prices are reached by searching rather than printed. As of 2026-09-22.

A second of hardware against a second of videoA comparison of the per-second figure this page prints with the one the ledger records. Three tenths of a cent buys one second of a reserved graphics card. A second of finished video consumes an unstated number of those, decided by model, resolution and clip length, none of which the page fixes.A second of GPU timeA second of videoPublished here$0.00310, and $9.00 an hourNo figure on the pageWhat fixes itThe clock, while the card is yoursModel, resolution and clip lengthPredictable before useOnly if you know the runtimeYes, where a channel prints itTwo figures that share a unit name and measure different things
Fig. 1 The cheapest-looking figure in the register belongs to the most usage-dependent purchase on this page, which is why the unit has to be read before the number.
What is and is not on Segmind's own pricing pages, read on 2026-09-22.
ItemOn the page
GPU time per hour and per secondPublished
A per-run price banded by inference stepsPublished for one model
Per-model pricesReached through a search box
Seconds of video as a billing unitNot published
A per-second figure for generated videoNot published

Inclusion rule. Items a per-second rate would need, plus what the vendor publishes instead. Items no vendor in this field publishes are not listed. Order. Published items first, then the missing ones.

1A per-second price that prices the machine, not the output

Three tenths of a cent a second looks like the cheapest figure in this entire register until the unit is read. It prices a reserved graphics card for a second of wall-clock time, and a second of finished video takes many of those seconds — how many depends on the model, the resolution and the length of the clip, none of which this page fixes.

That is the distinction the ledger's method page exists to hold. Two figures can share a unit name and measure different things, and a comparison that ranks them together is not slightly wrong but inverted: the cheapest-looking row here belongs to the most usage-dependent purchase on the page.

2Banded by steps, which is a third billing shape

One model on the page is priced by the run in three bands: a few dollars under a hundred and fifty inference steps, double that to five hundred, and triple above it. Steps are a quality knob, so this is a price that rises with how hard the buyer asks the model to work, which is neither a rate per second nor a flat price per clip.

A production cannot budget video from it, because the step count for a video generation is not something the page relates to a duration. It is recorded because it is published and because it shows how many shapes a price can take in one market: per second of output, per clip, per credit, per hour of hardware, per run banded by effort.

3Prices behind a search box are published, but not readable as a list

The page invites the reader to search for a model to see its pricing. Each individual answer may well be public, and none of them is on a page that can be read as a table, so there is nothing here to record as a channel-level rate. This register reads pages; it does not enumerate a catalogue one query at a time and present the result as a vendor's published price list.

If the video models were listed with their units on a readable page, this entry would move to the ledger or not depending on what that unit turned out to be. As things stand the only units on offer are hardware time and run bands, and neither converts.

4The production behind the price

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

Each segment is generated on whatever tier was selected at the time, and the episode composites them together.

SceneMixer, 480P, 720P or 1080P: Which Tier to Pick — “Can I mix tiers in one episode?” (read 2026-10-13)

The longest an episode may run: 240 seconds for Short Drama, 300 for TV Series, none for Film.

SceneMixer, Short Drama, TV Series or Film — “What is the episode cap?” (read 2026-10-13)

5Sources

Read from segmind.com, checked 2026-09-22. What this register accepts as a published rate is on the method page; the channels that do publish one are on the ledger. What Segmind publishes in the other columns: what the page meters. Also without a published rate: Synthesia, Luma.

  • What Segmind publishes instead of a rate
    GPU time by the hour and by the second, plus a per-run price for one model, and no figure per second of videoSegmind, pricing page / recorded 2026-09-22
  • The only per-second figure on the page
    $9.00 an hour, printed also as $0.00310 a second, for a dedicated H100 endpointand it prices GPU timeSegmind, pricing page / recorded 2026-09-22
  • A per-run price banded by inference steps
    $3 under 150 steps, $6 from 150 to 500 steps and $9 above 500 steps, stated for Flux-ProSegmind, pricing page / recorded 2026-09-22
  • Where the video model prices sit
    Per-model prices are reached by searching for a model rather than printed on the pageSegmind, pricing page / recorded 2026-09-22