Most artifact problems are one setting. Artifacts do not work unless Code execution and file creation is switched on, under Settings then Capabilities, and almost every guide online still points at a Feature Preview menu that no longer does this. Check that first. If it is already on, the next most likely cause is an ad blocker, since artifacts render in a sandboxed frame that privacy extensions tend to block.
You ask Claude for something that should open in the side panel and it does not. Or the panel opens and stays blank. Or it says the artifact failed to load.
The frustrating part is that the most common cause is a setting, and the instructions for finding that setting have changed, so most of the advice you will find points somewhere that no longer exists.
Which one are you seeing?
No panel opens at all, Claude just writes the content into the chat
The capability is off. Fix 1, and it is not where older guides say it is.
The panel opens and is blank, white, or empty
Something is blocking the frame it renders in. Usually an extension. Fix 2.
A shared or published artifact link opens blank for someone else
Different problem with its own causes. See the section on published artifacts.
Fix 1: turn on Code execution and file creation
This is the one. Artifacts are no longer supported without it.
On Free, Pro and Max: click your initials in the lower left, go to Settings, then Capabilities, and switch on Code execution and file creation.
On Team and Enterprise: an owner does this at Organization settings, then Capabilities. If you are not an owner you cannot turn it on yourself, and this is worth knowing before you spend an afternoon on browser settings.
If you have read elsewhere that this lives under Feature Preview, that was true once and is not now. It is the single most repeated piece of out-of-date advice on this topic.
Fix 2: the panel is blank
Artifacts render inside a sandboxed frame on a separate domain, which is deliberate and is also exactly the pattern privacy extensions block.
Open the same conversation in a private window, where extensions are usually disabled. If the artifact appears, an extension is your cause. Ad blockers and anti-tracking extensions are the usual ones. Re-enable them one at a time to find which, then allow claude.ai and its artifact domain.
If private browsing does not fix it, clear claude.ai’s site data. A stale cached copy of the app produces exactly this symptom, and it explains the version of this problem where it worked yesterday and nothing changed.
Fix 3: try a different browser
Chrome and the desktop app are the best-supported paths. If you are on Safari or Firefox and getting blank panels or load failures, testing in Chrome tells you in one minute whether the browser is the cause.
On mobile, viewing artifacts works but editing and iterating is poor. If you are doing real work with artifacts, do it on desktop.
Fix 4: work and school networks
Because artifacts load from a separate sandbox domain, a network can allow claude.ai and still block the thing artifacts render in. That produces a working chat with a permanently blank artifact panel, which looks like a product fault and is not.
Test on your phone’s mobile data. If artifacts work there, ask whoever runs your network to allow Claude’s artifact domain as well as claude.ai, and mention that they are different hosts, because allowing only the main domain is the usual mistake.
Published and shared artifacts
Two things surprise people here.
Artifacts you create in a conversation do not appear in the Artifacts section of your sidebar on their own. You have to open the artifact and publish it. If you are looking for something you made last week and cannot find it, it is in the conversation, not the sidebar.
Publishing and sharing also mean different things by plan. On Free, Pro and Max, publishing makes an artifact available to anyone with the link. On Team and Enterprise, sharing keeps it inside your organisation and viewers have to be signed in. If a colleague reports a blank page from your link, check whether they needed to be signed in to your organisation and were not.
When the artifact itself is broken
Worth separating a platform problem from a code problem, because they look identical from the outside.
If the panel opens, shows a frame, and something inside it errors or renders wrong, that is the artifact’s own code and not the artifacts feature. Ask Claude to fix it, and paste the error if there is one. Many interfaces offer a button that does this for you.
The tell is consistency. A capability or extension problem breaks every artifact. A code problem breaks one.
How to avoid it next time
Check the Capabilities setting before troubleshooting anything else, especially on a new account or a work one where an admin may control it.
Keep one browser with a clean extension setup for anything that renders in a frame. It saves a lot of time across more tools than this one.
And publish anything you want to find again, or it stays inside the conversation you made it in.
Written by the team at Lead Source, who build lead attribution software and hit this the first time an artifact opened blank and every guide pointed at the wrong menu.