Localization vs Translation: What's the Difference

Many confuse translation and localization. They're different things. If you're building a site for another country — you need localization, not just translation.

Translation is words

Translation is replacing words of one language with words of another. "Hello, World!" → "Bonjour, le monde!". That's it.

Localization is context

Localization is adapting all content, design, and functionality to the target culture. It includes translation but goes much further.

What localization includes

1. Date and time

USA: 05/12/2025 (month/day/year). Europe: 12/05/2025. Japan: 2025-05-12. Leave the American format on a Ukrainian or German site, and users will get confused.

2. Currency and numbers

"$1,234.56" in USA. "1.234,56 €" in Germany (dot and comma swap!). "1 234,56 ₴" in Ukraine. Different number rules.

3. Units of measurement

USA — miles, pounds, Fahrenheit. Rest of the world — kilometers, kilograms, Celsius. A food delivery site with weights in pounds will scare Europeans.

4. Colors and symbols

In China red = happiness, white = mourning. In Europe — opposite. The blue-green approval checkmarks that work in the US may evoke different associations in other countries.

5. Images and photos

Models in photos should be from the target country. Ukrainians and Germans react better to local faces than to overly cheerful American smiles; Chinese want to see Chinese in photos.

6. Forms and fields

USA address: street, city, state, ZIP. Germany: street + number, postal code + city. Ukraine: postal code, region, city, street, building, apartment. Japan: written in reverse — from general to specific. Standard US forms won't work.

7. Legal requirements

GDPR in Europe requires specific cookie notifications. Ukrainian law (152-VIII) — consent for personal data. California — CCPA. All this needs accounting for.

8. Payment methods

In Germany: SEPA bank transfer, PayPal, Klarna. In Ukraine: ПриватБанк, monobank, Apple/Google Pay. In China: WeChat Pay, Alipay. PayPal, dominant in the US, isn't used in some countries.

Real example

When Microsoft localized Excel for Turkey, it translated all formulas — SUM became TOPLAM. Good for users, but Turkish Excel documents stopped opening in other versions. They had to add support for both formula formats.

When translation is enough

• Personal blog
• Simple product description
• Internal documentation
• Chat messages

When you need localization

• E-commerce (need currency, payment, shipping)
• Corporate site for new market
• Mobile app
• Game
• SaaS service

Cost

Translating a small site: $100-$1000. Full localization: 5-10x more, because it includes UX designer, marketer, lawyer, and tester from the target country.

Main advice

Before entering a new market, hire a native speaker from that country — let them look at the site with local eyes. What seems obvious to you may turn out funny or offensive.