What Is In-Page Translation? How Reading a Page in Another Language Actually Works

Reading something in a language you don’t speak fluently usually means one of two things: translating the whole page and reading a machine-translated version start to finish, or copying a single confusing sentence into a separate translator and pasting it back mentally into the article. Neither is quite right for every situation. Sometimes you want the whole page translated because you don’t read the source language at all; other times you’re mostly fine and just hit one paragraph that lost you. In-page translation, done well, should support both without forcing you to pick one approach for every page you visit.

What browsers already do, and where it stops

Most Chromium-based browsers, including Chrome itself, already ship with a translate prompt: land on a page written in a language different from your browser’s default, and a small bar or icon offers to translate it. Click it, and the whole page is replaced with a translated version.

That built-in feature covers the most common case reasonably well, but it has a narrow shape:

• It’s whole-page or nothing. There’s no quick way to translate just one paragraph or a highlighted sentence without triggering a full-page translation.
• It’s cloud-based by default. The page text is sent to a translation service to be processed, which is a reasonable trade-off for most public web pages but not always what you want for something you’d rather keep off a third-party server.
• It only prompts when the browser detects a mismatched language. If you’re reading in a language your browser doesn’t flag as “different,” or you’ve dismissed the prompt already, there’s no obvious way to bring it back for just the part you’re stuck on.

None of that makes it a bad tool — it solves the “I don’t read this language at all” case well. It’s the narrower, more common case — “I read this fine, except this one sentence” — that a whole-page-only tool doesn’t really address.

Whole page vs. just a selection

The distinction that matters most in practice is between translating everything and translating only what you’ve selected:

• Whole page makes sense when the source language is genuinely unfamiliar to you and you need the full article to make sense of it, not just one part.
• Selection only makes sense far more often than it gets used for: a news site that quotes a source in another language, a product page with one untranslated review, a forum thread where most replies are in your language except one. Translating the entire page in these cases is more work than the situation calls for, and it throws away the original wording for text you didn’t actually need translated.

Keeping both available, and switching between them per page rather than being locked into whichever one the browser happened to prompt for, matches how translation needs actually show up while reading.

Why running it on-device matters

Some newer browsers can translate certain language pairs entirely on the device, without sending the page text to a server at all, once the relevant language model has been downloaded locally. When that’s available, it’s generally the better default: it’s private, it doesn’t depend on network conditions, and it doesn’t cost anything per request.

It isn’t always available, though — it depends on the browser, the specific language pair, and whether the on-device model has already been downloaded. A translation tool that only works when the on-device path is available ends up unreliable in practice, so falling back to a cloud-based option when the on-device path can’t handle a given language pair is what keeps translation working consistently rather than only working sometimes.

Reversibility matters more than it sounds

Translating a whole page is easy to do and easy to regret slightly — you translate the page, read it, and then want to check the original wording of one sentence, or copy a quote in the source language. If translating the page overwrites the original with no way back short of reloading, that small follow-up need means losing your scroll position and starting over. A one-click “revert to original” that restores the page exactly as it was, without a full reload, avoids that trade-off entirely.

How ReadEase’s Translate feature works

ReadEase’s Translate panel adds both modes directly to any page:

• Pick a target language from a curated list of common languages; the choice is remembered for next time.
• Whole page replaces the page’s text in place with a translated version, with a Revert to Original button that restores the original wording without reloading the page.
• Selection only translates just the text you’ve highlighted and shows the result in a small popover next to it, leaving the rest of the page untouched.
• Translation prefers running on-device when your browser supports it for the language pair involved — private, and it doesn’t require a network request at all. When the on-device path isn’t available, it can optionally fall back to your own AI API key, so translation still works rather than simply failing.
• If neither path is available — no on-device support for that language pair, and no fallback key set — Translate says so clearly instead of spinning indefinitely or failing silently.

Who this helps most

• Language learners reading native-language material that’s mostly within reach, who want to check the occasional unfamiliar sentence without derailing into a fully translated page. This pairs naturally with Define on Select for single unfamiliar words — translation for a sentence you’re lost on, dictionary lookup for one word you just don’t know yet.
• Anyone reading a page that’s mostly in their language except one section — a quoted source, a pasted excerpt, a comment thread with a few replies in another language.
• Anyone who wants to read foreign-language material without sending it to a cloud service, whenever the on-device path covers the language pair they need.
• Readers combining translation with listening — pairing a translated page with Read Aloud lets you hear the translated text while you follow along, which is useful for judging whether a translation reads naturally out loud, not just on the page.

Setting it up

1. Install ReadEase, a free Chrome extension.
2. Open the popup and make sure ReadEase is turned on for the page you’re reading.
3. Open the Translate panel and pick a target language.
4. Choose Whole page to translate everything, or Selection only to translate just the text you highlight.
5. For whole-page mode, click Translate Page — then Revert to Original whenever you want the page back exactly as it was.
6. For selection mode, highlight text on the page and click Translate Selection to see the result in a popover next to it.

Frequently asked questions

Does this replace my browser’s built-in translate prompt?

It doesn’t disable it, but it covers what the built-in prompt doesn’t: a selection-only mode for translating just part of a page, a remembered target language instead of relying on auto-detection, and a clear revert option for whole-page translations. You can use either, depending on what a given page needs.

Does translation work without an internet connection?

Only if the on-device path is available for that specific language pair on your browser and the language model has already been downloaded — otherwise translation needs a network connection, either for the on-device model’s initial setup or for the fallback path.

Do I need to add an API key to use Translate?

No. The on-device path, when your browser and the language pair support it, works without any key at all. An API key is only needed as a fallback for language pairs the on-device path can’t handle.

Will translating a page change the original text permanently?

No. Whole-page translation replaces what’s displayed in your browser tab only; it doesn’t modify the page itself, and Revert to Original puts your own view back to the untranslated version at any time.