CLAUDE ARTIFACTS AND STANDALONE SITES
Publish a Claude Artifact as a website.
An Artifact can be shared in Claude. A standalone website is a set of files deployed to a host you choose.
Choose the right export for your artifact.
Sharing an artifact gives people access through Claude; it does not put a standalone site on your domain. Access depends on the artifact type and account settings. Public publishing and embed controls apply to legacy artifacts.
For a current Design artifact, click Export and choose standalone HTML or a ZIP. For a legacy artifact, use the panel controls to view code, copy content or download it. Other templates export different formats, so a document or slide download is not necessarily a website.
Check what the export includes. Claude-powered features may depend on Anthropic’s infrastructure or user authentication, and exported files may reference external services. Test the result and replace those dependencies before treating it as standalone.
See Anthropic’s guides to artifact types and export and sharing artifacts.
Prepare files a web host can serve.
Download or recreate the complete site.
Collect the HTML pages, CSS, JavaScript, images, fonts, and any other referenced assets. Put the homepage in
index.html. Preserve folders and filenames so the links in the code resolve. Remove private keys or environment settings.Check whether a build is needed.
If the output is already plain browser files, it can be uploaded as a static site. If you have React or another framework’s source components, run the project’s documented build process first and locate its generated output directory. A component or design preview alone is not the complete built site.
Open the result locally.
Check all pages, navigation, images, and responsive layout. Static files do not supply server logic, a database, secure accounts, or data processing for forms. Any such behavior needs a separate service, and Artifact AI functions may need to be redesigned for that host.
Deploy the standalone folder.
For a manual upload, drag the ready folder or ZIP into Netlify Drop. No Git repository is needed. Claim an unsigned upload and check its visibility settings before sharing the netlify.app URL. If the files need a build, sign in and submit the project so Netlify can detect and run supported build steps; otherwise submit the built output. Re-upload the updated output to publish later changes. The official Drop guide explains deployment and visibility.
You can choose another static host that accepts your files. Check its deployment method, ownership, usage rules, custom-domain instructions, and ongoing update process before relying on it. Then test the public URL on phone and desktop before changing DNS.
Benchlight is another hosting workflow.
The Benchlight assistant connector can create a private draft from static website files, within 100 files and 3 MB per request. To publish through Benchlight, use its website UI and a Benchlight hosting plan. Its assistant connector does not publish, buy hosting, or change DNS. You can follow the standalone Netlify steps above without Benchlight.