Back to blog
|May 26, 2026

How to Prepare InDesign Files for a Translation Agency (Step-by-Step)

Learn how to prepare InDesign files for a translation agency the right way — export IDML, package fonts, and avoid the common mistakes that delay multilingual projects.

How to Prepare InDesign Files for a Translation Agency (Step-by-Step)

Sending an InDesign project to a translation agency seems straightforward — until the agency comes back asking for fonts, linked images, a proper IDML export, or an explanation of why your text frames are locked. A poorly prepared handoff wastes days on both sides and often introduces layout errors that are expensive to fix at the end of a project.

This guide walks you through exactly how to prepare InDesign files for a translation agency so the handoff is clean, the turnaround is faster, and the final multilingual layout needs minimal rework.


Why Preparation Matters Before Handing Off to Translators

Translation agencies don't work directly in .indd files. The .indd format is version-specific and platform-dependent — a file saved in InDesign 2024 may not open correctly in an older version. Agencies also need to extract the text into a format their translation tools (CAT tools like memoQ, SDL Trados, or Phrase) can parse.

The standard exchange format is IDML (InDesign Markup Language) — an XML-based, version-agnostic package that any modern CAT tool and any version of InDesign can open. Getting this right before you send is step one.


Step 1: Export IDML from InDesign

Open your .indd file in InDesign, then go to:

File → Export → InDesign Markup (IDML)

Name the file clearly — use the document name and the source language, for example: product-catalog-EN.idml. This makes it easy for the agency to track multiple language versions later.

If your document is book-length (multiple chapter files linked via InDesign's Book panel), export an IDML for each chapter separately. Agencies typically translate each IDML as an individual unit and reassemble the book at the end.


Step 2: Package the Document (Fonts and Links)

Translators don't just need the IDML — they need every asset the layout depends on, including fonts. Go to:

File → Package

This creates a folder containing:

  • The original .indd file
  • A copy of all linked images and graphics
  • A copy of all fonts used in the document
  • An automatically generated instructions PDF

Include both the .indd package folder and the IDML export in your handoff. The agency will work from the IDML for translation, but they need the packaged assets to open, proof, and re-export the final translated layout in InDesign.

Tip: If your project uses cloud fonts (Adobe Fonts), note which fonts are cloud-only. The agency may not have Adobe Fonts access and will need you to either supply the font files separately or substitute with fonts they own.


Step 3: Use Text Frames Correctly

Translation agencies and translation tools extract text from IDML at the story level — each threaded text frame chain is one story. Before you export, make sure your text frames are set up cleanly:

  • Avoid overriding master page frames unless necessary. Overrides can fragment stories in ways that confuse translation tools.
  • Thread continuation frames properly. Text that overflows into disconnected frames won't be picked up as a single translation unit.
  • Don't use separate frames for text that should flow together. For example, a sidebar with an introductory sentence and a body paragraph should be one threaded story, not two isolated frames.

Step 4: Flatten Paragraph and Character Styles

Translation quality goes up when text styles are consistent. Before handing off:

  • Make sure all body text uses a defined paragraph style (not "Basic Paragraph" with manual overrides).
  • Character styles should be applied for all inline formatting like bold, italic, or superscript — not achieved through direct manual formatting.

This matters because CAT tools track formatting as tags. Inconsistent formatting creates tag noise in the translation editor, which slows translators down and introduces the risk of broken formatting in the final file.


Step 5: Identify Non-Translatable Content

Flag anything the agency should not translate:

  • Brand names, product codes, model numbers
  • URLs and email addresses
  • Legal boilerplate that must stay in the source language

The cleanest way to do this is to add a note in a separate handoff brief (more on that below), or to use InDesign's Conditional Text feature to mark non-translatable strings. Most professional agencies will ask you for a DNT (Do Not Translate) list — prepare it upfront to avoid back-and-forth.


Step 6: Create a Handoff Brief

A one-page handoff brief eliminates most agency questions before they arise. Include:

FieldExample
Source languageEnglish (US)
Target language(s)French (FR), German (DE)
Document typeProduct catalog, 24 pages
Target audienceB2B retail buyers
ToneProfessional, not casual
Word count (approx.)3,200 words
Font notesAdobe Garamond Pro — cloud font, contact us if unavailable
DNT listBrand names: Acme Pro, Acme Lite; model numbers: X100, X200
Layout constraintsGerman text typically runs 30% longer — allow for text expansion in frames
Deadline2026-06-10

The layout constraint note is especially important. If the agency translates into German and your text frames have no overflow tolerance, the translated file will come back with overset text throughout. Alerting the agency in advance lets them flag problematic frames before they deliver.


Step 7: Automate the Round-Trip with TranslateInDesign

If your team sends InDesign files to agencies regularly, the manual export-package-brief cycle becomes a serious time sink. TranslateInDesign automates the IDML round-trip: you upload your InDesign file, the translated text comes back, and the layout is rebuilt automatically — fonts, styles, and frame structure intact.

This is especially useful for:

  • Marketing agencies running multilingual campaigns across multiple regions
  • In-house design teams that translate the same master template into 5–15 languages per quarter
  • Publishers with recurring multilingual editions

Instead of coordinating IDML exports, agency hand-offs, and manual reimporting, the workflow collapses into a single upload-and-download step.


Common Mistakes to Avoid

1. Sending the .indd file without an IDML export The agency can open .indd, but their CAT tools can't parse it directly. Always include IDML.

2. Forgetting to package fonts If the agency can't open the file with matching fonts, they'll either substitute fonts (breaking your layout) or wait for you to send them.

3. Not accounting for text expansion Languages like German, Finnish, and Spanish typically expand 20–40% over English source text. Design with this in mind — or use TranslateInDesign's auto-fit options to handle expansion after translation.

4. Sending the full linked-image package when the agency only needs translation If your document contains large linked images (photography, product shots), there's no need to send those for a text-only translation job. Send the IDML and a low-res comp for reference. This keeps the handoff lightweight.

5. No version control on the IDML Use clear versioning: product-catalog-EN-v1.idml, product-catalog-EN-v2.idml. If you make a source edit mid-translation, the agency needs to know which version is current.


Summary

To properly prepare InDesign files for a translation agency:

  1. Export IDML from File → Export
  2. Package the document with fonts and linked assets
  3. Clean up text frame threading and paragraph/character styles
  4. Prepare a DNT list and handoff brief
  5. Flag layout constraints (text expansion targets)
  6. Consider a tool like TranslateInDesign for repeatable multilingual workflows

A clean handoff means faster turnaround, fewer revision rounds, and multilingual layouts that hold up without emergency last-minute fixes.

Share this article

Related Articles