Localization Isn't Just Translation: What Breaks When You Go Multi-Language
"Just translate the site" is the phrase that starts almost every localization project, and it's the phrase that most understates what's actually involved. Translation is swapping words. Localization is making the whole experience make sense in a different language, culture, and sometimes legal context — and the gap between those two is where most multi-language launches run into trouble.
What actually breaks
- Layout — text that's 40% longer in German than in English will break a button or navigation item sized for the shorter language.
- Right-to-left languages, which don't just flip text direction — they flip the entire visual layout, including where icons and controls sit.
- Date formats, currency, and number formatting, which differ enough between locales to genuinely confuse users if left as-is.
- Content that doesn't translate culturally at all — an idiom, a joke, or a reference that makes perfect sense in one market and means nothing, or means something wrong, in another.
The technical foundation that has to exist first
Before any translation happens, the codebase needs to actually support it — text pulled out of components into translatable strings, layouts built to flex rather than assume fixed-width English text, and a routing structure that handles locale-specific URLs cleanly. Retrofitting this into an app that was never built with it in mind is a much bigger project than adding it from the start.
Do you have a real, funded plan to support customers in that language too — not just show them a translated page? Localization without support behind it just moves the friction to a different point in the customer journey.
Plan for this the same way we'd plan for any production concern in a Next.js app — as a foundational decision made early, not a feature bolted on once the English version is already live.
Talk to us
Have a project in mind? Tell us about it.
Four quick questions and we'll reply within one business day with an honest view on the fastest way to ship it, whether that's our own products, a custom build or an integration.
Start your project
Let’s build something great
Which industry does your business belong to?
Pick the closest match — we'll tailor the rest for you.
Keep reading
Next.js in Production: What We Wish We Knew Before Our First Client Launch
The tutorials get you to a working app. They don't tell you what happens when that app has real traffic, a real client, and a real invoice riding on it staying up.
Web DevelopmentThe Real Cost of a Slow Website (and How to Fix It Without a Rebuild)
A one-second delay doesn't sound like much until you translate it into how many people quietly closed the tab before your page finished loading.
Web DevelopmentChoosing a Tech Stack Without Chasing Hype
Every year has a stack everyone's excited about on social media. Almost none of that excitement should factor into what you actually pick for a client's business.