# General Translation Knowledge Base: What is a translation management system (TMS)? URL: https://generaltranslation.com/en-US/kb/what-is-a-translation-management-system.mdx Docs index: https://generaltranslation.com/llms.txt Description: A translation management system (TMS) is software that stores your source content and its translations and runs the translation workflow: translation memory, glossaries, review, machine translation, and integrations. Its translation memory reuses earlier translations by exact or fuzzy match. Crowdin, Lokalise, Phrase, Smartling, and Transifex are common examples. Category: Workflow Tools Last updated: 2026-10-20 Authors: Kevin Wu, Jackie Chen Published: 2026-10-20 A TMS sits between the people who write source content and the people (and engines) who translate it. Content goes in as files or strings, gets translated and reviewed inside the TMS, and comes back out in each target language. It doesn't render anything in your app; that's the job of an i18n library. ## What does a TMS do? Most TMS platforms combine the same building blocks: - **A content repository.** Source files or individual strings, each with its translations per locale, versions, and status (untranslated, translated, reviewed). - **Translation memory (TM).** A database of earlier source and target pairs. [Microsoft's glossary](https://learn.microsoft.com/en-us/globalization/reference/glossary) describes how a TM recycles existing translations by exact match or a "fuzzy" (similarity) match, which keeps repeated sentences consistent and cuts cost. TMX is the standard format for moving a TM between tools. - **A termbase or glossary.** Approved translations of product names, feature names, and technical terms, plus terms that must never be translated. Termbases have their own exchange format, TBX. (See Microsoft's [localization guide](https://learn.microsoft.com/en-us/globalization/localization/localization).) - **Workflow and review.** Steps such as translation, editing, and proofreading, assigned to people by language, with an editor where translators see the source, TM matches, and glossary terms side by side. - **Machine translation, AI, and vendor connectors.** Pre-translation through machine translation (MT) engines or LLMs, and connections to language service providers who supply human translators. - **QA checks.** Automated checks for missing placeholders, length limits, glossary violations, and inconsistent translations. - **Integrations.** A CLI, an API, and connectors for Git hosts, CMSs, and design tools that move content in and out. ## How a TMS works in a software project 1. Engineers extract user-facing strings into resource files (JSON, YAML, `.strings`, `strings.xml`, PO) under keys, with an i18n library reading those files at run time. 2. A CLI or Git integration pushes the source files to the TMS. With Crowdin's CLI, for example, that's `crowdin upload`, configured in `crowdin.yml`. 3. The TMS pre-translates new strings from the TM and an MT engine or LLM, then routes them to translators and reviewers. 4. QA checks run, and reviewers approve. 5. The translated files come back through `crowdin download`, a sync, or a pull request, and the app ships them in its next release. Steps 1, 2, and 5 are the parts engineers own, and the loop repeats whenever copy changes. ## What are examples of translation management systems? Each platform pairs those building blocks with its own emphasis: - **[Crowdin](https://crowdin.com/)** calls itself an "AI-powered localization platform," with translation memory, glossaries, built-in QA checks, MT engines, and vendor integrations. - **[Lokalise](https://lokalise.com/)** targets web and mobile apps, games, and other digital content, with automated workflows that apply TM, run QA checks, and route approvals. - **[Phrase](https://phrase.com/)** offers Phrase TMS, a translation management system, and Phrase Strings for software localization. - **[Smartling](https://www.smartling.com/)** calls its TMS an "all-in-one translation orchestration platform" and offers human translation services alongside the software. - **[Transifex](https://www.transifex.com/)** has a per-project [translation memory](https://help.transifex.com/en/articles/6224636-introduction-to-translation-memory), glossaries, and [Transifex Native](https://developers.transifex.com/docs/native) for pushing strings from code. Open-source and developer-oriented options such as [Weblate](/kb/general-translation-vs-weblate), [Tolgee](/kb/general-translation-vs-tolgee), and [Locize](/kb/general-translation-vs-locize) cover parts of the same ground. ## How is a TMS different from an i18n library or a translation agency? The three get confused because a localization program usually needs all of their jobs done: | | i18n library | TMS | Language service provider (LSP) | | --- | --- | --- | --- | | What it is | Code in your app | A software platform | A company of translators and project managers | | Examples | i18next, react-intl, next-intl | Crowdin, Lokalise, Phrase, Smartling, Transifex | Translation agencies and freelancers | | Its job | Pick the locale, load translations, format dates, numbers, and plurals | Store strings and translations, run translation and review workflows | Translate and review content | | Produces translations? | No | Through MT, AI, or the people it routes work to | Yes, by people | | Who uses it | Developers | Localization managers, translators, reviewers | Your localization manager, as a vendor | An LSP often works inside your TMS, or brings its own. Microsoft's localization guide lists the choices: an LSP, single-language or multi-language vendors, or freelancers. ## When you need a TMS, and when you don't Evaluate a TMS when: - Translators or agencies need a CAT (computer-assisted translation) editor and reusable translation memory. - Vendors exchange XLIFF or Office documents, or require specific review and approval workflows. - A localization manager coordinates many content sources, vendors, and release schedules. You may not need a separate TMS when: - A teammate can translate and review a small amount of copy in one or two languages directly in the repository. (See [building i18n in house](/kb/general-translation-vs-in-house-i18n)). - Your existing translation workflow already covers the formats, terminology, review, and delivery your team needs. Frequent releases and code-based content do not rule out a TMS: its Git and CI integrations may automate delivery. Compare the remaining manual work, required approvals, file formats, and vendor integrations before choosing a tool. ## Where General Translation fits General Translation is an alternative for developers who want translation generation and review connected to their code releases. Its [``](/docs/react/reference/components/t) component keeps JSX copy in place; the CLI extracts the marked structure and context notes for the service to translate, and the library renders the results. That avoids maintaining a separate source key and description for every UI message. You can also keep an existing library and its reviewed catalogs. [`npx gt upload`](/docs/cli/reference/commands/upload) imports existing translations; [`npx gt translate`](/docs/cli/reference/commands/translate) generates updates for configured repository files and reuses matching translations. Shared [Glossary terms and Custom Prompts](/docs/platform/dashboard/guides/defining-context-for-translations) keep app and docs terminology aligned, and the [Dashboard editor](/docs/platform/dashboard/guides/reviewing-translations) gives reviewers a place to correct wording before release. A TMS remains a strong fit when language vendors, CAT editors, and XLIFF exchange organize the work. For the decision between that workflow and GT's code-based approach, see [General Translation vs. a TMS](/kb/general-translation-vs-tms). That comparison covers engineering work, context, delivery, and cost in detail. ## Key takeaways - A TMS stores content and translations and coordinates translating them, with translation memory, a termbase, review workflows, MT and vendor connectors, QA checks, and integrations. - Crowdin, Lokalise, Phrase, Smartling, and Transifex are the commonly compared platforms; each pairs a TMS with AI translation and access to human translators. - An i18n library renders translations in your app, a TMS manages producing them, and an LSP supplies the translators. - General Translation connects code-derived context, generation, and review to releases, with an option to keep existing catalogs and libraries. Choose a TMS when vendor coordination and CAT workflows are central. ## Related questions - [General Translation vs. a TMS (Crowdin, Lokalise, Phrase)](https://generaltranslation.com/en-US/kb/general-translation-vs-tms.mdx): Choose General Translation when developers want translation generation, code-derived context, and review connected to product releases. Keep your existing catalogs and rendering library, or author inline JSX without translation keys. A TMS fits programs centered on language vendors, CAT editors, and XLIFF exchange; its integrations can automate the file transfers. - [What is the best localization software for developers?](https://generaltranslation.com/en-US/kb/best-localization-software.mdx): The best localization software for developers translates content where it is written in the code, with context from your product, and keeps every language current. General Translation does this with open-source libraries, Context Groups, and Locadex, an AI agent which opens pull requests. - [Internationalization vs. localization (i18n vs. l10n)](https://generaltranslation.com/en-US/kb/internationalization-vs-localization.mdx): Internationalization (i18n) is the code and design work that lets one product support many locales, such as formatting dates with Intl and supporting right-to-left text. Localization (l10n) adapts it for one locale, which covers translation plus currency, date formats, units, tone, and legal details. - [Crowdin alternatives: General Translation vs. Crowdin](https://generaltranslation.com/en-US/kb/general-translation-vs-crowdin.mdx): Choose General Translation to keep copy in your components and generate translations with your build. Crowdin manages translation projects around resource files, translators, and review workflows, which engineers connect to the app and maintain as the product changes. Crowdin remains a strong fit for open-source community translation and vendor-led programs. - [Lokalise alternatives: General Translation vs. Lokalise](https://generaltranslation.com/en-US/kb/general-translation-vs-lokalise.mdx): General Translation is a strong Lokalise alternative for teams that want readable copy in JSX and translation built into development. Lokalise is built around shared keys, design-tool integrations, and mobile over-the-air delivery. General Translation generates translations from the app's marked content and supports review in its Dashboard or in GitHub pull requests. ## Previous and next questions - Previous question: [Subdirectory vs. subdomain vs. ccTLD for multilingual SEO](https://generaltranslation.com/en-US/kb/multilingual-url-structure.mdx) - Next question: [What is hreflang, and how do I set it up?](https://generaltranslation.com/en-US/kb/what-is-hreflang.mdx) ## Sitemap See the [Knowledge Base sitemap](https://generaltranslation.com/en-US/kb/sitemap.md) for every article.