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

WhereWhat you'll see
HomeCards in your installed row get an amber update tag, and the stat strip counts how many updates are waiting.
The game pageThe install button becomes an update button, and the Releases tab shows what changed since your version.
NotificationsThe bell gets an alert the moment a team publishes a new version of something you installed.
HK
Hollow Knight: SilksongUpdate available

You have v2.4.0, the team published v2.5.0 yesterday

An installed card noticing a newer build, updating, and settling on it. The amber tag is the only thing that changes without you asking; the update itself waits for the button.

· Community

· Translation support

  • Sam replied to TZ-1053Fixed in the next build, can you check on 1.4.2?Aug 10
  • Emily replied to TZ-1053The greeting still says goodbye on my copy.Aug 10
  • Sam replied to TZ-1053Attached a screenshot of the shop.Aug 10

· Builds

Update alerts arrive with your other notifications. Clicking one takes you straight to the game so you can update from there.

Updating

  1. 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.

  2. Skim the changelog

    The Releases tab lists what the team changed: new coverage, fixes, new audio. Ten seconds of reading tells you whether it's worth updating mid-playthrough.

  3. 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 Releases tab on a game page answers the only question that matters mid-playthrough: is there something newer than mine, and does it fix what I'm hitting? The line at the top says where your install stands, amber with Update when you are behind. Under it the newest release is shown in full, and everything before it sits on a timeline with yours flagged You are here. Betas step off the line in amber, since they are there to try rather than something you are missing.

You have v2.4.0, one release behind.
v2.5.0Latestyesterday · 1,040 downloads
  • 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
  1. v2.5.1Beta2 days ago · 154

    Act 4 dub, test build.

  2. You are here
    v2.4.03 weeks ago · 640

    Main story complete. Menu font replaced so accented letters render.

  3. v2.3.12 months ago · 301

    Typo pass on chapter 2 reported by players.

A translation's Releases tab. Your build is flagged on the timeline, so everything above it is exactly what you'd gain by pressing Update. Any older release can be rolled back to from its own card.

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.

First install, everything the pack ships4.8 GB
Update to v2.5.0, changed files only340 MB
New side quests and Act 3 dubbing1,120 files rewritten, about 30s on a normal connection
Three real kinds of release measured against the first install. Even a release with new chapters and fresh dubbing is a fraction of the original download.

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.