How to Tell if an AI Translation Is Correct?

Someone types a message to a landlord, hits translate, and the sentence comes back smooth, confident, natural. It sounds right, and that is exactly the problem: knowing how to tell if an AI translation is correct has never been harder, because sounding right is what translations do now, wrong ones included. The doubt lingers because the stakes do. A misplaced word can change a lease clause, a visa answer, a sentence in a paper about to be submitted. The machine does not hesitate, so its user must.

That hesitation is the new normal. The old tell was a broken phrase, a grammar crash, some obvious scar where the meaning bled out. Today the output reads like a human wrote it, which only means the human might have been wrong. Fluency is no longer evidence. The question is not whether it sounds native, but whether it says what was meant, in the tone intended, with the precision needed.

So the real work begins after the first draft. The translation looks finished, but the checking has just started. The answer to how to tell if an AI translation is correct is not a feeling; it is a procedure, a stack of tests each catching the errors the others miss.

What "correct" actually means #

A translation is correct when it preserves the meaning of the source, sounds natural in the target language, matches the intended register, and respects idiomatic usage.

The classic split in the evaluation literature is adequacy versus fluency: does it say the right thing, and does it say it the way a native speaker would. Those two are not enough. A text can be accurate and still feel stiff or overly formal for its context, or it can read beautifully while missing a crucial nuance because the idiom does not travel. Juliane House, in her book Translation Quality Assessment: Past and Present, frames correctness as tied to function: a translation that serves its purpose in the new language is correct for that purpose, even if it diverges from the original in tone or structure. That is why a single translation can be accurate but unnatural, natural but wrong-register, grammatical but idiomatic nonsense, and why asking "is it correct" without saying which axis is meant is a question with no answer.

The fluent lie #

The translations that worry people are exactly the ones that look fine. They arrive polished and confident, with none of the old scars of machine output, and that is the problem. Fluency is easy to produce now and impossible for the sender to audit unaided. Douglas Hofstadter demonstrated this in The Shallowness of Google Translate: a bilingual author feeding his own writing to the tool and watching it return passages that read smoothly while carrying almost none of what the original said. Fluent, confident, hollow.

The turning point was 2016, when Google announced its neural system in a post titled Found in translation. The accompanying GNMT paper reported that the new system reduced translation errors by an average of 60 percent compared with the phrase-based system it replaced, in a human side-by-side evaluation, and that in some cases human and machine translations were nearly indistinguishable on the simple isolated sentences sampled for the experiment. That was the moment fluency stopped being a quality signal, because the wrong translations started sounding right too. The technical reasons the output reads so well are covered in why LLMs are good at translation; the short version is that the models are trained toward plausible output, so their errors read as confident prose.

The failure mode is not hypothetical. A commenter on the Hacker News thread about Hofstadter's piece described a years-long benchmark of their own: "The word is 'χελιδόνι', meaning 'swallow' (the bird) in Greek. For as long as I've been trying this tiny little experiment, Google has been translating it to the French word 'avaler' - the verb 'to swallow'." Perfectly fluent French, wrong part of speech, wrong meaning, no visible seam. Multiply that by a sentence that cannot be checked, and the shape of the risk becomes clear (thread).

The people who build translation tools feel the same doubt. The author of Offline Translate wrote: "For a long time, I was concerned about using translation apps when writing emails to my doctor or public offices that included personal information." The author of Loqi, a local-first translation tool, echoed it: "Even with all the opt-out options and privacy policies, it never felt right especially for some work documents, personal writing, or anything sensitive." And the community advice is blunt, in the title of a much-shared r/languagelearning PSA: "Always double check the translation with another software and/or a teacher because DeepL will occasionally generate random translations that are completely unrelated to what you actually input." Can Google Translate, or DeepL, or any of them be trusted? For casual use, mostly yes, and their fluency is real. For anything with stakes, fluency is not evidence, and the only honest answer is to run checks that do not rely on how the text sounds.

Send it back the way it came #

Back translation is the oldest verification trick there is: the translation goes back into the original language, and what comes home is read. If the round trip returns the intended meaning, the translation probably preserved what mattered. If it comes back as something that was not meant, the problem is found before a reader finds it. The question it answers is the one people ask in every language-learning community, in threads like "How do I check if my translation is correct?" on r/Korean.

The check works because the two directions of a translation rarely fail in the same way. An error introduced on the way out usually does not survive the trip back intact; it surfaces as a mismatch that can be read in the original language, where nothing hides behind imperfect command of the target language. Running the return trip with a different tool than the outbound one avoids a shared blind spot repeating itself, and the result is read as a claim about meaning, not as prose to judge for style.

The limit is honest and worth knowing: a round trip can launder an error when both directions share the same wrong assumption, and the mistake sails home disguised as confirmation. An unchanged round trip is evidence, not proof, which is why it is one check in a stack rather than the whole answer. There is also a second, entirely different use of the same mechanic, as a study technique for learners; the study-method version of back translation covers that angle.

Read it like a native, aloud #

Knowledge of the source language is not required to catch many translation problems. That is the premise of a long-running discussion on r/books that asks "How do you judge the quality of a translation without being familiar with the original language a work is written in?", and the answer the community keeps arriving at is to judge the target text on its own terms. A target-language speaker reading a translation catches unnatural rhythm, wrong register, idioms no native would ever use, a tone that shifts from formal to casual mid-paragraph. None of that requires seeing the source.

What they structurally cannot catch is whether the meaning matches. A native reader of the target text is checking fluency, register, and idiom, the axes that live entirely in the target language; accuracy lives in the relationship between two texts, and someone who reads only one of them is blind to it by construction. This asymmetry is exactly why the monolingual check and the round trip belong in the same routine: each covers the other's blind side.

The division of labor can even be productive. A commenter on a Hacker News thread about human-corrected machine translation put it precisely: "I can't translate a word of Chinese, but I can usually do a good job of correcting a good machine translation" (thread). The machine handles the direction the sender cannot, the native speaker audits the result in the language they know cold. And the cheapest version of this check needs no second person at all: reading the translation aloud. The ear catches what the eye skips: a rhythm that is off, a sentence nobody would say, a word that is technically correct and never actually used.