Transliteration is the process of converting words or text from one writing system into another while preserving pronunciation.
Unlike translation, transliteration does not change meaning; it changes how words are represented across alphabets or scripts. It is commonly used for names, brands, locations, and languages that use different writing systems.
Transliteration and translation are often confused, but they serve different purposes. While translation converts meaning between languages, transliteration converts words from one writing system into another while preserving pronunciation.
Understanding transliteration is essential for global brands, multilingual content, and localization workflows.
This article explains what transliteration is, how it differs from translation and localization, and when it applies in real content workflows.
We’ll walk through definitions, side-by-side comparisons, common use cases, examples, and the practices that keep transliterated content consistent across markets.
Transliteration vs. translation vs. localization
Transliteration, translation, and localization all move content across languages and markets, but each solves a different problem.
The table below breaks down the differences on the axes that matter most.
| Factor | Transliteration | Translation | Localization |
|---|---|---|---|
| Goal | Preserve pronunciation | Preserve meaning | Adapt for market |
| Focus | Script conversion | Language conversion | Meaning conversion in cultural context |
| Example | Москва → Moskva | Москва → Moscow | Localized city naming convention |
In the Moscow example, transliteration produces Moskva (the Russian source rendered in Latin script with the pronunciation preserved), while translation produces Moscow (the English exonym, a different word altogether), and localization adjusts the surrounding content for the target market's conventions.
Global strategies often require translation, localization, and transliteration together to ensure clarity, usability, and brand consistency across markets.
How transliteration works
Transliteration follows a defined process regardless of the source and target scripts.
Step 1. Source word in original script
Start with the source term as it appears in the source language, using whatever writing system that language uses. Cyrillic for Russian, Arabic script for Arabic, Devanagari for Hindi, Chinese characters for Mandarin, and so on.
Step 2. Script conversion rules applied
Apply the script conversion rules for the source-target pair. Each pair of scripts has established conventions for mapping characters or character combinations, with rules that reflect how the source sounds are best represented in the target script.
Step 3. Pronunciation preserved
Confirm the transliterated result. The finished spelling reads (in the target script) as close to the original pronunciation as the target script allows, without introducing meaning from the target language.
Common use cases for transliteration
Personal names and identity documents are the most common transliteration use case. A birth certificate issued in one script needs to be readable in another when the person crosses borders, and the transliterated name serves as the official target-script version.
Brand names get transliterated to keep brand recognition consistent across markets that use different scripts. Global companies transliterate rather than translate their brand names so that customers hearing the name in one market recognize it in another.
Geographic names appear in transliterated form on maps, in travel content, in logistics addresses, and in any application where a place name from one script needs to be readable in another.
Transliteration keeps the pronunciation recognizable across scripts, which matters when the reader needs to speak the name to a taxi driver or hotel clerk.
Search and SEO applications use transliteration to help multilingual users find the content they're looking for. When users type queries in one script for content that lives in another, transliterated tags and metadata connect the two.
Regulated and legal use cases require transliteration for official records, contracts, and government documents. When a person's name appears in a legal record, transliteration produces the canonical target-script version that other jurisdictions reference consistently.
Platforms like Smartling help organizations manage multilingual content workflows where transliteration, translation, and terminology consistency must work together.
Examples of transliteration
Example 1. Personal names
The Arabic name محمد transliterates to Muhammad in Latin script. Pronunciation is preserved (the target-script version reads with the same sounds as the source), and meaning is unchanged (the name refers to the same person).
The same name transliterates differently in different conventions. Mohammad, Muhammed, and Mohamed are all recognized Latin-script transliterations of the same Arabic source, which is one reason personal names are among the trickiest transliteration cases for consistency.
Example 2. Brand names
Global companies transliterate rather than translate their brand names to preserve identity across markets. Coca-Cola in Chinese renders as 可口可乐 (Kěkǒu Kělè), which combines pronunciation-matching with characters that also carry positive meaning. Nike in Chinese renders as 耐克 (Nàikè), preserving the sound while using characters that fit the brand.
The transliteration keeps the brand name recognizable to customers who encounter it across scripts, protecting global brand consistency.
Example 3. Geographic names
The Russian city name Москва transliterates to Moskva in Latin script. A local speaker pronouncing Moskva produces the same sounds as the Russian source. By comparison, the English translation Moscow is a different word (the English exonym), not the transliterated pronunciation.
When to use transliteration vs. translation
Content type determines whether transliteration, translation, or both apply.
| Scenario | Transliteration | Translation |
|---|---|---|
| Personal names | Yes | No |
| Product instructions | No | Yes |
| Brand names | Often | Sometimes |
| Legal documents | Sometimes | Yes |
Personal names transliterate. A person's name reads the same sounds in every market where it appears in official records.
Product instructions translate. Users need to understand what to do, not just how the source language would pronounce the words.
Brand names usually transliterate, though some brands translate the meaning of their name in specific markets when a translated version carries stronger associations.
Legal documents usually translate for meaning, with transliteration applied to proper names, place names, and identifiers within the document.
Challenges of transliteration
Multiple acceptable spellings are the most common challenge. Many source-target script pairs have more than one recognized transliteration convention, and different systems produce different spellings for the same source word.
Regional differences compound the problem. A name that transliterates one way in one region renders differently in another, and the same variation applies across other regional differences.
Brand consistency issues arise when different teams within the same organization use different transliterations of the same brand or product name. Without centralized terminology, the transliteration of the brand name drifts across marketing, legal, and support content.
Search inconsistency follows from spelling variation. When users search using one transliteration variant and content uses another, discoverability drops even when the underlying content is relevant.
Maintaining consistency across transliterated terms often requires terminology management and centralized workflows.
How to maintain transliteration consistency across markets
Centralized terminology solves the consistency problem at the source. A single glossary that includes the approved transliteration for every relevant term (brand names, product names, place names, key personal names) ensures every team works from the same set of choices.
Smartling Glossaries provide a shared termbase across projects and source languages, so linguists and reviewers work from the same reference.
Governance rules define who owns the transliteration for what. Which team approves the transliteration of a new brand product name, which team approves personal name transliterations for legal documents, and which team approves geographic transliterations for marketing content all get named in the governance model.
Style guides record the transliteration conventions the organization has decided to follow. Rather than relying on ad hoc decisions, the style guide documents the transliteration systems used per language pair and the reasoning behind them. Smartling supports language-specific style guides that translators access while working in the Smartling CAT Tool (the translator workbench).
Workflow automation applies the approved transliterations at content creation and translation time. Instead of asking linguists to remember the correct spelling, the workflow surfaces the approved term from the glossary automatically. Smartling workflows route content through translation, editing, internal review, and approval based on content type and language.
Quality assurance (QA) closes the loop. Smartling Quality Check Profiles support glossary compliance, target-and-source consistency checks, blocklisted terms, and custom checks, with high-severity issues blocking content from advancing until resolved.
Smartling helps organizations maintain consistent multilingual terminology through centralized glossaries, workflows, and quality controls.
Common transliteration mistakes that create confusion
Inconsistent spelling is the most visible mistake. When the same term appears with different spellings across pages, campaigns, or products, users notice the inconsistency even when they don't identify it as a transliteration issue.
Mixing translation and transliteration is the mistake that produces the worst content. A brand name that gets translated in one market and transliterated in another shows up as two different names, breaking global brand consistency.
Ignoring regional conventions produces content that reads awkwardly for target audiences.
A transliteration system that works for one region produces unnatural spellings in another, and defaulting to a single convention worldwide misses the regional preferences that make content feel native.
Lack of governance is the underlying mistake behind the other three. Without a defined process for approving transliterations and applying them consistently, teams default to independent decisions that drift over time.
Risks of poor transliteration
Brand inconsistency is the risk with the widest reach. When the transliteration of a brand or product name varies across markets, the brand feels different in each market, and marketing spend produces weaker recognition than it should.
Search confusion cuts discoverability. When users search using one transliteration variant and content uses another, search engines return less relevant results and users find less of what they're looking for.
Legal and documentation issues surface when transliterations don't match across records. A person whose name appears with one spelling on their passport and another on a contract faces identity verification issues, and correcting the discrepancy takes real work.
Poor user experience follows from all of the above. Users encountering inconsistent transliterations experience the content as disorganized rather than the coherent global brand experience it should be.
Bring transliteration into your multilingual content workflow
Transliteration preserves pronunciation, translation preserves meaning, and both usually happen inside the same document.
Smartling LanguageAI Platform manages multilingual content through terminology governance, localization workflows, and centralized translation systems that keep transliterated terms aligned with the approved glossary across every market.
Learn more about Smartling’s capabilities by watching the 2-minute demo or schedule a meeting today!