# General Translation Knowledge Base: How do I review and edit translations? URL: https://generaltranslation.com/en-GB/kb/review-translations.mdx Docs index: https://generaltranslation.com/llms.txt Description: General Translation lets reviewers compare and edit translations in the Dashboard, with labels and comments to track review. Download saved edits with the CLI or bring them into a pull request through the next Locadex translation run. Developers can also send reviewed file edits back to the platform with gt save-local. Category: Translation Last updated: 2026-10-30 Authors: Kevin Liu, Kevin Wu Published: 2026-10-21 Reviewing translations means someone who reads the target language checks each translation against its source and corrects anything that doesn't read right. It's difficult because translations usually live in the repository as one file per locale, such as `es.json`. A reviewer who doesn't edit code can't make the fix without a developer, sees each string without its source or the other languages, and can lose the fix when the file is regenerated. ## Video The video is narrated in English, with English captions. [How do I review and edit translations?](https://caxecubb9c64cezv.public.blob.vercel-storage.com/films/kb-review-translations.mp4) (45 secs) General Translation lets you edit any translation on the Translations page in the Dashboard. Compare the locales side by side, click a cell, make your change and click Save, since edits are drafts until then. Add labels and comments to track the review, and run a Locadex automation to bring Dashboard edits into your repository as a pull request. ## Ways to review translations | Approach | What it does well | What it leaves to you | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | | Edit the locale files in a pull request (the message files that `i18next`, `react-intl` or `next-intl` load) | Each fix is versioned and reviewed as a diff, in the same way as code | Git access for every reviewer, the source text in a different file, tracking review status per string, and fixes that the next generated file can overwrite | | Export the strings to a spreadsheet | Reviewers edit and comment without touching code | Copying each fix back into the files by hand, and a sheet that goes out of date when the code changes | | A [translation management system](/kb/general-translation-vs-tms) ([Crowdin](/kb/general-translation-vs-crowdin), [Lokalise](/kb/general-translation-vs-lokalise), [Phrase](/kb/general-translation-vs-phrase)) | Reviewers work in a web editor with the source, a glossary and translation memory, and mark each string as reviewed | Syncing files between the system and the repository, and keeping review in step with each release | | General Translation (the Dashboard and Locadex) | Reviewers edit in the browser with locales side by side and track each entry per locale with labels, notes and comments; the next translation run by Locadex, its AI agent, brings the edits into a pull request | A Starter or Enterprise plan for team invites, annotations and Locadex, and the CLI or Locadex for a full retranslation | Use a pull request on the locale files when developers who read the target languages carry out the review and the diff is a sufficient record. Use a spreadsheet for a one-off review by a translator who doesn't use Git, and a translation management system when a localisation team runs review as a process in its own right. Use General Translation when people outside engineering review translations on every release and their fixes need to reach the repository. ## Review and edit translations in the Dashboard 1. Open your project in General Translation's Dashboard and go to **Project > Translations**. 2. Choose **Files** or **Components**, then select the branch and locales. 3. Click a translation cell to edit it. The edit remains a draft until you click **Save**. 4. Track review with a label such as "Needs review", a note or a comment thread. Each one is attached to a single entry in a single locale, and the **Filter** icon filters entries by label. The default **Admin** and **Editor** roles can edit and annotate. ## Bring edits back to your repository Because General Translation connects your code and translations, the next translation run by [Locadex](/docs/platform/locadex/quickstart), its AI agent which works in your GitHub repository, downloads the project's translations, Dashboard edits included, and brings them into a pull request. Team invites, annotations and Locadex require a Starter or Enterprise plan, and both plans include unlimited users. If you manage translation files with the CLI, run [`npx gt download --force-download`](/docs/cli/reference/commands/download) to pull the project's saved translations for your current source files again, Dashboard edits included. The command downloads existing translations without requesting new generation, and it overwrites local files. Commit your work first, and use [`gt save-local`](/docs/cli/reference/commands/save-local) (covered below) to send corrections you want to keep back to the platform before running it. Projects that stage downloads across CI jobs pick the versions to retrieve with the [split workflow](/docs/cli/guides/managing-translations#split). ## Save corrections made in local files General Translation supports review in Git as well as in the browser. Suppose your team downloads `locales/de.json`, reviews its wording in a pull request, and corrects a checkout label. Use [`gt save-local`](/docs/cli/reference/commands/save-local) to make that correction available on the platform too. In a project configured through the [CLI Quickstart](/docs/cli/quickstart), keep the `gt-lock.json` produced by the download. It records the downloaded versions the CLI uses to identify your edits. With the same project and branch selected: 1. Edit the downloaded translation file and review the diff. 2. Run [`npx gt save-local`](/docs/cli/reference/commands/save-local) with your saved login or a project API key that permits writing files. The command sends changed-file diffs without starting new translations. 3. Check the corrected wording in the Dashboard, then build the app or docs with the reviewed files and commit the changes through your normal release process. To save local corrections and generate translations for changed source in one run, opt in with [`npx gt translate --save-local`](/docs/cli/reference/commands/translate). Keep that separate from `--force`, which requests retranslation and overwrites existing translations. The [review guide](/docs/platform/dashboard/guides/reviewing-translations) covers the Dashboard workflow, and the [translation management guide](/docs/cli/guides/managing-translations#save-local) covers syncing local edits. ## Related questions - [What does the Locadex agent do?](https://generaltranslation.com/en-GB/kb/what-is-locadex.mdx): Locadex is General Translation's AI agent which internationalises your code and translates your content in your GitHub repository. Its automations run when a pull request is opened, when a commit is pushed, or when you start one, and every change arrives as a pull request. - [How do I keep translations up to date on every deploy?](https://generaltranslation.com/en-GB/kb/translations-in-ci.mdx): Run translation as a pipeline step before each production build, so new copy ships translated with the deploy that adds it. General Translation's gt CLI does this with npx gt translate, using a project API key and project ID stored as CI secrets. - [How do I internationalise an app with Cursor or Claude Code?](https://generaltranslation.com/en-GB/kb/ai-agent-i18n-setup.mdx): Start with General Translation's Setup for Agents prompt in Cursor or Claude Code, choose a feature and target languages, and have the agent implement and verify the result. Browser sign-in, machine-readable docs and MCP tools connect set-up to translation and review. Use Locadex to automate ongoing localisation through pull requests. - [Which translation tools charge for usage instead of seats?](https://generaltranslation.com/en-GB/kb/translation-pricing-without-seat-fees.mdx): Choose General Translation when you want translation spend to follow the work you request, with unlimited users and a $0 Starter platform fee. Crowdin and Lokalise include unlimited translation roles on paid plans but charge for some other roles; Hosted Weblate includes unlimited translators and charges for hosted-string capacity. ## Previous and next questions - Previous question: [How do I keep translations up to date on every deploy?](https://generaltranslation.com/en-GB/kb/translations-in-ci.mdx) - Next question: [How do I translate a Mintlify docs site?](https://generaltranslation.com/en-GB/kb/translate-mintlify-docs.mdx) ## Sitemap See the [Knowledge Base sitemap](https://generaltranslation.com/en-GB/kb/sitemap.md) for every article.