How to Package InDesign Files for Translators: A Complete Guide

When a translator opens your InDesign file and gets a wall of font-missing warnings and broken image links, the project stalls. They can't translate text they can't see, and they can't assess layout impact without the linked graphics in place.

Packaging InDesign files for translators solves this. InDesign's built-in Package function collects every dependency — fonts, linked images, the document itself — into a single folder that opens cleanly on any machine. This guide walks through the full process, what to include alongside the package, and which mistakes kill handoffs before translation even starts.

1. Why Packaging Matters

InDesign documents are not self-contained. The .indd file is a set of instructions that reference:

• Fonts stored elsewhere on your system (or in Adobe Fonts cloud)
• Linked images at absolute file paths on your machine
• Placed PDFs and other documents embedded by reference

On your machine, everything renders perfectly. On the translator's machine, those absolute paths don't exist, those fonts may not be licensed, and the document falls apart.

Missing fonts are especially disruptive. If a translator opens a document with an absent typeface, InDesign substitutes a fallback — usually Minion Pro — and every text frame reflows. They lose visual context for how translated text fits the designed layout. Missing images are less critical for translation itself, but broken link warnings interrupt the workflow and can prompt translators to restructure frames to work around gaps.

Packaging eliminates these variables before the file leaves your desk.

2. Step-by-Step: Package via File > Package

InDesign's Package dialog is straightforward but has a few decisions worth understanding.

Step 1: Open the Package dialog

Go to File > Package (or File > Package for Book if you're working with a multi-document book). InDesign runs a preflight check before presenting the dialog. Adobe's official Package documentation covers every dialog option in detail.

Step 2: Review the Summary panel

The Summary panel is the first thing you see. It lists fonts used, linked images, colors, and any problems found. Check:

• Fonts: Are all fonts listed as "OK"? Any font flagged with a warning may not be licensable for sharing — more on this in Common Mistakes.
• Links and Images: Every linked image should have a status of "OK." Yellow triangles indicate modified links; red circles indicate missing files. Fix these before packaging — don't package a file with missing links.
• Colors and Inks: Relevant for print QA, less critical for translators. Note any RGB objects if the final output is print — this is worth flagging in your handoff brief.

Step 3: Work through the panel tabs

After Summary, the dialog shows individual tabs for Fonts, Links and Images, Colors and Inks, Print Settings, and External Plug-ins.

In Fonts, InDesign shows every typeface used and its protection status. A "Protected" flag means the font's EULA restricts distribution — you cannot legally include it in a package sent to a third party. Note these fonts by name so you can brief the translator on what to install separately.

In Links and Images, you can relink any broken references directly from this panel without closing the dialog. Fix them here rather than canceling out.

Step 4: Click Package and configure the output

Once the summary looks clean, click Package. You'll be prompted to save a PDF print instructions file — this is optional; skip it for translation handoffs unless you need it for print reference.

The Create Package Folder dialog lets you configure what gets included:

• Copy Fonts (Except CJK): Check this. This copies the font files into a Document Fonts subfolder inside the package. InDesign automatically activates fonts from this folder when the document is opened — no manual font installation needed.
• Copy Linked Graphics: Check this. Copies all linked images into a Links subfolder and updates the document's internal links to point there.
• Update Graphic Links In Package: Check this. Ensures the packaged .indd references the copied images, not the originals on your machine.
• Include IDML: Check this. This is the most important option for translation. More on IDML below.
• Include PDF (Print): Optional. Include if you want the translator to have a visual reference PDF.
• Include Hidden and Non-Printing Layers: Check this if you have any text layers set to non-printing that still need translation.

Click Package. InDesign creates a folder containing the .indd, the Document Fonts subfolder, the Links subfolder, and the .idml if you checked that option.

3. What to Include Alongside the Package

The package folder gives the translator the raw materials. A complete handoff adds a few more items:

IDML file — if you didn't check "Include IDML" during packaging, export it separately via File > Save As > InDesign Markup (IDML). IDML is the format translation tools and CAT software actually parse. Most professional translation workflows never open the .indd directly.

Instructions file — a plain text or PDF document in the root of the package folder with:

• Source language and target language(s)
• Document type and audience
• Non-translatable strings: product codes, URLs, brand names, phone numbers
• Terminology glossary or link to one
• Any frames with tight text budgets that need concise phrasing
• Delivery format expected back (translated IDML, InDesign, or placed PDF)

A visual reference PDF — useful for print documents where the translator needs to understand layout context. Export at screen resolution; full print-quality PDFs are unnecessary here.

4. Common Mistakes When Packaging for Translation

Protected fonts in the package. Many professional typefaces have EULAs that prohibit distribution. When you package such a font, InDesign includes the file but you may be in breach of the license. More importantly, the translator may be blocked from using it. Solution: identify protected fonts before packaging, note them in the instructions file, and either negotiate a license transfer with your foundry or ask the translator to source their own copy.

Packaging without resolving overset text. InDesign lets you package a document with overset (overflow) text frames. The translator receives a file where text is already cut off in the source language — a problem that only gets worse after translation, since most target languages run longer than English. Fix all overset before packaging. For a full pre-packaging checklist, see How to Prepare InDesign Files for Translation.

Not including the IDML. Sending a .indd-only package forces the translator to work with a version-locked file. If they're on a different version of InDesign, the document may not open. If they're using a CAT tool or automated translation service, it almost certainly can't parse .indd. Always include IDML.

Forgetting placed PDFs. InDesign can place PDFs as linked graphics. These show up in the Links panel and are collected during packaging — but they're worth checking specifically. A placed PDF that's a chart or table with editable text creates an ambiguity: does that text need translation? Note placed PDFs in your instructions file and clarify whether their content is in scope.

RGB images in a print document. Not strictly a translation problem, but if your Links folder contains RGB images for a CMYK print job, the translator or a downstream printer will flag them. It's cleaner to resolve this before packaging.

5. IDML vs .indd — Which Format to Send?

Send both, but make clear that the IDML is the working file.

.indd is InDesign's native binary format. It contains everything — layout, styles, content, document history, metadata. It is also version-locked: a file saved in InDesign 2024 may not open in InDesign 2022. Most CAT tools (SDL Trados, memoQ, Phrase, Wordfast) cannot extract text from .indd without a plugin or intermediary step. Agencies that receive only .indd often have to convert it to IDML themselves before starting work, which adds time and introduces a risk of conversion artifacts.

IDML (InDesign Markup Language) is an open XML format that InDesign introduced specifically as a version-agnostic interchange format. It opens in any version of InDesign from CS4 onward. It is human-readable XML, which means translation tools can parse it directly — extract the source text, insert translated text, and write back a new IDML that InDesign can open with all styles and layout intact.

For agencies and CAT tool workflows, IDML is the standard. See how translation agencies handle InDesign files for the full agency intake-to-delivery workflow. For automated translation services like TranslateInDesign, IDML is the only required input — no package needed at all.

The practical rule: include both .indd and .idml in your package, but label the IDML clearly as the translation-ready file.

6. Skip the Manual Packaging — Translate Directly

If your team translates InDesign documents regularly, the package-and-ship workflow adds up: preflight, fix links, check fonts, export IDML, write instructions, zip, send, wait. Then review the returned file, check for style drift, handle overset frames.

TranslateInDesign cuts this down to a single upload. Drop in your IDML, choose your target language, and get a translated IDML back with every paragraph style, character style, and text frame setting preserved. Overflow detection flags any translated segment that exceeds the original frame — so you know exactly which frames need attention before opening InDesign.

For one-off jobs, the manual workflow above is fine. For teams doing this repeatedly, it's worth seeing how much of it can be automated.

Summary

Packaging InDesign files for translators is a two-part job: use File > Package to collect fonts and linked images, and include an IDML alongside the .indd so translators have a version-agnostic, tool-compatible file to work from.

• Fix all overset text and missing links before packaging
• Check font protection status — note any fonts the translator must source separately
• Always include an IDML — it's what translation tools actually use
• Include an instructions file with non-translatable strings and a glossary
• Note any placed PDFs and whether their text is in translation scope

Ready to skip the packaging step entirely? Upload your IDML to TranslateInDesign.co and get a translated file back in minutes — styles, layout, and formatting intact.