# Publish a Claude artifact as a real website To publish a Claude artifact you need the one file Claude hands you: a React component or an HTML page. Drop that file here and it runs at a real HTTPS address, in the visitor browser, with no build step, no npm install and no server. Multi-file projects need a build first, and this page says so rather than guessing. ## What is a Claude artifact, in hosting terms? A single file with no build output. Usually a React component in .jsx or .tsx, often with Tailwind classes, sometimes a complete HTML page. Claude renders it inside its own window; publishing it means running that same file at a public address so anyone can open it without a Claude account. The reason this normally requires a build is that browsers do not understand JSX or TypeScript. Something has to transform them into plain JavaScript first, and that something is usually a bundler running on your machine or on a build server. Here the transform happens in the visitor browser instead, using a runtime served from our own edge along with React and a Tailwind runtime. The result is that a lone component file becomes a working page with nothing installed anywhere. That trick has an honest boundary. It works for one file. A multi-file project has its own Tailwind configuration, a dependency tree and often server code, and rendering it without its real build produces something visually wrong rather than something broken enough to notice. So a project upload is told exactly that, with a link to the three-step export guide, instead of being published as a page that looks almost right. ## How it works 1. **Save the artifact as a file.** Download the artifact from Claude, or copy its code into a file. A React artifact is a .jsx or .tsx; an HTML artifact is a single .html page. That one file is all you need. 2. **Drop the file.** Upload it. The JSX and TypeScript are transformed in the visitor browser by a runtime we host ourselves, with React and the Tailwind classes Claude writes. Nothing you upload ever runs on our servers. 3. **Share the link.** The artifact is live on an HTTPS address you can send to anyone. Upload a new version and the link stays the same, so what you already shared keeps working. ## What you get ### The single-file runtime This is the feature the page exists for. It is scoped deliberately, and the scope is stated everywhere rather than discovered. - A .jsx or .tsx file is transformed in the visitor browser, not on our servers. - React, the JSX runtime and a Tailwind runtime are served from our own edge. - A Babel-flavoured HTML page works the same way. - Nothing you upload is ever executed on our infrastructure. We serve static files. ### Packages are named, not silently fetched An artifact often imports an icon set or a UI kit. Pulling those from a public CDN on your visitors' behalf would run third-party code in their browser and hand that CDN their IP address, so we do not. - The live page lists the missing packages by name instead of rendering blank. - The fix is to build the project locally and upload the output folder. - The deploy guides cover the frameworks those projects usually use. ### One link across every revision Artifacts get regenerated. The address belongs to the site, so the link you sent after the first version still shows the current one. - Up to 25 publishes a day on the free plan. - From Pro, restoring the version that worked is one click. - The switch is atomic; a visitor never sees a half-published page. ### It behaves like a published site, because it is one An artifact at an address gets the same treatment as any other site here, which is more than a share link normally gets. - Password protection from Starter, checked at the edge. - Visitor analytics from Pro. - Expiring links from Starter, for something meant to be temporary. - The deploy-time security check, on every plan, including free. ## What the free plan includes Publishing an artifact costs nothing, and the address does not move when you republish, which matters when most artifacts are shared once and then edited twice. - 1 live site on a real free plan, not a trial of a paid one, and no card to start. - Up to 25 MB per upload and 25 MB of storage across the account. - 5,000 visits and 5 GB of traffic a month. - HTTPS with a real certificate, issued and renewed for you. - Up to 25 publishes a day, so you can iterate without asking permission. - The deploy-time security check, which reads what you published and warns about a stray .env file, a .git folder, a private key or an API key left in your JavaScript. - A small Droply badge in the corner of the page. Removing it starts on Starter. - Free sites are served noindex, so search engines do not list them. Search visibility starts on Starter. ## Compared with Static.app Static.app has its own Claude hosting page, which makes this an unusually checkable comparison: the rows below come from what each product says about the same file. - **Loose .html file accepted.** Droply: Yes, dropped on its own. Static.app: No. Its Claude page states a loose .html file is not accepted and must be zipped. - **React artifact without conversion.** Droply: A single .jsx or .tsx runs at the URL, transformed in the visitor browser. Static.app: No. Its Claude page says React-based artifacts need a self-contained HTML version instead. - **Multi-file project.** Droply: Refused with a named reason and a link to the export guide. Static.app: Accepted as a ZIP of built output. - **Third-party packages.** Droply: Not fetched from a public CDN; the live page names what is missing. Static.app: Depends on the self-contained HTML you supply. - **Free plan.** Droply: 1 site, 25 MB storage, no card, and a plan rather than a trial. Static.app: A 7-day trial with no credit card, then paid. 1 site and 50 MB during it. - **Entry paid price.** Droply: $5 a month for Starter. Static.app: $5 a month, or $60 a year, for 2 sites and 500 MB. - **Password protection.** Droply: From Starter, enforced at the edge. Static.app: Not listed on any of its plans. - **Security check on deploy.** Droply: Every publish, every plan, free included. Static.app: Not offered. Static.app figures checked 8 September 2026 on its own pricing page (free tier: 1 site, 50 MB, a 7-day trial with no credit card; Starter $5 a month or $60 a year for 2 sites and 500 MB with a custom domain; Medium $10; Large $15) and on its Claude hosting page, which states that a loose .html file is not accepted and must be zipped, that React-based artifacts need an extra step because you have to ask Claude for a self-contained HTML version, that Import from URL takes claude.ai and claude.site links, and that the first 7 days are free with no credit card. Product plans can change. ## When Droply is the wrong choice The single-file runtime is a real capability with a real edge, and the edge is where people get disappointed. These are the cases it does not cover. - Your artifact is a multi-file project. Build it locally and upload the output; nothing here renders a project without its build. - It imports packages beyond React. They are not fetched for your visitors, so the page will name them rather than render them. - It calls an API that needs a secret. A published page is readable by anyone, so any key inside it is public the moment it goes live. - You need a database, a login system, or code that runs on the server. Droply serves files; it does not execute your application. - You want a build to run on every push to a repository. Droply has no Git integration and no CI: you build locally and upload the result. - You are running WordPress or another PHP application. A static export of it can be hosted here, but the application itself cannot. ## Frequently asked questions ### What is a Claude artifact, in hosting terms? A single file with no build output: usually a React component in .jsx or .tsx, sometimes with Tailwind classes, or a complete HTML page. Publishing it means running that same file at a public URL. ### Do I need to run npm or a build step? No, not for a single-file artifact. The JSX and TypeScript transform happens in the visitor browser using a runtime served from our own edge, with React and a Tailwind runtime included. Nothing is installed and nothing runs on our infrastructure. We still only ever serve static files. ### What about packages the artifact imports? React and the JSX runtime are provided. Any other package, such as an icon library or a UI kit, is not fetched from a public CDN on your behalf: that would run third-party code and leak your visitors' IP addresses to it. The live page lists the missing packages by name, and the fix is to build the project locally and upload the output. ### My artifact is a whole project with several files. Does that work? Not in the browser. A multi-file project has its own Tailwind config, dependency tree and often server code, and rendering it without its build would come out visually wrong. Upload it and the page says exactly that, with a link to the three-step export guide. ### Can I publish artifacts from ChatGPT, v0, Lovable or bolt.new the same way? A single HTML or JSX file from any of them, yes: the path is identical. Lovable and bolt.new exports are usually full projects, so they take the build-first route. There is a page per tool covering the export and what breaks: ChatGPT, v0, Lovable, bolt.new, and the rest are listed on the AI hosting hub. ### Is the published artifact a static site? Yes. It has no server, no database and no server actions. If the artifact calls an API, that API has to exist somewhere else and allow requests from a browser. ### Can I put a password on it? Yes, from Starter. The password is checked at the edge before any file is served, so the runtime and its assets are covered as well as the page. ### Can I update the artifact after sharing the link? Yes. Upload the new file and it is published at the same address, so the link you already sent shows the current version. From Pro you can also restore an earlier one. ### Is it free to publish an artifact? Yes: 1 site with HTTPS, 25 MB of storage and 5,000 visits a month, with no card and nothing to claim afterwards. ### Will the artifact be indexed by search engines? Not on the free plan, which is served noindex on purpose. Indexing starts on Starter if you want the page found rather than just shared. ## Related - [Host an AI-Generated Website](https://droply.host/host-ai-generated-website) - [HTML to URL](https://droply.host/html-to-url) - [HTML Hosting](https://droply.host/html-hosting)