Skip to main content
Use the Content Editor to inspect source and target text, correct translations, and approve content for a locale. Generation and approval are separate steps: review completed job output before delivering it.

​
Open the Content Editor

  1. Open a project from Projects.
  2. Open Files.
  3. Select a source file and a target locale.
Native projects: upload with Add files, then Upload, if the list is empty. Provider-backed projects browse files from the connected TMS. If the project supports it, Content Editor in the project sidebar opens an all-files queue instead of one file at a time.

​
Workspace tabs

The Content Editor has three tabs: When the file has a website preview, you also get Desktop preview, Tablet preview, and Mobile preview. Use Highlight translatable, then click a string to load it in Selected string. Native .html and .htm files keep the key queue (html.body.h1, html.p.strong) and also offer File view of the stored page. That view is a preview and code pane, not the markdown document editor. If the queue is empty, check the ingest status on the file: extracting and failed ingest are shown instead of a silent empty list. Re-upload an older HTML file if keys still look like html.143b270a32602d41. See Translate HTML.

​
Edit a segment

Select a row in Queue or click a string in the preview. The Content Editor loads source, target, and suggestions from translation memory, glossary, and AI. On a native project, Approve saves the current target text. On a TMS-backed project, Save to provider (or Approve) writes the target back to the provider. When a Braze or Intercom automation is attached to the project, the editor header can show Ingest next to Push to Braze or Push to Intercom. Ingest queues the same import as Automations Run now. Push writes copies or drafts to the connected service. Those actions do not publish. Push to Braze writes locale-suffixed email-template copies or campaign/Canvas translation maps, depending on the automation that owns the open file. Translators can prepare drafts; approval requires a reviewer, localization manager, or administrator with project access. See Roles and permissions. Format checks on the segment include Placeholders & ICU and Length. Fix those before you approve. Unreal Engine tags in gettext .po files appear as chips such as UE#0; keep them and translate the words around them. See Unreal Engine rich text in gettext PO.

​
Filter the queue

Use Filter queue and Search key, source, or translation… to narrow the list. Common filters:
  • All strings
  • Untranslated
  • Needs review
  • Approved
  • Has issues
  • Skipped
  • Hidden
  • Not hidden (native and Crowdin projects only)
  • Unsaved translations
Provider-specific filters such as QA issues and Machine translations appear when the connected TMS supports them. Load more continues the infinite-scroll list.

​
Download filtered view

Use Download on the queue toolbar (download icon next to Filter queue) to export the segments you see after filters and search—not the whole project file.
  1. Set Filter queue and Search key, source, or translation… the way you want the export scoped.
  2. Open Download and pick a format:
Each row includes the segment key, source text, target text (empty when untranslated), locales, and source file path when the queue spans multiple files. Exports include up to 5,000 matching segments. If more segments match your filters, the download contains the first 5,000 in queue order; narrow filters or search to export a smaller slice. If nothing matches the current filters, download fails with a message that no segments match. For complete target files, use the project’s Download translations action. See Download translated files to choose the correct export.

​
Board

Open Board in the project or workspace sidebar when a segment needs a tracker item instead of an in-line comment. Filter the queue with Has issues to find those strings. Include the file, key, locale, and decision needed in the issue. See Resolve translation issues. Issue writes require a role that can write translations back to the project.

​
Merge identical strings

Open View → Show strings and choose Merge identical strings to collapse exact source-text duplicates into one row. Translate that row once and every unlocked copy in the current file scope updates. Rows whose copies already disagree show Different translations. Project Settings → Translation & Content Editor behavior → Automatically merge identical strings sets the default for the project. See Merge strings for when to use it, how to switch views, and how Apply to all works.

​
Next

Download translated files after review, or prepare a review handoff for another teammate. See translation quality troubleshooting if checks or suggestions do not match your expectations.