How to translate a webpage: The complete guide (2026)

You're looking at a page in the wrong language. Or maybe you're a developer trying to figure out what your users experience before you ship proper translations. Either way, here's everything you need.

This guide covers two perspectives:

• Users: how to translate any webpage you're reading right now, using your browser or free tools
• Developers: how to make your own website or app properly multilingual (hint: browser auto-translate is not the answer)

For users: How to translate a webpage

Browser translation has gotten remarkably good. In most cases you won't need anything else.

Google Chrome

Chrome uses Google Translate and handles this automatically. When you open a page in a language different from your browser's default, a Translate button appears in the address bar. Click it, confirm the target language, and the page reloads in your language.

The translation result looks good; the text is readable and makes sense. However, the translation may not be perfect, especially for pages with a lot of text or complex content.

Note:

• You can change Chrome's translation language preferences under Settings → Languages.
• Right-click anywhere on the page and select Translate to [Language] to translate the page to your main language.
• Highlight a specific text on the page and select "Translate Selection" to translate the selected text.

Safari (Mac and iOS)

When Safari detects a foreign-language page, a Translate button (looks like an aA icon) appears in the address bar. Click it and choose Translate to [Language] from the dropdown.

The translation isn't perfect, and it may be difficult to read when the page contains a lot of text, but it can help you understand the content of the page better.

Learn more about Safari translation options and settings.

Note:

• On iPhone or iPad: tap the aA icon in the address bar, then Translate Website. If the option is greyed out, the language isn't supported yet, Safari currently supports around 30 languages.
• You can change the languages used for translation in Safari in Language & Region preferences.
• To translate a specific text selection in Safari, highlight the text, right-click (or long-press on iOS), and choose Translate.

Firefox

Firefox ships with its own on-device translation engine, so it doesn't send your content to a cloud service, which is useful if you're translating anything sensitive.

Click the translation icon in the address bar when it appears, or go to Tools → Translate Page. Choose the source and target language and hit Translate. Firefox supports around 20 languages at the moment.

Note:

• You can change the languages and translation preferences in Firefox settings.
• To translate a specific text on the page, you can select the text and right-click to translate it using the "Translate Selection" option.
• Some languages may not be supported yet by the Firefox translation service.
• Firefox translation feature won't translate non-text elements such as images, videos, or interactive elements

Full Firefox translation guide →

Microsoft Edge

Microsoft Edge uses Microsoft Translator to provide a translation of a webpage into the user's preferred language. When Edge detects that a webpage is in a different language from your preferred language, it will display the Translate option in the address bar to translate the page into your preferred language.

To translate a webpage in Microsoft Edge, click on the Translate button in the address bar and select the target language from the list of available languages. Hit Translate to view the translated page.

Notes:

• You can change the languages used for translation in Edge settings.
• To translate a specific text on the page, you can select the text and right-click to translate it using the browser's built-in translation feature.

Tools and extensions

Browser translation is fast and free, but it has real limits: it doesn't know the context of your product, it can't handle all scripts well, and it sometimes produces fluent-sounding text that's subtly wrong. A few alternatives:

Google Translate (web): Go to translate.google.com, switch to the Websites tab, paste a URL, and choose your languages. Useful when your browser extension isn't working or you want to translate a specific URL without loading it yourself.

DeepL: Better quality for European languages than Google Translate in many cases. The browser extension for Chrome (available also for Firefox and Edge) lets you translate any page or selected text. Full-page translation requires a DeepL Pro account; text selection is free.

Other extensions worth knowing:

• Mate Translate: supports 100+ languages, translates on hover
• ImTranslator: Chrome and Firefox, includes text-to-speech
• TWP - Translate Web Pages: open source, Firefox-first

Manual translation tools (for a word or phrase, not a full page):

• DeepL Translator: best quality for European languages
• Linguee: shows real translation examples in context
• WordReference: excellent for grammar questions alongside translation
• Reverso: good for idiomatic expressions and conjugations
• Bab.la: includes slang and regional variations

On mobile

All the major browsers have translation built in on mobile now.

Chrome on Android/iOS: When you open a foreign-language page, a translation bar appears at the bottom. Tap it to translate. If it doesn't appear, tap the three-dot menu and choose Translate.

Safari on iPhone/iPad: Tap the aA icon in the address bar → Translate Website.

Firefox on Android: Tap the translation icon in the address bar when it appears, or use the menu → Translate page. (iOS support is more limited.)

If you regularly translate text from images (menus, signs, printed documents) Google Translate's camera feature (iOS, Android) is genuinely impressive and does this in real time.

For developers: Why your users shouldn't rely on browser translation

If your product serves users in multiple languages, browser translation is not a solution, it's a patch. Here's why it matters and what to do instead.

What browser translation gets wrong

Browser translation works on the rendered text of a page. It doesn't know whether "Home" is a navigation button or a real estate listing. It doesn't know your brand voice, your technical terminology, or the 12-character limit on your mobile UI label. It translates everything, including things you never intended users to read in another language (button aria-labels, error codes, internal strings).

Worse: it can make a professionally designed product look sloppy. Awkward phrasing, missed context, inconsistent terminology: users notice, and it affects trust.

The right approach: internationalization + proper localization

The foundation of a multilingual web app is internationalization (i18n): restructuring your code so that every user-facing string is stored in a translation file rather than hardcoded in your components.

A simple example. Instead of this:

Save changes

You write:

{t("settings.save_changes")}

And your translation files carry the actual content:

// en.json
{ "settings": { "save_changes": "Save changes" } }

// de.json
{ "settings": { "save_changes": "Änderungen speichern" } }

// ja.json
{ "settings": { "save_changes": "変更を保存" } }

At runtime, the i18n library loads the file that matches the user's locale. Add a language, add a file. The component code never changes.

This separation is what makes multilingual software maintainable. Without it, every translation becomes a find-and-replace exercise across your entire codebase.

What comes after i18n

Once your code is internationalized, you need:

• A translation management system (TMS) to organize your translation files, collaborate with translators, run auto-translations, and keep everything in sync with your releases
• Locale detection: URL-based (/de/pricing), cookie-based, or Accept-Language header, each with different trade-offs for SEO and caching
• Locale-aware formatting for dates, numbers, and currencies (never hardcode MM/DD/YYYY or $)
• A language selector so users can override whatever locale you detected

For the full technical picture, architecture patterns, RTL support, CI/CD integration, pluralization rules, and more, see our complete technical guide to i18n and software localization.

If you're at the strategy stage, which markets to prioritize, how to measure ROI, when to start, the localization strategy guide for SaaS teams is the right starting point.

Quick reference: Translation tools by use case

Conclusion

Browser translation is a useful tool for quick access to content in an unfamiliar language, but it shouldn't be the default experience for your users. If you care about delivering a polished, trustworthy product to a global audience, invest in proper internationalization and localization. Your users will thank you for it.