Send one message. Everyone reads it in their language.
Write once in your language. Paste a URL anywhere. Every recipient sees the message in their own language, automatically — no app, no account, no copy-paste between translator tabs. Here's the exact flow, and the answers to the five questions people always ask first.
The five-step version
Open heybabel.com/p
No account. No email. Nothing to install. It loads instantly.
Pick your language, type your message
The default is set to your browser language. Optional title, body up to 2,000 characters. Nothing fancy — just write what you want to say.
Click Publish link
Your message is encoded into the URL itself (the part after the # symbol). The full URL is copied to your clipboard. We never see what you wrote — URL fragments don't leave the browser.
Paste the URL anywhere
WhatsApp, email, Slack, Twitter/X, SMS, LinkedIn DM, Discord — anywhere you'd send a link. You can send the same URL to five different people in five different countries.
They open it, read it in their language
Their browser decodes the URL, detects their language, fetches a translation from a public translation service, and renders your message in it. They can toggle the original, pick another language, or click a speaker icon to hear it read aloud. They never touch a "translate" button.
When this actually saves time
International team announcement. You're leading a team split across Berlin, Tokyo, and São Paulo. You want to tell them something matters. Instead of writing it three times or asking them to paste into Google Translate, you paste one URL into the team Slack. Each person reads it in their language on open. The message lands with full weight in all three places at once.
Customer support without a localized agent. A French-speaking customer writes in. You don't have a French agent available. You write the reply in English, paste the Babel Post URL into the helpdesk reply. The customer opens it in French, sees a real answer in their language, in your voice.
Outreach to press, founders, or partners. You're a solo founder emailing a Japanese journalist. Your Japanese is good enough to say "hello" but not to pitch a story. Write in English, send them a Babel Post URL. They open it, read in Japanese, reply in Japanese — and you can open their reply the same way, reversed.
Family across continents. Your grandmother speaks Tagalog, your cousin speaks Portuguese, you speak English. Three languages in one family group chat. Send a Babel Post URL; everyone reads in theirs. Nobody feels left out of the message.
The short version: anywhere you currently copy-paste between Google Translate tabs or accept that a message "won't land as well as you want," a Babel Post URL takes the friction out. One URL, every language, no one installs anything.
Alternatives, and when they win
Google Translate / DeepL are great destination products — you go to them, paste text in, paste text out. They win when you only need one translation, one-way. They lose when the recipient should see a rendered message in their language without manually pasting anything. That's the use case this tool solves.
In-app translation (WhatsApp, Telegram auto-translate) works if you and the recipient are on the same app with the feature enabled. It doesn't work across apps, or when the recipient is on a channel that lacks translation, or when you want to send a single URL to twenty people across ten different platforms.
Professional translation wins for legal, medical, and marketing content where perfect nuance matters. A Babel Post produces a directional translation — good for "this is what I mean," not good for "this is a legally binding document."
Frequently asked questions
Is this really free?
Yes. No account, no payment, no credit card, no email address. The translator runs client-side in the recipient's browser and calls a free public translation API. As of today, there is no paid tier.
Does the recipient need to install anything?
No. They click the URL, their browser loads the page, the page reads the URL fragment, and it renders the translation. It works in any modern browser (Chrome, Safari, Firefox, Edge). No app, no extension, no signup.
Is my message private?
Your text is encoded into the URL itself (the part after the #). URL fragments are never sent to web servers — only processed in the browser. We literally cannot see what you wrote. The translation API call contains only the text and a language pair; we don't store it.
How many languages does it support?
24 source and 24 target languages: English, Spanish, Portuguese, French, German, Italian, Dutch, Mandarin, Japanese, Korean, Arabic, Hindi, Bengali, Indonesian, Tagalog, Vietnamese, Thai, Turkish, Persian, Russian, Polish, Ukrainian, Hebrew, and Swahili. Any of these can be the source or target.
What if the URL is too long?
Babel caps the message at 2,000 characters, which produces a URL of roughly 3,000 characters — well within the safe limit for every major browser, messaging app, and email client. If you need longer, break it into two posts or link to a doc and add a short Babel Post as the intro.
What about voice messages and real-time chat?
The post is text-only, but the recipient can tap a Listen button to hear it spoken aloud in their language using their device's built-in voice. For live, side-by-side chat in 5 target languages at once — with voice input on your side — use the live translator instead. It's the same philosophy applied to conversational messages.
Can I calculate what English-as-default actually costs me personally?
Yes. The Language Tax Calculator gives you a directional personal estimate in about 30 seconds — cognitive overhead + career-premium gap, based on your native language, work domain, income, and weekly hours spent operating in English as a second language.
Thirty seconds. Try it.
Write your first Babel Post. Send the URL to one person in another language. See what happens when they open it.
Write a Babel Post →