Credit balance
Your available credits appear in Member and on relevant submit pages after login. If a team buys more credits, refresh the page after payment confirmation so the newest balance can be loaded.
Use Member billing for credit balance and payment records. Use Member usage for consumption records.
Estimate before you submit
Submit pages show an estimated credit cost before task creation. Review it before confirming the task, especially for long video files or workflows with several output options.
- Video workflows are usually affected by duration.
- Image workflows are usually affected by image count and selected mode.
- Dubbing, translation, subtitle rendering, text removal, and reprocessing can change the estimate.
- Draft edits can use more credits when you enable processing that was not part of the first submission.
What changes credit use
Longer videos and larger image sets usually need more processing time and credits.
Translation, dubbing, removal, extraction, and subtitle rendering each add work to the task.
Multiple target languages or repeated exports may increase total credit usage.
Some retries are free when the original task failed; optional reprocessing can require credits.
API usage
API tasks follow the same product credit rules as the web app. API key management is handled from Member, while implementation details live in the API docs.