Credits measure generation—not team contribution
The previous version of this article confused production credits with employee credit or project-management allocation. In afterSora, credits are a usage balance for video, image and optional generation operations. Buy them once, then spend them according to the model and settings selected in the dashboard.
Start with the live charge table
MiniMax H3 is charged at 1 credit per generated second at its standard setting and 2 credits per generated second at 2K. Always check the live pricing page because models, availability and promotions can change after an article is published.
- Sora 2 at 720p: 1 credit per generated second.
- Sora 2 Pro at 720p: 2 credits per generated second.
- Sora 2 Pro at 1024p: 4 credits per generated second.
- afterSora Imagine standard: 1 credit per image.
- afterSora Imagine at 2K Precision: 2 credits per image.
- GPT Image 2: 0.2 credits at Low, 1 at Medium and 2 at High per image.
Use a simple production formula
For video, begin with duration multiplied by the selected model's credits per second. Multiply that result by the number of variations. Then add a separate allowance for prompt tests, revisions and optional optimisation. For images, multiply the per-image charge by the number of outputs and planned edit passes.
- Base generation budget = duration × model rate × variations.
- Revision allowance = base budget × expected revision rounds.
- Exploration allowance = a small fixed pool for prompt and reference tests.
- Total planned credits = base + revisions + exploration + optional tools.
Example: a short social campaign
Suppose a team needs three approved eight-second Sora 2 clips. One first-pass variation for each clip costs 24 credits in total. If the team budgets one additional full variation per clip, the generation allowance becomes 48 credits. Add a small test pool rather than assuming every first prompt will be usable.
If the same plan uses Sora 2 Pro at 720p, the video portion doubles. At 1024p it quadruples relative to Sora 2 at 720p. This is why resolution should be chosen from the actual delivery requirement, not selected automatically.
Account for variations and optional tools
- Each variation is another generation, not a free preview.
- Advanced prompt optimisation has its own displayed charge.
- Storyboard generation uses the same one-credit Optimize pass shown in the composer.
- Character creation can carry a separate setup charge.
- Editing operations may create new provider jobs and therefore consume credits.
Failed generations should not consume the budget
afterSora reserves credits when a job begins. The failure path returns the reserved credits when the generation does not deliver. Check the credit history after a provider failure before retrying repeatedly; a missing refund is an account issue to report, not a cost to silently absorb.
Treat promotions separately
Do not build a recurring production budget around a temporary multiplier or bonus balance. Record unrestricted credits separately from model-limited bonus credits, and confirm the eligible models before scheduling work. Use standard pricing for the core plan; treat promotional credits as additional runway.
A useful team planning sheet
- Deliverable and owner.
- Model, duration, resolution and aspect ratio.
- First-pass variations.
- Expected revision rounds.
- Optional optimisation or character setup.
- Planned credits, actual credits and refunded credits.
- Approved output link and final delivery status.
