InDesign TOC Translation for Multilingual Documents

A generated Table of Contents is one of the most useful things InDesign builds for you — and one of the first things that breaks when you translate the document. Page numbers shift, entry text gets overwritten, styles drift, and headings reflow. Done right, InDesign TOC translation keeps the TOC as a live, generated object in every target language so it regenerates natively instead of being rebuilt by hand. This guide covers why the TOC breaks after translation, how IDML preserves the structure, and the correct step-by-step workflow for a multilingual table of contents InDesign document.

Why the InDesign TOC Breaks After Translation

An InDesign TOC is not typed text. It is a generated object: InDesign scans the document for paragraphs tagged with specific paragraph styles (your "TOC entry" styles), collects their text and page numbers, and writes the result into a TOC story using TOC styles you defined. That generation step is what makes the TOC self-maintaining — and it is also why naive translation wrecks it.

Four things go wrong when a translator edits the TOC directly:

• Paragraph-style mapping is lost. The TOC entries only exist because source headings carry paragraph styles the TOC is configured to pick up. If a translator restyles headings or pastes translated text into the TOC story as plain text, the link between heading and entry is severed and the next "Update TOC" overwrites the translation.
• Generated text is mistaken for editable text. The TOC story is a generated artifact. Editing it directly is wasted work — the moment someone updates the TOC, InDesign regenerates from the headings and discards the manual edits.
• Page numbers reflow. Translated text almost always expands (German runs ~30% longer than English; RTL scripts can shift line counts). Layout reflows, page breaks move, and every page number in the TOC is now wrong until the TOC is regenerated against the new layout.
• TOC styles get overwritten. TOC styles (the entries under Layout → Table of Contents Styles) define which paragraph styles map to which TOC level. If those styles are renamed or the mapping is broken during translation, the TOC regenerates empty or incomplete.

The core mistake is treating the TOC as text to translate. It is not text — it is a rule. Translate the headings, keep the rule intact, and let InDesign regenerate the TOC in each language.

How IDML Preserves TOC Structure

IDML (InDesign Markup Language) is Adobe's open, XML-based export of an InDesign document, produced via File → Export → InDesign Markup (IDML) inside Adobe InDesign. We accept IDML only — INDD, the proprietary binary InDesign format, cannot be parsed. We return a translated IDML file, ready to re-open in InDesign.

IDML is what makes clean InDesign TOC styles translation possible, because it carries every part of the TOC system as structured XML:

• TOC styles are stored as document-level objects, so the rule "Heading 1 → TOC Level 1, Heading 2 → TOC Level 2" survives the round-trip.
• Paragraph styles are preserved by name and definition, so the headings the TOC scans for are still tagged correctly after translation.
• Story XML keeps generated text separate from source headings. Each story is its own Story_*.xml. The TOC story and the heading stories are distinct, so a translation tool can translate the heading stories, leave the TOC story alone, and let InDesign regenerate the TOC from the freshly translated headings.
• Page geometry and frame threading are preserved, so when translated text expands and the layout reflows, re-opening in InDesign and updating the TOC produces correct page numbers in the target language.

The result: you translate InDesign TOC by translating the sources the TOC is built from, not the TOC itself. Re-open the translated IDML in InDesign, run Layout → Update Table of Contents, and the TOC regenerates in the target language with correct entry text, correct styles, and correct page numbers. For the broader end-to-end workflow, see how to translate InDesign files.

Step-by-Step: Translate an InDesign TOC the Right Way

1. Set up TOC styles and paragraph styles first. Before exporting, confirm every heading the TOC should pick up uses a named paragraph style (e.g. Heading 1, Heading 2, Chapter Title), and that a TOC style under Layout → Table of Contents Styles maps each of those paragraph styles to a TOC level. Named styles are the contract the TOC relies on; ad-hoc local formatting breaks generation.
2. Generate the source TOC. Run Layout → Table of Contents and place it. This confirms the mapping works in the source document before you translate — if the source TOC is wrong, the translated one will be wrong too.
3. Export to IDML. In Adobe InDesign, File → Export → InDesign Markup (IDML). Do not export INDD; do not copy-paste the TOC into a text file.
4. Translate via TranslateInDesign. Upload the IDML at translateindesign.co and pick your target language(s). The platform translates the heading stories (and all other stories) while preserving paragraph-style tags and TOC style definitions — the structural contract the TOC needs.
5. Re-open the translated IDML in InDesign. The layout, frames, styles, and TOC style mappings come back intact; only the text has changed language.
6. Update the TOC. With the translated document open, run Layout → Update Table of Contents. InDesign scans the translated headings, regenerates the entry text in the target language, and pulls fresh page numbers from the reflowed layout. The TOC is now a correct, live, generated object in the target language.

This is the workflow that makes InDesign table of contents multilingual documents maintainable: one source, many target IDMLs, each regenerated locally. For the full localization playbook around it, see the InDesign localization guide.

Common TOC Translation Mistakes

• Editing TOC text directly. The TOC story is generated. Any text typed into it is discarded on the next update. Translate the headings, then regenerate.
• Unlinking styles. Removing or renaming the paragraph styles the TOC is mapped to breaks generation. Keep style names stable across source and translated documents.
• Ignoring text expansion. Translated copy is longer; layouts reflow; page numbers change. If you translate the TOC text but never update the TOC after reflow, every page number is stale.
• Forgetting to update after layout reflows. Even with a perfect IDML round-trip, the TOC must be regenerated after any layout change in the translated document so page numbers match the new pagination.
• Exporting the wrong format. INDD cannot be parsed; a PDF or DOCX export loses the TOC styles entirely. IDML is the only export that carries the TOC system as structured data.

Translate the TOC Without Rebuilding It

The pattern is the same every time: set up named paragraph styles and a TOC style in the source, export IDML, translate the heading stories through TranslateInDesign, re-open in InDesign, and update the TOC. The result is a generated, live, multilingual table of contents — correct entry text, correct styles, correct page numbers — in each target language, with no manual TOC rebuild.

Manually re-laying out a TOC per language takes hours and breaks on the next content change. Running the same source IDML through TranslateInDesign and regenerating the TOC in InDesign takes about 4 minutes per language.

Upload your IDML file — get a translated IDML back with TOC styles intact, ready to regenerate in InDesign.