Official Claude public-share size limit
Not documented
Anthropic's Artifact help articles do not publish a fixed megabyte cap for public sharing.
Troubleshooting · Updated September 16, 2026
Claude Artifact Too Large to Share? Keep the Full Version Online
If Claude says this version can't be shared publicly, the Artifact may still work for you. Size is one publicly reported cause. Plan rules, Claude Code sharing limits, and unpublished viewer restrictions can produce the same error. Do not treat every Publish failure as a 16 MB cap.
Why does Claude say “This version can't be shared publicly”?
The usual message is: “This version can't be shared publicly. Publish a new version or change the shared version, then try again.” People report that the Artifact still opens in the private viewer, and that repeating Publish does not clear the error.
Size is one plausible cause in recent public cases. It is not the only cause. Official Claude docs also say Team and Enterprise Artifacts can only be shared inside the organization, and Claude Code Artifacts cannot be shared publicly at all. A content-security restriction on the public viewer is another unconfirmed suspect in third-party write-ups.
Is there a Claude Artifact size limit?
Anthropic does not currently document a fixed public-sharing size limit for Claude Artifacts. Recent third-party reports suggest large rendered Artifacts around the mid-teens of megabytes can fail to publish publicly, but this is an observed threshold rather than an official limit.
A September 2026 third-party report describes a self-contained design-system Artifact of about 13–14 MB that viewed fine privately and failed public sharing after several republishes. Some guides mention about 16 MiB. Neither figure appears in Anthropic's help center, so do not quote it as Claude's official cap.
Third-party observation
Mid-teens MB
Public reports describe rendered Artifacts around 13–16 MB failing to publish. This is not an official limit.
HTMLShare guest upload
1 MB HTML · 3 MB ZIP
Temporary no-login previews. Too small for most oversized Claude Artifacts.
HTMLShare signed-in project
5 MB HTML · 20 MB total
Use one HTML file under 5 MB, or extract images and assets into a ZIP whose unpacked files total 20 MB or less.
What makes a Claude Artifact too large?
Claude Artifacts are often one self-contained HTML document. Everything the page needs has to live in that file, which is convenient until the inlined payload outgrows public sharing.
Base64 images and data URIs
Claude often inlines screenshots and icons so the Artifact stays self-contained. Base64 encoding makes those images about a third larger, and a handful of screenshots can add several megabytes.
Inlined React, ReactDOM, and Babel
Interactive Artifacts may paste full libraries into the page instead of loading them once. Nested iframes can repeat the same libraries several times.
Embedded fonts and large SVG
Self-contained pages sometimes include font files and detailed SVG as data URIs. Those blocks are easy to miss in the visual preview and expensive in the saved HTML.
Nested iframes and srcdoc pages
A design-system or multi-demo Artifact may wrap each example in its own document. Each nested document carries its own CSS, scripts, and images.
Embedded datasets and JS bundles
Dashboards that ship the full dataset, plus a bundled charting script of a megabyte or more, grow with the data rather than with the visible UI.
Option 1: make the Artifact smaller
Shrink first when the extra weight is accidental — uncompressed screenshots, duplicated libraries, or a dataset you do not need in the page.
Measure the saved HTML
Copy the Artifact code into a local file and check its byte size. If it is already above 10 MB, inspect the largest Base64 or script blocks first.
Replace inlined images
Compress screenshots and swap data URIs for ordinary image files with relative paths. This is usually the largest saving.
Stop duplicating libraries
Ask Claude to keep one copy of React or a chart library, or to load an allowed CDN if the published Artifact still renders.
Flatten iframes and trim data
Prefer one document with sections over a document of documents. Chart a summary of the dataset instead of embedding every row.
Publish a new version
The share check runs against the version you publish. Editing and re-sharing an old version does not rerun the check on the new file.
Option 2: export and host the full Artifact
Keep the full version when shrinking would remove the point of the page — a complete design system, an offline demo, or a report with baked-in charts. The path is: Claude Artifact → copy or export HTML → upload to HTMLShare → browser URL.
HTMLShare limits: guest uploads are 1 MB HTML and 3 MB ZIP. Signed-in projects accept one HTML file up to 5 MB and a total project up to 20 MB. A 13–14 MB self-contained Artifact will not upload as a single HTML file. Extract images, fonts, and data into a ZIP first. HTMLShare publishes static files only and does not replace Claude Artifact storage, MCP, or AI-powered Artifact features.
Open the Artifact
Confirm it still works in the private Claude viewer. If the private copy is already broken, fix that first.
Copy or export the HTML
Use the code view, copy control, or download action. Save the current version as artifact.html.
Make it portable if it is over 5 MB
Ask Claude for a standalone HTML file or an index.html plus assets folder with relative paths. Extracted images usually compress below the original Base64 size.
Upload to HTMLShare
Sign in, then upload the HTML file (5 MB max) or a ZIP whose files total 20 MB or less. Guest uploads stop at 1 MB HTML and 3 MB ZIP.
Send the browser URL
Open the preview yourself, then share the link. Recipients do not need a Claude account.
Large Claude Artifact hosting vs Claude Publish
Use Claude Publish when the Artifact is small enough, your plan allows a public or org link, and reviewers should stay in Claude's sharing experience. Use independent HTML hosting when you need the full static page, a client who should not open Claude, or a snapshot that is no longer tied to the chat.
NeedClaude PublishHTMLShareWhy
Iterate inside Claude
Best fit
Not the job
Keep prompting and previewing in the Artifact window.
Public link on Free, Pro, or Max
Works when publish succeeds
Standalone preview URL
Claude public links follow Anthropic's publish rules; HTMLShare serves the exported static snapshot.
Team or Enterprise sharing
Org-only
Anyone with the preview URL
Official Claude docs say Team and Enterprise Artifacts cannot be published publicly.
Claude Code Artifact
Not publicly shareable
Host the exported HTML
Anthropic documents Claude Code Artifacts as private or org-visible, never public.
Keep a 10 MB+ self-contained page
Public share may fail
ZIP under 20 MB after extracting assets
HTMLShare does not accept a single HTML file over 5 MB. Split images and assets first.
Client review without Claude
Depends on publish/share mode
Normal browser URL
The recipient opens the rendered page, not the Claude conversation.
Claude Artifact works privately but won't publish
Work through this order before you rewrite the whole page.
- 1. Confirm the Artifact still renders privately.
- 2. Check the plan: Team and Enterprise cannot publish publicly; Claude Code Artifacts also cannot be public.
- 3. Publish a new version after a real content change, or create a new Artifact. Re-sharing the old version is not enough.
- 4. Save the HTML and measure the file size.
- 5. Inspect embedded images, fonts, iframes, libraries, and datasets.
- 6. Shrink a copy, or export a portable HTML/ZIP and host it outside Claude.
What if the Claude Artifact link says “Page not found”?
That is a different problem from the size error. On September 1, 2026, GitHub issue #91126 reported that the Artifact tool became unavailable mid-session in Claude Code, and previously published Artifact URLs then returned “Page not found.” Around September 15, 2026, GitHub issue #94434 reported the Artifact tool missing in Claude Code 2.1.268. Neither report is a documented size limit. See Claude Code Artifact tool missing for the publish-unavailable path.
If the published URL 404s, recover from local source files if you still have them, then publish a static HTML or ZIP copy. HTMLShare cannot restore a Claude-hosted Artifact that Anthropic has already dropped.
How to make a Claude Artifact portable
Ask Claude for a copy that does not depend on the Claude viewer. Keep the look and interactions, switch to relative asset paths, and prefer one HTML file or an index.html plus assets folder.
Create a portable version of this Artifact for external static hosting. Preserve the current appearance and interactions. Use relative asset paths, remove dependencies on the Claude viewer runtime, and produce either one standalone HTML file or an index.html + assets folder.
FAQ
Common questions
Why is my Claude Artifact too large to share?
Public sharing can fail when the rendered HTML is very large, usually because of Base64 images, inlined libraries, nested iframes, or embedded datasets. Size is a common reported cause, not a confirmed official rule, and other sharing restrictions can produce a similar failure.
What is the Claude Artifact size limit?
Anthropic does not currently document a fixed public-sharing size limit. Third-party reports describe public-share failures around the mid-teens of megabytes. Treat that as an observed threshold, not an official Anthropic number.
Why does Claude say “This version can't be shared publicly”?
The full message usually asks you to publish a new version or change the shared version. That can happen after a large render, after a Team or Enterprise org-only share rule, on Claude Code Artifacts that cannot be published publicly, or for another unpublished reason. Do not assume every instance is a size error.
Can I host a large Claude Artifact somewhere else?
Yes, if you can export static HTML. Copy the Artifact code, save it as a file or a ZIP of index.html plus assets, and publish it on a static host. Recipients can open a normal browser URL without a Claude account.
How do I export a Claude Artifact as HTML?
Open the Artifact, switch to the code or source view, and copy the HTML. You can also download the file from the Artifact window. For a portable version, ask Claude to emit a standalone HTML file or an index.html plus assets folder with relative paths.
How do I reduce Claude Artifact file size?
Measure the saved HTML first. Replace Base64 images with compressed files, remove duplicate inlined libraries, minify CSS and JavaScript, flatten nested iframes, and keep large datasets out of the page. Then publish a new Artifact version rather than re-sharing the old one.
Can I host Claude Artifact HTML without Claude?
Yes. Once the page is ordinary static HTML, CSS, JavaScript, and assets, it can run in a browser outside Claude. HTMLShare publishes that static output as a noindex preview link. It does not reproduce Claude-only features such as Artifact storage, MCP tools, or AI-powered Artifact APIs.
Why does my Claude Artifact work privately but not publicly?
Private viewing and public publishing are different checks. Public sharing can fail because of size, plan rules, Claude Code public-share restrictions, or content that the public viewer will not run. Keep the private copy, then either shrink a new version or export the HTML.
Why does my Claude Artifact URL say Page not found?
That is a separate Claude Code issue from the size error. A September 1, 2026 GitHub report describes Artifact URLs returning Page not found after the Artifact tool became unavailable in the same session. Recover from local files and publish a static copy if you still need a shareable link.
Can HTMLShare host a large Claude Artifact?
Yes, within HTMLShare's current static limits. Guest uploads are 1 MB for HTML and 3 MB for ZIP. Signed-in projects accept a single HTML file up to 5 MB and a total project up to 20 MB. A 10 MB+ self-contained file usually needs extracted assets in a ZIP, not a single oversized HTML upload.
Need the full Artifact as a browser link?
Export the HTML, stay under HTMLShare's 5 MB file and 20 MB project limits, and send a standalone preview URL. Sign in first if the Artifact is larger than the 1 MB guest HTML cap.