What is email internationalization (i18n)?

Still have a question, spotted an error, or have a better explanation or a source we should cite?

Internationalization (i18n) is the technical plumbing that lets your email system handle multiple languages and regions without falling apart. It's the engineering work you do once so that your template can work anywhere. Think of it like building a house with plumbing that's ready to deliver water to any location. Localization is choosing which faucets to install where. (i18n is the infrastructure. Localization is the application.)

Here's what i18n actually covers: You need UTF-8 encoding everywhere. database to ESP to email headers. Your templates can't assume English is the longest language. German typically runs 30% longer than English. Chinese is often more compact. You need template structure that can switch languages without breaking. Right-to-left language support (Arabic, Hebrew) needs extra HTML considerations. Your systems have to store multiple versions of the same string, indexed by locale code so the right one goes to the right person.

The "18" in i18n is a numeronym. there are 18 letters between the 'i' and the 'n' in "internationalization." Getting i18n right from the start is dramatically cheaper than trying to retrofit it later when you've got hundreds of templates and years of data structure. You're building for scale. Your subscribers will never see the i18n infrastructure, but they'll immediately notice when it's broken. garbled characters, wrong language, layout collapse. Build it right once.

Related: internationalization, email design best practices, email accessibility.

Contributors

Who worked on this answer

Every name links to their profile. Every company links to their site. Real people, real accountability.

Ask an AI · tailored to your setup

Audit my i18n setup

I'm sending emails in multiple languages and want to make sure my technical foundation is solid. My current setup (fill in what applies): - Email platform/ESP: Mailchimp, HubSpot, custom, other - Languages you support: list them - Template tool: ESP builder, MJML, custom HTML, other - Where translations are stored: CMS, spreadsheet, translation tool, other - Have you had any encoding issues: yes, no, unsure I need to understand: 1. Is my ESP set to UTF-8 (and how do I verify it) 2. What encoding issues to watch for 3. How to test my setup supports the languages I need 4. Whether I need to plan differently for RTL languages

Edit the yellow boxes, then send to the AI of your choice.