You've finished the design. The layout looks great, the client is happy, and now it's time to translate it into three more languages. You zip up the InDesign file and send it off.
Two days later, the translator or agency sends back a file that's missing styles, has broken text frames, and looks nothing like what you designed.
Sound familiar?
Most translation problems start before the translator ever opens the file. Preparing your InDesign files correctly is the single highest-leverage thing you can do to get clean, layout-preserving translations back — fast.
This checklist covers every step a designer needs to take before sending files for translation.
Why File Prep Matters
Translation tools and agencies work best when your InDesign document is clean and structured. Unlinked images, overset text, inconsistent paragraph styles, and non-IDML handoffs are the top causes of translation rework. A 30-minute prep session can save you days of back-and-forth.
The checklist below follows the sequence you'd work through in InDesign, from pre-flight to final handoff.
The Prepare InDesign Files for Translation Checklist
1. Export to IDML — Not INDD
The most important step. Always send an .idml file, never the binary .indd.
Why it matters: IDML is an open XML format that translation tools and professional translators who work with InDesign can actually parse. INDD is a proprietary binary format that requires an identical version of InDesign to open, and most translation tools cannot extract text from it without structural loss.
How to export:
- Open your document in Adobe InDesign
- File > Save As
- Set format to InDesign Markup (IDML)
- Save alongside your source
.inddfile
If your client or agency asks you to "send the InDesign file," they almost certainly want the IDML — clarify upfront.
2. Resolve All Overset Text Before Handing Off
Run a preflight check and fix every overset (pink overflow) text frame before the file leaves your desk.
Why it matters: Translations are almost always longer than the source, especially from English to German, Portuguese, or Finnish. If your source file already has overflow, the translator has no way to know where the cutoff was — and the translated version will overflow even more.
How to check: Open the Preflight panel (Window > Output > Preflight) and filter for overset text errors. Alternatively, do a quick scan for pink plus-sign icons at the bottom-right of text frames.
Fix every instance before sending. If a frame is deliberately truncated (e.g., "read more" teaser), note this explicitly in your handoff brief.
3. Consolidate and Name Paragraph Styles
Translators and automated tools like TranslateInDesign preserve your paragraph styles through the IDML XML structure. But only named styles translate cleanly.
Common problems:
- Local overrides applied directly to text (not via styles) are fragile and often lost
- Dozens of
[Basic Paragraph]variations with no names create ambiguity - Styles with special characters in the name can break XML parsing in some tools
Best practice:
- All text should use a named paragraph style, not local formatting
- Names should be descriptive:
Body Copy,Headline H1,Caption,Pull Quote - Avoid names with slashes, ampersands, or angle brackets
4. Flatten or Package Linked Images
Before export, run File > Package to collect all linked images, fonts, and assets into one folder.
Why it matters: If your IDML references images via absolute paths that don't exist on the translator's machine, InDesign will show broken link warnings and the translator may modify or remove those frames to work around missing assets.
If you're using an automated tool like TranslateInDesign, images are preserved in the IDML structure — you don't need to send images at all. But for agency handoffs where a human will open the file, packaging ensures a clean experience.
5. Flag Non-Translatable Text
Not every text frame should be translated. Product codes, phone numbers, URLs, brand names, and legal registration marks usually stay in the source language.
How to handle it:
- Create a "No Translate" character style in your document (even if you never apply special formatting — it's a signal, not just styling)
- List all non-translatable strings in your handoff brief:
["SKU-4821", "+1-800-555-0100", "translateindesign.co"] - For automated tools, check if the platform supports
do-not-translatemarkup or exclusion lists
This prevents translators from guessing and saves you a review round.
6. Provide a Terminology Glossary
Consistent terminology is the difference between a professional translation and one that reads like a first draft. Build and send a two-column glossary with your source terms and the approved target-language equivalents.
Minimum entries to include:
- Your product and brand name
- Key feature names
- Industry-specific terms with specific meanings in your context
- Any terms the client has approved in previous projects
For ongoing work with the same language pair, this glossary compounds in value over time.
7. Write a Handoff Brief
Even if you're using an automated tool, a one-page brief eliminates ambiguity. Include:
- Source language and target language(s)
- Word count (export from InDesign via Utilities > Word Count for the full document)
- Document type (brochure, annual report, product sheet, packaging)
- Audience and tone (B2B technical, consumer-facing casual, formal regulatory)
- Non-translatable strings (see step 5)
- Glossary location (link or attached file)
- Text expansion expectations — if frames are tight, note that the translator should prioritize concise phrasing
- Deadline and delivery format (translated IDML back, or placed PDF for review?)
This takes 10 minutes to write and saves hours of back-and-forth.
8. Consider Text Expansion Budgets in Your Layout
This is a design-time concern, but worth flagging here: if you know a document will be translated, design with 20–35% extra vertical space in text frames for European languages, and plan for right-to-left layout variants (Arabic, Hebrew) at the architecture level.
For documents already designed without this budget, identify your tightest frames and note them in the brief. TranslateInDesign's overflow detection automatically flags translated segments that exceed original frame dimensions — so you know exactly which frames need design attention before you open the file.
Common Mistakes That Cause Rework
Sending INDD instead of IDML. The number one cause of "the translator said they couldn't open it." Always export IDML.
Not resolving overset text. Any overflow in the source is worse after translation. Fix it before handoff.
Relying on local formatting. If your body text is styled with direct formatting instead of paragraph styles, those overrides are fragile across the translation pipeline. Use styles for everything.
No glossary for multi-language projects. Translating the same document into four languages without a shared glossary produces four different versions of your brand terms.
Forgetting non-translatable strings. Phone numbers and URLs translated into German cause embarrassing errors that take time to find and fix.
The Fastest Way to Prepare and Translate InDesign Files
If you're translating frequently or working with multiple language pairs, TranslateInDesign handles the most time-consuming parts of this checklist automatically:
- Upload your IDML and get a clean translation back that preserves every paragraph style, character style, and layout instruction
- Overflow detection flags any translated segment that would break your frame dimensions — before you open InDesign
- Preview the first rows of translation free, so you can verify quality before committing
The checklist above still matters — especially steps 1, 2, 3, and 5 — but the translation step itself takes minutes instead of days.
Summary
Preparing InDesign files for translation is mostly about hygiene: clean styles, resolved overflow, IDML export, and a clear brief. Do these steps before every handoff and you'll rarely need a second round of corrections.
- Export IDML, not INDD
- Fix overset text before sending
- Use named paragraph styles throughout
- Package linked files for agency handoffs
- List non-translatable strings in your brief
- Provide a glossary for consistent terminology
- Write a one-page brief so nothing is left to guessing
Ready to translate your next InDesign project? Upload your IDML to TranslateInDesign and see the first preview free.