Why AI-generated layouts break when you open them in InDesign

You asked Claude or ChatGPT for a report. It looked good in the browser. Then it had to become an InDesign file and everything went sideways. Here are the six ways that happens, what causes each one, and what to do instead.

1. The text is one locked picture

What you see: the page looks right, but you can't click into a single word. Select anything and the whole page moves as one object.

Why: the design was printed to PDF from the browser and placed. InDesign treats a placed PDF as a graphic, full stop. It doesn't matter how editable the PDF looked in Acrobat. On top of that, browser PDF export often turns text into outlines, so even a PDF converter has nothing to recover. The placed-PDF guide covers this one in detail.

The fix: don't make the PDF. The HTML is the source; convert that.

2. The text is in forty tiny frames

What you see: the text is editable, technically. Each line, sometimes each word, sits in its own frame. There are no paragraph styles, nothing threads, and changing one sentence means re-laying out the whole column.

Why: the design went through a PDF-to-InDesign converter such as PDF2DTP or PDF2ID. Those tools are good at their job, and their job is reverse-engineering a flattened file. A PDF stores positioned glyph runs, not paragraphs, so the converter has to guess where one paragraph ends and the next starts. When the guess is wrong you get fragments.

The fix: same as above. Structure that's rebuilt from a flattened page is a guess. Structure that's read from the live layout is a fact.

3. The fonts are wrong, or pink

What you see: pink highlighting over the text, or a fallback font that makes the whole thing look like a 2004 intranet.

Why: two different causes. Pink means the document names a font InDesign can't find. AI tools reach for Google Fonts almost every time (Inter, Poppins, Playfair, Lora), and those aren't installed on most machines. The fallback-font case is worse: a PDF converter couldn't identify the font at all, so it substituted one and the name is gone.

The fix: for pink text, install the fonts. Google Fonts are free, and this takes two minutes. For substituted text, there's nothing to fix downstream; you need a conversion that carries the font name through. idmly binds fonts by name and never outlines them, so the file asks for the right font and installing it is the whole job. More on keeping fonts editable.

4. The charts are pictures

What you see: a bar chart you can't recolour, a gradient that's now a JPEG, a table that's a screenshot of a table.

Why: AI tools draw charts as inline SVG or as HTML elements with CSS. Anything that goes through a PDF or a screenshot flattens those to pixels or outlines. The chart survives visually and dies structurally.

The fix: ask the AI tool for charts and tables as real elements (inline SVG, HTML tables) rather than images, then use a converter that redraws them as vectors. idmly turns SVG and CSS-drawn charts into editable vector objects and HTML tables into InDesign tables.

5. Everything landed on one enormous page

What you see: one InDesign page, four metres tall, with the whole report on it.

Why: HTML has no idea what a page is. A web page scrolls. Unless the design says where the page breaks are, a converter has nothing to split on and gives you the honest answer: one tall page.

The fix: tell the AI tool to wrap each page in a fixed-size container: 816 by 1056 pixels for US Letter, 794 by 1123 for A4, with overflow:hidden. idmly then emits one InDesign page per container, at that size, with everything where the browser drew it. The ChatGPT guide has the exact prompt.

6. InDesign says the file is damaged

What you see: "Cannot open the file. Adobe InDesign may not support the file format, a plug-in that supports the file format may be missing, or the file may be damaged."

Why: InDesign opens two things, .indd and .idml. It got something else. The usual suspects: a raw HTML file with the extension changed, a zip renamed to .idml, or an IDML written by a tool or a script that only roughly followed the spec. IDML is a zipped package of XML with a strict internal layout, and InDesign checks.

The fix: rename the file to .zip and open it. A real IDML has designmap.xml at the top level and folders called Spreads, Stories and Resources. If that's not what you see, the file was never an IDML. Get one from a converter that writes valid IDML, or export one from InDesign or Affinity Publisher. IDML vs INDD explains what should be inside.

The one cause behind all six

HTML describes a layout for a browser. InDesign wants frames on pages with named styles and linked assets. Nothing in the middle translates one into the other, so people improvise, and every improvisation is lossy. The PDF route loses structure. The converter route guesses it back. Copy and paste loses everything but the words.

There are only two honest ways to get from HTML to InDesign. Recover the structure from a flattened artifact, which is what PDF converters do, and accept the cleanup. Or read the structure from the rendered page while it's still alive, and write InDesign's own format directly. The second is what idmly does: it opens your HTML in a real browser, reads the computed layout (positions, fonts, sizes, colours, the lot), and writes a native .idml with real text frames, named paragraph and character styles, editable vector charts, and images linked in place. No PDF is ever made, so nothing has to be guessed back.

What a layout that converts cleanly looks like

The file needs to be self-contained and paged. Everything else is optional.

• ✓One HTML file, CSS inline. All styles in a <style> tag in the head. No external stylesheets or scripts, except a Google Fonts link.
• ✓Fixed-size page containers. Each page in its own div at Letter, A4 or slide dimensions, overflow:hidden, and positioning that doesn't reflow (absolute or flex, not fluid percentages on the page itself).
• ✓Charts and tables as elements. Inline SVG or HTML tables, never a PNG of a chart.
• ✓Images that resolve. Base64 inline, or public https URLs. A path to a file on the AI tool's server is a broken image.
• ✓Fonts by name. A Google Fonts link in the head, and the same names installed on the machine that opens the InDesign file.
• ✓The download, not the share link. A claude.ai or chatgpt.com share link opens the app, not the file. Download the .html and convert that.

Some AI exports are web-component bundles that open blank on their own because their component scripts stayed behind on the server. idmly defines the missing components and rebuilds the pages at the size the file declares, so a blank download usually still converts. If it doesn't, re-download a fresh copy rather than re-saving the opened page.

The thirty-second version

1. Save the design as HTML.From Claude, ChatGPT, v0, Lovable, Bolt, Gemini or Figma Make: download the .html file itself, not a PDF, not a screenshot, not the share link.
2. Drop it into idmly.The first two pages convert free, no account. A design with images comes back as a zip with the .idml and a Links folder.
3. Open the .idml in InDesign and Save As.It opens as an untitled document with live text, named styles and vector charts. Save it and it's an .indd like any other. Install any fonts it asks for.

Frequently asked questions