Type in Your Language, Send in Theirs: Input Translation Across the Web
Almost every browser translator is built for the reading half of the web — you land on a foreign page, you click translate, you read. That solves only half the problem. The other half is writing: you type a reply, an email, a tweet, a comment in your native language, and it has to land in another. This article is about that second half — how Input Translation works in Swiftin, where it shines, and how to set it up.
What Input Translation actually does
On any input field on any webpage — a chat compose box, an email body, a tweet composer, a form, a Reddit reply — you type in your own language. Trigger Input Translation, and the field's contents update in place with the translated version. You review, you edit, you send.
No copy-paste. No second tab. No leaving the conversation. The reply goes through the platform's native send path — the recipient sees the translated message, not a flag-emoji indicator that you used a translator.
Where it shines
- Chat platforms — Discord, Slack, X DMs, Telegram Web, WhatsApp Web, Reddit replies. The compose box is the surface; Swiftin updates it in place.
- Email — Gmail, Outlook Web, ProtonMail. Type a reply in your language, switch to the recipient's, send.
- Cold outreach — LinkedIn DMs, Upwork proposals, sales emails. Tone styles let you switch the register from casual to professional based on the relationship.
- Forms and applications — visa application notes, job application cover letters, customer-service tickets. Anything with an open text field.
Three tone styles, one input
Pro and Team plans unlock three tone styles for Input Translation, each with Min and Max intensity:
- Normal — clean, neutral, accurate. The default for general use.
- Slang — casual, native-sounding, internet-aware. Good for Discord, Reddit, fan communities.
- Business — polished, polite, professional. Good for LinkedIn, Gmail, client work.
The same English sentence translated through Slang vs Business produces meaningfully different output. The recipient's expectations differ based on the platform and the relationship; Input Translation lets you match.
Input field types
Swiftin only activates on plain text inputs, search boxes, textareas, and rich-text editors. Password fields (type="password") and other browser-typed inputs (email, tel, number, url, hidden) are never activated, so you will not accidentally trigger translation on your own password. If a site uses a plain text input for sensitive data (some payment forms, OTP codes, custom phone widgets), you can disable Swiftin per-site in the extension settings.
Setup — under a minute
- Install Swiftin from the Chrome Web Store
- Sign in (free, no card required)
- Open any webpage with a text input — start typing in your language
- Trigger Input Translation via hotkey or the floating button next to the field
- Review the translated version, edit if needed, send
Hotkey is configurable in Settings → General → Hotkeys. Default works out of the box on every Chromium browser.
Why this matters
Reading-only translators turn the foreign web into a magazine you can browse. Adding Input Translation turns it into a conversation you can join — chat with people in Berlin, write to a client in Tokyo, post in a Brazilian fan thread, all in their language and in a tone that fits. That is the difference between consuming a multilingual web and participating in one.
Related: Translation styles · Bilingual reading mode · Pricing