How to turn a Claude artifact into a real app

A Claude artifact can already be a small working app you share by link. When you need your own address, sign-ins, a database or a phone app, here are three routes, from least to most work.

By Brian Boisjoli 6 min read claudeartifactsapp-buildersgetting-started

Short answer: first check whether you need to. A Claude artifact is already a small working app: you can share it by link, and on paid plans it can save data. You need to turn it into a real app when you want your own web address, sign-ins for your users, a real database, payments, or something on the App Store. Then there are three routes: copy the code and host it as a static page, give it to a coding agent such as Claude Code to grow it, or rebuild it on an app platform.

We build VibeKit, one of the routes below. Everything said about Claude here was checked against Anthropic's help center in November 2026.

What can a Claude artifact already do?

An artifact is the window that "opens beside your conversation" when Claude makes something you can use: a calculator, a tracker, a small game, a mockup. Anthropic says "Artifacts are available on Free, Pro, Max, Ultra, Team, and Enterprise plans."

More than people expect:

If a shared link and saved data cover what you need, you may already be done.

When do you need more than an artifact?

Anthropic's pages list a few limits that matter once real people use what you made:

If you need any of those, pick one of the routes below.

Route 1: copy the code and host it as a static page

Good for: a tool that works on its own in the browser, like a calculator or a quiz.

  1. Get the code. Anthropic's help page says: "Use the controls at the top of the artifact panel to view the code, copy the content, or download it." Template artifacts have an Export button instead.
  2. Make it one file. If the code is a single HTML page, it runs as is. If it's a React component (a .jsx file), ask Claude: "Turn this into a single index.html that runs when I open it in a browser."
  3. Put it online. GitHub Pages "takes HTML, CSS, and JavaScript files straight from a repository on GitHub"; on GitHub Free, the repository must be public. Netlify Drop is simpler: "drag and drop a folder of files and it goes live instantly, no account required."

The catch: an artifact's saved data and its calls to Claude come from Claude, so they stop working once the code runs somewhere else. A static page can still keep simple things in each visitor's own browser, like settings or a personal high score (ask Claude to use the browser's localStorage). Data shared between people, data that follows someone to another device or sits behind a sign-in, and calls to an AI model that don't expose your key all need a server. That's Route 2 or 3.

Route 2: give the code to Claude Code

Good for: people comfortable with a terminal who want full control of the code.

Claude Code "reads your codebase, edits files, runs commands". Make an empty folder, save the artifact's code into it, and ask:

This is a Claude artifact. Turn it into a web app with a real database and sign-up, so each user sees only their own data. Keep the look the same.

Claude Code will write the server and database code. Two things stay with you: hosting it somewhere people can reach, and testing it. We cover both in where to host AI apps and how to test an app Claude Code built.

Route 3: rebuild it on an app platform

Good for: people who want the app live without setting up a server, or who want it on a phone.

On VibeKit you describe the app in a chat, from your iPhone or the web, and paste the artifact's code or a screenshot as the starting point. The agent builds it and puts it live at its own address (<name>.vibekit.page). The Free plan costs $0 and includes 2 apps. Paid plans start at $9.99 a month (Starter) and add a database and custom domains.

Two differences from an artifact matter for real users:

Which route should you pick?

You want Route
A tool friends can use from a link Stay with the artifact
The same tool at an address you control, with nothing shared between users Route 1: static hosting
Full control of the code, and you're happy to run a server Route 2: Claude Code
Sign-ins, a database and hosting handled for you, or a phone app Route 3: an app platform such as VibeKit

For the bigger picture of what Claude can build and how, see can Claude build an app?.

FAQ

Can I put a Claude artifact on my own domain? Anthropic's artifact pages don't describe a custom domain option. To use your own, copy the code out (Route 1) and host it, then point your domain at that host, or rebuild it on a platform that handles domains (Route 3).

Will my artifact's saved data come with it? Anthropic's help page describes exporting the code, not the saved data. Plan to start the new app with fresh data, or copy what you need by hand.

Do people need a Claude account to use my artifact? Not to open most shared links. They do need one for the parts that use Claude, and that usage counts against their own Claude plan.

Are artifacts free? Making artifacts is available on the Free plan. Saving data in an artifact needs Pro, Max, Ultra, Team or Enterprise.

Can Claude turn the artifact into an app for me? Yes, with the right tool. In the Claude app it makes artifacts; Claude Code (Route 2) or an app platform running Claude (Route 3) can build the server, database and hosting around it.

Turn your artifact into an app with its own address
Paste the artifact's code or a screenshot, describe what it should do, and VibeKit's agent builds and hosts it at a real URL. Free to start on your iPhone or the web, no card.