Multilingual InDesign Master Pages: Layout That Survives IDML
Most designers set up multilingual InDesign master pages the same way they set up a single-language master: one master per section, running headers hard-coded in English, page-number frames sized for Latin digits, primary text frames laid out for left-to-right reading. Then they translate the IDML, re-open the file, and discover the translated running headers no longer fit, the German footer wraps to two lines, and the Arabic version reads right-to-left on a layout that was built left-to-right. The master page survived the IDML round-trip — its geometry, guides, and frames came back intact — but the content assumptions baked into it did not. This article explains what an IDML translation actually preserves on a master page, what it quietly breaks, and the structural patterns that make a master page scale across languages instead of failing in each one.
For the broader picture of why master pages matter in multilingual work, see our earlier guide to InDesign master pages for multilingual layouts. This piece focuses specifically on the IDML round-trip and the structural decisions that keep a master page reusable across every language variant.
What the IDML Round-Trip Preserves on a Master Page
When you export an InDesign document to IDML via File → Export → InDesign Markup (IDML), the master page definition is written to the Resources/MasterSpreads.xml file inside the IDML package. Everything structural about the master is preserved:
- Guides and margins — column guides, ruler guides, baseline grids, margin settings all round-trip exactly.
- Text frame geometry — the position, size, and shape of every master text frame comes back identical.
- Anchored and repeating objects — repeating headers, footers, and pinned graphics stay anchored where you placed them. See our guide to InDesign anchored objects and IDML translation for the edge cases.
- Auto page-number markers — the
A,B,Next Page/Previous Pagemarkers survive and re-render correctly in the translated file. - Named paragraph and character styles — style definitions applied to master text frames are preserved on the round-trip.
What does not survive cleanly is the text content sitting inside those master text frames, and any layout assumption that depends on a specific language's text length or direction.
Where Master Pages Break After IDML Translation
Three failure modes account for almost every broken multilingual master page. Each is preventable, but only if you design the master for translation from the start.
1. Running headers and footers don't get translated
This is the single most common master-page failure. Text that lives directly on a master page — a running header reading "Quarterly Report", a footer reading "Confidential" — is stored in the master's own story, separate from the document's main stories. Many translation workflows process the main Stories/ files and skip or mishandle the master spread stories. The translated IDML comes back with the body text swapped but the running header still in English.
The fix is structural: move translatable master-page text off the master. Place running headers, section labels, and footer copy on document pages using a primary text flow or a text variable that pulls from the section name, and let those document-page frames inherit the master's geometry. Text variables (Type → Text Variables → Define) that reference section markers or chapter titles get translated correctly because they resolve to document-level content, not master-level content.
2. Text expansion overflows master frames
Translated text is almost always longer than the source. German runs roughly 30% longer than English; Spanish and French 15–25% longer; many Asian languages run shorter per character but taller per line because of leading. A footer frame sized for an 8-word English line overflows the moment it holds a 12-word German line. On a document page you see overset text and fix it. On a master page, the overflow propagates to every page based on that master — one tight frame becomes a hundred broken pages.
The fix: size master text frames for the longest expected translation, not the source language. Give running headers and footers at least 30% horizontal headroom, or set the frame to auto-size with a defined growth direction (Text Frame Options → Auto-Size). Pair this with paragraph styles that allow justified or balanced line breaks. For the full treatment of text expansion behavior, see our guide to text expansion in multilingual InDesign.
3. RTL languages render on an LTR master
A master built for English has page numbers bottom-right, running headers top-left, and a primary text flow that starts left. Translate that document to Arabic or Hebrew and the body text flips right-to-left — but the master's frame positions, page-number placement, and header alignment stay left-to-right. The result is a document where the body reads one direction and the chrome reads the other.
The structural fix is to maintain a separate RTL master for each section, with frame positions mirrored, page numbers moved to the bottom-left, and the primary text flow set to start from the right. Use InDesign's Layout → Margins and Columns with Enable Layout Adjustment off, and apply the RTL master to the Arabic or Hebrew document variant via Window → Pages → Apply Master to Pages. Binding direction matters too: Arabic and Hebrew books bind right-to-left, so set the document binding accordingly in File → Document Setup. For the deeper RTL workflow, see our Arabic InDesign RTL translation guide.
A Pattern Set That Scales Across Languages
The three failures above all share a root cause: the master was designed for one language. A master page that scales across languages follows four rules.
- No translatable text on the master. Running headers, section names, and footer copy live on document pages or resolve through text variables. The master holds geometry, guides, and non-translatable chrome (logos, decorative rules) only.
- Frames sized for the longest target language. Every master text frame is built to the worst-case expansion ratio in your language set, with auto-size enabled where possible.
- One master per direction. LTR and RTL variants get separate masters with mirrored geometry. The document's binding direction matches the master's direction.
- Named styles, no local overrides. Every paragraph and character format on the master uses a named style. Local overrides are the second most common source of post-translation reflow bugs after master-level text — see our InDesign paragraph styles and translation guide for why.
Following these rules means a single source document can ship in English, German, French, Spanish, Arabic, and Hebrew without rebuilding the master for each variant. The IDML round-trip preserves the structure; the structure is what does the work.
The IDML-Only Constraint
One format note that affects master pages directly: we accept IDML only — never INDD, never PDF, never DOCX. INDD is Adobe's proprietary binary InDesign format; we cannot parse it, and no translation tool can reliably extract its master spread definitions. IDML is Adobe's open XML export of the same document, produced via File → Export → InDesign Markup (IDML) inside Adobe InDesign, and it is the only format that carries the master page structure as translatable XML. We return a translated IDML file, ready to re-open in InDesign with the master intact.
If you have been handed a .indd, open it in InDesign, apply the master-page patterns above, and export IDML before sending it for translation. For the format background, see IDML vs INDD for translation and our how to export IDML from InDesign walkthrough.
Conversion Bridge
Structuring multilingual InDesign master pages by hand — sizing frames for text expansion, splitting LTR and RTL masters, pulling running headers off the master, and re-exporting IDML for each language variant — is a 1–2 hour exercise per document, and it has to be redone every time the source layout changes. TranslateInDesign handles the IDML translation step in minutes: you export IDML, we return a translated IDML file with master-page geometry preserved and body stories swapped, ready to re-open in InDesign. The master-page prep above is still yours to do on the source, but the translation round-trip itself — the part that usually breaks the master — is what we get right. Try it with an IDML file.