Credit allowance: capacity bundled with a clean file
A credit allowance is a monthly balance of generation units. Where the first real allowance begins at the same plan that stops the mark, a user crosses the marking boundary because they needed capacity. As of 2026-09-22.
| The term | Credit allowance |
|---|---|
| What it names | A monthly balance of generation units attached to a plan |
| What it is not | A measure of how many finished videos a plan produces |
| Where the register uses it | The prose of paid-tier readings, where the two coincide |
Inclusion rule. Words this site uses in a narrow sense, where the ordinary sense would lead a reader to misread a cell. No vendor statement appears on this page. Order. Fixed order: what the word names, what it excludes, then where it is used here.
1When two limits sit on one line
On several entries the plan that stops the mark is also the first plan with a workable allowance. Below it, output is capped at a few short videos or a single grant of credits; at it, a monthly balance begins. A user who needs to produce anything crosses the boundary regardless of what they think about marking.
That makes the marking boundary invisible as a decision on those entries. It is not that the mark is cheap to remove; it is that nobody ever chooses to remove it separately from choosing to have capacity, and a register that reported only the crossing point would suggest otherwise.
2Where the two limits come apart
On one entry a paid plan buys capacity and leaves the mark in place, so the two decisions are genuinely separate and a subscriber can be paying and still marked. That is the arrangement where the crossing point is worth reading as a decision rather than as a side effect.
The register records the crossing point in the cell and the relationship in the prose, because the relationship is what a production plans around. Knowing that a boundary is unavoidable is as useful as knowing where it sits.
3Why credits are not comparable across entries
A credit is whatever each vendor says it is: a second of video on one product, a generation on another, a weighted unit that varies by model on a third. Nothing published makes two allowances commensurable, so the register quotes each in the vendor's own terms and does not convert.
That is the same discipline applied to prices quoted on different billing bases. Converting would produce numbers no vendor publishes, in cells that are supposed to hold what a vendor published.
Nothing on this page is a vendor statement; the values it helps read are on the support table, with the page and the date each one was read from. See also the paid tier column, reading a plan table. Nearby terms: output cap, recorded field, evidence class.