Host a Claude Artifact as a Website Without Downloading It

The short answer

Yes, if the Artifact is a static page and you still have the Claude conversation that created it. Turn on the Birta connector in that conversation, ask Claude to turn the selected Artifact into an ordinary static site, inspect the Birta draft preview, and approve publication only when it works.

No HTML download or dashboard upload is involved. Claude already has the source in the conversation, and the connector lets it write that source into a Birta draft. This is not a public-Artifact-link importer, and it does not move Claude-only AI, storage, or connector features to another host.

First check whether you need a separate host at all. Anthropic's Publish action already gives a qualifying Artifact a link on Claude. Use that when the Claude link, access rules, and runtime are the finished result. Use the workflow below when a compatible static page should become a separately hosted site that your agent can update through Birta.

If that choice is not obvious, the Artifact-link-versus-owned-site guide owns the comparison. This page begins after you have chosen the separate site.

For the broader definition and the differences between normal, AI-powered, Claude Code, and Cowork output, read the Claude Artifacts guide. This page has one narrower job: moving a suitable Artifact from its source conversation to a hosted static site.

Check that the Artifact can leave Claude

The easiest candidate is a self-contained HTML page. A Markdown document, SVG, diagram, or simple interactive component can also work if Claude can express it as normal HTML, CSS, and browser JavaScript. Birta needs index.html at the site root; styles, scripts, images, and fonts can sit beside it or in subfolders.

Run a compatibility check before creating the project:

• Usually suitable: a one-page site, report, calculator, diagram, portfolio, or prototype whose behavior runs entirely in the browser.
• Needs conversion: an interactive React Artifact that relies on Claude's preview packages or component library. Claude must rewrite or bundle it into browser-ready files, and exact visual parity is not guaranteed.
• Does not transfer as-is: a Claude-powered Artifact, persistent Artifact storage, Artifact connector calls, user accounts, a database, private keys, or any server-side action. Those are runtime capabilities, not static files.
• Needs an asset check: uploaded images and fonts. Claude may be able to write them through the connector, but a file it cannot access as bytes still needs a separate, authorized source. “No download” is not a promise to recover missing assets.

Publish it from the same Claude conversation

1. Step 1Select the sourceOpen the conversation that created the Artifact and switch to the exact version you want to host.
2. Step 2Enable BirtaTurn on the Birta connector for this conversation and authorize it the first time Claude asks.
3. Step 3Create a draftAsk Claude to check compatibility, create a project, write static site files, and return a preview without publishing.
4. Step 4Check and publishTest the preview, request fixes in the same chat, then explicitly approve publication.

Step 1: Select the source version

Open the original conversation, open the Artifact panel, and use its version selector to display the exact revision you want. If the conversation contains several Artifacts, name the intended one in your request. “The pricing calculator on the right” is safer than “the Artifact.”

Do not start from only its public link. The useful advantage here is that Claude has the current source and the surrounding instructions in the same context.

Step 2: Enable Birta in that chat

Follow the current Claude connection guide to add Birta as a custom connector. Then enable Birta from the conversation's connector menu. On first use, Claude opens Birta in your browser so you can sign in and approve access.

Anthropic notes that custom connectors can take actions for you. Connect only to a server you trust, read the requested permissions, and check write actions before approving them. Its current connector documentation is the source of truth for Claude's controls and organization rules.

As a quick connection test, ask Claude to list your Birta projects. If it can, the same conversation is ready for the site request.

Step 3: Give Claude a bounded publishing prompt

Replace the project name in this prompt and send it while the intended Artifact version is open:

Use the current version of the Artifact in this conversation as the source.

First, check whether its visible behavior can run as a static website with a root
index.html and ordinary browser files. Tell me what will change or stop working,
especially any Claude-powered calls, persistent storage, connector actions,
private data, or server-side behavior.

If it is compatible, create a new Birta project named “Client calculator.” Create
an unpublished draft, rewrite the Artifact into index.html plus any CSS,
JavaScript, images, or fonts it needs, and give me the draft preview URL. Do not
publish it until I have checked the preview and explicitly approve publication.
Do not try to import a public Artifact URL.

The compatibility answer matters more than the happy path. If Claude says the Artifact depends on a feature that cannot run on a static site, decide whether to simplify that feature, rebuild it using a suitable external service, or keep the Artifact on Claude. Do not ask the model to hide the limitation.

Step 4: Check the preview before it goes live

Open the preview Claude returns and test the result as a website, not as a still image:

• check the page on a narrow phone width and a desktop width;
• use every button, link, tab, calculator control, and keyboard path;
• confirm that images, fonts, icons, and external links load;
• compare important copy and values with the selected Artifact version;
• check that no placeholder, private prompt text, or test data appears;
• verify that a feature described as removed really is absent or clearly replaced.

Ask for fixes in the same chat. Claude edits the draft while the live site, if there is one, stays unchanged. When the preview passes, say: “Publish this Birta draft and give me the live URL.” Open that URL and repeat the critical checks.

What “without downloading” removes

The connector does not make the conversion disappear. It changes who carries the files between systems.

The owner still makes the important decisions: which version is the source, whether conversion losses are acceptable, whether the preview is correct, and when it can go live. The eliminated work is the repeated local file handoff.

What happens behind the prompt

Claude does not send an Artifact object to Birta. It uses Birta's connected operations to create an ordinary site:

1. Project: Claude creates the name and standard site address.
2. Draft: it creates an unpublished version with a separate preview address.
3. Files: it writes index.html and any supporting browser files one at a time. Other draft files stay intact when one file changes.
4. Validation: Birta checks the root page and accepted static file types. A failed check leaves the draft available to fix.
5. Publication: a separate action makes that checked draft live and returns the site URL.

This distinction is why the process can work without a download while still being honest about portability. Claude translates source it can already see; Birta stores and serves the resulting website. It does not preserve the Artifact as an Anthropic runtime object.

If the phrase “connector” is unfamiliar, the plain-language MCP guide explains how an agent receives safe, named actions from another product.

Fix the common failures

Claude uses the wrong Artifact or version

Stop before it writes more files. Open the intended version, name the Artifact and a distinctive piece of its content, then ask Claude to restate which source it will use. Delete the mistaken empty draft or ask Claude to overwrite it only after the source is unambiguous.

Claude cannot see Birta tools

Make sure Birta is enabled for this specific conversation, not merely present in account settings. Ask Claude to list your projects. If that fails, return to the current Claude setup guide and reconnect rather than pasting credentials into the chat.

The draft cannot publish

The most important structural rule is a root index.html. An index.html inside another folder is not the start page for this draft. Ask Claude to list the draft files, put the finished entry page at the root, repair its relative asset paths, and publish again. A validation failure should leave the draft intact.

The preview is blank or looks different from Claude

The Artifact may depend on React packages, generated styles, or components that exist in Claude's preview but not in a normal browser page. Ask Claude to identify every runtime import and replace it with portable HTML, CSS, and JavaScript. Do not accept “it should work” without reloading the preview and using the controls.

If accurate conversion would require a package build that Claude web cannot perform in this flow, use a file-capable coding agent instead. Claude Code has a separate Birta connection guide; this page does not pretend the two products have the same path.

Images or fonts are missing

Look for temporary Claude URLs, references to conversation attachments, and absolute paths that only worked in the Artifact sandbox. Ask Claude to list every external asset and confirm that Birta received each file. If Claude cannot access the original bytes, obtain the asset from its authorized source. This is the case where a manual file handoff may be unavoidable.

An AI or saved-data feature disappeared

That is not a hosting glitch. Anthropic documents AI-powered calls, Artifact connectors, and persistent storage as features of its own Artifact runtime. Ordinary static files do not carry those services with them. Keep the native Artifact, remove the feature, or design a replacement before publishing; Birta does not turn those dependencies into a backend.

Update the hosted site later

After the first publication, the Birta site no longer depends on finding the original Artifact conversation. In a later Claude chat with Birta enabled, ask Claude to list the project and its versions, create a draft from the live version, make the requested edit, and return the new preview.

The public URL keeps serving the current version while you review. Publishing the draft updates that URL. If the change is wrong, Claude can restore an earlier published version without deleting the newer history. The edit-and-republish guide covers that ongoing loop in more detail.

Frequently asked questions