This article explains how the editor works in Lokalise Vantage and how to use it to review, update, and approve translations.

The editor is the main workspace for translation and review in Vantage. It shows your source content, translated segments, project progress, and review tools in one place.

After you create a Vantage project and start translation, you are automatically redirected to the editor. You can also return to it later by opening the Vantage project and selecting the Editor tab.

The editor is where you can:

The content management side panel on the left includes two tabs:

The editor is split into three main parts:

Each row in the editor represents a segment, similar to translation keys in Lokalise Expert. The source text is shown in the center of the editor, while the target translation for the selected language is shown on the right. The left-side panel is used for content navigation and translation assets.

You can edit translated content directly in the Target column. This allows you to:

While editing, you can also use the Asset panel to check translation memory matches and glossary terms for the selected segment, then insert or apply them where useful.

The source text is shown for reference, but it cannot be edited directly in the editor.

Each translated segment includes an approve action in the Target column. Approving a segment marks it as reviewed and accepted.

As segments are reviewed and approved:

You can approve multiple segments at once. To select all currently visible segments, click the checkbox in the top toolbar:

Alternatively, open the dropdown next to the checkbox to select all segments, all approved segments, or all unapproved segments. You can also clear the current selection from the same dropdown:

Once multiple segments are selected, the bulk action controls appear at the bottom of the editor:

From there, you can:

Each segment includes a menu with additional actions that help you quickly adjust translations or manage edits.

Available actions include:

If a segment appears multiple times in your project, you don’t need to update each instance manually.

After you approve a segment that has identical duplicates, a hint will appear below it indicating that matching segments exist elsewhere in the project. Click Review segments to open the Identical translations dialog.

In this dialog, you can:

Vantage organizes translatable content into content units and segments. A content unit is a logical piece of the original content. For example:

Vantage can split a content unit into multiple segments to make translation and translation memory matching more efficient. For example, one paragraph may appear as a single content unit containing several sentence-level segments.

In the editor, segments that belong to the same content unit are grouped together. This helps you see which pieces of translated text belong to the same source field or document element.

Some checks and limits apply to the entire content unit rather than to an individual segment. For example, an inherited character limit is calculated using the combined translation of all segments within the content unit.

Vantage uses QA checks to help identify translation problems while you work in the editor.

There are two types of checks:

Issues found by both types of checks are shown directly in the editor, but they behave differently.

Rule-based checks run automatically as you edit a translation. You do not need to start them manually.

Vantage currently checks for:

Tag, placeholder, and double-space checks apply to individual segments.

Character limits work differently: they apply to the entire content unit. If a content unit contains several segments, Vantage combines their translated character counts when checking the limit.

Rule-based warnings remain active until the underlying problem is resolved. Approving a translation does not dismiss them. Currently, rule-based QA checks cannot be disabled, and their severity levels cannot be changed manually.

AI checks use Pro AI to identify language and translation quality issues that are not covered by the rule-based checks.

For content translated by Pro AI, these checks run automatically as part of the translation process. However, a reviewer may introduce new issues while editing a translation. For example, a manual change can introduce a typo, change the meaning, or make the translation less natural.

To check the latest version of a translation, click Run AI checks.

Vantage analyzes the translation again and displays any detected issues in the editor. AI checks can identify problems such as:

AI checks do not produce a numeric quality score in Vantage. Instead, Vantage shows the individual issues it detects.

You can run AI checks again whenever you want to review the current translation.

This is especially useful after:

After making changes, run the checks again to see whether the detected issues have been resolved or whether new ones remain. AI checks may take some time to complete. If the check cannot be completed, Vantage displays an error and you can try again.

When AI checks find issues, click Fix issues next to the detected issues.

Vantage analyzes the translation and generates one or more revised versions that attempt to fix the problems it found. Review the suggested translations and choose the version you want to use. Insert the suggestion into the segment, then review it before approving the translation.

If needed, you can run AI checks again after inserting the suggestion to verify the updated translation.

AI-generated fixes may not resolve every issue correctly, so always review the result before approving it.

Approving a translation dismisses AI-detected issues for that translation. Vantage assumes that the reviewer has evaluated the content and chosen to accept it.

Rule-based warnings are not dismissed by approval. Problems such as missing tags, incorrect placeholders, double spaces, or character limit violations can still remain visible until they are fixed.

This distinction helps prevent structural problems from being ignored while still allowing reviewers to make the final decision about language-quality issues.

Vantage displays formatting tags as small numbered chips inside the segment. Tags can represent formatting or structure from the source content, such as bold text, links, or nested formatting.

Because word order may change between languages, you can move tags to the correct position in the translation by dragging and dropping them.

Nested tags are shown as separate numbered chips so you can identify matching opening and closing tags and place them correctly.

Vantage automatically checks whether required tags are present in the translation.

If a tag is missing or placed incorrectly, a rule-based QA check appears below the segment. For example, you may see:

You can fix the issue in either of these ways:

When using /, Vantage suggests available tags in order, which can help when working with multiple or nested tags.

Tag checks are rule-based checks and run automatically as you edit translations. Unlike AI checks, they do not need to be started manually.

Some content imported through integrations can include a character limit defined in the source system. Vantage inherits this limit and shows it in the editor.

Character limits cannot currently be added or changed manually in Vantage. They are available only when they are provided by a supported integration.

Character limits apply to the entire content unit, not to an individual segment. If a content unit contains multiple segments, Vantage combines the character count of their translations when checking the limit.

For example, if a content unit has a limit of 200 characters and contains two translated segments:

the total character count for the content unit is 185 characters.

Editing either segment updates the character count for the entire content unit. Character limits are checked separately for each target language. This means one language can exceed the limit while another remains within it.

The editor shows the current character count while you translate. As the translation approaches the limit, the character count is highlighted as a warning. If the combined translation exceeds the limit, Vantage:

Character limits in Vantage are soft limits. Exceeding a limit does not prevent you from saving or approving a translation, but the issue remains visible so it can be resolved later.

You can also use issue filters to find content that exceeds its character limit.

When a translation exceeds the character limit, Vantage can suggest shorter versions of the translated text. Shortening works at the segment level, even though the character limit applies to the entire content unit.

For a content unit containing multiple segments, you can shorten one segment and see how this changes the total character count. If the content unit is still over the limit, you can shorten another segment until the combined translation fits.

Suggested shortened versions show how many characters they reduce. Review the suggestion before inserting it to make sure the meaning and required terminology are preserved.

If translated content still exceeds an inherited character limit when you send it back through an integration, Vantage warns you before export. Depending on the destination system and field configuration, content that exceeds the limit may be truncated or fail to export correctly.

You can filter for affected content units and shorten their translations before exporting.

Use the Files panel in the editor to manage project files without leaving the translation workspace.

From the panel, you can:

For detailed instructions on uploading, downloading, and managing files, see Lokalise Vantage: Files.

The Assets panel gives you access to translation memory and glossary suggestions directly in the editor. You can use it to reuse existing translations, check approved terminology, and search translation assets without leaving the segment you are reviewing.

When you select a segment, the panel shows assets relevant to that segment:

You can also use the Assets panel as a search tool. Search is workspace-scoped, which means it looks through the translation memories and glossary shared across your workspace, not only the current project.

When a segment is selected, the Assets panel shows fuzzy TM matches that may help you reuse previous translations. Each match includes a match percentage, source and target text, and metadata such as who added or updated the translation, when it was added or updated, and which translation memory storage the match comes from.

To use a TM match:

For fuzzy matches below 100%, Vantage does not simply copy and paste the TM entry into the segment. Instead, it uses ProAI to retranslate the segment with the selected TM entry as the main context. This helps preserve required tags, placeholders, and code-like elements.

Always review the result before approving the segment.

The Assets panel also shows glossary terms relevant to the selected segment. Use these suggestions to keep product names, brand terms, campaign wording, and other approved terminology consistent.

You can:

Glossary term filters apply to the target language and combine with other active filters.

You can search translation memory and glossary entries directly from the Asset panel.

Search works across the workspace assets shared with your workspace. This is useful when you want to check how a phrase was translated before, even if it does not appear as a direct suggestion for the current segment.

Search behavior depends on whether a segment is selected:

You can also insert glossary terms directly while editing a translation.

Type / in a segment to open a term picker. The suggested terms are matched to the current segment’s languages. Keep typing to narrow the list, then select the term you want to insert.

To exit the picker and leave your text as-is, type a double space.

You can view previous versions of a translation directly from the editor. To open the history for a segment:

The history panel shows previous translation versions for that segment. This helps you compare the current translation with earlier versions without leaving the editor.

For each previous version, you can:

Use translation history when you want to check how a translation changed during review, recover an earlier version, or compare edits before approving a segment.

For supported file formats, you can preview translated content directly in the Vantage editor.

The preview helps you review translations in context, check how translated content fits into the surrounding document, and quickly move between the preview and individual segments in the editor.

Vantage supports two preview modes:

The available preview modes depend on the file format.

You can select the preview language from the controls at the top of the preview. For formats that support both modes, you can also switch between Interactive and Static preview.

Click the close icon to hide the preview.

Vantage remembers your preview settings, so when you return to the editor, the preview opens with the previously selected configuration.

Interactive preview is designed for reviewing translations in context and navigating between the preview and the editor.

It is available for:

For formats such as HTML and MD, only interactive preview is available. These formats do not provide a separate static preview.

Changes to translations are reflected in the interactive preview automatically.

Hover over translated content to highlight the corresponding segment.

The highlight color indicates its approval status:

When you hover over a segment, a small action menu appears. You can use it to:

This makes it possible to review content visually and jump directly to the translation when changes are needed.

Click Compare mode to display two language versions side by side. You can choose which language appears in each preview, allowing you to:

Scrolling and segment highlighting are synchronized between the two previews. You can interact with segments in either preview using the same preview actions, such as copying text, opening translation history, or locating the segment in the editor. You can also switch to a full-screen view.

Vantage remembers the selected previews and their arrangement during the current session.

For DOCX files, page headers and footers are not shown in the interactive preview.

The translatable content is not affected, but text placed in Word headers or footers may be missing from the interactive preview.

If headers, footers, or the exact document layout are important, switch to Static preview.

Static preview provides a more faithful rendering of the original document.

It is available for:

Use static preview when:

Static preview preserves document layout and structure more accurately than the editor view and includes page headers and footers in DOCX files. However, it uses a default system font instead of the original document fonts.

Unlike interactive preview, static preview does not update immediately when translations change. If the preview becomes outdated, a banner appears prompting you to regenerate it.

The top area of the editor provides project-level tools and status information. From there, you can monitor translation and review progress across the project. Click the Approved segments dropdown to open the Statistics panel.

The Statistics dropdown shows progress for each target language of the whole project, including:

The Filters menu helps you narrow down the segment list.

You can filter segments by criteria such as:

For example, you can show only segments that are:

This is especially useful when reviewing large documents or focusing on assigned work.

You can use the search field at the top of the Editor to find specific text segments.

Search helps you quickly locate:

This is useful when working with longer documents or verifying repeated terms.

You can add new target languages from the project settings:

Once a new language is added, Vantage automatically starts translating the project content into that language.

If the project uses the AI + human review workflow, Vantage also creates a separate review task for the newly added language.

Target languages can be added, but they cannot be removed once added.