Ship your game in every language. Without the tofu boxes.

One bad language can now sink your whole rating.

In August 2025 Steam made per-language review scores the default, and called out "translation issues" and "cultural references" by name. Your localization quality is now a public, per-region number that players see before they buy. You cannot hide a broken language behind a good one anymore.

Here is the kind of thing we find on a real game screen.

Take one character card and look closely. The same screen can hide three very different classes of bug at once: technical, contextual and cosmetic. None of them shows up in a string table. All of them show up to a player.

sample game screen · under test

// illustrative · sample game card · not a client build

«Come closer, <$user_name$!»

Technical

The text cannot even render

The font is missing the glyphs, the encoding is wrong, or raw code leaks into the string. The player sees boxes and tags instead of words.

tofu □□□ unsupported chars leaked tag <b> code fragment in text

Contextual

It renders, but it is wrong here

Grammar that breaks on gender, a line that does not fit the scene, or flat machine-flavored phrasing. Correct in a cell, wrong on the screen.

leaked placeholder "Come closer, {user_name}!" wrong gender agreement off-tone / MT-flavored line

Cosmetic

It fits the data, not the box

The translation is fine, the layout is not. Text outgrows its button, gets cut off, overlaps a neighbor or shrinks to a cryptic abbreviation.

overflow "Einstellun..." cut-off text unclear abbreviation overlapping labels

No procurement. No telephone game. Just send the build.

You already know how to ship a beta. We plug into the channel you already use, our native testers play it, and you get bugs back the way your devs like them: in your tracker, with screenshots and repro steps.

The bugs that are invisible in a spreadsheet and obvious on screen.

A translation can be perfect in the string table and broken in the game. These only show up when someone actually plays the localized build, in the target language, on a real device.

What lands in your tracker.

Every finding arrives as a card your devs can act on, not a verdict they cannot. A screenshot, the exact location, repro steps, a severity tag and a proposed fix. Never "the German is bad". On the Lead tier you also get an MQM-style quality score, so quality is a number you can defend.

Some bugs are not typos. They are bans.

1-hour minimum, buy only what you need  ·  rare/scarce natives (Nordic, Japanese) +$10/hr  ·  AAA or NDA-heavy scope? let's scope it

We don't proofread strings. We play your game.

A string checker reads your text out of context. A player meets it in a box, at a moment, on a screen. Only one of them finds the bug your actual players would.

120+ languages. The hard scripts included.

CJK line-breaking, RTL shaping, Cyrillic and diacritics: the scripts that break naive code are exactly the ones we test hardest, with native speakers who actually game in that language.