Welcome back, {name}. Your trial ends soon.{' '}
Compare plans
);
}
```
The sentence, the name, and the link stay in the component, and [`npx gt translate`](/docs/cli/reference/commands/translate) translates the block as one unit while keeping the name untranslated.
- **Faster.** In the banner above, the copy, variable, and link are edited together. The CLI extracts that block and generates changed translations before your build, reusing matching completed work. This removes source-key and rich-text mapping work from each copy change.
- **Usage-based billing.** SimpleLocalize's member and key allowances affect what you pay as your catalog or review team grows. General Translation's [usage-based pricing](https://generaltranslation.com/pricing) has no seat charges or key-count tiers, so inviting another reviewer doesn't increase a seat bill.
- **JSX structure as context.** Keep a note such as "Trial means a software subscription trial" next to the banner. The extracted structure carries the greeting and pricing link together, and reviewers can correct the generated wording in the [Dashboard](/kb/review-translations). The [context guide](/kb/ai-translation-context) shows how to add surrounding source lines and shared terminology.
- **Lower risk.** Start with the i18next or next-intl catalogs your app already renders and retain reviewed translations. Inline JSX can come later. For React and Next.js repositories, configured Locadex **Generate code** runs propose wrappers for newly unmarked text in a reviewable pull request. An app configured to load all translations locally with the MIT-licensed `gt-react` or `gt-next` can render them without a GT account or runtime service calls.
## When SimpleLocalize is the better fit
Choose SimpleLocalize when translators or reviewers want to edit text on your live site through a browser extension, when you want users to suggest translations, when you need different wording for individual customers, when native mobile apps need over-the-air string updates, or when your apps use formats such as [Flutter ARB, XLIFF, Java properties, or Excel](https://simplelocalize.io/docs/file-formats/arb/).
## Moving from SimpleLocalize to General Translation
1. **Export and back up.** Export a matching snapshot of your source and complete, reviewed target files from SimpleLocalize, and keep a backup. Finish incomplete locales first, so untranslated entries aren't imported as translations.
2. **Pause SimpleLocalize's writes.** Before General Translation writes any files, pause the GitHub App and remove SimpleLocalize download steps from CI. If two tools write the same files, whichever writes last wins.
3. **Set up context.** Configure `gt.config.json` for those files, carry key descriptions and length limits into [keyed metadata](/docs/cli/reference/keyed-metadata) for JSON or YAML, and import your glossary into a Context Group, so the first translations use them.
4. **Upload.** Run [`npx gt upload`](/docs/cli/reference/commands/upload) to import the target files that match the source snapshot.
5. **Translate and verify.** Run [`npx gt translate`](/docs/cli/reference/commands/translate) and check a locale in the app. For i18next or next-intl, keep your existing library while the CLI [generates subsequent translations](/docs/cli/guides/generating-translations); moving copy inline is a separate, later choice.
## Is General Translation an alternative to SimpleLocalize?
Yes. Your reviewed translations, key descriptions, and glossary carry over, and an i18next or next-intl app keeps its library. What changes is the loop: translation runs in your build from the component or file instead of through a synced catalog, and you can move copy inline into [`