Google Docs Adds Integrated Translation
Google is making the most of its translation technology by introducing it to more and more of its products. The latest to take advantage of it is Google Docs. Users can now translate documents from inside the editor, choosing from 53 languages, without copying text into a separate window.
The convenience is the whole story. Other than saving a few clicks, the feature does not add anything to the quality of the translations above the standard google translate output. It is the same engine, wrapped in a menu item.
Along with the new feature, Google is introducing another small change that some are really going to appreciate: the option to use standard quotes rather than the smart quotes Docs applies by default. For anyone who needs straight quotes in their documents, particularly for publishing and for code, it is a genuinely useful addition.
What the button actually does
Select Tools, then Translate document, then a target language, and Docs produces a new file containing a machine-translated copy. The original stays untouched. Formatting mostly survives, though tables and text boxes come through unevenly, and anything in an image is ignored entirely because the engine only sees text.
That last point trips people up more than anything else. A document full of screenshots with embedded labels will come back looking translated while half the words on the page are still in the source language.
Why the quality does not change
Behind the menu sits the same public Google Translate service that anyone can use for free. It runs on neural machine translation, which since the mid-2010s has produced far more fluent output than the phrase-based systems it replaced. Fluent is not the same as accurate, and the gap between the two is exactly where the trouble starts.
Neural systems are trained to produce text that reads like the target language. When they lack information, they do not stop and flag the problem. They guess, and the guess reads perfectly. A mistranslated dosage, a reversed liability clause or an inverted negation arrives in a confident sentence with correct grammar, which makes errors far harder to catch than the mangled output of older tools.
Where it works and where it does not
For understanding, the feature is excellent. A supplier sends a Portuguese quotation, you translate it in place, you get the gist in three seconds. For internal notes, meeting minutes and any document whose only job is to be understood once and thrown away, machine translation is now good enough that arguing about it is a waste of time.
For publishing, it is not. Contracts, medical instructions, safety documentation, marketing copy and anything carrying legal weight need a human in the loop. The industry has a name for that loop: post editing, where a qualified translator takes the machine output and fixes what the engine got wrong. Done properly, it is faster than translating from scratch. Done badly, it is slower, because the editor spends the time hunting for errors that read as if they belong.
Professional workflows already handle this at a different level of control. Translators run engines inside their own tools, with translation memories and approved glossaries steering the output, an approach explained in this guide to machine translation in CAT tools. That setup keeps company terminology consistent across thousands of files, which a general-purpose engine cannot do because it has never seen the company's glossary.
What the 53 languages hide
The language count is a marketing number. Engine quality varies enormously by pair, and the variation tracks the amount of training data available. Spanish, French and German into English are excellent, because the internet is full of parallel text in those combinations. Finnish, Hungarian and most African languages are noticeably weaker, because the parallel data simply does not exist in the same volume.
Language distance matters too. English into Dutch is an easy hop. English into Japanese requires the engine to rebuild word order, drop pronouns that Japanese leaves implicit and choose a politeness level that the English original never specified. The engine picks one, silently, and a reader in Tokyo may find the result oddly brusque or oddly formal with no way to tell why.
None of this appears in the dropdown. Every language in the menu looks equally supported, and a user with no knowledge of the target language has no way to judge which output to trust.
The confidentiality question
The other issue is one that most people clicking Translate document never think about. The text leaves the document and goes to a translation service. For a restaurant menu, nobody cares. For an unsigned acquisition agreement, a patent draft or a patient record, the compliance team may care a great deal, and legal departments in regulated sectors have written policies specifically to stop staff from pasting confidential text into public engines.
Enterprise contracts and self-hosted engines exist precisely to solve this. They cost money, which is why the free button in the sidebar keeps winning.
The smart quotes footnote
The quote change deserves more credit than it will get. Docs replaces straight quotes with curly ones automatically, which is right for prose and wrong for anything that will be parsed by a machine. Paste a curly apostrophe into a code snippet, a CSV file or a command line and it breaks. Being able to switch the behaviour off removes a small, permanent annoyance for technical writers, and small permanent annoyances are what people actually complain about.
Taken together, the two changes tell you what Google thinks Docs is for. It is a place where documents get read, shared and understood quickly, in whatever language the reader happens to have. It is not a place where finished translations get produced, and the 53 languages in the menu do not change that. Machines have taken over comprehension. Publication is still human translation, and the people arguing about it on r/translator every week are arguing about the same line.