Claude Design Export Not Working? Fixes for the Most Common Problems

You built something good in Claude Design, you hit export, and now you are staring at a blank download, a blurry PNG, or a PowerPoint that looks nothing like the screen. This is a calm walkthrough of the failures people actually hit, why each one happens, and how to get clean output anyway.

The exports break for mechanical reasons, not because the design is wrong. Once you know what is happening under the hood, every one of these has a fix.

The export button does nothing, or the download never finishes

You click export and nothing happens, or the spinner runs forever and no file lands. This is almost always a browser or session quirk rather than a problem with the design itself. The export runs in your tab, so a stalled tab, a lost session, an aggressive ad blocker, or a large design that times out can all leave you with no file.

The fix, in order: retry the export once, because a single failed run is often just a transient hiccup. If it stalls again, reload the tab so the session re-initialises, then try a different export type (a PDF or standalone download instead of the one that hung). If it still will not move, open the design in a fresh tab or a private window with extensions disabled. Big multi-slide decks are the most likely to time out, so exporting a smaller piece first tells you whether size is the cause.

The PNG comes out blurry or low resolution

You screenshot the design or save the preview, and the result is soft, with fuzzy text and fringed edges. This happens because a screenshot captures at your screen's scale, not at the design's real pixel dimensions. On a standard display that means you get roughly half the resolution you need for a crisp social post, and any later resizing only makes it worse.

The fix is to render at a 2x device scale factor and at the exact pixel dimensions the platform expects, rather than capturing whatever your monitor happens to show. A 1080 by 1350 Instagram post rendered at a 2x scale factor produces a 2160 by 2700 PNG, which stays sharp on retina screens and survives the platform's recompression far better than a screen-scale capture. Screenshots cannot do this reliably because they are tied to your display. A renderer that sets the scale factor deliberately can. This is exactly what Renda does on every PNG.

The PowerPoint export breaks fonts and shifts the layout

You use the native .pptx export, open it in PowerPoint, and the fonts have fallen back to defaults, the gradients look flat, and elements have nudged out of place. The reason is that a .pptx export rebuilds your design as native PowerPoint shapes and text boxes instead of capturing what was on screen. PowerPoint then renders those shapes with whatever fonts your machine has, so any web font drops to a substitute and layered gradients flatten.

The reliable fix is to stop asking PowerPoint to re-interpret the design and instead put a faithful render of each slide into the deck. When every slide is a pixel-perfect image sized to the slide, the fonts, gradients, and spacing match the original exactly because PowerPoint is no longer rebuilding anything. You lose editable text boxes, but you gain a deck that looks like the design you approved.

The carousel exports as one tall image instead of separate slides

You wanted four square slides for a LinkedIn or Instagram carousel, and the direct image export handed you a single tall PNG with all of them stacked. This happens because the image export captures the whole scroll height of the design as one canvas. It does not know where one slide ends and the next begins, so it concatenates them.

The fix is per-slide capture at the carousel ratio. Each slide needs to be isolated and rendered on its own at, say, 1080 by 1350, so you end up with numbered files you can drag straight into the upload. Cropping the tall image by hand technically works, but it is slow and the crop lines are never quite right. A tool that detects the slide boundaries and renders each one separately removes the guesswork.

The exported design still shows arrows, page counters, or pip dots

Your carousel exports with the navigation arrows, a "1 of 5" counter, or the little pip dots baked into the image. That UI is interactive chrome that Claude Design adds to the HTML so you can click through the preview. It is part of the page, so anything that captures the page as-is captures the chrome along with the design.

The fix is to hide that chrome before the capture happens. The navigation elements need to be removed or set to hidden in the DOM, and only then should each slide be rendered. Doing this by hand means editing the exported HTML, which is fragile because the selectors change between designs. The dependable approach is a render step that knows which elements are navigation and hides them automatically for every layout.

Fonts look wrong, or boxes and symbols appear

The export comes out with the wrong typeface, or worse, with empty rectangles and stray symbols where text should be. This is a timing problem. Web fonts load asynchronously, and if the capture fires before the fonts have finished downloading, the renderer grabs the fallback font (or no glyphs at all) and freezes that into the image.

The fix is to wait for fonts to be fully loaded before capturing. A screenshot taken a beat too early bakes in the wrong state, which is why the same design sometimes exports fine and sometimes does not. A render pipeline that waits on the document's font-ready signal before it captures sidesteps the race entirely, so the right typefaces show up every time.

Quick reference

The reliable path

Every failure above comes from the same place: capturing a live, interactive page at the wrong moment, at the wrong scale, with the wrong elements visible. The dependable fix is to take the design out of the browser and render it deterministically instead.

That is what Renda does. You drop in the Claude Design HTML export (the zip), and it renders clean output the same way every time: per-slide PNGs at exact platform dimensions and 2x scale, a working .pptx where each slide is a pixel-perfect render rather than rebuilt shapes, multi-page LinkedIn carousel PDFs, and ready-to-post social packs. An AI-generated render recipe handles the parts that trip up screenshots: it waits for fonts to load, picks the right selectors, isolates each slide, and hides the navigation chrome. So the blur, the broken decks, the tall stacked image, and the stray arrows simply stop happening.

The free tier is 10 renders a month with no account needed, so you can fix the export you are stuck on right now and see the difference. Pro is £4.99 a month if you render at volume.