InDesign Tagged Text Explained: What Translators Need to Know

If a client or project manager sends you a .txt file full of angle-bracket codes like <ParaStyle:Body Text> and tells you to "translate the text but leave the tags alone," you've received InDesign tagged text. It's a format Adobe built into InDesign as a way to extract and reimport text while preserving formatting — and it works, right up until a translator accidentally edits the wrong thing and the reimport breaks.

This guide explains what InDesign tagged text actually is, how to work with it safely, where it fails for translation, and why most localization projects are better handled through IDML-based tools like TranslateInDesign.

What Is InDesign Tagged Text?

InDesign tagged text is a plain-text export format that encodes both content and formatting in a single .txt file using Adobe's proprietary tag syntax. When a designer exports a text frame as tagged text, InDesign writes every formatting instruction — paragraph styles, character styles, font overrides, tracking, kerning — as visible inline tags surrounding the actual copy.

A short excerpt looks like this:

<ASCII-WIN>
<Version:8><FeatureSet:InDesign-Roman>
<ParaStyle:Headline>Annual Report 2025
<ParaStyle:Body>This section summarizes results across all regions for the fiscal year.
<cFont:Minion Pro><cBold:1>Revenue grew 12% year-over-year.<cBold:0><cFont:>
<ParaStyle:Caption>Figure 1: Regional revenue breakdown

The <ParaStyle:> tags mark paragraph style changes. The <cFont:> and <cBold:> tags mark character-level overrides — in this case, bold applied to a specific sentence. Every piece of formatting in the original InDesign document becomes a readable instruction in the tagged text file.

The idea is that a translator can open this file, translate the human-readable strings between the tags, and leave all the < > sequences untouched. When the file is reimported into InDesign, the formatting reconstructs exactly.

How to Export Tagged Text from InDesign

Designers export tagged text on a per-frame basis:

1. In InDesign, select the text frame using the Selection tool.
2. Go to File → Export.
3. In the format dropdown, choose Adobe InDesign Tagged Text.
4. Click Save.
5. In the options dialog, choose Encoding (ASCII or Unicode) and Tag Form (Abbreviated or Verbose).

Verbose tag form is always safer for translation. Verbose writes <ParaStyle:Body Text> instead of <e9> or similar short codes. The full names are readable, which reduces the chance you'll accidentally edit part of a tag you didn't recognize as one.

Encoding matters. If the document contains any non-Latin characters — accented vowels, Cyrillic, Arabic, CJK — the designer must export with Unicode (UTF-16) encoding. Opening a UTF-16 file in a tool that saves as UTF-8 silently corrupts the file. The reimport will fail, and the error message won't tell you the encoding is wrong.

There's no batch export in InDesign's GUI. Each text frame exports separately. A 40-page brochure with 150 frames produces 150 tagged text files.

What Tagged Text Looks Like: A Closer Read

Here's what the tag syntax means in practice — annotated for a translator encountering it for the first time:

<ASCII-WIN>                          ← File encoding declaration. Never touch this line.
<Version:8>                          ← InDesign version. Never touch this line.
<FeatureSet:InDesign-Roman>          ← Language set. Never touch this line.
<ParaStyle:Body Text>Here is the    ← "Body Text" is the style name. Translate "Here is the"
first paragraph of copy.             ← Continue translating
<ParaStyle:Body Text>Second          ← New paragraph — same style
paragraph follows here.
<cFont:Helvetica Neue><cSize:10.0>  ← Character formatting starts. Do not translate anything
Small print disclaimer text.        ← Translate "Small print disclaimer text."
<cFont:><cSize:>                    ← Character formatting ends. Do not touch.

The rule is simple in theory: translate everything that isn't inside angle brackets. In practice, the tricky cases are:

• Tags that span line breaks. InDesign sometimes breaks long tag sequences across lines. Inserting a line break inside a tag corrupts it.
• Tags with style names that look like translatable text. <ParaStyle:Body Text> — "Body Text" is the style name in the InDesign document, not copy to translate. Translating it will break the reimport.
• Numeric values inside tags. <cSize:12.0000> — the 12.0000 is a point size, not a number to translate.
• Empty closing tags. <cFont:> with nothing after the colon is a closing tag, not a typo. Deleting it removes the formatting end marker.

Editing Tagged Text for Translation

Once you understand what to leave alone, the editing workflow is:

1. Open the .txt file in a plain text editor or a CAT tool with a tagged text filter.
2. Translate only the text that appears outside angle brackets.
3. Preserve all whitespace and line breaks exactly as written.
4. Save in the same encoding the file was exported with — do not let your tool auto-detect and convert encoding.

CAT tool support is inconsistent. Phrase (formerly Memsource) and some configurations of memoQ can handle InDesign tagged text files using a custom filter. SDL Trados requires a workaround. Many CAT tools will import the file as plain text and strip the tags entirely, which means the reimport reconstructs the document with no formatting. Before you start, confirm whether your specific CAT tool has a verified InDesign tagged text filter.

If you're translating the file manually in a text editor, use one that can open large files without auto-converting line endings or encoding. Notepad++ on Windows and BBEdit on Mac are common choices.

How to Reimport Tagged Text Back into InDesign

With the translated file ready, the designer reimports it:

1. In InDesign, click the frame that held the original text.
2. Go to File → Place (Cmd+D / Ctrl+D).
3. Select the translated tagged text file.
4. Check Show Import Options.
5. In the dialog, leave Remove Text Formatting unchecked — checking it strips all the tags and imports plain text.
6. Click OK.

If the reimport succeeds, the translated text appears in the frame with formatting intact. If InDesign reports an error, the file has a malformed tag. Common causes: a missing angle bracket, a space inserted inside a tag name, or an encoding mismatch between the file and its declared header.

The Problems with Tagged Text for Translation

The workflow above works for small, simple files with experienced translators. For anything else, tagged text creates problems that compound as the project scales:

Tag corruption is common and hard to catch. A translator who modifies a tag, even slightly, won't see an error until reimport. By that point, they may have translated 30 files and the same mistake appears in all of them.

No layout preview. Translators working with tagged text files have no way to see whether their translation fits the frame, whether text is overflowing, or whether a style looks correct in context. Layout feedback only comes at reimport, after the translation is done.

Per-frame file management doesn't scale. Fifty-frame document into three languages means 150 files to track, match, and deliver without mix-ups. Naming conventions help, but the overhead is real.

Non-technical translators find it error-prone. Even with clear instructions, translators who aren't familiar with markup formats will occasionally edit a tag. It's not carelessness — the format is genuinely confusing to someone who has never seen it before.

IDML: A More Reliable Alternative

For full-document translation — which is most InDesign localization work — IDML handles the same job without most of these risks. IDML is InDesign's XML-based interchange format. When you prepare InDesign files for translation, exporting to IDML gives you the entire document — all frames, all styles, all master pages — in a single structured archive.

An IDML-based tool extracts the translatable text from the XML automatically, presents it in a clean segment view (no tags visible), and rebuilds the formatted IDML after translation. Translators see clean source and target text. Styles and layout are never at risk from an accidental tag edit because translators never touch the XML directly.

TranslateInDesign works this way. You upload an IDML file — for more on the format, see what is IDML and why it matters for translation — and the tool extracts text, manages translation memory, and returns a fully formatted translated IDML ready to open in InDesign. No per-frame export, no encoding management, no tag briefing for translators.

If you need to translate InDesign files and want to understand the full workflow comparison between manual approaches and IDML tools, that guide covers it in detail.

When Tagged Text Makes Sense

Tagged text isn't always the wrong choice. It fits when:

• You're editing one or two text frames in-house, not handing off to an external translator
• The document is simple, with minimal character-level formatting overrides
• The person editing the file understands the tag syntax and has done it before
• You need a quick in-context edit without exporting the entire document

For everything else — multi-page documents, external translators, multiple target languages, recurring localization cycles — the overhead and error rate of tagged text make IDML-based translation the faster, safer path.

Try TranslateInDesign Free

If you've landed here because someone handed you tagged text files and you're looking for a better way: TranslateInDesign lets you upload an IDML file and get a clean, layout-safe translation without touching a single tag. The first rows of translation are free, so you can verify the output on your actual document before committing.

Export to IDML instead of tagged text, upload, and skip the tag-corruption debugging entirely.