VIAXCorporate Language Solutions

TRANSLATION & LOCALIZATION

Translation vs. localization: what is the difference?

Translation changes content from one language into another. Localization goes further by adapting the translated content to the place, product, audience or context in which it will be used.

The difference matters most when content is part of a website, software product, online store, marketing campaign or other customer experience where language is only one part of what needs to work locally.

What is translation?

Translation is the process of expressing the meaning of source-language content in another language.

A professional translator considers meaning, terminology, grammar, tone and context rather than replacing individual words mechanically. The result should communicate the same information naturally in the target language.

For many documents, this is the main task. A contract, report, technical document or internal communication may primarily need an accurate and well-written version in another language.

What is localization?

Localization adapts content for the language and the environment in which the target audience will use it.

The translated words still matter, but other elements may also need attention. These can include terminology used in the local product, dates, numbers, measurements, interface space, links, cultural references, search terms and the way a message is normally expressed in that market.

Localization is especially common for digital products and customer-facing content because the translation has to work inside something: a website, an app, a user interface, an online store or a campaign.

Translation and localization compared

TRANSLATION

Language is the main focus.

Typical considerations:

  • meaning
  • terminology
  • grammar
  • tone
  • style
  • consistency
  • accuracy against the source

LOCALIZATION

Language is considered together with the target context.

Typical considerations:

  • all translation requirements
  • interface context
  • local terminology
  • character limits
  • dates and number formats
  • units and conventions
  • links and local references
  • market-specific wording
  • search behaviour where relevant

Localization includes translation, but the amount of adaptation varies by project. Some content needs only a few local changes. Other content may require substantial rewriting or market-specific decisions.

What can change during localization?

The exact changes depend on the content and product. Common examples include the following.

  • Terminology

    Product, feature and category names may need to match the terminology already used in the local version.

  • Dates

    Date order and formatting may vary between markets.

  • Numbers

    Decimal and thousands separators can differ between languages and regions.

  • Measurements

    Units may need conversion or different formatting where the project requires it.

  • Currency

    Currency symbols, placement and formatting may differ, although pricing decisions themselves remain the client’s responsibility.

  • Interface length

    A translated button, menu item or message may be longer or shorter than the source and may need wording that fits the available space.

  • Links & references

    Local pages, help resources or other market-specific references may need to replace source-market links where instructed.

  • Tone

    Customer-facing wording may need small changes so that it sounds natural for the local audience.

Examples of translation and localization

  • Website

    A company report published as a PDF may mainly require translation.

    A commercial website usually needs more localization. Navigation, product terminology, calls to action, metadata, links and other elements need to work together in the target-language version.

    Typical localization considerations:

    • navigation
    • page titles
    • calls to action
    • local terminology
    • metadata
    • internal links
    • local search terms where SEO forms part of the project
    Software & Website Localization →

  • Software

    A software string may contain only one or two words, but its correct translation can depend on where it appears, what action it performs and how much space is available.

    For example, the same English word may need different translations depending on whether it is a button, menu heading, status or instruction.

    Typical localization considerations:

    • context
    • character limits
    • placeholders
    • variables
    • interface consistency
    • product terminology
    • regular releases
    What makes software localization different? →

  • E-commerce

    An online store may contain thousands of product descriptions, categories, filters, checkout messages, emails and support pages.

    Localization helps keep product terminology and customer-facing language consistent across the complete shopping experience rather than treating each piece of text separately.

    Typical localization considerations:

    • product categories
    • descriptions
    • specifications
    • checkout content
    • emails
    • returns information
    • local search terminology
    E-commerce & Retail →

  • Marketing

    Marketing content may need more freedom than either straightforward translation or standard localization.

    A campaign headline or slogan can be linguistically accurate and still sound weak in another language. In these cases, the message may need transcreation: a more creative adaptation that preserves the purpose and tone rather than the exact wording.

    Transcreation & Copywriting →

When is translation enough?

Translation may be the appropriate service when the main requirement is to communicate the source content accurately in another language and there are few market-specific elements to adapt.

Examples may include:

  • corporate documents
  • reports
  • contracts
  • technical documentation
  • internal communications
  • policies
  • training material

The decision still depends on how and where the content will be used. Even a document may contain local conventions or terminology that need to be considered.

When is localization needed?

Localization becomes more important when translated content forms part of a product, platform, customer journey or market-specific communication.

It is commonly used for websites, software, apps, online stores and other digital content where the translated words have to work within an existing interface or local user experience.

  • Digital product

    The content appears inside software, a website, app or platform.

  • Local conventions

    Dates, numbers, units or other market-specific formats matter.

  • Customer-facing language

    The wording needs to sound natural for users in a particular market.

  • Product terminology

    Feature names, categories and recurring terms need to match the local product.

  • Regular updates

    The same content environment receives new releases or changes over time.

How does a localization project work?

The exact workflow depends on the content and the client’s existing setup, but a typical localization project may follow these stages.

  1. 01

    Project setup

    The languages, content, files, deadlines and localization requirements are confirmed.

  2. 02

    Reference material

    Existing translation memories, terminology, style guides and previous approved content are prepared where available.

  3. 03

    Translation & localization

    Linguists translate the content while considering its context and local requirements.

  4. 04

    Queries

    Unclear strings, terminology questions or missing context can be raised during the project.

  5. 05

    Review & QA

    The agreed linguistic review and technical checks are completed.

  6. 06

    Delivery & updates

    Localized content is delivered in the required format, and approved project resources can be updated for future work.

Technology & Quality

Why translation memory and terminology matter

Localization projects often contain repeated content. Product names, buttons, features, categories and customer messages may appear across websites, software, documentation and marketing.

Translation memories store previously translated segments. Terminology resources record approved words and phrases. Together, they help linguistic teams reuse approved decisions where appropriate.

On long-term projects, these resources become especially useful as new content and product updates are added.

Terminology Management

Common localization problems

  • Missing context

    A short string can be difficult to translate correctly when the linguist cannot see how it is used.

  • Inconsistent terminology

    The same product feature may be translated differently across pages or releases if terminology is not maintained.

  • Text that does not fit

    Translations can expand and may no longer fit buttons, menus or other interface elements.

  • Broken placeholders

    Variables, tags and placeholders need to remain intact during localization.

  • Old translations

    Previous wording may continue to appear even after terminology or product language has changed.

  • Disconnected review

    Internal feedback can become inconsistent if decisions are not recorded and shared with the linguistic team.

Localization does not always mean rewriting everything

The amount of adaptation should match the project.

A technical interface may require careful local terminology and formatting but very little creative rewriting. A marketing campaign may need much more adaptation. A product catalogue may sit somewhere between the two.

The purpose of localization is to make the content work correctly in its target environment. The process should therefore be based on the actual content rather than applying the same level of adaptation to every project.

PROJECT EXAMPLE

Localization as ongoing work

Some localization programmes continue for years as products, websites and customer communications change.

VIAX’s long-term fintech localization work includes around 9 million translated and localized words across 21 languages, with four to seven new requests arriving on a typical working day.

View fintech case study →

~9M

Words translated and localized

21

Languages

4–7

Requests daily

FAQ

Frequently asked questions

Is localization the same as translation?

No. Translation focuses on expressing the source content accurately in another language. Localization includes translation but may also adapt content to the target market, product, interface or user context.

Does every translation need localization?

No. Some content mainly requires professional translation. Localization is more important when market-specific conventions, digital interfaces, customer experience or local product terminology also need to be considered.

Is localization only for software?

No. Software is a common localization use case, but websites, e-commerce content, apps, marketing and other customer-facing content may also require localization.

Does localization include SEO?

It can. Multilingual SEO may include local keyword research and adaptation of metadata, headings and other search-related content. It should be included as a defined part of the project rather than assumed automatically.

What is the difference between localization and transcreation?

Localization adapts content to the target language and market. Transcreation allows more creative freedom and is mainly used where the message, tone or marketing effect is more important than following the source wording closely.

Can localization be managed across several languages at the same time?

Yes. Multi-language localization can be coordinated under one workflow, with separate linguistic teams using shared terminology, translation memories and project instructions.

RELATED

Need translation or localization?

Send us the languages, content type, files and deadline. We’ll review the material and recommend a suitable workflow.

Get a Quote