Over 40% of the Web Is Not in English
The English-language internet is vast, but it is far from comprehensive. W3Techs data shows that English accounts for roughly 58% of all web content by volume, which means over 40% of the indexed web exists in other languages. That percentage shifts dramatically depending on the subject matter. Japanese automotive engineering forums, German industrial machinery specifications, Korean skincare research, Brazilian academic papers, Mandarin market analysis, and Arabic historical archives all represent deep reservoirs of knowledge that English-only readers miss entirely.
The professional implications are real. A 2023 McKinsey report on global information access found that companies with multilingual research capabilities identified market opportunities an average of six months earlier than monolingual competitors. For academic researchers, a study in Scientometrics showed that excluding non-English publications from literature reviews caused systematic gaps in 73% of examined meta-analyses across STEM fields.
Translation is not a niche concern. It is a core capability for anyone who takes information seriously.
Safari’s Built-In Translation: What It Does and Where It Falls Short
Apple introduced built-in translation to Safari in iOS 14 and macOS Big Sur. The feature, powered by Apple’s Neural Engine, supports approximately 18 languages and works directly from the address bar. When Safari detects a foreign-language page, a translate icon appears, and you can translate the entire page with one tap.
For casual use, this works reasonably well. The translations are decent for common language pairs (English to Spanish, French, German, Chinese, Japanese, and a few others), and the on-device processing means your content never leaves your device.
But the limitations become apparent quickly:
Limited language support. Safari’s built-in translator covers approximately 18 languages. That sounds like a lot until you need to read a page in Turkish, Vietnamese, Swahili, Thai, Hebrew, or any of the dozens of other languages it does not support. For a feature billed as “translate web pages,” the coverage is incomplete.
No selective translation. Safari’s built-in feature translates the entire page or nothing. If you are reading a bilingual document, a page with code snippets mixed into foreign-language explanations, or a forum thread where some posts are in your language and others are not, the all-or-nothing approach creates problems. Code gets mangled. Already-English text gets “translated” into awkward paraphrases. Proper nouns get erroneously translated.
No translation memory or glossary. Professional translators rely on translation memory (storing previously translated segments for consistency) and custom glossaries (ensuring that domain-specific terms are translated correctly). Safari’s built-in tool treats each page as an isolated translation task, which means the same technical term might be translated differently on different pages.
Inconsistent availability. The translate button does not always appear. Safari’s language detection algorithm sometimes misidentifies the page language, especially on pages with mixed-language content, short text, or heavy use of proper nouns. When detection fails, you cannot manually trigger translation.
Alternative Translation Methods
Before diving into the extension approach, it is worth understanding the full landscape of web translation options.
Copy-and-Paste to Translation Services
The most basic approach: select text, copy it, switch to Google Translate or DeepL in another tab, paste, read the translation, switch back. This works for short passages but is brutally inefficient for full pages. You lose context, formatting, and any embedded links or images. For a single word or sentence, it is fine. For sustained multilingual research, it is unsustainable.
Google Translate Chrome Extension
Google’s translate extension is one of the primary reasons people cite for using Chrome over Safari. It supports 133 languages, offers both full-page and selected-text translation, and integrates tightly with Google’s translation API. But it requires using Chrome, which means giving up Safari’s battery efficiency advantages (Safari typically delivers 2-3 more hours of battery life on MacBooks), its deeper Apple ecosystem integration, and its stronger privacy protections. The extension also sends all page content to Google’s servers for processing.
DeepL Browser Extension
DeepL offers higher-quality translations than Google Translate for its supported languages (approximately 30), particularly for European language pairs and nuanced text. However, DeepL’s Safari extension has historically lagged behind its Chrome and Firefox counterparts in features and update frequency. The quality gap between DeepL and other services is also narrowing as neural machine translation models converge in capability.
Dedicated Safari Translation Extension
A purpose-built Safari extension combines the convenience of in-browser translation with broad language support, selective translation capabilities, and Safari-native performance. This is the approach that balances coverage, quality, and workflow efficiency.
Using Translator Safari Extension
Translator Safari Extension integrates translation directly into Safari’s browsing experience. It supports dozens of languages with automatic source language detection, offers both full-page and selected-text translation modes, and preserves the original page layout during translation.
Installation
On Mac:
- Open Safari and go to Safari > Settings > Extensions.
- Click More Extensions to open the App Store.
- Search for “Translator Safari Extension” and install it.
- Return to the Extensions tab and enable the extension.
- Set website access to “All Websites” for automatic language detection on every page, or configure per-site access for more selective use.
On iPhone and iPad:
- Go to Settings > Apps > Safari > Extensions.
- Tap More Extensions, find Translator Safari Extension, and install it.
- Toggle the extension on and configure permissions.
Translating an Entire Web Page
Full-page translation replaces all text on the page with translated content while maintaining the original layout, images, navigation, and interactive elements. This creates a reading experience that feels natural rather than like pasted machine translation.
On Mac:
- Navigate to a foreign-language page.
- Click the Translator Safari Extension icon in the toolbar.
- The extension automatically detects the source language.
- Select your target language from the dropdown.
- Click Translate. The page content updates in place.
On iPhone and iPad:
- Open a foreign-language page in Safari.
- Tap the extensions menu (the puzzle piece icon or the aA menu in the address bar).
- Select Translator Safari Extension.
- Choose your target language and tap Translate.
The translated page maintains clickable links, expandable sections, embedded media, and form inputs. You can interact with the translated page exactly as you would with the original.
Translating Selected Text
Selected-text translation is the right tool when you do not need the entire page translated. Common scenarios include:
- Bilingual documents where some content is already in your language.
- Technical pages with code snippets, variable names, or mathematical notation that should not be translated.
- Forum threads where only certain posts are in a foreign language.
- Product pages where you want to read translated reviews but keep prices and specifications in their original format.
To translate selected text:
- Highlight the text you want to translate by clicking and dragging (Mac) or tap-and-hold to select (iPhone).
- Right-click (Mac) or access the contextual menu (iPhone).
- Choose the translate option from the menu.
- A popup displays the translation near your selection.
This approach is also faster than full-page translation for quick lookups of individual words or phrases.
Setting a Default Target Language
If you predominantly translate into one language, configuring a default target language eliminates a selection step on every translation:
- Open the extension’s settings (click the toolbar icon and look for a gear or settings option).
- Set your preferred default language.
- Future translations will default to this language, though you can override it per-translation as needed.
Translation Quality: Understanding the Limitations
Machine translation has improved dramatically since the introduction of neural machine translation (NMT) in 2016, but it is not perfect. Understanding where machine translation excels and where it struggles helps you use it more effectively.
Where Machine Translation Excels
Informational content. News articles, product descriptions, Wikipedia pages, government documents, and other factual content translates well because the language tends to be straightforward and the meaning is unambiguous.
Common language pairs. Translation between widely spoken languages (English, Spanish, French, German, Chinese, Japanese, Korean) benefits from enormous training datasets, producing more natural and accurate output.
Structured content. Recipes, how-to guides, lists, and other structured formats translate reliably because the format provides contextual cues that aid the translation model.
Where Machine Translation Struggles
Idiomatic expressions. Phrases like “it’s raining cats and dogs” or cultural references that do not have direct equivalents in the target language often produce confusing literal translations.
Domain-specific terminology. Legal, medical, and highly technical documents use specialized vocabulary that general-purpose translation models may render inaccurately. A “tort” in legal English is not a “torte” (cake) in German, but a translation model unfamiliar with legal terminology might make that mistake.
Ambiguous pronouns. Languages handle pronoun reference differently. English “they” can refer to a group of people, a single non-binary person, or a vague antecedent. Translating into a language with gendered pronouns requires disambiguation that the model must infer from context, and it sometimes guesses wrong.
Literary and poetic text. Tone, rhythm, wordplay, and cultural nuance are extraordinarily difficult for machine translation. If you are reading translated poetry or literature, treat the output as a rough guide to meaning rather than a faithful rendering.
Improving Translation Results
Read in context. When a translated sentence seems odd, look at the surrounding sentences. The meaning often becomes clear from context even when individual sentences are awkwardly phrased.
Toggle between original and translated. If a translated passage is confusing, switch back to the original text. Even if you do not speak the source language, cognates (words that look similar across languages) and proper nouns can help you reconstruct the intended meaning.
Use selective translation for critical passages. When accuracy matters, translate one paragraph at a time rather than the full page. This lets you cross-reference each passage with its original.
Cross-reference with a second service. For critical content, translate the passage using a different service (DeepL, Google Translate) and compare results. Where multiple services agree, you can be more confident in the translation. Where they disagree, the passage likely contains ambiguity worth investigating.
Practical Translation Workflows
International E-Commerce Research
When comparing products from international retailers, translate product descriptions and specifications but keep pricing in the original format. Use selective translation for customer reviews, which often contain the most candid product assessments. Pair translation with a currency conversion tool like Convert to handle price comparisons across currencies. For more on this workflow, see our guide on Safari extensions for smarter online shopping.
Academic and Professional Research
For literature reviews that include non-English sources, translate abstracts first to assess relevance before committing to full-document translation. Save translated pages as PDFs using Save as PDF to build a searchable archive of translated references. Our guide on saving web pages as PDFs in Safari covers the setup.
Travel Planning
When planning trips to non-English-speaking destinations, translate local tourism boards, restaurant review sites, and transportation schedules. These local-language sources often contain more detailed and current information than their English equivalents, which are frequently maintained as secondary priorities. Translation removes the penalty for consulting primary sources.
News and Current Events
Many international news outlets publish higher-quality reporting in their native language than in their English editions, which are often shorter summaries. Regular translation of foreign-language outlets provides perspective diversity that English-only news consumption cannot match.
Language Detection Edge Cases
Automatic language detection works by analyzing character frequency, word patterns, and script type. It handles most pages accurately, but certain content types cause misidentification:
Mixed-language pages. A page with English navigation and Japanese body text might be identified as either language depending on the ratio of content. If detection fails, manually selecting the source language resolves the issue.
Short text. Pages with very little text (mostly images, for example) may not provide enough signal for reliable detection. This is inherently a difficult problem since even human readers sometimes cannot identify a language from just a few words.
Transliterated text. Content written in Latin script that represents a non-Latin language (like romanized Japanese, Hindi transliterated into English letters, or pinyin Chinese) often confuses detection algorithms. These cases usually require manual source language selection.
Code-heavy pages. Programming documentation that mixes code snippets with natural-language explanations may trigger misdetection because code tokens dilute the natural-language signal.
Translation and Accessibility
Language accessibility is a dimension of web accessibility that does not receive enough attention. The W3C’s Web Accessibility Initiative acknowledges that “content should be as understandable as possible” and that language barriers represent a form of accessibility challenge.
For users who need additional accessibility tools beyond translation, our guide on accessibility extensions for Safari covers extensions for dyslexia, low vision, and general reading difficulty. Translation can be combined with these tools: translate a page into your language, then apply dyslexia-friendly formatting or text enlargement for an even more comfortable reading experience.
For a complete overview of every Safari extension category, including AI tools that can summarize translated content to help you quickly assess relevance, see our best Safari extensions for iPhone and Mac in 2026 guide.
FAQ
Does translation work on pages behind a login? Yes, as long as Safari can load the page content, the extension can translate it. The extension processes the rendered DOM, so any content visible in the browser is translatable regardless of whether it required authentication to access.
Are my translated pages sent to external servers? Check the extension’s privacy label in the App Store listing. Extensions that process translations on-device provide better privacy but may have more limited language support. Extensions that use cloud APIs can support more languages but do send page content to external servers for processing.
Can I translate PDF documents viewed in Safari? Safari renders PDFs in a specialized viewer that differs from standard web pages. Translation extensions generally cannot process PDF content displayed in Safari’s PDF viewer. For PDF translation, you would need to extract the text first or use a dedicated PDF translation tool.
Does the extension work with Safari’s Reader Mode? Yes. You can activate Reader Mode first to strip away navigation and ads, then translate the cleaned-up content. This often produces better translation results because the translation model is not wasting capacity on boilerplate navigation text and advertisements.
Why does the translation sometimes change the page layout? Translated text is often a different length than the original. German text is typically 20-30% longer than its English equivalent, while Chinese text is usually shorter. These length differences can cause text to overflow containers, buttons to resize, or column widths to shift. This is a fundamental challenge of in-place translation and cannot be fully eliminated.