Inspiration
Claude artifacts examples
The examples
Build one of these today
Business proposal artifacts
An interactive proposal with scope, timeline, and a live pricing table the client can explore, instead of a 12-page PDF attachment. The kind of artifact people most often publish behind a password.
Build a single-file HTML proposal for [client] covering scope, timeline, and pricing. Clean, professional design, an interactive pricing table with three tiers, mobile-friendly, all CSS inlined.Calculator & tool artifacts
ROI calculators, quote builders, savings estimators: small single-purpose apps that run entirely in the browser. Great as a leave-behind after a sales call: the prospect keeps playing with their own numbers.
Build a single-file HTML ROI calculator for [your service]. Inputs: [the variables]. Show the result as a headline number plus a simple chart. No external libraries, all CSS and JS inlined.Dashboard & report artifacts
Paste your numbers into Claude and get back a designed status report: charts, tables, and a narrative summary. Republish each month to the same link and the recipient always opens the current one.
Turn this data into a single-file HTML dashboard: [paste your data]. Include a summary section, 2–3 charts, and a detail table. Inline everything: no external files or API calls.Product demo artifacts
A clickable walkthrough of your product or concept: screens, flows, and copy a prospect can step through at their own pace, on their own time.
How teams send client demos →Build a single-file HTML clickable demo of [product]: 4–5 screens the viewer steps through with next/back buttons. Realistic UI, mobile-friendly, all assets inlined.Pitch deck artifacts
A web-native deck: keyboard navigation, responsive layout, animation that survives because it’s never flattened to PDF. Publish it as a link and you’ll know which day the investor opened it and how long they stayed.
Why founders track their decks →Build a single-file HTML pitch deck for [company]: 10 slides, arrow-key and click navigation, bold typography, mobile-friendly. All CSS and JS inlined, no external assets.The next step
Publish your own example
An artifact only becomes useful when someone else can open it. As of October 2026, an artifact shared through Claude opens only for people signed in to Claude, unless it is a published legacy artifact. Publish it as a Pagelive link (say “publish this” in Claude or upload the HTML file) and it opens in any browser with no Claude account, noindex by default.
Then you’ll know what happened after you hit send: a view count on every page, and on Solo and Team unique viewers and reading time, with bot opens filtered out.
Frequently asked
Yes, they’re here to be copied. Paste one into Claude, swap in your own details, and iterate from there. The single-file/inline-everything wording matters: it’s what makes the artifact render reliably once published.
Three ways: Claude’s own Share menu (viewers need a Claude account as of October 2026; only legacy artifacts get a public Publish link), the Pagelive connector (say “publish this” in Claude), or export the artifact’s HTML and upload the file. A Pagelive link is noindex by default and opens for anyone, in under two minutes.
No. You describe what you want, Claude writes the HTML, and publishing is a sentence or a drag-drop. The prompts on this page are plain language: the bracketed parts are the only thing you change.
Yes. Every Pagelive page shows a view count, and Free emails you the first time each page is opened. Solo and Team add unique viewers, reading time, by-day, country, and referrer (with bot opens filtered out), and an email on every open.
More guides: Claude artifacts: what they are, how to share and publish them · how to use Claude artifacts · share an artifact without a login. Sending a proposal you built? See AI proposal software.