Claude artifact too large to share.

What the failure looks like

The complaint arrived twice this month in two places. On X, someone noted their Claude artifact was "apparently too large to share" and that this was not an obvious limitation. On GitHub, a Claude Code user filed the fuller version: a self-contained design-system showcase of roughly 13 to 14 MB rendered HTML, with several iframes carrying inlined React, ReactDOM and Babel, a 2 MB bundled script, and a handful of small SVG data URIs. It viewed perfectly in private. Every attempt to share it publicly returned the same line: "This version can't be shared publicly. Publish a new version or change the shared version, then try again."

They did what the message says. Republished with confirmed content changes, several times. Published the identical content to a brand-new artifact. Same result. The issue was closed as stale with no response naming the cause.

What is documented, and what is not

Anthropic's help center article on publishing and sharing artifacts covers who can view a published artifact (anyone with the link, no sign-in), the Team and Enterprise rule (org-only, never public), and unpublishing (permanent; the same artifact cannot be published again). It does not mention a size limit, a reason publishing can fail, or what the error above means.

Third-party guides fill the gap with a number: a rendered size of about 16 MiB, with large embedded images as the most common cause. The GitHub reporter's 13 to 14 MB page sits just under that, which suggests the public-share check is stricter than the render limit, or that something else in the page (scripts assembled with new Function, which a tighter content security policy on public pages would refuse) is the trigger. Nobody outside Anthropic has confirmed which. The practical rule is the same either way: above about 10 MB, expect trouble.

Where the weight comes from

• Images as data URIs. A base64 image is a third larger than the file it encodes, and Claude embeds them by default because the artifact has to be self-contained. Four screenshots can be 8 MB.
• Inlined libraries. React, a charting library, Babel for JSX, each pasted into the page rather than loaded from a CDN. The GitHub case had these inside several iframes, so the same libraries were counted more than once.
• Iframes with srcdoc. Each nested document carries its own full copy of everything it needs.
• Generated data. A dashboard that embeds the dataset it charts, rather than a summary of it, grows with the data.

Five ways to get under the limit

1. Measure it. Open the artifact's code view, copy it into a file, and look at the byte count. If it is over 10 MB, find the largest blocks first; they are almost always image data.
2. Host the images elsewhere. Replace data URIs with URLs to images you host, and compress them on the way. This is usually the whole fix.
3. Load libraries instead of inlining them. Ask Claude to reference React or the chart library from a CDN rather than pasting it in, and check the artifact still renders, since published artifacts run under a content security policy that allows some hosts and not others.
4. Flatten the iframes. One document with sections, rather than a document of documents.
5. Split it. A showcase can be three artifacts with links between them. Each publishes on its own.

Then publish a new version. The share check runs against the version you share, so re-sharing the old one after editing does nothing, which is what the error message is trying to say.

Or move the page

Sometimes the size is the point. A design system with every component rendered, a report with the charts baked in, a demo that has to work offline. Shrinking it would make it worse. In that case take the HTML out of Claude and host it somewhere with room.

On Stacktree a page can be 25 MB on the free plan, 250 MB on Solo and 1 GB on Firm. Copy the artifact's code and paste it, or from Claude Code let the agent publish it in one MCP call. What comes back is a private link that opens with no Claude account, which is more than the public artifact link offered anyway: add a passcode if the page is for one client, set an expiry if it is a review copy, put it on your own domain if it is going out under your name, and replace it in place when the next version is ready. The size check that failed you was Anthropic's public-share gate. There is no equivalent here, because the page was never going to be public.