To hand over an InDesign file to a translation partner correctly, you should export an IDML file, package all linked assets, fix any text issues in advance, and share a clear brief alongside the files. Getting this preparation right saves time, prevents errors, and keeps your project on schedule. The questions below walk through each step in detail so your handover goes smoothly from the start. At Crestec Europe, we work with InDesign files regularly and know exactly what makes a handover work well.

What should be included when sending an InDesign file for translation?

When sending an InDesign file for translation, you should include the IDML export of your document, all linked images and fonts packaged together, any reference materials such as glossaries or style guides, and a written brief explaining the project scope and target languages. Missing assets are the most common cause of delays in InDesign translation projects.

A complete handover package typically contains the following elements:

  • The IDML file exported from InDesign
  • All linked images, graphics, and embedded assets
  • Fonts used in the document (where licensing allows)
  • A glossary of product names, technical terms, or brand-specific language
  • Any previous translations of related documents for consistency
  • A project brief covering word count, target audience, and deadline

Sending everything together in one organized folder avoids back-and-forth requests and lets your translation partner start work without interruption. If your document uses fonts that cannot be shared due to licensing restrictions, flag this clearly so your partner can source compatible alternatives.

What is an IDML file and why do translators prefer it?

An IDML file is an open, XML-based format that InDesign can export, making the document’s text and structure accessible to translation tools without requiring a licensed copy of InDesign. Translators prefer IDML because it works directly with computer-assisted translation (CAT) tools, which speeds up the process and improves consistency across large projects.

The native InDesign format (.indd) is a proprietary binary file that many translation tools cannot read directly. IDML strips away that barrier by representing the document in a structured, readable format. This means translators can extract text, translate it within their preferred environment, and reimport it cleanly into InDesign without manually copying and pasting content.

Another practical advantage is version compatibility. An IDML file can be opened in older versions of InDesign, which removes software version conflicts between your team and your translation partner. It is always worth exporting a fresh IDML every time you make changes to the source document, since working from an outdated export can introduce errors during the final layout stage.

How do you package an InDesign file correctly before handover?

To package an InDesign file correctly, use the built-in Package function found under File in the InDesign menu. This collects the document, all linked assets, and font files into a single folder, ensuring your translation partner has everything needed to work with the file without missing links or substituted fonts.

Follow these steps to package your file properly:

  1. Open your InDesign document and resolve any preflight warnings, particularly missing links or fonts
  2. Go to File and select Package
  3. In the Package dialog, review the summary to confirm all links and fonts are included
  4. Choose a clear destination folder and name it consistently, for example: ProjectName_Language_Date
  5. Check the box to include a PDF for visual reference if your partner requests one
  6. Export the IDML file separately and add it to the same folder

A well-named, clearly organized folder makes the entire process more efficient. If you are sending files for multiple languages, keep each language as a separate subfolder to avoid confusion during the localization workflow.

What text issues should you fix in InDesign before sending for translation?

Before sending your InDesign file for translation, you should fix overset text, manual line breaks that force specific layouts, text in outlined or expanded form, and any content embedded inside images rather than in editable text frames. These issues either prevent translation or create significant rework during the DTP stage after translation.

Overset text is particularly problematic because it means content exists in the document but is not visible in the layout. A translator working from IDML will translate that hidden text, but it will not appear correctly when the file is reimported. Always resolve overset text before handover.

Avoid using manual line breaks (Shift + Enter) to control how text wraps, since translated text rarely matches the original character count and these breaks will create awkward line splits in the target language. Similarly, text that has been converted to outlines for design purposes cannot be edited at all, so keep editable versions of any text-based graphics and share those instead.

If your document contains text inside images, for example labels or callouts baked into a graphic, flag these clearly in your brief. Your translation partner will need to either recreate the image or handle the text separately.

Should you use InDesign styles before handing off to a translator?

Yes, you should use paragraph styles and character styles in InDesign before handing off to a translator. Consistent styles make the document far easier to manage during translation and DTP, allow translators to understand the hierarchy of the content, and ensure the layout can be reconstructed accurately after text is replaced.

Documents built with ad hoc local formatting, where each heading or caption is styled manually rather than through a named style, become unpredictable during the localization process. When translated text is reimported, local formatting is often lost or inconsistently applied. Named styles act as anchors that survive the translation and reimport cycle.

Styles also help your translation partner identify content types quickly. A translator or DTP specialist can see at a glance which text is a heading, a body paragraph, a warning note, or a caption. This context improves translation accuracy, particularly for short phrases where meaning depends on the role the text plays in the document.

If your document does not yet use styles, it is worth investing the time to apply them before handover. The effort pays off immediately in reduced DTP corrections and a cleaner final result.

What information should you share with your translation partner alongside the file?

Alongside your InDesign file, you should share a project brief, a glossary of key terms, any existing translations for reference, the target audience description, the intended use of the document, and your deadline. The more context your translation partner has, the more accurate and consistent the result will be.

A project brief does not need to be long. A single page covering the following points is enough:

  • Source and target languages
  • Subject matter and industry context
  • Target audience (for example, end users, technicians, or procurement managers)
  • Tone of voice (formal, friendly, technical)
  • Any terms that should not be translated, such as product names or trademarks
  • Preferred spelling conventions or regional variants
  • File format required for delivery

A glossary is especially valuable for technical documents, product manuals, or anything with industry-specific terminology. Even a short list of twenty to thirty key terms significantly reduces inconsistencies across a large document or a series of related files.

If this is part of an ongoing relationship rather than a one-off project, sharing previous translations allows your partner to maintain consistency across all your materials over time. We always encourage clients to build up a translation memory and glossary from the very first project, since these assets become more valuable with every subsequent job. If you are ready to get started, request a quote or get in touch with us and we will be happy to guide you through the process.

Frequently Asked Questions

How do I handle right-to-left languages like Arabic or Hebrew in InDesign before handover?

For right-to-left (RTL) languages, make sure your InDesign document is set up using the correct text frame direction and that you are using the Middle Eastern or World Ready Composer under Paragraph settings. Inform your translation partner in advance so they can prepare the appropriate DTP workflow, as RTL layouts often require significant structural changes beyond simple text replacement. If your current document was built purely for left-to-right languages, flag this in your brief so your partner can advise on whether a new layout template is needed.

What should I do if my InDesign document has multiple versions or language layers already?

If your document uses layers to separate language versions, clearly label each layer and specify in your brief which layer contains the source text to be translated. Export a separate IDML for each language version if they differ structurally, rather than sending a single file with multiple layers and expecting your translation partner to sort through them. Providing a clean, single-language source file is always the safest approach and reduces the risk of content being missed or incorrectly overwritten.

How much extra space should I allow in my InDesign layout to accommodate translated text?

As a general rule, allow 20–30% extra space for European languages, as translated text is often longer than English source text, particularly for German, Finnish, or French. For languages like Chinese, Japanese, or Korean, text may actually be shorter, but character spacing and line height requirements differ significantly. Building flexible text frames with some overflow tolerance and avoiding fixed-height text boxes where possible will save your DTP team considerable time during the post-translation layout stage.

Can I send an InDesign file for translation if I only have the PDF version?

Translating directly from a PDF is possible but significantly less efficient and more error-prone than working from an IDML file, as text extraction from PDFs can introduce formatting artefacts, broken line breaks, and missing characters. If the original InDesign source file is unavailable, inform your translation partner upfront so they can assess whether PDF extraction is viable or whether the document needs to be recreated. Whenever possible, always retain and share the original editable source files rather than relying on PDF exports for translation purposes.

What is a translation memory and should I ask my partner to build one for my InDesign project?

A translation memory (TM) is a database that stores previously translated segments so they can be reused automatically when the same or similar text appears again, ensuring consistency and reducing costs over time. Yes, you should absolutely ask your translation partner to build and maintain a TM from your very first project, as it becomes increasingly valuable across subsequent documents, updates, and related materials. Combined with a project glossary, a translation memory is one of the most cost-effective long-term investments you can make if you produce multilingual InDesign documents regularly.

How do I check the quality of the translated InDesign file once it is returned to me?

When you receive the translated file back, open it in InDesign and run a preflight check to catch any missing links, font issues, or overset text that may have been introduced during the reimport process. Review the layout visually against the source document to check for text overflow, broken alignment, or inconsistent spacing caused by differences in text length. If possible, have a native speaker of the target language do a final proofread directly in the laid-out document, since some translation issues only become apparent in context within the actual design.

Is it better to translate one large InDesign file or break it into smaller sections first?

For very large documents such as product catalogues or technical manuals, breaking the file into logical sections — by chapter, product category, or content type — can make the translation workflow more manageable and allow work to begin on completed sections while others are still being finalized. However, splitting files also increases the risk of inconsistency if not managed carefully, so this approach works best when combined with a shared glossary and translation memory that applies across all sections. Discuss the structure of your document with your translation partner before splitting anything, as they will have a preferred workflow that balances efficiency with consistency.

Related Articles