About
A home for interactive artifacts.
The short version: drop in an HTML or JSX file, get a shareable page, a preview image that unfurls nicely in chat, and a profile that collects everything you've made.
What this is
An artifact is anything you can express as a single interactive page — a tool, a visualization, a calculator, a mini-game, an explanation you can click through. artifact.land treats those as first-class objects: each one gets its own URL, cover, profile home, and fork lineage.
Publishing is a drag-and-drop upload or one CLI command. Viewing is a link anyone can open — no account, no paywall, no setup. Artifacts are sandboxed on a separate domain so scripts can't touch your session or leak across origins.
The aim is social, not technical. The frame around an artifact matters less than the artifact itself — and the best ones start conversations, get forked, travel further than their author.
Why now
AI coding tools have made it cheap to generate small, working, interactive programs. A tide of prototypes, bespoke calculators, demos, and explanations is being produced every day — and most of it is stuck inside the chat window that created it.
Existing platforms push that kind of work toward code views, login walls, or dev-tool aesthetics. That's the wrong frame. These artifacts aren't source snippets; they're finished things you can hand to a friend. We wanted a place where the artifact is what you see first — not the repo, not the stack, not a screenshot of the output.
Who's behind it
artifact.land is built by Sublayer, a small software studio. Follow @artifactland for updates and signpost artifacts from the team. Say hi at [email protected] — we read everything.
What's not here
- No ads, no tracking beyond privacy-friendly page counts.
- No AI metering — we don't charge per generation, and we don't gate on it.
- No creator tier that paywalls the features publishers actually need to share work.
- No algorithmic feed tuned to keep you scrolling. The feed is chronological and people-shaped.
If you're new, the guide walks through publishing. If you prefer your terminal, the CLI page has install instructions.