InDesign Book Translation with IDML: Keep Chapters, Styles, and Page Numbers Intact

An InDesign Book (.indb) is not a single document — it is a container that coordinates several chapter documents (.indd) into one publication, synchronizing page numbers, styles, cross-references, and the table of contents across all of them. That structure is exactly what makes InDesign book translation IDML workflows tricky: you cannot export the whole book as one file, and the cross-chapter links that hold the book together have to survive the translation round-trip. The correct approach is to export each chapter as IDML individually, translate each one, then reassemble the book in InDesign and let it re-synchronize. Done that way, styles stay consistent, page numbers renumber automatically, and cross-references rebuild against the translated content.

What an InDesign Book Is — and Why You Translate It Chapter by Chapter

An InDesign Book (.indb) is a manifest, not a document. It lists a set of independent .indd chapter files and coordinates features that span all of them:

• Page numbering — sequential across chapters ("Continue from previous document").
• Style synchronization — one source chapter pushes paragraph, character, object, and table styles to every other chapter.
• Cross-references — a link in chapter 3 pointing to a heading in chapter 7, stored as a reference to a specific paragraph.
• Book-level TOC and index — generated by scanning all chapters at once.

The .indb itself contains none of your text, images, or layout — all of that lives inside the individual .indd chapter files. You translate the chapters, not the book.

There is no "export entire book as a single IDML" operation. IDML is a per-document format — each .indd chapter exports to its own .idml file. And we accept IDML only — never INDD (the proprietary binary InDesign format, which we cannot parse), never PDF, never DOCX. We return a translated IDML file, ready to re-open in InDesign. So the path for any multi-chapter InDesign translation is:

1. Open each chapter .indd in InDesign.
2. Export each to IDML via File → Export → InDesign Markup (IDML).
3. Translate each IDML.
4. Re-open each translated IDML in InDesign (producing a new .indd per chapter).
5. Create or re-link a book file that references the translated chapters.

For the export mechanics, see our how to export IDML from InDesign guide, and for why INDD cannot participate, our IDML vs INDD for translation comparison.

Keeping Cross-References Intact Across Chapters

Cross-references are the single most fragile part of InDesign cross-references translation in a book. A cross-reference is not a hyperlink — it is a live link from one paragraph to another, often in a different chapter, that carries a formatted reference string ("see Chapter 7, 'Typography' on page 142"). It survives only if the target paragraph is still findable after translation.

IDML stores cross-references as XML elements that reference target paragraphs by their internal IDs and by the paragraph style the target carries. Two things preserve them through the round-trip:

• Paragraph style names stay constant. IDML carries style definitions by name, so a heading tagged "Heading 1" in the source is still "Heading 1" in the translated file. The cross-reference's target lookup still resolves.
• Anchor markers and paragraph IDs are preserved in the XML. TranslateInDesign operates on the story XML without stripping or re-creating paragraph anchors, so the reference targets survive.

What breaks cross-references is not translation itself — it is manual editing that deletes or merges target paragraphs, or a workflow that renames styles mid-translation. Keep style names consistent across every chapter before you export, and the cross-references ride through. If your book uses a single source chapter for style synchronization (the normal setup), that consistency is already in place.

Page Numbering and the Book-Level Sequence

Book-level page numbering — where chapter 2 starts on page 47 because chapter 1 ended on page 46 — is a property of how the book coordinates its chapters, not something baked into each chapter's content. Each chapter's IDML preserves its own numbering setting ("Continue from previous document" or "Start at"), and the book re-applies the sequence when you reassemble.

This means translated InDesign book page numbering translation is largely automatic, provided you reassemble correctly:

• Export and translate each chapter. The translated IDML re-opens with the same numbering setting it had.
• Re-link the translated chapters into a book. Open the original .indb (or create a new one), replace each chapter reference with the translated .indd, and the book renumbers from chapter 1 onward.
• Let text expansion shift page counts. German runs roughly 30% longer than English; translated chapters will have different page counts. That is fine — the book recalculates the sequence, and cross-references and the TOC pick up the new page numbers when regenerated. See our text expansion in InDesign guide for the details.

The mistake to avoid: trying to hard-code page numbers into cross-reference text or the TOC. Those are generated values. Translate the content, reassemble, regenerate, and the numbers recompute.

Style Synchronization Across Chapters

A well-built InDesign book uses one chapter as the style source and synchronizes its paragraph, character, object, and table styles to every other chapter. That consistency is what makes InDesign book translation IDML round-trips clean — every chapter's IDML carries the same style names, so translated copy picks up the correct formatting automatically.

The workflow after translation:

1. Re-open all translated chapter IDML files in InDesign.
2. Assemble them into a book.
3. Designate one chapter as the style source (typically chapter 1).
4. Run "Synchronize Styles" from the Book panel to push the source styles to every chapter.

This catches any drift introduced during translation and guarantees that every chapter uses identical style definitions. For the broader style-preservation mechanics, see our InDesign paragraph styles translation guide.

TOC and Index: Regenerate, Do Not Translate

A book-level TOC and index are generated objects — InDesign scans every chapter for paragraphs carrying the configured styles and assembles the result. They are not text you translate directly.

After reassembly:

• Regenerate the TOC (Layout → Update Table of Contents) so it reflects translated headings and recomputed page numbers. For the full workflow, see our InDesign TOC translation guide.
• Regenerate the index (Index panel → Generate Index) so index entries pick up translated terms and new page numbers.

Editing the TOC or index text by hand is wasted work — the next regeneration overwrites it. Translate the source content, reassemble, and let InDesign rebuild these objects natively.

The Step-by-Step Book Translation Workflow

A clean translate InDesign book chapters workflow, end to end:

1. Prep the source book. Confirm every chapter uses consistent style names, cross-references are live (not retyped), and the TOC and index are generated. Run "Synchronize Styles" so all chapters share definitions. See our prepare InDesign files for translation checklist.
2. Export each chapter as IDML. Open each .indd, run File → Export → InDesign Markup (IDML), and save to a per-chapter folder. For batch export tips, see our batch translate InDesign files guide.
3. Translate each IDML. Upload each chapter's IDML and receive a translated IDML with styles, cross-references, and structure preserved.
4. Re-open each translated IDML in InDesign. Each produces a new .indd in the target language.
5. Reassemble the book. Open the original .indb (or create a new one), replace each chapter with the translated .indd, and save.
6. Synchronize styles from one source chapter across the book.
7. Regenerate the TOC and index so they reflect translated headings and recomputed page numbers.
8. Update cross-references (Type → Hyperlinks & Cross-References → Update Cross-References) so every inter-chapter link resolves against the translated targets.

Steps 6–8 are the book-level coordination that the .indb was built for. They run in minutes once the chapters are translated and reassembled.

How TranslateInDesign Handles Book Translation

TranslateInDesign accepts an IDML file, translates the stories inside it, and returns a translated IDML ready to re-open in Adobe InDesign (see Adobe InDesign). Because the platform operates on the story XML rather than extracting plain text, everything the book coordination relies on stays intact:

• Paragraph and character styles are preserved by name, so synchronized styles resolve correctly after reassembly.
• Cross-reference targets and anchor markers survive in the XML, so inter-chapter links rebuild on update.
• Page numbering settings carry through per chapter, so the book renumbers automatically.
• TOC and index generation rules are preserved, so both regenerate against translated content.

You export each chapter as IDML, upload them, pick your target language(s), and re-open the translated files. Then reassemble the book, sync styles, and regenerate the TOC and index — the coordination the .indb was designed for handles the rest.

If you are translating an InDesign book chapter by chapter and spending hours rebuilding cross-references and restyling each chapter by hand, export your chapters as IDML and upload them to translateindesign.co. The translation takes minutes; the reassembly takes minutes more; the book does the synchronization itself.