How to Host and Publish a Claude Artifact Online

Claude can design and build a complete web page for you right inside a chat, but that page lives in Claude as an "artifact." It is not a real website yet: there is no clean public link you can hand to a client, post on social media, or point a domain at. To turn that artifact into a real website, publish its HTML as a static site: paste the artifact's public link into Static.app's "Import from URL", or save the HTML as index.html, zip it and upload the ZIP yourself, and either route gives you a live URL in a couple of minutes, for free.

What is a Claude artifact?

An artifact is the preview panel Claude opens when it generates something self-contained, such as an HTML page, a small web app, or a landing page. You can see it and click around inside the Claude interface, and Claude gives you a shareable artifact link. That link, though, opens inside Claude's own viewer wrapped in Claude's interface. That artifact link is perfect for showing a draft. It is not your own website, and you cannot attach your own domain to it. For a fuller tour of Claude artifacts, including what else Claude can build in one and how publishing works, see what are Claude artifacts.

Why host it as its own website?

Hosting a Claude artifact as its own website gives you four things an artifact link cannot: a public URL that needs no Claude account, your own custom domain, plain static files that load fast, and a page that keeps working after the chat is gone.

• A clean, permanent URL you can share anywhere, with no Claude account needed to view it.
• Your own custom domain instead of a viewer link, so the page looks like a real product.
• Speed and control: the page is served as plain static files, so it loads fast and stays exactly as you published it.
• Longevity: your live website keeps working even if the original chat is gone.

How to publish a Claude artifact on Static.app

Publishing a Claude artifact takes one of two routes, and both end with a live URL. Route one imports the artifact's public link, so the page is fetched and packaged for you. Route two copies the artifact's HTML out of Claude and uploads it as a zipped index.html, which is the route to pick when you want to edit the file before it goes live.

Option 1: Import straight from the artifact link (fastest)

1. In Claude, open your artifact and use Publish to give it a public link, then copy that link. Publish is the action on the Free, Pro, and Max plans. Share, on Team and Enterprise, keeps the artifact inside your organization instead, so a shared link will not open for a client. Publish and Share work this way as of August 2026, per Anthropic's Help Center.
2. Go to Static.app Claude hosting, click "Import from URL", and paste that link into the "Claude Artifact URL" field.
3. Your artifact is fetched and packaged as a ready-to-publish website. Confirm, and you get a live URL right away.

Option 2: Copy the HTML and upload it

1. In Claude, open the artifact's code view and copy the full HTML.
2. Save it as a file named index.html. If you want to tidy it first, run it through the HTML formatter or preview it in the HTML viewer.
3. Zip that file, then drag the ZIP onto Static.app's HTML upload and publish. The uploader takes a ZIP, so zip the file even when it is the only one.

Add your own domain

You connect a custom domain to a hosted artifact from your dashboard, once the website is live. Add the domain, then point its DNS at Static.app. The artifact then lives at your own address instead of the subdomain it launched on. A custom domain is not included on the free plan, so this step needs a paid plan (see pricing). This is the step that turns an AI draft into something you can put on a business card.

Updating the page later

You update a published Claude artifact from your dashboard, on the website you already created, and the URL and any custom domain stay the same. Open that website's files, then either edit index.html in the built-in editor and paste the new version over the old one, or delete the old index.html and upload the new file. Uploading a file that shares a name with one already there does not replace it, it arrives under a new name, so delete first if you want a clean swap. Importing again from the Claude hosting page does not update the old website, it starts a new one, which on a single-website plan is the wrong route.

Common questions

The three answers below cover what hosting a Claude artifact costs, whether interactive artifacts still work, and how artifacts made of several files are handled.

Is it free?

It is free to start. A new account opens on a 7-day trial covering one website, 50 MB of storage, a free subdomain in the form yoursite.static.domains, and an SSL certificate, with no credit card asked for. You create that account as part of your first upload, and your website goes live right away. Publishing after the trial ends needs a paid plan, and so does a custom domain, so check pricing for both.

Will interactive artifacts work?

Interactive Claude artifacts keep working once they are hosted as a static website. Anything that runs in the browser works: HTML, CSS, and client-side JavaScript. Artifacts that need a server or a database behind them will not run as a static website, because there is no backend to talk to.

What about multi-page or multi-file artifacts?

Put every file your artifact needs (HTML, CSS, images, scripts) into one folder with index.html at the top level, then zip that folder and upload the ZIP. The whole folder is served as one website, so links between your pages keep working.