> For the complete documentation index, see [llms.txt](https://support.checksub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.checksub.com/help/faq/how-credits-work.md).

# How credits work

### You use credits in proportion to your use of the platform.

#### SUBTITLES

The credits deducted correspond to the length of the video multiplied by the number of languages produced.

For example, if you generate the English subtitles of an English video with a duration of 1 minute, it will require 1 min of credits.

If you generate the subtitles in English, French and Spanish for the same video you will need 3 minutes of credits \[1min \* 3 languages]

Credit usage is rounded to the second loan.

#### AI-DUBBING

If you generate an automatic dubbing, you will need 3 minutes of credits per minute for each language. The number of credits used for voice cloning and library voice is the same.

#### LIP-SYNC

If you generate a lip sync the number of credits will vary regarding the model you're using. You will get the information when you create the lip sync in the application.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.checksub.com/help/faq/how-credits-work.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.