Plan or organization setting
Claude Code Artifacts require Pro, Max, Team, or Enterprise. Team plans are on by default. Enterprise needs an Owner to enable Artifacts. CMEK, HIPAA, or Zero Data Retention can block them.
Troubleshooting · Updated September 17, 2026
Claude Code Artifact Tool Missing? Turn the Local HTML Into a Link
If Claude Code has already generated the HTML but its Artifact publishing tool is unavailable in your session, you can host the local HTML or static ZIP separately instead of waiting on the built-in publish path. Anthropic still documents Artifacts as a Claude Code capability. A missing tool is not proof it was permanently removed.
Why is the Claude Code Artifact tool missing?
Official docs say: if Claude cannot publish, or writes a local HTML file without a link, the tool is not enabled for your session. That can come from documented availability conditions, a local disable flag, or a reported regression. Separate those before assuming a product shutdown.
Login vs API key session
Official docs require a session backed by a claude.ai account via /login. Sessions using an API key, gateway token, or cloud-provider credential cannot publish.
Model provider
Artifacts are documented for the Anthropic API. They are not available on Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry.
SDK, Actions, or print-mode surfaces
The tool is off by default in Agent SDK, GitHub Action, and MCP-server contexts. Separate reports also say print mode (claude -p) often does not load Artifact even with enableArtifact true.
Local disable flags
enableArtifact false, CLAUDE_CODE_DISABLE_ARTIFACT=1, CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC, or an Artifact deny permission can hide the tool even when your plan is eligible.
Version or feature-flag regression
A September 15, 2026 report says 2.1.268 stopped exposing the tool while the feature code remained in the binary. Treat that as an availability report, not a documented removal.
Quick fix: publish the local HTML instead
The usual path is: Claude Code creates report.html → upload report.html to HTMLShare → copy the browser URL → share. Multi-file projects should keep this shape:
site/ ├── index.html ├── styles.css ├── script.js └── assets/
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. HTMLShare publishes static files only. It does not replace Claude Artifact storage, live session updates, MCP connectors, comments, or AI-powered Artifact features.
Keep the local file
If Claude wrote report.html or index.html instead of returning a claude.ai/code/artifact URL, that file is already the publishable output.
Package a ZIP when needed
A self-contained HTML file can upload directly. A folder with CSS, JavaScript, images, or fonts should become a ZIP with index.html at the expected entry.
Ask for a portable copy
Tell Claude Code not to depend on the Artifact viewer runtime. Prefer relative asset paths and keep client-side interactions working.
Upload to HTMLShare
Sign in for 5 MB HTML or 20 MB total. Guest uploads stop at 1 MB HTML and 3 MB ZIP.
Send the browser URL
Open the preview yourself, then share the link. Reviewers do not need Claude Code, a Claude account, or a local folder.
Check whether Artifacts should be available
Work through Anthropic's published requirements before treating a missing tool as a version bug.
Plan
Pro, Max, Team, or Enterprise
Free-plan Claude.ai conversation Artifacts are a different product surface from Claude Code publish.
Authentication
/login to claude.ai
API keys, gateway tokens, and cloud-provider credentials cannot publish Artifacts.
Provider
Anthropic API
Bedrock, Google Cloud Agent Platform, and Microsoft Foundry sessions cannot publish.
Surface
CLI 2.1.183+ or desktop 1.13576.0+
Off by default in Agent SDK, GitHub Action, and MCP-server sessions.
Org policy
No CMEK / HIPAA / ZDR
Owners can also turn Artifacts off, or keep public sharing off on Team and Enterprise.
Local settings
enableArtifact not false
Also check CLAUDE_CODE_DISABLE_ARTIFACT and permissions.deny for Artifact.
Claude Code 2.1.268 Artifact tool disappeared
GitHub issue #94434, opened September 15, 2026, reports that the built-in Artifact tool stopped appearing in interactive, SDK/headless, and print-mode sessions after an update to 2.1.268, even though Artifact feature strings remained in the binary.
The reporter said the same account could publish from 2.1.223 through 2.1.263, then lost the tool everywhere after 2.1.268. They also said a retained 2.1.263 binary failed in print mode on September 14, 2026. That second detail is consistent with a server-side flag or with print mode never exposing the tool, not only with a client removal.
The 2.1.268 changelog still lists Artifact publish fixes and does not announce a removal. Anthropic's current Claude Code Artifacts documentation still treats publishing as a supported feature. Do not write 2.1.268 as a permanent behavior.
Artifact publish alternative for local HTML
Use Claude Artifact publishing when the tool is available and you want live session updates, org sharing, or connector-backed pages. Use independent static hosting when you already have a local HTML snapshot and need a URL that does not depend on the Artifact tool.
NeedClaude ArtifactHTMLShareWhy
Iterate inside Claude Code
Best fit when the tool is available
Not the job
Keep prompting and republishing in the session.
Publish after the Artifact tool is missing
Blocked until availability returns
Host the local HTML/ZIP
The file already exists on disk. Independent hosting does not wait on the Artifact tool.
Live session updates on the same URL
Built-in when publish works
Replace on Pro or Max
Claude Artifacts update in place. Pro and Max HTMLShare users can keep one preview URL across revisions.
MCP live data or AI-powered Artifact APIs
Claude-only
Static snapshot only
HTMLShare serves files. It does not run Claude connectors or Artifact APIs.
External images, fetch, or extra CDNs
Blocked by Artifact CSP
Ordinary browser page
Claude's viewer allows a short CDN allowlist and blocks most external images and fetch.
Client review without Claude
Depends on share mode
Normal browser URL
The recipient opens the rendered page, not the coding session.
Other third-party tools also publish local Claude HTML to independent URLs, including CLI publishers and paste-to-URL hosts. HTMLShare is a last-mile fallback when the next job is a static preview link, not a Claude-hosted Artifact.
Ask Claude Code to make the output portable
If the page still assumes the Claude Artifact viewer, ask for a copy that can run as ordinary static files.
Prepare this output for external static hosting. Create either one self-contained HTML file or an index.html with relative asset paths. Do not depend on the Claude Artifact viewer runtime. Keep all client-side interactions working.
What if my existing Artifact URL says Page not found?
That is a different issue from the 2.1.268 missing-tool report. GitHub issue #91126, opened September 1, 2026, describes the Artifact tool becoming disabled mid-session, after which previously published Artifact URLs returned Page not found.
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. If the current problem is only that the tool is missing and old URLs still load, host a new snapshot rather than assuming the old link is gone.
Size-related public-share failures are another separate path. See Claude Artifact too large to share.
Claude Artifact CSP vs external HTML hosting
Claude Code wraps the published file in an HTML shell with a strict Content Security Policy. That is useful inside Claude and a common reason a page that works locally looks broken after Artifact publish.
External images
Claude Code's Artifact CSP blocks every external image. Claude inlines images as data URIs instead. Independent HTML hosting can load ordinary image files.
Fetch, XHR, and WebSockets
Official docs say fetch, XHR, and WebSocket calls may reach only the page's own origin and Google Fonts hosts. A static host uses normal browser network rules for that origin.
Scripts and CDNs
Allowed script hosts are cdnjs, the Tailwind and jQuery CDNs, and selected jsDelivr paths such as /npm/. Other external scripts and stylesheets are blocked.
Single-page shell
An Artifact is one self-contained page. Relative links to sibling files do not resolve. A ZIP with index.html plus assets can keep a small static project together.
When to use HTMLShare instead
Use HTMLShare when the Artifact tool is unavailable, when reviewers should not open Claude, or when the page needs ordinary browser behavior that Artifact CSP will not allow.
- 1. Local HTML reports and generated documentation
- 2. Dashboards that already have the data baked in
- 3. PR walkthroughs and annotated diffs saved as HTML
- 4. Prototypes, presentations, and static demos
- 5. Client review when the Artifact tool is unavailable
FAQ
Common questions
Why is the Artifact tool missing in Claude Code?
Official Claude Code docs say Artifacts require a supported plan, a session signed in with /login, the Anthropic API, and an eligible organization policy. The tool is also off by default in Agent SDK, GitHub Action, and MCP-server sessions. If those conditions are met and the tool is still absent, treat it as a session or availability issue, not a confirmed product removal.
Did Claude Code remove Artifacts?
No public Anthropic changelog says Artifacts were removed. Claude Code 2.1.268 still documents Artifact publish fixes. Anthropic's Claude Code docs continue to describe Artifacts as a current capability. One September 15, 2026 GitHub report says the tool disappeared in 2.1.268 while the feature code remained in the binary.
Is Artifact broken in Claude Code 2.1.268?
GitHub issue #94434 reports that the Artifact tool was missing in interactive, SDK/headless, and print-mode sessions after updating to 2.1.268. The same report notes that a retained 2.1.263 binary also failed in print mode on September 14, 2026. That is not enough to treat 2.1.268 as a permanent break.
How do I publish HTML when Claude Code Artifacts are unavailable?
Use the local file Claude already wrote. Upload a self-contained HTML file, or zip index.html with relative CSS, JavaScript, images, and other assets, then publish it to a static host. HTMLShare turns that snapshot into a browser URL.
Can I host Claude Code output without claude.ai?
Yes, once the page is ordinary static HTML. Recipients open a normal browser link and do not need a Claude account. HTMLShare does not reproduce Claude-only Artifact features such as live session updates, MCP connector calls, comments, or AI-powered Artifact APIs.
Can I upload a Claude Code HTML file directly?
Yes. 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. If the HTML references local assets, zip the folder with index.html at the expected entry.
Why does Claude Code say the Artifact tool is disabled?
The official docs list several disable paths: enableArtifact false, CLAUDE_CODE_DISABLE_ARTIFACT=1, an Artifact deny permission, organization policy, or a session that is not signed in with a claude.ai account. GitHub issue #91126 also describes the tool becoming disabled mid-session, which is a different report from the 2.1.268 missing-tool case.
What is an alternative to Claude Code Artifact publishing?
Any static HTML host that accepts a file or ZIP can publish the local output. HTMLShare is one last-mile option when you already have report.html or an index.html project and need a shareable preview URL. Other third-party tools also publish Claude Artifact HTML to independent URLs.
Need a URL while Artifact publish is unavailable?
Upload the local HTML or ZIP, stay under HTMLShare's 5 MB file and 20 MB project limits, and send a standalone preview URL. Sign in first if the file is larger than the 1 MB guest HTML cap.