How to Use InDesign Tagged Text for Translation Workflows

InDesign tagged text translation is one of those workflows that looks straightforward until you're two hours in, hunting down a broken character style because a translator accidentally deleted a closing tag. This guide explains exactly how InDesign tagged text works, when it makes sense to use it for translation, and where it tends to break down — so you can decide whether it's the right approach for your project before you commit to it.

What Is InDesign Tagged Text?

InDesign tagged text is a plain-text export format that encodes both the text content and its formatting in a single .txt file using Adobe's own tag syntax. When you export a text frame as tagged text, you get something like this:

<ASCII-WIN>
<Version:8><FeatureSet:InDesign-Roman>
<ParaStyle:Headline>Quarterly Report 2025
<ParaStyle:Body>This section covers financial performance across all regions.
<cFont:Minion Pro><cSize:12.0000>Key findings are highlighted below.<cFont:><cSize:>

The <ParaStyle:> tags identify paragraph styles. The <cFont:> and <cSize:> tags mark character-level overrides. Every formatting change in the document — bold, italic, font switches, kerning overrides — becomes a visible tag in the output. When you reimport the file, InDesign reads those tags and reconstructs the formatting exactly.

This makes tagged text a self-contained format: a translator or editor who receives it can, in theory, edit the text content while leaving the tags untouched, and the reimport will reconstruct the formatted document correctly.

In practice, "leaving the tags untouched" is where most translation workflows using tagged text run into trouble.

When to Use Tagged Text vs IDML for Translation

Both tagged text and IDML can carry InDesign formatting through a translation round-trip. The choice comes down to scope and tooling.

Use tagged text when:

• You're translating one or two individual text frames, not an entire document
• You're editing content in-house and the person touching the file understands the tag syntax
• You're working with a very simple document where formatting overrides are minimal
• You need to hand a text frame off for quick edits without exporting the whole layout

Use IDML translation when:

• You're translating a full multi-page document
• You're working with a professional translator or translation agency
• The document has complex formatting — multiple master pages, tables, inline graphics, character styles applied frequently
• You need to track which frames changed across versions

The practical limit of tagged text is that it works at the story level, not the document level. Each text frame (or linked story chain) exports as a separate tagged text file. A 40-page brochure with 200 frames produces 200 separate files. Managing those files, keeping them matched to the right frames, and preventing translator-side tag corruption across all 200 files is a significant coordination overhead. IDML keeps the entire document in a single structured archive.

How to Export Tagged Text from InDesign

Exporting tagged text is straightforward, but encoding matters and is easy to get wrong.

Step 1 — Select the text frame

Click the Selection tool, then click the frame containing the text you want to export. If your text is threaded across multiple frames, clicking any frame in the chain selects the full story.

Step 2 — File → Export → Tagged Text

With the frame selected, go to File → Export. In the format dropdown, choose Adobe InDesign Tagged Text. Click Save.

Step 3 — Set encoding and tag form

InDesign prompts you to choose:

• Encoding: ASCII (for Latin-alphabet documents) or Unicode (UTF-16 — required for CJK, Arabic, or any non-Latin content)
• Tag Form: Abbreviated or Verbose. Verbose is safer for translation — it writes out full tag names like <ParaStyle:Body Text> instead of short codes, which makes the file readable and reduces the chance a translator corrupts a tag they didn't recognize

Click OK. InDesign writes a .txt file with the tagged content.

Repeat this for every text frame you need to translate. There's no bulk export to tagged text in InDesign; you export one story at a time.

Working with Tagged Text in a Translation Workflow

Once you have the tagged text files, you hand them to a translator. Here's where the workflow gets complicated.

CAT tool compatibility is limited. Most professional translation tools — SDL Trados, memoQ, Phrase — don't have a native filter for InDesign tagged text. Some have workarounds (memoQ has a tagged text filter, but it requires configuration), but many translators working in CAT tools will either strip the tags entirely or pass them through as untranslatable placeholders. Ask before assuming your translator's tool handles tagged text correctly.

Manual translation pitfalls. If a translator edits the .txt file directly in a text editor, they need to:

• Never delete or alter a tag (any character inside < > marks is part of a tag)
• Preserve whitespace and line breaks exactly as written
• Not change the file encoding — opening a UTF-16 file in a tool that saves as UTF-8 will cause the reimport to fail
• Leave the header lines (<ASCII-WIN> or <UNICODE-WIN>, <Version:>, <FeatureSet:>) completely untouched

None of these are obvious to a translator seeing the format for the first time. In practice, even experienced translators occasionally delete a closing tag or save in the wrong encoding. The error usually surfaces on reimport, not during translation, which means the problem is discovered late.

How to Re-Import Tagged Text After Translation

With the translated .txt files in hand, re-import them into InDesign to restore the layout.

Step 1 — Select the target frame

Click the frame where this story lives in the InDesign document. Make sure you've selected the right frame — importing tagged text into the wrong frame overwrites its content.

Step 2 — File → Place

Go to File → Place (or press Cmd+D). In the file browser, navigate to your translated tagged text file. Check Show Import Options.

Step 3 — Tagged Text Import Options

In the import options dialog, InDesign asks how to handle style conflicts:

• Use Typographic Quotes: usually leave checked
• Remove Text Formatting: leave unchecked — if you check this, InDesign strips all the tags and reimports raw text with no formatting
• Resolve Style Conflicts: InDesign compares the style names in the tagged text file against the document's existing styles. If styles match, the existing styles take precedence. If a tag references a style that doesn't exist in the document, InDesign creates a new style — which you likely don't want

Click OK. InDesign places the translated text into the selected frame with formatting intact.

If the reimport succeeds but formatting looks wrong, check whether any tags were modified during translation. Even a space inserted inside a tag (<ParaStyle: Body> instead of <ParaStyle:Body>) will cause InDesign to misread the tag.

Common InDesign Tagged Text Errors and How to Fix Them

"The text file has formatting problems." This is InDesign's catch-all import error. Most often it means a tag is malformed — a missing angle bracket, a modified tag name, or a character that got inserted mid-tag. Open the .txt file and search for any < > sequence that doesn't match the format <TagName:Value>. Pay particular attention to the opening header lines.

Text imports as plain text with no formatting. The file was saved in a different encoding than declared in the header, or the translator opened the file in a tool that converted the encoding on save. Ask the translator to resave with the correct encoding, or compare the file header to the actual encoding reported by a hex editor or advanced text editor.

Style conflicts create unwanted new styles. A translator changed a style name in a tag — for example, corrected a typo in the source document's style name or translated the style name itself. Before importing, compare the style names in the translated file against the InDesign document's Paragraph Styles panel and correct any mismatches.

Overset text after reimport. The translated text is longer than the source and overflows the frame. This is expected for most translation pairs — German and Finnish run roughly 30% longer than English; Spanish and French run 15–25% longer. Plan for it by leaving extra leading in the source frames, or handle it during the DTP review pass.

When to Skip Tagged Text Entirely

Tagged text works for targeted edits on small documents or individual frames. For any serious InDesign translation workflow — multi-page documents, multiple target languages, agency handoffs, repeating publication cycles — the overhead and error rate of tagged text make it the wrong tool.

If you need to translate InDesign documents at scale, IDML-based translation handles the same job at the document level: one file in, one translated file out, all styles and frames preserved automatically. There's no frame-by-frame export, no per-file encoding management, and no need to brief a translator on a tag syntax they've never seen before.

TranslateInDesign automates this for you. Upload your IDML file, select a target language, and download a fully translated IDML with all paragraph styles, character styles, and frame references intact — in a fraction of the time a manual tagged text round-trip requires. The first rows of translation are always free, so you can verify the output on your actual file before committing.

If you're doing a one-off two-frame edit, tagged text is fine. If you're translating a 30-page brochure in three languages, use the tool that was built for it.