What They Love About Us Customized Solutions, Top Customer Support, Confidentiality & Security

Photoshop, Illustrator, or InDesign: Which One Actually Matters for Multilingual DTP

Ask which software matters most for multilingual desktop publishing, and the honest answer is that the question is slightly wrong. Foliage Solutions works primarily in InDesign for multilingual layout, with targeted Illustrator support for embedded graphics, because the tool matters less than what happens to a file once translation enters the picture. A vendor who cannot explain that distinction has not thought through the multilingual stage of the work at all. 

This article is written for Vendor Managers and Localization PMs evaluating a DTP vendor’s software claims, not for individuals choosing a single tool for personal design work. 

InDesign: the industry standard for a specific reason

InDesign is built around structured, multi-page layout with a text-frame model that keeps content editable and reflowable, which is exactly the property multilingual work depends on. Text lives in frames that can expand, contract, and reflow as translated text runs longer or shorter than the source, and InDesign’s paragraph and character style system means formatting can be applied consistently across every language version without manually reformatting each one. 

This structural design is also what makes InDesign genuinely compatible with CAT-tool workflows. Text can be exported cleanly, translated in a CAT tool, and re-imported without the layout collapsing, provided the file was built correctly in the first place. Most professional multilingual DTP work runs through InDesign as the primary layout tool for exactly this reason: the software’s own architecture supports the round-trip that translation requires. 

None of this happens automatically simply because a vendor opens the file in InDesign. A poorly structured InDesign file, text set outside proper frames, styles applied inconsistently, tables built as manually positioned text boxes rather than real table structures, creates the same round-trip problems a different tool might, just inside software that is theoretically built to prevent them. 

Nested styles are a particular case worth naming specifically. A heading style built on top of a body style, with local overrides layered on top of both, can translate correctly in the source language and then break in ways that are hard to diagnose once translated text of a different length interacts with those layered overrides. A DTP vendor who builds clean, non-nested style hierarchies from the start avoids this entirely. One who inherits a client’s existing messy style structure needs to flag it before translation begins, not discover it during layout. 

Preprocessing Phase

Illustrator: a narrower, specific role 

Illustrator’s role in multilingual DTP is narrower and more specific: vector graphics, infographics, and diagrams that need text editing inside them. Illustrator handles vector text as live, editable content in most cases, which means that text can potentially be extracted and translated rather than needing to be recreated from scratch in every language. 

The common failure point is text that was flattened into outlines or rasterized into a raster layer at some point in the file’s history, often to lock in a specific font appearance for print or web use. Once text is flattened, it is no longer text at all. It is a shape, indistinguishable from any other graphic element, and it cannot be extracted for translation through normal channels. A vendor preparing an Illustrator file for translation needs to check for this specifically, not assume that because the software supports live text, the actual file still has it. 

This is a common and easy-to-miss problem precisely because flattened text still looks like text visually. Nothing about the file’s appearance signals that the text layer has been lost. It only surfaces when someone tries to extract it for translation and finds there is nothing there to extract. 

Photoshop: rarely the right tool for translatable content 

Photoshop is a raster image editor, not a layout tool, and it should rarely appear in a serious multilingual DTP workflow for content that needs translation. Text added in Photoshop exists as pixels once flattened, or as an editable text layer that most CAT-tool workflows are not built to extract from directly. 

This matters because Photoshop is sometimes used, incorrectly, for tasks that belong in InDesign or Illustrator: marketing graphics with headline text, simple one-page flyers, or quick visual assets that get treated as finished deliverables rather than as a step in a longer multilingual pipeline. A Photoshop file with English headline text baked into a flattened layer has to be entirely rebuilt, not edited, for every target language, which is slower and more expensive than working in a tool built for editable, translatable text in the first place. 

There are legitimate uses for Photoshop inside a broader project, photo editing, texture work, background preparation, but text-heavy content intended for translation is very rarely one of them. 

Photoshop’s text tools have improved over the years, and modern versions do support editable text layers more reliably than older ones did. That improvement does not change the fundamental workflow problem: Photoshop was not designed around multi-language reflow, style consistency across dozens of pages, or CAT-tool export in the way InDesign was. Using an improved tool for the wrong job is still using the wrong tool. 

What the software question is actually asking 

The real question a Vendor Manager should ask is not which software a vendor uses, but whether that vendor understands how each tool’s output behaves once it enters a CAT-tool workflow. A vendor who defaults to Photoshop for text-heavy multilingual work, or who cannot say whether their Illustrator files use live text or flattened outlines, is signaling a gap in process, not just a software preference. 

A more useful evaluation question: ask a prospective vendor to describe, specifically, how they check whether an Illustrator or InDesign file’s text is still live and translatable before the file reaches a translator. A vendor with a real process will have a specific, concrete answer. A vendor without one will describe general software familiarity instead.

The cost of getting this wrong 

Rebuilding a flattened graphic under deadline pressure costs more than catching the problem during intake, and it costs more in a way that rarely shows up as a single visible line item. A rush rebuild means paying overtime rates, or accepting a delivery delay that cascades into the client’s own downstream schedule, or both. None of that appears on the original quote, which only ever priced the assumption that the file would translate cleanly the first time. 

How this plays out on a real multilingual project

A typical multilingual DTP batch rarely uses just one of these tools. A product brochure might combine InDesign for the main layout, an Illustrator diagram embedded on page three, and a photograph that needed light retouching in Photoshop before being placed into the InDesign layout. The question is not which single tool the vendor prefers. It is whether the vendor checks every element in that mixed-format file for translatability, not just the InDesign body text that is easiest to catch. 

A diagram with three lines of Illustrator text is just as capable of blocking a translation project as a missing paragraph in the main document, and it is far more likely to be overlooked, because it sits visually inside a graphic rather than in the obvious text flow most reviewers check first. 

Consider a technical product sheet: two pages of InDesign body copy, a comparison table built with real table structure, and one Illustrator-based exploded diagram showing product components with callout labels. A generalist reviewer checking the file for translation-readiness reads through the body copy, checks the table, and calls the file ready. The exploded diagram’s callout labels, built as Illustrator text years ago and flattened at some point during a rebranding update, never get flagged, because nobody thought to check a component diagram the same way they checked the paragraphs. That is exactly the kind of gap a process built specifically around multilingual DTP is designed to catch, and a process built around general design competence is not. 

What Foliage checks before a file reaches translation 

Every InDesign file is reviewed for structural integrity before translation: proper text frames rather than manually positioned text, consistent style usage, and real table structures rather than positioned text boxes made to look like tables. Every embedded Illustrator graphic is checked specifically for live, editable text versus flattened outlines, with any flattened text flagged and addressed before the file moves forward. Photoshop is used only where it belongs, image editing and photo preparation, never as the primary tool for translatable text content. 

Where flattened text is found in a graphic that genuinely needs to be translated, the practical options are limited and worth understanding upfront. The text can sometimes be recreated as live type over the existing artwork, if the source design files or fonts are available. Where they are not, the graphic may need to be rebuilt substantially, which affects both timeline and cost. Flagging this at file intake, before translation begins, avoids the far worse alternative: discovering it after a translator has already completed the surrounding document and the graphic becomes the one piece holding up final delivery. 

Talk to Foliage Solutions about which format your next multilingual project actually needs, and how we check for translatability before a file ever reaches a translator.

Like our article? Share with your network!

Ready to optimize your translation projects with our expert Desktop Publishing services?

Trust that your desktop publishing needs are in capable hands with our proven experience in serving translation companies and LSPs.

Foliage Solutions Contact Form
First
Last
GDPR