Localization is often described as “translation,” but a successful multilingual launch involves far more than moving words from one language to another. A smooth translation workflow is a coordinated sequence of planning, linguistic work, technical checks, design adaptation, testing, and ongoing improvement. When the stages happen in the right order, teams avoid rework, missed context, embarrassing language errors, and last-minute release delays.
TLDR: A proper localization workflow begins with planning and content preparation, then moves into translation, review, testing, and final publishing. The best results come from giving translators context, using glossaries and style guides, and testing the finished experience in the actual product or layout. Localization does not end at launch; updates, feedback, and terminology improvements should feed back into the next cycle.
1. Project Scoping and Localization Planning
The first stage is not translation. It is planning. Before anyone translates a word, the team needs to know what is being localized, for whom, into which languages, and under what constraints.
This stage usually defines:
- Target markets and languages: For example, Spanish for Mexico is not the same as Spanish for Spain.
- Content types: Websites, apps, legal pages, support articles, ads, subtitles, packaging, or software strings.
- Deadlines and release dates: Localization should be built into the launch schedule, not added at the end.
- Quality expectations: Marketing copy may need transcreation, while technical documentation may prioritize precision.
- Stakeholders: Product managers, developers, designers, translators, reviewers, legal teams, and market specialists.
Good planning prevents the most common localization problem: treating every text as if it has the same purpose. A button label, an onboarding email, and a compliance disclaimer each need different handling.
2. Content Audit and Source Text Cleanup
Next comes the content audit. Teams identify what needs localization and remove anything outdated, duplicated, or irrelevant. Translating messy source content leads to messy multilingual content, multiplied across every language.
This is also the time to improve the original copy. Sentences should be clear, consistent, and free of unnecessary idioms. For example, a phrase like “hit the ground running” may work in English marketing copy, but it can be confusing or awkward in other languages. A cleaner version, such as “start quickly and effectively,” is easier to localize.
Source cleanup saves money because translation is often priced by word count. It also improves quality because translators are not forced to interpret vague, inconsistent, or outdated material.
3. Internationalization and Technical Preparation
For software, websites, and apps, internationalization should happen before translation. Often shortened to i18n, this stage prepares the product to support different languages, scripts, formats, and cultural expectations.
Internationalization includes making sure the product can handle:
- Longer or shorter text strings
- Right to left languages such as Arabic or Hebrew
- Different date, time, number, and currency formats
- Plural rules that vary by language
- Special characters and accents
- Text expansion in buttons, menus, and forms
If internationalization is skipped, translators may produce accurate translations that simply do not fit or display correctly. A German button label may overflow. A Japanese line break may look unnatural. A currency format may confuse users. Technical readiness is therefore a foundation, not an optional extra.
4. Building the Localization Kit
Before translation begins, the team should provide a localization kit. This gives linguists the context and rules they need to make good decisions. Translators do not work well in a vacuum; they need to know what the product does, who the audience is, and how the brand should sound.
A strong localization kit includes:
- Style guide: Tone, formality level, punctuation preferences, and brand personality.
- Glossary: Approved translations for product names, features, technical terms, and repeated phrases.
- Translation memory: Previously translated segments to maintain consistency and reduce cost.
- Reference materials: Screenshots, wireframes, product demos, or live environment access.
- Do not translate list: Brand names, code variables, placeholders, tags, and legal terms that must remain unchanged.
This stage is especially important for products with specialized vocabulary. Without agreed terminology, one translator might call the same feature a “dashboard,” another a “control panel,” and another a “main view.” Consistency builds trust.
5. Content Extraction and File Preparation
Now the content is prepared for translation. In software localization, text is usually extracted into resource files or a translation management system. In document localization, files may be prepared from formats such as DOCX, InDesign, XML, HTML, JSON, or subtitles.
During preparation, teams protect code, variables, and formatting tags. For example, a string like “Hello, {first_name}” must preserve the placeholder. If it is deleted or translated incorrectly, the user experience breaks.
This stage also involves segmentation, where text is divided into translatable units. Good segmentation helps translation tools match repeated content and helps reviewers compare source and target text clearly.
6. Translation
Only now does the actual translation stage begin. Professional translators convert the content into the target language while following the glossary, style guide, and project instructions. Their job is not only to be accurate, but also to make the text sound natural for the audience.
For some content, literal translation is not enough. Marketing slogans, app store descriptions, advertising headlines, and campaign copy may require transcreation, which adapts the message creatively while preserving the original intent. A joke, metaphor, or emotional hook may need to be rewritten rather than translated word for word.
Context matters enormously. The English word “save” could mean store data, rescue someone, or spend less money. Screenshots and product notes help translators choose the correct meaning.
7. Editing and Linguistic Review
After translation comes editing, sometimes called bilingual review. A second linguist compares the translation with the source text to check accuracy, completeness, terminology, grammar, and style.
This step catches errors that the original translator may miss. It also ensures that the translation follows the approved voice. For example, a brand that sounds friendly and conversational in English should not suddenly sound stiff and bureaucratic in French, unless local expectations require a more formal tone.
In many workflows, there is also an in country review. This review is performed by someone familiar with the local market, such as a regional marketing manager or subject matter expert. Their job is not to rewrite everything according to personal taste, but to verify that the content works for local users and business goals.
8. Quality Assurance Checks
Once the translation and review are complete, the files go through quality assurance. Linguistic QA tools can automatically detect many issues, including inconsistent terminology, missing numbers, incorrect punctuation, double spaces, untranslated text, and broken tags.
Automated QA is valuable, but it cannot replace human judgment. A tool may confirm that a term is consistent, but it cannot always tell whether the sentence sounds persuasive, polite, or culturally appropriate. The best workflows combine technology with expert review.
9. Layout, Design, and Desktop Publishing
Localized text often changes length. English to German may expand significantly, while English to Chinese may become more compact. This affects brochures, landing pages, mobile screens, packaging, presentations, and interface layouts.
In the desktop publishing or layout stage, designers and localization specialists adjust spacing, line breaks, typography, font support, and visual hierarchy. They also check that images, icons, and colors are culturally appropriate. A hand gesture, symbol, or stock photo that seems harmless in one market can feel odd or inappropriate in another.
10. Functional and Linguistic Testing
Testing is where localization meets the real user experience. For digital products, localized content should be tested inside the website, app, or software interface. This stage checks whether the translation displays correctly and whether users can complete tasks without confusion.
Testers look for issues such as:
- Text cut off in buttons or menus
- Broken links and incorrect redirects
- Wrong date, number, or currency formats
- Untranslated strings appearing in the interface
- Search, filters, and forms behaving incorrectly
- Layout problems in mobile or desktop views
Linguistic testing also checks the translation in context. A sentence that looked perfect in a spreadsheet may sound strange when placed beside a product image or inside an error message. This is why final testing should never be skipped.
11. Final Approval and Publishing
After fixes are implemented, the localized content goes through final approval. Stakeholders confirm that language, formatting, legal requirements, and technical performance are ready for publication. Then the content can be launched.
Publishing may involve uploading files to a content management system, merging localized strings into a software build, updating metadata, or scheduling regional marketing campaigns. At this stage, version control is essential. Teams should know exactly which source content and translated files were approved.
12. Post Launch Maintenance
Localization does not end when the content goes live. Products change, help centers expand, campaigns evolve, and users find issues that internal teams missed. The final stage is maintenance.
Post launch work includes collecting feedback, fixing bugs, updating translation memories, refining glossaries, and tracking performance in each market. If users in one country abandon a checkout process more often than others, the issue might be technical, cultural, linguistic, or all three.
The Correct Order, in Short
A reliable localization workflow follows this sequence: plan, audit, internationalize, prepare resources, extract content, translate, edit, review, run QA, adjust layout, test, approve, publish, and maintain. Some stages may overlap in agile teams, but the logic remains the same: prepare before translating, review before testing, and test before release.
When localization is treated as a structured workflow rather than a last-minute task, the result is more than accurate translation. It becomes a product experience that feels natural, trustworthy, and intentionally built for each audience.