The conversion looks wrong. Here’s what happened, and the fix.
Published November 2026
idmly converts what a browser draws. When the result looks wrong in InDesign, the cause is nearly always one of eight things, and most of them happen before the file reaches the converter: part of the design didn’t get uploaded, or the export lost the layout.
Find what you’re seeing. Each one has a fix you can do now.
It came out as plain text
What you see: Black Times-style text down the left of the page, no colour, empty boxes where the images were. Or idmly refused the file and named a stylesheet that wasn’t uploaded
.
Why: The .html you uploaded is only part of the design. Its colours, fonts and layout live in files that sit next to it: a styles.css, an images folder, sometimes a script. Upload the .html alone and none of those come with it.
The fix, if you have the folder: zip the whole folder (every .html, the .css files, the images folder, any scripts) and drop the .zip into idmly. Each .html in the zip becomes a page.
The fix, if an AI tool made it: ask for one file that carries everything.
Give me this design as one self-contained .html file. Put all the CSS in a <style> tag and all the JavaScript inline, embed images as data URIs, and don’t link to any other files.
How to check before you upload: copy the .html to an empty folder and open it in a browser. If it has lost its styling there, it isn’t self-contained yet.
It’s mostly empty
What you see: A photo, then empty-looking text frames and blank space where the design should be. idmly marks the result Your export is missing parts of the design
.
Why: The export gave every layer a colour and a font size and nothing that places or sizes it. Coloured panels collapse to no height, so a white headline ends up on the white page. Open the exported .html in a browser and it looks just as empty there. idmly rebuilds what the browser draws, faithfully, including nothing.
The fix is in the export, not in InDesign. The text is in the file (select it and give it a colour), but the design isn’t.
If an AI tool made it:
Export this design as one self-contained .html file with a fixed page size. Set explicit widths and heights for all panels and backgrounds, ensure text is readable, and check that it matches the design in a browser.
If it came from a design tool such as Figma: export tools vary a lot. Some carry the whole layout into the HTML and some only part of it. Try another export route, and open the result in a browser before you convert it. I’m testing the Figma routes now and will name the ones that hold up on the Figma guide. Until then, send me the file and tell me what you exported it with.
Every page is blank, or it wouldn’t convert
What you see: Every page came out empty
, this looks like a Claude Bundled Page that didn’t finish unpacking
, or that URL isn’t a design
.
Why: Three different things. The design needs files that weren’t in the upload, so nothing drew (the plain-text case, one step worse). Or a Claude Bundled Page was re-saved from the browser and broke on the way. Or the link you pasted opens an app, not the file.
- ✓Needs its folder: zip the whole folder, or use the self-contained prompt above.
- ✓Bundled Page: download a fresh copy with Claude’s own Download. Don’t use the browser’s
Save page as
. - ✓Share link: a claude.ai or chatgpt.com share link opens the app. Download the
.htmland upload that.
Every message the converter can return, with its fix, is listed in What converts.
Images are empty boxes
What you see: Grey or crossed frames where photos and logos should be.
Why: Images are linked, never embedded in the .idml. A design with images comes back as a zip: the .idml and a Links folder. Separate them and InDesign can’t find the pictures. The other cause is upstream: the file pointed at images it didn’t carry.
- ✓Keep
Linksbeside the.idml. Unzip, leave both where they land, open the.idml. If you already moved it, relink from the Links panel. - ✓idmly said images could not be loaded: they sit in a folder next to the file. Zip the folder, or re-export with images embedded.
- ✓Lots of linked images: one conversion downloads up to 64 images from the web on the free preview and 150 with a license. Embedded images don’t count.
- ✓SVG logos and shapes arrived as empty grey frames: that was mine, for
.svgfiles in a zipped folder. Fixed on 19 November 2026. Convert again and they come in as editable vectors.
The fonts are pink, or the text has reflowed
What you see: Pink highlighting, a fallback typeface, or lines that wrap in the wrong place and push everything down.
Why: The .idml asks for fonts by name and InDesign doesn’t have one of them. A substitute font has different letter widths, so lines break differently and the frame grows over what’s below it. Most the layout is broken
reports are this.
Activate the fonts first, then judge the layout. The result card lists them by name. Install them, or activate them in Adobe Fonts, and reopen the file.
If your copy of a font names its weights differently, use Type > Find/Replace Font with Redefine Style When Changing All
ticked. When a design embeds its own fonts, idmly reads the real style names from them, so a family whose normal weight is called Book
is asked for as Book.
More in keeping fonts and charts editable.
Everything is on one tall page
What you see: One InDesign page, several metres tall, with the whole document on it.
Why: HTML has no pages. Unless the design says where each page starts and ends, there is nothing to split on, so you get the honest answer: one tall page.
Ask the tool to mark the pages, then convert again:
Wrap each page of this design in its own container with class="page", at a fixed size (816 by 1056 px for US Letter, 794 by 1123 px for A4) with overflow hidden, so every page is a separate block. Keep everything else the same.
idmly then emits one InDesign page per container, at that size.
The colours are off
What you see: Duller than the screen, a tint that became a solid, or a colour that is plainly wrong.
Why: idmly reads the colour the browser paints and writes it as an RGB swatch. Three things follow from that.
- ✓It’s RGB. Prepress is left to you: convert to your CMYK profile in InDesign.
- ✓Transparency is baked. A 6% white card on a dark page becomes the solid colour you saw, not a transparent swatch.
- ✓Converted before 19 November 2026? Colours written as
oklchorcolor-mix(Tailwind’s default) came out dark or the wrong hue. That’s fixed. Convert the file again.
A blue where there was a green is not you. Send the file.
Text overlaps, or columns have run together
What you see: A paragraph sitting on the one below it, a table over the text that follows, two columns of text set as one.
Why: Usually fonts: a substitute font reflows the text (see above). When the fonts are right and it still overlaps, the engine read the layout wrong.
Activate the fonts and reopen. If it still overlaps and you converted before 19 November 2026, convert again: two-column text around a full-width table or heading, lists inside table cells, and text that wrapped differently in InDesign were all fixed that week.
Still wrong? That’s a bug and I want the file. Send it.
None of these? Send us the file
If the design looks right in a browser and wrong in InDesign, that’s the engine, and the fastest way to get it fixed is to show me.
- ✓From the result card: tap
Something’s off
. The file you just converted is already attached. - ✓Later: open the report form and pick the
.htmlor.zip. No need to convert it again. - ✓By email: support@idmly.com, with the file and a line on what looked wrong.
Tell me what tool it came from if you can. The file goes to me and nowhere else. I run it, fix what broke, and the fix ships for everyone. Every case on this page started as a file someone sent.
Fixed the export? Convert it again.
A failed conversion doesn’t use up a free one. Drop the new file in and its two most detailed pages come back as a native, editable InDesign file.