Ask an AI about this
Translation teams keep improving their work after you install it. Tranzio spots new versions for you; updating is one click, and always your choice.
Keeping translations up to date
Translation teams keep improving their work after you install it. Tranzio spots new versions for you; updating is one click, and always your choice.
A translation isn't a finished product the day you install it. Teams keep polishing: fixing typos players report, translating the side quests they hadn't reached, recording more voice lines. Each time they build and publish again, a new version exists, and Tranzio quietly compares it against what you have. When yours is older, you'll know. Nothing updates behind your back; you always pull the trigger yourself.
How you find out
| Where | What you'll see |
|---|---|
| Home | Cards in your installed row get an amber update tag, and the stat strip counts how many updates are waiting. |
| The game page | The install button becomes an update button, and the Versions section shows what changed since your version. |
| Notifications | The bell gets an alert the moment a team publishes a new version of something you installed. |
You have v2.4.0, the team published v2.5.0 yesterday
Updating
Open the game (or click the notification)
Any of the paths above lands you on the game page, where the button now reads Update instead of Install.
Skim the changelog
The Versions section lists what the team changed: new coverage, fixes, new audio. Ten seconds of reading tells you whether it's worth updating mid-playthrough.
Press Update
Updates run through the same installer as the original install, restore point included, and are usually much smaller because only changed files download. Your saves are untouched, as always.
When the game itself updates (a Steam patch, for example), parts of a translation can be overwritten by the game's new files. If a game suddenly shows some original-language text after one of its own updates, just reinstall the translation from its game page. The team may also publish a compatibility update shortly after; that's exactly what the notification is for.
Not sure an update is safe mid-story? Updates never touch saves, and you can always revert to original and reinstall any version later. There's no state you can get stuck in. See Installing a translation.
Reading the changelog
The Versions section on a game page is a running history of the translation, newest first, with your installed build marked. It's the fastest way to answer the only question that matters mid-playthrough: does this update fix something I'm actually hitting?
- v2.5.0yesterdayNewest
- Side quests in the Citadel translated, 4,120 new strings
- Voice lines for Act 3 dubbed
- Fixed the item names that stayed in English after the 1.0.7 game patch
- v2.4.03 weeks agoYou have this
- Main story complete
- Menu font replaced so accented letters render
- v2.3.12 months ago
- Typo pass on chapter 2 reported by players
Teams write these themselves, so the detail varies. A good changelog names the chapters or systems it touched; a thin one at least tells you the release exists. Either way, an entry mentioning the game's own version number ("fixed after the 1.0.7 patch") is the one you want to take straight away.
Why updates are small
A translation isn't one giant file, it's hundreds of small ones. An update ships only the files that actually changed, so a typo pass costs you a few megabytes even though the original install was several gigabytes. That's why updating mid-evening is a coffee break rather than a plan.
The one exception is a rebuilt pack, where a team changes something structural and every file is replaced. Those look like a fresh install in the Downloads page, and the changelog usually says so.