BETA

Theme
Language

How to Turn a Claude Artifact into a Real Website

How to Turn a Claude Artifact into a Real Website

You asked Claude to build something — a budget calculator, a habit tracker, a little dashboard that finally makes your data make sense. The artifact appeared in the panel on the right. It worked perfectly. You played with it for a few minutes, showed someone over your shoulder, and thought: this should be a real thing.

Then the chat session ended.

Now you’re back and the artifact feels harder to find. The person you wanted to share it with can’t open it — they don’t have a Claude account. The URL you sent them shows a login screen instead of your app.

This is the artifact problem, and it happens to everyone.

Why artifacts disappear

Claude artifacts are genuinely impressive, but they live in one place: inside a Claude conversation. That comes with some hard limits.

They’re tied to your account. When you share an artifact link, the person on the other end needs to be signed into Claude to view it. Your coworker, your client, your mom — none of them are clicking a Claude link and getting your app.

They’re tied to the session. Artifacts don’t have their own URL on the internet. They’re not websites. They’re previews that exist inside the Claude interface. You can’t bookmark them, you can’t Google them, and you can’t send someone a link that just works.

They don’t persist data. Most interactive artifacts lose everything the moment you refresh. Your tracker forgets your entries. Your form resets. You start from zero.

An artifact is a demo. A Deplixo URL is a website. The difference is real.

The fastest path: just tell Claude to put it online

Here’s the part most people don’t know: you can connect Claude to Deplixo once — a five-minute setup — and then any time you want something to go live, you just say so. In the same conversation where you’re building. Without copying anything.

You: Build me a habit tracker with daily check-ins and a weekly summary. Put it online with Deplixo.

Claude writes the app and publishes it directly. You get back a live URL and a link to claim the app as your own. Anyone with the link can open it — no Claude account, no sign-in, no friction.

That’s the whole flow. You described what you wanted. Claude built it. Claude put it online. You have a link you can paste anywhere.

The setup takes a few minutes and you never have to do it again. Here’s how.

One-time setup: add the Deplixo connector

Full instructions are in the Deplixo setup guide, but here’s the short version.

On claude.ai

  1. Go to claude.ai/settings/connectors
  2. Click Browse Connectors
  3. Search for Deplixo
  4. Click the + button to add it

Done. Claude can now put your apps online.

Adding the Deplixo connector in Claude settings

On Claude Desktop

Open your MCP config file:

  • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this to the mcpServers section:

"deplixo": {
  "type": "streamablehttp",
  "url": "https://mcp.deplixo.com/"
}

Restart Claude Desktop and you’re set.

How it looks in practice

Once the connector is in place, you just talk to Claude the way you always have — except now you can include “put it online” in the same breath as “build this thing.”

You: Build me a project status tracker where I can add projects, mark them as in progress or done, and filter by status. Make it clean. Put it online with Deplixo.

Claude builds the app, publishes it, and comes back with:

  • A live URL — click it and your app is working, on the real internet, right now
  • A claim link — click this to attach the app to your Deplixo account so you can manage it later

Claude responding with a live Deplixo URL after building an app

Anyone with the link can use the app. They don’t need to know what Claude is. They don’t need an account anywhere. They just click and it works.

What about an artifact you already built?

If you have an existing artifact you want to make permanent — something from an earlier session — the paste flow works great.

  1. Open the artifact in Claude and click Copy code in the artifact panel
  2. Go to deplixo.com/launch
  3. Paste the code into the editor
  4. Click Publish

You’ll get a live URL in a few seconds. This is a good option when you’re starting with something you already have and don’t need to rebuild it.

Pasting artifact code into the Deplixo launch page

The connector approach — where Claude publishes directly — is more seamless for new builds. The paste approach is great when you already have something. Both get you to the same place: a real URL on the real internet.

Keep iterating without starting over

This is the part that makes the connector approach genuinely special.

Stay in the same conversation and ask Claude to make changes:

You: Nice. Can you add a notes field to each project and a way to sort by last updated?

Claude updates the app and republishes it — to the same URL. The link you already shared still works. The people who have it see the updated version automatically. No new setup. No second deployment.

You’re having a conversation with Claude about your app, and every change goes live as soon as you ask for it.

Give it a real address

Apps published without an account live for 30 days — plenty of time to share, get feedback, and figure out whether it’s worth keeping.

When you’re ready to make it permanent, click the claim link Claude gave you. That adds the app to your Deplixo dashboard. From there, you can upgrade to the Personal plan and get a URL like deplixo.com/yourname/your-app instead of the random characters.

A clean address matters more than it might seem. It’s easier to share verbally. It looks intentional. It signals that this is a real thing, not a throwaway experiment — which, after all, is exactly what you were trying to say.

Your app also remembers things

One more thing that makes Deplixo different from running an artifact in a chat window: your app can remember data between sessions.

Tell Claude “make sure the data persists” and it will write the app using Deplixo’s built-in storage layer. Your habit tracker will remember your habits. Your project tracker will remember your projects. The data stays put when you close the tab and come back tomorrow.

This is the gap that most AI-generated apps can’t cross on their own. Artifacts live in the moment. Apps on Deplixo stick around.

What’s next

If you haven’t added the connector yet, the Deplixo setup guide walks through the full process with screenshots for both claude.ai and Claude Desktop. It takes about five minutes.

If you’re curious about the broader problem of sharing AI-built things, How to Share a Claude Artifact with Your Team covers the sharing options in more detail — including why the other options fall short and when each one makes sense.

And if you want to skip straight to seeing it work: go to deplixo.com/launch, paste your artifact code, and get a live URL right now. No account needed. No setup. Just paste and click.

Your artifact is already a real app. It just needs somewhere real to live.