AI video credits explained: estimate output before you buy

Start with the credit formula

The simplest usage model charges a fixed number of credits for each rendered second. In that case, the base formula is credits per second multiplied by video duration multiplied by the number of versions. If a 15-second video costs 30 credits per second, one render costs 450 credits. Four language or presenter versions would cost 1,800 credits before retries.

Other tools charge per finished video, per minute, per generation step or by feature. Voice cloning, higher resolution, translation, face changes and priority rendering may use separate balances. Read the current usage table and do not assume the word unlimited applies to rendering just because deployment or downloads are unlimited.

Translate credits into usable projects

A credit balance becomes meaningful only after it is divided by a realistic project size. Write down the normal clip duration, how many audience or language versions you need and how often a script changes after review. Include internal approvals and client revisions if the work is commercial.

For a first estimate, calculate a clean-render maximum and a buffered maximum. The clean number assumes every render is usable. The buffered number reserves part of the balance for mistakes, quality checks and revisions. A 25% to 40% planning buffer is more realistic for a new workflow than spending the entire balance on the first schedule.

CastAI credit example checked July 13, 2026

The current CastAI producer FAQ stated that 720p transformations consume 30 credits per second. The same offer listed 1,800 credits for Core and 3,000 for Full. On that arithmetic, a 15-second transformation uses 450 credits and a 30-second transformation uses 900 credits.

If no other charges apply, 1,800 credits cover four 15-second first-pass renders or two 30-second first-pass renders. A 3,000-credit balance covers six 15-second renders with 300 credits left, or three 30-second renders with 300 left. These are planning calculations, not a promise of finished output, because retries and feature choices can change real usage.

• 15 seconds x 30 credits = 450 credits per transformation.
• 30 seconds x 30 credits = 900 credits per transformation.
• Core: 1,800 credits before revisions or other usage.
• Full: 3,000 credits shared with the selected workflow.

Account for website presenter videos separately

The CastAI FAQ also described website videos as consuming 300 credits each. Full includes the website deployment layer, so a buyer planning both transformations and website presenters should allocate the same balance across both jobs. Ten website videos would consume 3,000 credits if that were the only usage.

A mixed example is more practical: four 15-second transformations consume 1,800 credits, while four website videos consume another 1,200. That uses a 3,000-credit Full balance with no revision buffer. The exact product rules can change, so confirm the live usage table before relying on this allocation.

Revisions are part of the cost

AI rendering does not eliminate production review. Lip synchronization, pronunciation, pacing, framing, captions and brand details can require another pass. If a client approves the script only after seeing the video, the first render may become a draft rather than the final asset.

Reduce waste by approving the script, names, numbers and call to action before rendering. Test the shortest practical sample when the platform allows it. Keep a small checklist for source-video quality, voice selection, output ratio and destination page so the same mistake is not repeated across every version.

Compare one-time pricing with refill economics

A one-time software price and a finite starting balance are different things. The account may remain accessible while additional production requires credit refills or an upgrade. Ask how credits are replenished, whether they expire, whether unused credits roll over and whether higher resolution changes consumption.

Estimate the cost of the next 10, 50 or 100 usable videos rather than comparing only the front-end payment. A subscription with predictable monthly output may be cheaper for steady production, while a one-time plan may suit occasional short projects. The right comparison depends on volume and revision rate.

Match the plan to the workflow

Choose the lower plan only when its features and balance cover a complete test. Buying a transformation-only plan and later discovering that website deployment is required creates another decision and possibly another checkout step. Conversely, paying for deployment features is unnecessary if the real need is only to transform and download short videos.

The current CastAI comparison separates Core transformation features from the Full website presenter workflow. Review the plan details, bundle and current checkout before using the credit calculations above.

Compare CastAI Core, Full, credits and limits

Credit planning checklist

Before paying, record the included balance, consumption unit, maximum duration, resolution, language or voice surcharges, cost per website video, refill price, expiry rules and refund treatment for consumed credits. Then build a small production forecast with a revision buffer.

Repeat the calculation whenever the seller changes the offer or your workflow expands. A credit table checked during a launch is a snapshot, not a permanent operating guarantee.

Frequently asked questions

Related AI buyer guides

CastAI Core vs Full, credits and limits

AI Website Spokesperson Guide: What to Check Before Choosing a Tool