# General Translation Knowledge Base: General Translation vs. Smartling: which should you use? URL: https://generaltranslation.com/en-US/kb/general-translation-vs-smartling.mdx Docs index: https://generaltranslation.com/llms.txt Description: 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. Category: Workflow Tools Last updated: 2026-10-16 Authors: Kevin Wu, Jackie Chen Published: 2026-10-16 Smartling sells end-to-end localization: a translation management system (TMS) with a CAT (computer-assisted translation) tool and translation memory, AI translation through its AI Hub, human translation from Smartling Language Services, and a Global Delivery Network (GDN) that translates websites as a proxy. For software, the code side runs through files: resource files in your repository become files in Smartling, their strings are parsed out and translated, and translations come back through the GitHub Connector, a self-hosted Repository Connector, or the CLI. General Translation starts from the code instead. ## What Smartling does well - **AI and human translation from one vendor.** Smartling's [translation services page](https://www.smartling.com/translation-services) lists machine and AI translation with instant turnaround, AI Human Translation (AI-assisted human translation) at 1 day, and Creative Translation (expert translation for complex projects) at 2 days, from a language services team of more than 4,000 linguists. - **AI Hub.** [LLMs and machine translation engines](https://help.smartling.com/hc/en-us/articles/10318350761883-Smartling-s-AI-Hub) such as DeepL, Google, and Microsoft, with your glossary and translation memory pulled into prompts. - **Websites without code changes.** The GDN serves translated pages as a [translation proxy](https://help.smartling.com/hc/en-us/articles/18558261190683-Introduction-to-the-GDN). - **Visual context.** [HTML captured with a Chrome extension or JavaScript library](https://help.smartling.com/hc/en-us/articles/360057484273--Overview-of-Visual-Context), screenshots matched to strings with OCR, PDFs, and video. - **Quality tooling.** A CAT tool, quality checks, and an [LQA Agent](https://help.smartling.com/hc/en-us/articles/49428460628507-LQA-Agent-AI-Powered-Quality-Assurance) that scores jobs against the MQM framework. - **Compliance and connectors.** [PCI Level 1, SOC 2, HIPAA, HITRUST, ISO 27001, and ISO 42001](https://www.smartling.com/security), plus 50+ connectors for CMSs and marketing tools such as AEM, Contentful, and Salesforce. ## What Smartling still leaves to your engineers Smartling's repository workflow moves resource files through a translation job: 1. Set up an i18n library and extract or write the resource files it loads. [Smartling's SDKs](https://help.smartling.com/hc/en-us/articles/1260806475390-Smartling-SDKs-Overview) connect to its API. 2. Connect the repository. The hosted GitHub Connector watches pull requests or commits, the self-hosted [Repository Connector](https://help.smartling.com/hc/en-us/articles/360008032174-Options-for-Automation-with-Source-Repositories) serves GitHub Enterprise, GitLab, Bitbucket, and SVN, or you push files with `smartling-cli files push`. 3. Wait for the translation job. In the GitHub Connector's [pull request mode](https://help.smartling.com/hc/en-us/articles/14901568064411-GitHub-Configuration-Modes-Pull-Request-Single-Branch-On-Demand), Smartling's docs say a pull request shouldn't be merged or deleted until its translations are delivered, so a feature pull request waits on translation. 4. Merge the delivery pull request (the [Repository Connector commits to the branch](https://help.smartling.com/hc/en-us/articles/44557348474139-Repository-Connector-Architecture-Overview) instead), wire each new language into the app, and check every screen. App strings also start without visual context: the GitHub Connector doesn't capture it automatically, and Smartling's [supported file types](https://help.smartling.com/hc/en-us/articles/360007998893--Supported-File-Types) table lists none by default for JSON, iOS, and Android files, so it comes from screenshots or captures your team adds. Smartling has a free-to-start Core plan and an Enterprise plan through sales, and it publishes per-word starting rates for each kind of translation. (See [Smartling plans](https://www.smartling.com/plans), checked October 2026.) ## Smartling vs. General Translation at a glance | Feature | Smartling | General Translation | | --- | --- | --- | | Where strings live | Resource files whose strings Smartling parses and stores | In your code inside [``](/docs/react/reference/components/t), or in the resource files you already have | | How code connects | GitHub Connector, Repository Connector, CLI, or API | [`npx gt translate`](/docs/cli/reference/commands/translate) in your build, or [Locadex](/docs/platform/locadex/quickstart) pull requests | | Who translates | AI Hub engines, Smartling AI Translation, or Smartling's linguists | AI with context from your code, Glossary, and Custom Prompts, reviewed by your team in the Dashboard | | Context for each string | Visual context capture, screenshots with OCR, glossary, translation memory, and style guides | Marked JSX structure, variable placeholders, context notes, Glossary, and Custom Prompts | | Websites | The GDN translation proxy | Translates the content in your code, with locale routing in `gt-next` | | Pricing | Core and Enterprise plans, plus per-word translation rates | [Usage-based](https://generaltranslation.com/pricing) | ## Why teams choose General Translation over Smartling With General Translation, the same code change that introduces copy can generate its translations. Copy stays readable inside [``](/docs/react/reference/components/t), and your build produces the language files the app needs. - **Faster.** Put [`npx gt translate`](/docs/cli/reference/commands/translate) before the application build to generate translations for the release you're shipping. Or configure [Locadex](/docs/platform/locadex/guides/configuring-automations) to open translation pull requests from repository events. Engineers can run localization through their existing build and review process instead of coordinating a separate delivery job. - **Cheaper to run.** Inline [``](/docs/react/reference/components/t) blocks remove key creation and resource-file handoffs from routine copy changes. The CLI reuses unchanged translations, so repeated builds generate only new or changed text. See [General Translation pricing](https://generaltranslation.com/pricing) for usage rates and [Smartling's service rates](https://www.smartling.com/translation-services) for its AI and human options. - **Higher quality.** Smartling lists no visual context by default for JSON, iOS, and Android files; teams supply screenshots or captures. General Translation carries the structure of marked JSX and variable placeholders into translation, with [context notes](/docs/react/reference/components/t) to clarify intent and your Glossary and Custom Prompts for product terminology. Reviewers can correct the result in the [Dashboard Translation Editor](/docs/platform/dashboard/guides/reviewing-translations), keeping generation and review in one workflow. - **Lower risk.** The MIT-licensed `gt-react` and `gt-next` libraries can render [bundled translations](/docs/react/guides/storing-translations) without a General Translation account or runtime service call. The generated files stay with your app, giving you control over its deployed copy. General Translation is SOC 2 Type II and ISO 27001 certified and GDPR compliant, and Enterprise plans add SSO, SCIM provisioning, audit logs, custom roles, and forward-deployed engineers. (See its [trust center](https://trust.inc/generaltranslation).) Cursor uses General Translation across its web product and documentation in 14+ locales. (See [production deployments](https://generaltranslation.com/enterprise).) ## When Smartling is the better fit Choose Smartling when you want AI and human translation bought from one vendor with a quality guarantee, when marketing sites need translating through a proxy without code changes, when your industry requires certifications such as PCI or HIPAA, when content lives in many enterprise CMS and marketing tools, or when you exchange XLIFF, TMX, or Office files with vendors. ## Moving from Smartling to General Translation Start with the resource files your app already loads, such as JSON or PO. [Configure the CLI](/docs/cli/guides/configuring) for those files and run [`npx gt upload`](/docs/cli/reference/commands/upload) to import the sources and existing translations before your first [`npx gt translate`](/docs/cli/reference/commands/translate) run. Your existing i18n library and file layout can stay in place. Import your glossary into a [Context Group](/docs/platform/dashboard/guides/defining-context-for-translations), then review generated copy in the Dashboard. Adopting inline [``](/docs/react/reference/components/t) is a separate option for teams that also want to stop maintaining source keys. For the broader platform decision, see [Why use General Translation instead of a TMS?](/kb/general-translation-vs-tms). ## Is General Translation an alternative to Smartling? Yes. General Translation combines code-aware generation, build automation, and Dashboard review for software teams. You can keep existing catalogs or use inline JSX. Smartling is a strong fit when you want a website translation proxy or human translation services from the same vendor. ## Key takeaways - Smartling is a full-service enterprise platform, strongest when you want AI and human translation, a website proxy, and broad compliance from one vendor. - Engineers still keep keyed resource files, and in pull request mode a feature pull request waits until its translations are delivered. - General Translation brings code context, generation, and review into the release workflow, while bundled translations keep production delivery in your app. ## 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. 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. 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. Transifex: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-transifex.mdx): 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. ## Previous and next questions - Previous question: [General Translation vs. react-intl: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-react-intl.mdx) - Next question: [General Translation vs. Symfony Translation: which should you use?](https://generaltranslation.com/en-US/kb/general-translation-vs-symfony-translation.mdx) ## Sitemap See the [Knowledge Base sitemap](https://generaltranslation.com/kb/sitemap.md) for every article.