From Claude Design to Instagram: The Missing Step Nobody Warns You About

There is a specific moment every Claude Design user eventually reaches. You have iterated on a carousel, it finally looks right, and now you want to post it on your feed. You find the PNG option in the artboard menu, download slide one, and realise there are nine slides to go, none of them sized for Instagram unless you set it up that way.

Ten minutes later you're still downloading.

What you actually get when you “export”

Anthropic's Claude Design hands you plenty of ways to move your work elsewhere: a zipped project, a PDF, a PowerPoint file, a self-contained HTML page, a jump straight into Canva, Gamma or Claude Code, and now a PNG of a single artboard at 1x or 2x.

What it doesn't hand you is a set of pictures sized for a platform.

That sounds odd for a design tool, but it makes sense once you understand what Claude Design is doing behind the curtain. Your “design” is a small piece of software. It is code running in a browser tab, which is exactly why the sliders, hover effects, and animations feel alive. A living web page has no fixed pixels. So the tool exports the code, documents generated from it, or a snapshot of one artboard at whatever size that artboard happens to be.

The trouble is that social platforms don't accept code, and they are fussy about size. Instagram, Facebook, LinkedIn, and X all want image files at a specific size, and a carousel wants one per slide, all matching.

Screenshotting: the trap disguised as a solution

Faced with a carousel and a one-at-a-time export, plenty of people still do the same thing. Zoom the canvas, line it up, hit the screenshot shortcut.

It works once. Then the problems compound:

• Your monitor becomes the ceiling. A screen grab can only ever be as sharp as your display. Feed that soft capture through a platform's compression and the text edges go fuzzy. Your design looked professional in the canvas; the post looks like a photo of a design.
• No two platforms agree on size. A feed post, a Story, a LinkedIn banner, and a YouTube thumbnail all demand different pixel dimensions (the size guide lists them all). A screenshot gives you one arbitrary rectangle, so you're off to a second tool to crop and stretch, and the composition you carefully balanced gets butchered along the way.
• It never ends. Client wants one word changed? New screenshot, new crops, all five sizes, again. The generation took two minutes; the exporting eats your afternoon.

Render the code instead of photographing the screen

Here is the reframe that fixes everything: Claude Design already gives you the perfect source. That HTML export isn't a consolation prize, it's the original. The smart move is to render it directly into images at exact dimensions, skipping the screen entirely.

Renda was built for precisely this job:

1. Grab the standalone HTML (or the zip) from Claude Design's Export menu (under Share inside a Claude conversation).
2. Drop it into Renda.
3. Choose where the design is headed. Renda re-renders the code at the platform's exact shape and hands back sharp, correctly sized PNGs, every slide in one go.

Because the output comes from the design's own code rather than a picture of your screen, there is nothing lost in between. What Claude generated is what lands in your download folder, at the size you pick. Five free PNGs a month (each slide counts as one), no card and no account required.

One bonus: if you have tried the built-in PowerPoint export and watched your layout fall apart on complex slides, Renda repairs that too. Anything past a basic layout tends to arrive scrambled, and getting a usable deck back out has been one of the most requested fixes.

A gap that is narrowing (use what fits the job)

Let's be honest: Claude Design now has a native PNG button, one artboard at a time. For a single graphic that is already the right size, take it.

But a carousel is not a single graphic, and your content calendar won't wait. Right now, every Claude Design user posting a carousel is either downloading slides one by one, screenshotting (and losing quality), or rendering the HTML properly in one pass. If your designs are meant to be seen anywhere outside that canvas, the last path is the one that respects the work you put in.