InDesign Master Pages for Multilingual Layouts: A Practical Guide

Master pages are where your InDesign document's layout logic lives: headers and footers, page numbers, guides, repeated graphical elements, text frame geometry. But they are also where many designers break their multilingual projects before translation even starts. You build a beautiful master page for English, send the document for translation, and the translated file comes back with running headers that no longer fit, page numbers positioned for left-to-right text but not right-to-left, and text frames sized for 8-word English headlines that buckle under 12-word German equivalents. Master pages designed for one language don't scale.

The good news is that this is entirely preventable. Getting InDesign master pages for multilingual layouts right is the difference between a file that adapts cleanly to any language and one that needs hours of rework every time you translate.

What Master Pages Store—and What They Don't

When you export an InDesign document to IDML via File → Export → InDesign Markup (IDML) — see our complete IDML export guide for the step-by-step workflow — the master page structure is preserved in full. Guides, frames, anchored objects, and auto page-number markers all travel through IDML unchanged. But there is a critical distinction that many designers miss: the content of text frames on master pages does not behave the same as the content of text frames on document pages.

Master page text frames—running headers, section labels, footer copy—are stored separately from your main story content. When you translate an IDML file, a translation service processes the story XML in the Stories/ subfolder. Text from document pages gets swapped out for translated text. But master page content often does not. If you have a footer that says "Page 1" or a running header that repeats your section name, that text stays on the master page in the original language unless you explicitly place it elsewhere or handle it in a separate translation pass.

This is not a limitation of IDML; it is actually how InDesign is designed. Master pages define the static blueprint. Document pages override and customize that blueprint. The XML structure reflects this separation.

What this means for your workflow: any text on a master page that needs to be translated must either be placed on individual document pages as an override, handled in a separate translation pass, or moved to a shared story that translation services can access. If you have running headers that are genuinely language-specific—think section titles in Arabic that need to run right-to-left—you may need language-specific master pages.

When Master-Page Text Needs Translation

Running headers, section labels, footer labels, and repeated disclaimers on master pages all need translation. But before you redesign your master pages, ask whether that text should live there at all.

The most robust approach: keep text that changes per language off master pages and instead place it on individual document pages. A section header like "Chapter 2" or a date label can sit on the first page of that section as a regular text frame. When you export to IDML and send it for translation, that text sits in the story XML where translation services expect to find it. When the translated IDML comes back, the text is already swapped in, positioned, and styled—no post-translation manual work needed.

For static labels that must appear on every page—footer copyright text, chapter names, repeated notices—you have two options:

1. Override the master page text on each document page. Select the master page text frame, hold Cmd+Shift (Mac) or Ctrl+Shift (Windows), and click it on the document page to override it. Edit the overridden text on the document page itself. This text becomes part of the story XML and translates normally. The trade-off: you have to override every page, which is tedious for long documents.

2. Create language-specific master pages. If you are building a document that will exist in multiple language versions, you can create separate master pages for each language—one with English headers, one with German headers, one with Spanish. Apply the appropriate master page to each language version of your document. This is cleaner for large, complex documents but requires more upfront planning.

The cleanest approach for most projects: use flexible, styled text frames on document pages for anything that needs translation, and reserve master pages for truly static elements—guides, graphical borders, page number markers.

Building Master Pages for Text Expansion

Even when you keep most text off master pages, you still need master pages that accommodate text expansion. Paragraph styles play a huge role here—they set frame geometry, insets, and leading that survive translation.

Read our detailed guide on handling text expansion in InDesign for the full breakdown, but the key principle for master pages is this: any text frame you anchor to a master page should have room to grow. If you have a narrow header area with a text frame that is exactly the height of English body text at 12pt with 120% leading, that frame will choke on German text at the same point size. German typically expands 25–35% by character count, and with longer words comes less efficient word breaking and more space needed.

On master pages, this means:

• Use auto-sizing frames cautiously. Fixed-height frames with auto-fit shrink the type to fit, which can make body text unreadably small. Instead, allow the frame height to be flexible or, if you must fix it, build in 20–30% extra space.
• Set generous insets. Insets (padding inside text frames) help prevent text from jamming against the frame edges. Set them based on the longest language you expect: 10–15mm insets on either side give breathing room for expanded text.
• Use paragraph styles, not direct formatting. Master page text that uses paragraph styles carries those style definitions through IDML. When you apply the same paragraph style in translated IDML, the frame attributes and spacing come along. Direct formatting—manual font, size, or leading changes—can break under translation.

The practical upshot: a master page designed with flexible, style-driven text frames adapts better to text expansion than one that relies on fixed dimensions and tight spacing.

Language-Specific Master Pages

Some languages require dedicated master page variations. Right-to-left languages like Arabic and Hebrew need reversed page geometry—text flows right to left, running headers appear on opposite sides, page numbers move. CJK languages (Chinese, Japanese, Korean) often use vertical text flow and different grid systems. If your document will appear in these languages, creating separate master pages per language family is cleaner than trying to override everything on document pages.

A naming convention helps: name master pages by language or script direction. Master - English (LTR) and Master - Arabic (RTL). When you prepare language-specific versions of your document for translation, apply the correct master page to each version before export. The translator or translation service doesn't need to touch master pages—they work with the story XML on document pages.

Document your master page choices in a brief style guide or README so anyone working with the translated IDML knows which master pages apply to which language version. This is especially important if you have a hand-off to designers in other regions or if multiple people are managing translated versions.

Page Numbering and Running Headers Across Languages

Auto page-number markers in InDesign are robust across translation. When you insert a page number marker into a text frame (via Text → Insert Special Character → Page Number), InDesign stores it as a special XML node in IDML. When the file is translated and reopened, that marker continues to point to the correct page number—no resetting needed.

Running headers are more fragile if they include language-specific labels. If a header reads "Chapter 3" on the document page (not the master page), it translates fine. But if the header reads "Chapter 3 — Introduction to IDML," and "Introduction to IDML" is the story title that translates to German as "Einführung in IDML," you need to ensure the story title text is in the story XML where translation services can find it, not hardcoded into the master page.

Section markers (via Type → Insert Special Character → Markers → Section Name) point to section prefix text set in the Section Options dialog. If you change section names when you create language versions of your document, update the section options before export. These settings are preserved in IDML and your translated file will pull the correct section markers.

Pre-Translation Checklist for Master Pages

Before you export to IDML and hand off for translation:

1. Audit text on master pages. Make a list of every text frame on every master page. Note which text needs translation and which is static.
2. Move or override translatable text. Any text that changes per language should either be on document pages as a regular text frame, or overridden on the first page it appears so translators can find it in the story XML.
3. Test frame flexibility. With sample text in your longest expected language (German, Finnish, or Polish for European projects), check that text frames on master pages don't overflow.
4. Verify paragraph style assignments. Paragraph styles used on master pages should match the same named styles used in your document body. Check the Paragraph Styles panel (F11) and confirm no master page text uses [Basic Paragraph] or [No Paragraph Style].
5. Set up language-specific masters if needed. If you are translating into RTL or CJK, create the alternate master pages now and document which applies to which language.
6. Check page number and section markers. Verify that auto page numbers are in text frames (not hardcoded), and that section markers point to section prefix text.
7. Document your master page structure. Add a note to the document or create a brief reference sheet: "Master — English (LTR)" for English, notes on overrides, and guidance for whoever rebuilds the layout after translation.

Bridging Master Pages to Translation

When master pages are clean, flexible, and properly structured, the rest of the translation workflow becomes much simpler. Export your document to IDML via File → Export → InDesign Markup (IDML), and send the IDML file for translation. A service like TranslateInDesign processes the story XML, preserves your master page structure and paragraph styles, and returns a translated IDML file that opens in InDesign with all layout intact. No manual frame resizing, no font resets, no hours spent repositioning text.

The key is that your master pages did their job: they provided the blueprint, they adapted to text expansion, and they didn't get in the way. That is worth the upfront planning.