Documentation
Limits
String counts, request sizes, and per-file caps.
Monthly strings
| Plan | Strings per month | Overage |
|---|---|---|
| Free | 50 | Hard limit — translation stops |
| Starter | 15,000 | $0.002 per extra string |
| Pro | 75,000 | $0.002 per extra string |
| Business | 200,000 | $0.002 per extra string |
| Enterprise | Custom | By agreement |
You are billed only for strings the provider actually returns. Skipped and preserved strings are never sent and never counted. A string the provider fails to return after a retry is left untranslated and not charged.
Characters per request
Each translate request has a total character ceiling. Exceeding it returns an error asking you to split the request.
| Plan | Characters per request |
|---|---|
| Free | 5,000 |
| Starter | 50,000 |
| Pro | 200,000 |
| Business | 500,000 |
| Enterprise | Unlimited |
Per-file and per-string caps
- A single file may contain at most 1,000 translatable keys. Split larger catalogs.
- A single string may be at most 10,000 characters. Longer strings are skipped and reported in the response rather than sent to the model.
Feature availability
| Feature | Requires |
|---|---|
| Tone and formality control | Starter |
| Provider choice | Starter |
| Glossary, skip and preserve patterns | Starter |
| Context | Starter |
| CLI and CI/CD access | Starter |
| GitHub sync | Starter |
| Saved configurations | Starter |
| Character limits | Pro |
| Per-key overrides | Pro |
Purchasing credits unlocks Starter-level features on a Free account, without a subscription.