Claude artifact won't load? 5 fixes that work in 2 minutes

Something went wrong with your Claude artifact. Before you start troubleshooting, narrow down which problem you actually have — the fix is different for each case.

• The artifact loads fine for you, but not for the person you shared it with. This is a sharing and authentication problem — the most common one. Start at Fix 1.
• The artifact won't load for you, even in your own Claude account. This is a browser or feature-settings problem. Start at Fix 2.
• The artifact loads but shows a blank screen or an error message. This is a code or compatibility problem. Start at Fix 3.

Fix 1 — If the recipient sees a sign-in wall

This is the most common report. Claude artifact links point to claude.ai, which requires authentication. When someone you sent the link to doesn't have a Claude account — or isn't logged in — they see a login page before they see your artifact. This affects anyone who doesn't already use Claude regularly. For the full explanation, see why Claude artifacts don't work for people without an account.

Option A: Ask them to create a free Claude account. Claude has had a free tier since February 2026. Basic artifacts work for free users. The downside: you're asking someone to sign up for a service just to view something you sent them. Expect some friction, especially for clients and non-technical recipients.

Option B: Host the HTML on a public URL. Every Claude artifact is standard HTML. If you host it outside of claude.ai, anyone can view it — no account, no subscription. ShareDuo does this in about 30 seconds. Download the artifact from Claude, upload it to ShareDuo, and share the new link. Anyone can open it in any browser.

Fix 2 — If the artifact won't load for you either

If you're logged into Claude and your own artifact isn't loading, check these in order:

Check that artifacts are enabled. Go to Settings → Feature Preview and make sure Artifacts is toggled on. This setting can reset after some account changes.

Try incognito mode or a different browser. Browser extensions — particularly ad blockers, privacy extensions, and script blockers — frequently break the Claude artifact preview pane. Open an incognito window (which disables extensions by default) and try again. If the artifact loads in incognito, an extension is the culprit. Disable them one at a time to find the offender.

Try the desktop app vs the web app. Claude's desktop app (macOS and Windows) runs in a slightly different environment. If the artifact works in one and not the other, that narrows down a browser-specific issue.

Hard refresh the page. Press Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows) to bypass the cache. Stale cached resources occasionally prevent artifacts from loading after Claude updates.

Fix 3 — If the artifact loads but is blank or showing errors

This is a code problem, not a sharing problem. A few common causes:

Click "Try fixing with Claude" if the button appears. Claude often detects runtime errors and offers to repair the artifact automatically. This fixes the problem about half the time. If no button appears, open the browser console (F12 → Console), copy the error message, and paste it back to Claude with a note to fix it.

External CDN resources getting blocked. Claude's artifact sandbox allows most external CDN scripts, but some firewalls, corporate networks, or browser security settings block them. If your artifact uses Chart.js, Google Fonts, or any CDN-hosted library, these might fail silently. Ask Claude to inline the critical styles or switch to a self-contained version.

Missing default props in React components. If Claude built a React component that expects props but renders without them, you'll get a blank output. Ask Claude to add default prop values so the artifact renders something on its own.

localStorage usage. Claude artifacts run in a sandboxed iframe that blocks localStorage and sessionStorage. If the artifact tries to read or write to local storage, it will either throw an error or silently fail. Ask Claude to rewrite persistent state using in-memory variables or URL parameters instead.

Fix 4 — If embedding on another site doesn't work

Claude's embed flow requires you to configure allowed domains before the iframe will render for visitors. Go to the artifact's Publish settings and add your site's domain to the allowed-domains list. This is easy to miss if you copied the embed code without completing that step.

Two other common causes of broken embeds:

• Mixed content. If your site is served over HTTPS but the iframe URL is HTTP (or vice versa), browsers block the request. Make sure both URLs use the same protocol.
• Iframe sandbox attributes. If you're adding the iframe manually to your HTML, avoid sandbox="allow-scripts" without also adding allow-same-origin — artifacts need both to function.

If the allowed-domains config feels like too much overhead for what you're trying to do, the simpler path is to export your artifact as a standalone HTML file and upload it to ShareDuo, then use that URL in your iframe. No domain configuration required — and the URL works for anyone who clicks it directly, too.

Fix 5 — Last resort: deploy the artifact as a static site

If you need permanent hosting with a custom domain and full control, you can take the artifact HTML and deploy it as a static site. Options include Vercel, Netlify Drop, or GitHub Pages — all have free tiers and accept single HTML files.

There are also open-source artifact runner tools on GitHub that automate this workflow for developers who want to run Claude artifacts locally or deploy them with a CI pipeline. These are worth exploring if you're a developer who regularly publishes artifacts as part of a product.

For everyone else, ShareDuo is the faster path — no deploy configuration, no custom domain setup, no CI pipeline. Upload the HTML and get a link in seconds.

Frequently asked questions

Why does my Claude artifact say "page not found"?

A "page not found" error usually means the artifact URL is broken or the artifact was deleted from Claude. Re-publish the artifact and use the new link. If you need a stable URL that doesn't disappear when you modify the conversation, ShareDuo generates a permanent link from the HTML file itself.

Why is my Claude artifact blank?

Blank artifacts are usually caused by a JavaScript error, a blocked external resource, or the artifact relying on localStorage (which doesn't work in the Claude sandbox). Open the browser console (F12), copy the error, and paste it back to Claude with a request to fix it.

Can I share a Claude artifact with someone who doesn't have an account?

Not via Claude's Publish button — those links require the viewer to be logged in. Use ShareDuo to host the artifact HTML on a public URL. Anyone can open it without a Claude account. See our full guide on sharing Claude artifacts without login.

Why does my Claude artifact work for me but not for others?

You're already logged in to Claude. The person you sent the link to isn't — so they see a login page. The fix is to host the HTML outside of claude.ai. ShareDuo does this in about 30 seconds.

Are Claude artifacts down right now?

Check status.anthropic.com for Claude's current service status. If Claude is loading but artifacts aren't working, the issue is more likely a browser extension, feature toggle, or sharing configuration rather than a system-wide outage.