Simple credit pricing for large file translation

Credits are the single currency for everything you translate, whatever the format. One credit equals one translated word in Standard quality mode. Your balance is checked when you approve a translation and the exact cost is reserved then, so a job can never start without the credits to finish it. You are charged only for words that are actually translated: if a cell is already in the target language, or you exclude a column, those words cost nothing. A failed translation returns its full reservation.

Because not every file deserves the same care. Standard is the default and uses a stronger model, one credit per word. Lite uses about one credit for every three words, so the same balance translates roughly three times more. Lite is for volume where a good result beats a perfect one: a large catalog, internal content, a first pass you will review anyway. Standard is for anything a customer reads. You pick the mode on each translation, so the two can live side by side in the same workspace, and Lite is available on every paid plan.

It depends where they came from. Credits bought in a pack last 12 months from the purchase. Subscription credits are granted fresh every month, and up to 50% of what you did not spend rolls over into the following month, so one quiet month does not cost you the whole allowance. Anything above that 50% is lost at renewal. The 10,000 credits on the Free plan are a one-time welcome grant rather than a monthly allowance, so they are not refilled.

Because the two match different rhythms. Credit packs suit occasional work: buy once, no commitment, spend the credits over the next 12 months. A subscription suits regular volume and costs less per word, on top of unlocking Lite mode, larger glossaries and credit rollover.

No. All twelve supported formats draw from the same credit balance, from a CSV catalog to an Android string resource. Structure, keys, tags and placeholders are read for context and are never counted as translated words.

A glossary is your own list of terms and their approved translations, per language pair. Brand names, product names and technical jargon then come back the same way in every file, instead of being translated a little differently each run. It is applied automatically to every translation in the workspace, so you write a term once rather than repeating it in each job. Plans differ in how many glossaries you can keep and how many terms each one holds.

Custom instructions are a short note you write for one translation, in plain language, telling the model how to handle your content. They cover the things a glossary cannot: leave the URLs inside the text untranslated, keep placeholders such as {count} exactly as written, address the reader informally, keep this product name in English. Anything visible inside a single string is fair game. It is per translation rather than a workspace setting, so a marketing file and a technical export can be handled differently without changing anything permanently. Available on every paid plan.

Two different things, and only one of them expires. Your translation log is kept for as long as your workspace exists, on every plan including Free: what you translated, when, into which languages and how many credits it cost. What your plan sets is how long the files stay downloadable, 7 days on Free, 30 on Starter and 90 on Pro, counted from when a translation finishes. That covers both the file you uploaded and the translated result. Once the window closes the download needs a higher plan for a while, and after that the file is deleted for good. So download or store the result if you need to keep it, and the record of the work stays either way.