AI Artifact
Definition
An AI artifact is output the assistant treats as an object rather than as more chat text. Instead of a wall of code in the reply, you get a thing you can click, read or look at, and you change it by asking for changes. The most common shape is one HTML file with the CSS inside a style tag and the JavaScript inside a script tag; other shapes include a React component the chat compiles in the browser, plain Markdown, or an SVG. Libraries the page needs are usually pulled from a public CDN when it loads rather than installed anywhere. The artifact belongs to the conversation: it renders because the chat window renders it, and someone without access to that conversation sees nothing. Assistants differ from one another and both change over time, so check what yours currently does before you rely on a specific detail.
Why It Matters
The gap between having an artifact and having something you can send is wider than it looks. Inside the chat it is tied to your account and your session, and a colleague you forward a screenshot to cannot press the buttons. Published as a file, the same 90 KB of HTML answers a URL that anyone can open on a phone, with no login and no install. The usual cost of getting this wrong is not technical — it is a working prototype nobody outside the conversation ever actually used, and one archived thread away from gone.
How It Works
Publishing an artifact is mostly a copy-and-save job. You take the artifact's source, save it as a file called index.html, and upload that file to a host that serves static files over HTTPS. The host stores the bytes, sends them back with a Content-Type of text/html, and that is the whole pipeline — no build, no npm install, no server process. Anything the page fetches from a CDN, such as a chart library or a font, is loaded by the visitor's browser at the moment they open the page, so those requests have to work from the public internet rather than from inside the chat. Anything that needed a server stays broken: a database write, a secret API key, a sign-in.
Real-World Example
A product manager builds a pricing calculator as an artifact — sliders for seats and contract length, a total that updates as she drags. It is about 120 KB of HTML with everything inline. She saves it as index.html, uploads it to 99helpers and picks a name, and it answers at acme-pricing.99helpers.site a few seconds later. The sales team opens it on their phones mid-call, and the conversation it came from stops mattering to anyone but her.
Common Mistakes
- ✕Sharing a link to the chat conversation instead of the file — anyone without access to that conversation, or without an account on that assistant, sees nothing at all
- ✕Saving the page under a name like artifact.html — a static host serves index.html by default, so the file will not answer at the root of the address
- ✕Assuming work the artifact saved while you used it in the chat travels with the file — the storage it used belongs to the browser and the address, and a new address starts empty
- ✕Leaving an API key in the source because it worked during the chat — once the page is public, the key is public with it
Related Terms
Claude Artifact
A Claude artifact is a self-contained piece of work Claude renders beside the conversation rather than printing as chat text — commonly a single HTML page or a React component — which you can view, iterate on and share.
ChatGPT Canvas
Canvas is a side-by-side editing surface in ChatGPT for documents and code. The work opens in a panel next to the conversation, where you can edit it directly or ask for changes to one part of it, rather than regenerating the whole reply each time.
Artifact Hosting
Artifact hosting is putting something an AI assistant built for you — usually one HTML file — at a public web address, so it can be opened by anyone with the link instead of only inside the conversation that produced it.
Single-File Web App
A single-file web app is a complete, working application contained in one HTML document, with the styles and the JavaScript written inside the same file. Open it in a browser and it runs — there is nothing to install and nothing to build.
Static File Hosting
Static file hosting serves files exactly as they were uploaded, byte for byte, with no code running on the server to assemble the response. Every visitor to a given address gets the identical bytes back.
Put a file online in seconds
Drop in a document, an image, a page or a whole static website and share the link — free, with no build step and no server to set up.
Host a file free →