Skip to main content
You asked Claude (or ChatGPT, or v0) for “a clickable prototype of my app idea” and got back a folder: an index.html, maybe a few more pages, some images. It works when you open it locally — now you need to put it in front of a few people for feedback. Deploying it to Vercel or Netlify works, but it’s overkill: you don’t want a build pipeline and a project dashboard, you want a link you can text someone. That’s exactly what Shareable is for.

​
What “prototype” means here

The kind of thing this guide covers — and what Shareable runs perfectly:
  • A clickable prototype — screens that link to each other, buttons that change state, a multi-step flow a stakeholder can walk through.
  • An app mockup — the UI of an app idea, fully interactive, with no real backend behind it yet.
  • An MVP front-end — a real interface that talks to an existing API or form endpoint (a Google Apps Script, an Airtable form, a public API).
All of these are static files that run in the browser. That’s the line: if it’s HTML, CSS, and JavaScript that runs client-side, Shareable hosts it as-is.

​
Publish it

1

Drop the folder in

On your pages, drag the whole folder Claude gave you (or a .zip of it) into the upload area. The index.html becomes the landing page; its images, CSS, and JS come along as bundled assets. No need to inline anything.
2

Name it and create a draft

Give it a title. You get a private draft you can preview and click through before anyone else sees it.
3

Choose who can see it

Publish, then in Share pick an access mode — anyone with the link, a password, specific invited people, or anyone with a verified email. See Sharing & access.
4

Send the link, gather feedback

Copy the link and send it. Turn on comments so reviewers can leave feedback right on the prototype, add a poll to ask “which direction?”, and watch analytics to see who actually opened it.
Prefer your agent? Ask Claude directly: “publish this prototype to Shareable and give me the link.” With the MCP server connected it uploads every file — pages and assets — and hands back the URL. See Publish from AI.

​
What works

Shareable serves your files raw, with no sandbox — so the prototype behaves exactly as it does on your machine:
  • Full interactivity. Inline <script>, click handlers, page transitions, canvas, Web Components — all of it runs.
  • Multi-page click-throughs. Relative links between pages (href="dashboard.html") resolve within your prototype.
  • Real assets. Images, stylesheets, fonts, and JSON ship alongside the HTML.
  • Calls to an existing backend. A fetch() to an API you already have, a form that POSTs to a Google Apps Script or Formspree, a public data source — these work, because the call happens from the viewer’s browser, same as anywhere.
  • Feedback built in. Comments, polls, view analytics, and email-on-view turn a prototype link into a feedback loop — the part a deploy pipeline doesn’t give you.

​
When you need real app hosting instead

Shareable hosts the front end. The moment your prototype needs a server of its own, it’s graduated into an app, and you want a platform like Vercel or Netlify:
You need…Use
A clickable prototype, mockup, or static MVP front-endShareable
Server-side code / your own API routes / SSRVercel / Netlify
A database, or user accounts for your app’s usersVercel / Netlify + a backend
A build step (Next.js build, bundler, env-var secrets)Vercel / Netlify
A custom domain per project, on a deploy pipelineVercel / Netlify
A useful way to hold it: Netlify and Vercel are for running apps; Shareable is for sharing them. If the thing already runs by opening an HTML file, you don’t need a deploy — you need a link with access control and feedback. If it needs to run code on a server, you need the deploy.
Secrets don’t belong in a prototype. Anything in your HTML or JS — including API keys — is visible to anyone who can open the page. That’s true on any static host. For a prototype calling a backend, use a public/read-only endpoint or a key scoped to do no harm; keep real secrets server-side, which means real app hosting.
When you paste a prototype link into iMessage or Slack, it shows a preview card. Set the link preview — a title, description, and image — from the Share dialog, or point og:image at one of your bundled images. A polished card makes “here’s my prototype” land better.