Can Claude Create InDesign Files?

In short:

• On its own, Claude can’t produce a usable InDesign file. The .indd format is closed and binary; whatever Claude writes directly either won’t open or won’t be a document you’d build on.
• With Sidekick, Claude works inside a running copy of InDesign. The file that comes out is a real InDesign document — paragraph styles, master pages, linked images, PDF export — because InDesign made it.
• What Claude can do with the other files in your workflow (your manuscript, images, spreadsheets) depends on which Claude you’re using. There’s a table below.

What happens if you just ask

Open Claude in your browser and ask for “an InDesign file for a two-page brochure”. You’ll get one of three things:

1. A description of the layout, in prose.
2. A pile of XML with instructions to save it as IDML.
3. A file with an .indd extension that is plain text inside.

The first isn’t a file. The third won’t open. The second is the interesting one, because IDML is a documented format and Claude does know it — but it’s a zip of dozens of interlinked XML files that all have to agree on resource IDs, geometry, and style references. A hand-written IDML that InDesign accepts is a big, brittle job. Sometimes it opens. Usually it opens with missing styles, wrong frame positions, or text that isn’t threaded, and you’d be faster starting over.

The same limit applies in reverse: Claude can’t read an .indd file you upload. It can read an IDML export, but with the same caveats.

Why: InDesign is the thing that makes InDesign files

There’s only one program that reliably writes .indd files, and it’s InDesign. So the realistic route isn’t to have Claude imitate InDesign — it’s to have Claude drive InDesign.

That’s what Sidekick does. You describe what you want; Claude writes InDesign scripting code; Sidekick runs it inside the InDesign that’s open on your machine; Claude takes a snapshot of the result and checks its own work. The document is created by InDesign and saved by InDesign. It’s a real file, not an approximation of one.

In practice that means Claude can:

• Create a new document with the right page size, margins, bleed, and facing pages.
• Set up paragraph and character styles, and apply them.
• Flow text into threaded frames across pages.
• Place images, set their frames and fitting, and give them alt text.
• Build and apply master pages.
• Open an existing document and change it — find and replace, restyle, audit alt text, update a pricing table from Excel.
• Export to PDF or IDML.

What it can’t do is conjure a file without InDesign. Sidekick needs InDesign running on your computer (or on a computer you’re connected to).

Where the files end up: it depends on which Claude

“Claude” is really four products, and they differ in one way that matters here: whether Claude can see and write files on your computer. That decides how the other files in a layout job — a generated chart, an SVG equation, a CSV of product data, a folder of photos — get from Claude into InDesign.

	claude.ai (browser)	Claude Desktop	Claude Cowork	Claude Code
Works with Sidekick	No ¹	Yes	Yes	Yes
Can read files on your computer	Only what you upload	Only what you upload ²	Yes, in the folder you share	Yes
Can write files to your computer	No — you download	No — you download ²	Yes, in the folder you share	Yes
Where a generated asset lands (chart, SVG, CSV, image)	Browser download	Download from the chat	Straight into your project folder	Straight onto disk
Can it place that asset into your document?	—	After you save the download and tell Claude where it is	Yes, in one step	Yes, in one step
Where the InDesign document lands	—	Wherever you save it from InDesign	Wherever you save it from InDesign	Wherever you save it from InDesign

¹ Sidekick is a local connection between the Claude app and InDesign on the same computer. The browser version can’t reach it. ² Unless you add a filesystem extension to Claude Desktop.

Text is the exception to all of this. Text never needs a file: with Sidekick, Claude writes it straight into a text frame. The file question only comes up for things InDesign has to place — images, graphics, data.

Which one should you use?

• Claude Desktop if you want to build or edit layouts from a conversation and your assets are already on disk. This is where most designers start.
• Claude Cowork if the job involves files — a Markdown manuscript, a folder of product photos, a spreadsheet — and you’d rather not touch a terminal. Cowork is newer and still maturing; see our note on it.
• Claude Code for automation: batch jobs, repeated scripts, anything you’ll run more than once. See Sidekick with Claude Code.
• claude.ai in the browser for thinking about the design. Not for making the file.

You can also run more than one at the same time against the same InDesign session.

Related questions

Can Claude read my InDesign file? Not by uploading it. With Sidekick, open the document in InDesign and Claude can read its structure — pages, frames, styles, text, links — directly.

Can Claude convert Word, Markdown, or Excel into InDesign? Yes, with Sidekick plus a Claude that can read the source file (Cowork or Claude Code, or Desktop with the file uploaded). Claude reads the source and builds the document in InDesign; no intermediate InDesign file is written by Claude.

What about ChatGPT or other assistants? The same limits apply: no assistant can write .indd on its own. Sidekick works with any MCP-compatible assistant, so the “drive InDesign instead of imitating it” approach isn’t specific to Claude.

Does Sidekick create the file for me? Sidekick doesn’t create anything itself. It’s the connection. Claude decides what to do, InDesign does it, and you save the document as you always would — or ask Claude to.