Bilingual Reading Mode: Side-by-Side vs Replace-in-Place
When you translate a webpage, you face a real design choice: do you want to see the original alongside the translation, or do you want the translation to replace the original cleanly? Both are useful. Both miss the mark on different days. SwiftIn ships both, you switch with one click. This explainer is for picking the right one for the page in front of you.
The two modes
- Bilingual (side-by-side) — original text on top, translation underneath, both visible. The page layout is preserved; the translation is inserted as additional content next to the source.
- Translation-only (replace-in-place) — the original is swapped out for the translation in the same spot. The layout stays intact, but the source is no longer visible.
Both modes work on every webpage you open in a Chromium browser. The mode you pick is a setting; you can change it any time from the SwiftIn launcher.
When bilingual mode wins
- Learning the language. Seeing the original side by side with the translation builds vocabulary faster than re-reading translations alone. The page becomes a reading lesson.
- Verifying a tricky term. Legal text, medical notes, technical docs — when one word can change the meaning, you want the original visible to cross-check.
- Idioms and culture-specific phrases. A casual Discord reply, a keigo Japanese email, a Russian meme — the translation might smooth over a nuance that matters. Bilingual mode lets you see both.
- Quotes, names, and codes. Brand names, function names, and identifiers should stay readable in the original. Bilingual mode keeps them visible without the cognitive overhead of mentally re-translating.
When translation-only wins
- Long-form reading at speed. A 4,000-word article, a research paper, a long Reddit thread — you do not want the visual noise of duplicated text. Translation-only mode reads like a normal page.
- Sites with dense layout. News sites, dashboards, e-commerce listings — the original layout is already information-dense. Adding a parallel translation column doubles the cognitive load.
- You do not speak the source language at all. If the original text is meaningless to you (you do not read Korean, Arabic, Hebrew), seeing it side by side gives you nothing. Replace-in-place wins.
- Sharing a translated screenshot or read-aloud. If you are going to copy a screenshot or use TTS to listen to a page, you want the cleaner translation-only view.
Switching modes
The SwiftIn launcher on every page has a mode toggle. You can also set a default in the extension settings — if you mostly read for learning, default to bilingual; if you mostly skim, default to translation-only. Override per-page when needed.
Both modes work the same on every webpage SwiftIn translates: news sites, blogs, documentation, GitHub repos, Wikipedia, forums, social feeds, and chat platforms. The rendering strategy is the same; only the layout differs.
A practical workflow
Most people end up with this pattern after a week:
- Daily-driver default: bilingual mode. You learn passively as you read.
- Long-form reading session: switch to translation-only for the article you are about to spend 20 minutes on.
- Anything sensitive (legal, medical, contracts): bilingual mode, always — you want both visible.
- Skim mode (browsing news headlines, scrolling Reddit): translation-only.
Related: Translate Hacker News · Input translation · Pricing