18 August 2026

InDesign automation: what can actually be automated in multilingual documents

Roughly two thirds of the twelve stations in a multilingual InDesign run can be automated. The remaining third, preparation, review and sign-off, sets the turnaround time. Automating only those two thirds speeds up a process whose duration arises elsewhere. This article walks the run station by station, from the source document to the released language version.

1What can actually be automated in InDesign?

InDesign ships with a full scripting interface. Text extraction, style assignment, image replacement, output and batch processing can be automated. Editorial judgement and sign-off cannot, because they require a decision about content.

Through that interface, documents can be opened, changed, exported and closed without anyone touching them. It is the technical basis for everything described here as automatable.

Adobe documents it as the Scripting DOM API, and the newer extension technology as UXP. Both are publicly specified and not tied to a single vendor.

2Which three levels of automation are there?

A script on the workstation, InDesign Server, and a platform with process control. The three differ less in technology than in how many people they can support.

The step from level one to level two is a technical one. The step from level two to level three is an organisational one.

The second step is the more effective one as soon as more than one person is involved in the process.

3Twelve stations, honestly assessed

A multilingual run has more steps than most process diagrams show. Nine of the twelve stations can be automated fully or in part, three stay human.

Nine of twelve stations can be automated fully or in part. The three marked stations set the turnaround time.

The three remaining stations, preparation, review and sign-off, account for the larger share of calendar time in most organisations.

Stations 3 to 5 raise the question of which engine is used and where its limits lie inside the layout. More on that in the article on where AI translation is headed.

Automation that ends at station 7 barely shortens the run. The text arrives in the layout faster and then waits for the review exactly as long as before.

4Why do automation projects stall at the same point?

Because stations 6 and 10 are dismissed as human work. That is only half right: the review is specialist work, the environment it happens in is a process decision.

And that decision is the biggest lever in the whole process. There are two common variants.

• Review next to the document. Produce a PDF, email it to the reviewer, get the comments back in annotations or as a text file, have someone transfer them into the layout by hand, produce a new PDF, run a second round.
• Review inside the document. The reviewer works directly in the rendered layout. No interim version, no transferring, no second person in the loop.

With fourteen languages, the first variant means fourteen parallel processes with fourteen interim versions and at least two rounds per language.

In the second variant, the overset text is visible in the same place where it is fixed.

The difference is not a question of processing power. It is the question of whether the review happens inside the document or next to it.

5What does your document have to bring?

Automation amplifies the structure it finds. If the structure is untidy, automation amplifies the error. Five conditions decide whether the effort pays off.

• Styles instead of local formatting. A script can address paragraph styles reliably. Manually applied formatting cannot be restored with any certainty.
• A maintained translation memory. Without one, every run starts from zero. With one, the volume that needs reviewing drops, and that volume is what sets the turnaround time.
• Binding terminology before the first run. A glossary handed to the engine costs effort once. Correcting the same term afterwards in fourteen languages costs fourteen times as much.
• One source for content changes. As soon as content work happens in a target language, no automatic comparison can decide which version applies.
• Naming and filing everyone sticks to. Unspectacular, and the most common reason a working script fails in daily use.

6The line item that appears in no budget: maintenance

A script is not a one-off effort. It is a small software product with a life cycle. Four things change reliably and make maintenance necessary.

• InDesign versions change. Adobe moved the extension technology to UXP, and older extensions do not necessarily keep running.
• Translation services change their interfaces.
• Document templates change, and the script does not know the new structure.
• The person who wrote the script moves to another department.

The last point is the most common one in practice. Automation only one person understands is a risk, not a process.

For in-house development, budget for ongoing maintenance and settle beforehand who will take it on.

7How InTO maps the stations

InTO covers stations 2 to 5, 7, 11 and 12 automatically, and moves stations 6 and 8 into the rendered layout.

DTP processing runs through an embedded InDesign Server. No additional software is needed on your side, and everyone involved works in the browser.

For a run across thirty documents in twelve languages, that means:

• Pre-translation and machine translation run without intervention, configurable per project type and language pair.
• The reviewers in the markets see their language in the layout, with the translation memory suggestions alongside. Released text goes back into the translation memory automatically.
• Language-dependent images are detected and managed through a media database.
• For the next edition, only what changed is translated and reviewed, and the language versions are carried forward.

What InTO does not automate: preparing your document and the editorial decision itself.

A layout without styles and without space allowance does not get faster on a platform either. Which file travels between the stations is covered in the article on IDML, INDD and XLIFF.