# General Translation Knowledge Base: General Translation vs. Transifex: which should you use? URL: https://generaltranslation.com/en-US/kb/general-translation-vs-transifex.mdx Docs index: https://generaltranslation.com/llms.txt Description: Choose General Translation to translate marked JSX with its structure and developer context, then bundle the results or serve them from its CDN. Transifex Native also keeps strings in code, but publishes them through its content delivery service. Transifex is a strong fit for teams using its translation partners, quality scores, or snippet-based website translation. Category: Workflow Tools Last updated: 2026-10-16 Authors: Kevin Wu, Jackie Chen Published: 2026-10-16 General Translation is the stronger fit when you want translation to follow your React development workflow: mark JSX with [``](/docs/react/reference/components/t), generate translations before the build, and ship them with the app. Transifex is a translation management system (TMS), [part of XTM International](https://xtm.ai/news/xtm-international-acquires-transifex) since January 2025, that combines AI, translators, and partner vendors. Transifex supports both resource files and strings marked directly in code through Transifex Native. Native pushes messages to Transifex and loads translations from its content delivery service (CDS). General Translation extracts marked JSX for translation and lets the app load the result from bundled files or its CDN. ## What Transifex does well - **Strings from code without files.** [Transifex Native](https://developers.transifex.com/docs/javascript-sdk) marks strings with a translation function or a React component, uses the source text as the key by default, and pushes strings with `txjs-cli push`. The SDKs and the [CDS](https://github.com/transifex/transifex-delivery) are open source under the Apache-2.0 license, and the CDS can be self-hosted. - **AI with quality scores.** Transifex AI translates with your glossary, translation memory, and context, and its [Translation Quality Index (TQI)](https://help.transifex.com/en/articles/9465000-translation-quality-index-tqi) scores AI translations. Those that meet a configured threshold can be marked as reviewed automatically. - **Human translation partners.** You can [order translations from partners](https://help.transifex.com/en/articles/6235673-ordering-translations) such as e2f, Gengo, and TextMaster inside Transifex. - **Websites without code changes.** [Transifex Live](https://help.transifex.com/en/articles/6244596-introduction-to-transifex-live) translates a website through a JavaScript snippet, though Transifex recommends Native for React and Vue apps. - **Unlimited collaborators.** The current plan doesn't charge for seats, projects, or hosted content. - **File formats.** [46+ formats](https://help.transifex.com/en/articles/6219670-introduction-to-file-formats), including XLIFF, Office files, and subtitles. ## What Transifex still leaves to your engineers Engineers connect the app to Transifex's translation and delivery workflow: 1. Mark each string for Transifex: extract it into a resource file under a key, or wrap it in Native's translation function or React component. 2. Send it to Transifex with [`tx push`](https://github.com/transifex/cli), a Git integration, or `txjs-cli push`, typically as a CI step. 3. Configure AI translation or a partner vendor, along with any review requirements. 4. Deliver the translations. In the file workflow, a [Git integration](https://help.transifex.com/en/articles/6265125-github-via-transifex-ui) opens a pull request or commits once a language reaches a completion threshold. Native fetches translations from the [CDS](https://developers.transifex.com/docs/content-delivery-service), whose content becomes stale after one hour by default; its refresh interval is configurable. Transifex AI uses [glossary terms, translation memory, context fields, and company information](https://help.transifex.com/en/articles/9867663-context-in-transifex-ai). Developer notes and string instructions can also be enabled. General Translation's React library supplies context through the marked JSX structure and named placeholders, with developer notes and project terminology added to guide translation. Pricing is one AI-first plan sold through sales and billed on AI-translated words, with no public rates. (See [Transifex pricing](https://www.transifex.com/pricing), checked October 2026.) ## Transifex vs. General Translation at a glance | Feature | Transifex | General Translation | | --- | --- | --- | | How strings get in | Resource files through `tx push` or Git integrations, or Native SDK strings through `txjs-cli push` | Content stays in your code inside [``](/docs/react/reference/components/t), or in the resource files you already have | | Who translates | Transifex AI with TQI scores, or partner vendors | AI with context from your code, Glossary, and Custom Prompts, reviewed by your team in the Dashboard | | Context for each string | Glossary, translation memory, context fields, and optional developer notes | Marked JSX, named placeholders, developer notes, Glossary, and Custom Prompts | | Delivery | Pull requests or commits for files; the CDS at run time for Native | Locally bundled translations or General Translation's CDN | | Pricing | AI-translated word volume, with quotes through sales | Published [usage rates](https://generaltranslation.com/pricing) | ## Why teams choose General Translation over Transifex - **Faster.** [`npx gt translate`](/docs/cli/reference/commands/translate) extracts marked content, generates translations, and downloads the results before the app build. That gives a release one translation step to run. If you prefer reviewing changes in GitHub, [Locadex](/docs/platform/locadex/quickstart) opens a pull request when your code changes. - **Cheaper to run.** General Translation reduces the engineering work of translating rich UI: a sentence can keep its links, formatting, and dynamic values inside one [``](/docs/react/reference/components/t) block instead of being reconstructed as a message string. You can estimate translation costs directly from the [published rates](https://generaltranslation.com/pricing). - **Higher quality.** Keeping a sentence and its nested elements together gives translation the relationship between the words, links, and placeholders. Developer notes clarify ambiguous copy, while assigned [Context Groups](/docs/platform/dashboard/guides/defining-context-for-translations) apply the same terminology to your app and website. Your team can refine the output in the [Translation Editor](/docs/platform/dashboard/guides/reviewing-translations). - **Lower risk.** With [local translations](/docs/react/guides/storing-translations), the app renders from files bundled in the release and makes no runtime calls to General Translation. Teams that want to publish translation edits without redeploying can use General Translation's CDN instead. The MIT-licensed JavaScript libraries work without an account when you supply the translations. Sierra ships 7+ locales across its web and go-to-market content with General Translation. (See [production deployments](https://generaltranslation.com/enterprise).) ## When Transifex is the better fit Choose Transifex when you want to translate a website with a snippet and no code changes, when you want to order human translation from its partner vendors, when TQI-based auto-approval fits your review process, when you exchange XLIFF, Office, or subtitle files, or when native iOS and Android apps need [over-the-air updates with offline bundles](https://developers.transifex.com/docs/ios-sdk). ## Moving from Transifex to General Translation For file-based projects using supported formats such as JSON, YAML, PO, or iOS and Android resource files, follow the [CLI quickstart](/docs/cli/quickstart). Configure source and locale paths, then import existing translations with [`npx gt upload`](/docs/cli/reference/commands/upload) before generating new ones. For a React app using Native, set up `gt-react` or `gt-next` through the [React quickstart](/docs/react/react-quickstart) or [Next.js quickstart](/docs/react/nextjs-quickstart). Migrate one screen at a time: put its copy and markup inside [``](/docs/react/reference/components/t), then run [`npx gt translate`](/docs/cli/reference/commands/translate). Keep the remaining screens on Native while you review the translated screen. Import your glossary into a [Context Group](/docs/platform/dashboard/guides/defining-context-for-translations) to carry product terminology across. ## Is General Translation an alternative to Transifex? Yes. Choose General Translation to generate translations from structured JSX before your build and deliver them as bundled files or through its CDN. You can also keep an existing file-based app and use General Translation to translate its catalogs. For a broader vendor comparison, see [Why use General Translation instead of a TMS?](/kb/general-translation-vs-tms). ## How is Transifex Native different from General Translation? Both use open-source SDKs and can keep source text in code. In [Transifex's React SDK](https://developers.transifex.com/docs/react-sdk), a `` message can receive React elements as interpolation values. General Translation's [``](/docs/react/reference/components/t) keeps the sentence and nested elements directly in JSX and extracts that structure for translation. Native delivers translations through the CDS; General Translation lets you choose bundled files or its CDN. ## Key takeaways - Transifex is a TMS with open-source Native SDKs, AI translation with quality scores, partner vendors, and Transifex Live for websites. - Native already supports strings in code. General Translation's React advantage is authoring and translating structured JSX, with developer notes and shared terminology. - General Translation generates translations before the build and supports both bundled delivery and CDN updates, so you can choose how translated content reaches users. ## Related questions - [Why use General Translation instead of a TMS (Smartling, Lokalise, Phrase, Crowdin, or Transifex)?](https://generaltranslation.com/en-US/kb/general-translation-vs-tms.mdx): A translation management system (TMS) such as Smartling, Lokalise, Phrase, Crowdin, or Transifex coordinates translators, but engineers still extract strings, send them out, wait for translations, and wire them back into the product. General Translation translates content in your code with its context, ships every language with each release, and runs on open-source libraries with no lock-in. - [General Translation vs. Crowdin: which should you use?](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. - [General Translation vs. Lokalise: which should you use?](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. - [General Translation vs. Phrase: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-phrase.mdx): General Translation is a strong Phrase Strings alternative when your app and documentation ship together. It generates translations from code and content files, applies shared terminology, and runs in your release workflow. Phrase combines software localization with a document-focused TMS, vendor management, and a broad choice of translation engines. - [General Translation vs. Smartling: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-smartling.mdx): Choose General Translation when you want app translations generated from code as part of your release. Smartling combines a translation management system, AI and human services, and a website translation proxy. General Translation keeps copy in your components, carries its context into translation, and gives your team a Dashboard for review. ## Previous and next questions - Previous question: [General Translation vs. Tolgee: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-tolgee.mdx) - Next question: [General Translation vs. vue-i18n: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-vue-i18n.mdx) ## Sitemap See the [Knowledge Base sitemap](https://generaltranslation.com/kb/sitemap.md) for every article.