You built a landing page, a proposal or a small tool in v0, Lovable or Bolt.new, and the preview link is not the thing you want to send: it expires, it carries a badge, or it needs an account. If what you have is one self-contained HTML file, host it on Hostus: a stable link with SSL in seconds, text edits in place on the same link, private or email-gated access, and any form in the page stores its responses without a backend. If what you have is a React project with a build step, Hostus is not the fit; deploy it on Vercel or Netlify. Vendor facts were checked on the tools' own docs on 2026-09-07.
Single HTML file or build output? Decide this first
Every tool here can produce two different things, and the host follows from which one you have.
- A single HTML file. One
.htmlwith CSS and JavaScript inline. It opens by double-clicking and needs no server. This is what Hostus hosts: the right shape for a landing page, a proposal, a report, a calculator or a form page. - A framework project. A folder with
package.jsonand a build command (React, Next.js, Vite, TanStack Start). It needsnpm run build, often server routes, and belongs on Vercel, Netlify or the tool's own hosting. A build folder can be uploaded to Hostus, but it is not the fit: no server routes, no SSR.
If you see package.json in the export, you have the second. That is the default for v0, Lovable and Bolt; all three can be talked into the first for a page that needs no backend, with the same prompt:
Rewrite this as a single static HTML file, no framework, no build step. All CSS and JavaScript inline, no external files or CDN links. If there is a form, use a plain <form method="post"> with a name on every field and no action URL.v0 by Vercel: what it exports and where to host it
What it exports. v0's docs state that it uses Next.js, React, TypeScript, Tailwind CSS and shadcn/ui, so the default output is a framework project. You can export the code to work locally, sync it to GitHub (v0 commits generated changes to the working branch automatically), or download a chat's code as a ZIP from the project menu. Publishing goes to Vercel: Publish, then Publish to Production.
Single file possible? Yes, for a page without server logic: ask for a single static HTML file, no framework, and copy the result.
Where forms go by default. Nowhere in a static export. A v0 form only reaches a server action or API route if v0 wrote one and you deployed the project with it.
Share links. v0's deployment docs describe preview deployments with unique URLs and a stable production URL on Vercel; who can open the app depends on your team's plan and deployment protection settings. The docs we read state no expiry for preview URLs, so check them.
Where to host. Single HTML file: Hostus. Next.js project: Vercel, where the Publish button already sends it.
Lovable: what it exports and how long the preview link lasts
What it exports. Lovable's FAQ says new apps created after 13 May 2026 use TanStack Start with server-side rendering, older projects run React and Vite, and styling is Tailwind. You can download the codebase as a zip from the code editor or from Project settings, then Git, and connect the project to GitHub. Publishing puts a snapshot at [subdomain].lovable.app; a published site stays live indefinitely, with no expiry. Custom domains are on paid plans.
Single file possible? Yes, for a static page: ask for a single static HTML file, no framework, and copy it from the code editor.
Where forms go by default. Lovable's FAQ names its built-in backend (Lovable Cloud) and Supabase as where form data is stored. A static HTML export has neither and posts nowhere until a host catches it.
How long a share link lasts. This is the number people search for, and it is on docs.lovable.dev: a shared preview link gives anonymous, view-only access to the latest in-progress version of your app, anyone with the link can open it without a Lovable account, and links expire after 7 days by default. On Free and Pro the expiry cannot be changed once the link is created; on Business and Enterprise you can choose 24 hours, 7 days, 30 days or no automatic expiration. The published lovable.app site does not expire.
Where to host. Single HTML file: Hostus, which has no expiry timer (revocation is instant instead), so the link you send on Monday still opens the Monday after. Framework project: Lovable's own publish, or Vercel or Netlify from the GitHub repo.
Bolt.new: what it exports and where its free hosting stops
What it exports. Bolt's help center says you can download a project as a zip: click the project title in the top left, then Export, then Download, and run it locally with npm install && npm run dev. That command tells you what you have: a framework project. Bolt also connects to GitHub and to Netlify; for a manual Netlify deploy its docs say to run the build command, download, and use Netlify's drag-and-drop.
Single file possible? Yes, for a static page: ask for a single static HTML file, no framework, and copy it from the file view.
Where forms go by default. Nowhere, until you connect a backend.
Share and hosting links. Publishing puts the project at a free bolt.host address; on the Free plan the site shows a Made in Bolt badge, has up to 10 GB of bandwidth and 333,333 requests a month with a hard limit, and stays offline until the next billing cycle once it hits the limit. Pro hosting comes with every paid subscription; custom domains are paid. The project share link is different: collaborators must have a Bolt account and be signed in. The docs we read state no expiry for either link.
Where to host. Single HTML file: Hostus, with no badge, no bandwidth cutoff on a client's page, and a reader who needs no account. Framework project: bolt.host, or Netlify through Bolt's integration.
Claude Code and Claude Design: the short version
Claude Code writes files directly, so ask it for one self-contained HTML file and you have one. It can also publish an artifact: a single HTML or Markdown page served from claude.ai, private until you share it, on Pro, Max, Team and Enterprise. Its docs are clear that an artifact is a static page with no backend and cannot store data submitted through a form. To publish the same file to Hostus from inside Claude Code, add the connector once with claude mcp add --transport http hostus https://app.hostus.io/api/mcp; Claude can then upload, update on the same link, and read form responses. Details in Claude connectors for publishing.
Claude Design (beta on Pro, Max, Team and Enterprise) exports as a .zip, PDF, PPTX or standalone HTML, and shares projects within your organization with view, comment or edit access. For a reader outside your organization, export the standalone HTML and host it on Hostus: no Claude account needed, email-gated if you want, form still working.
Which tool exports what, and where to host it
"Check docs" means the vendor page we read on 2026-09-07 did not state it. The last two columns are the decision.
| Tool | Default export | Single file possible? | Share link expiry (verified) | Forms by default | Host: single file | Host: build output |
|---|---|---|---|---|---|---|
| Any tool, single HTML file | One .html, CSS and JS inline | Yes (that is the file) | Hostus: no expiry; instant revocation | Stored on Hostus, no backend, 100 a month free | Hostus: edit in place, private or email-gated, reading by section | Not the fit |
| v0 by Vercel | Next.js, React, TypeScript, Tailwind, shadcn/ui; ZIP or GitHub | Yes, ask for it | Check docs (none stated) | Nowhere in a static export | Hostus | Vercel |
| Lovable | TanStack Start (SSR) or React + Vite; zip or GitHub | Yes, ask for it | Preview links: 7 days by default; Business and Enterprise: 24 h, 7 d, 30 d or never. Published site: none | Lovable Cloud or Supabase in the app; nowhere in a static export | Hostus | Lovable publish, Vercel or Netlify |
| Bolt.new | Framework project (npm run dev); Export then Download, or GitHub | Yes, ask for it | Check docs (none stated); free hosting stops at 10 GB or 333,333 requests a month | Nowhere until a backend is connected | Hostus | bolt.host or Netlify |
| Claude Code | Whatever you ask for; artifacts are one HTML or Markdown page | Yes, natively | Artifacts: none stated; private until shared | Artifact cannot store form input | Hostus (via the connector) | Vercel or Netlify from the repo |
| Claude Design | .zip, PDF, PPTX, standalone HTML | Yes, standalone HTML export | Org-scoped share link; check docs | None | Hostus | Not applicable |
Which host should you pick?
Default to Hostus when the export is a single HTML file and a person who matters will open it. The link does not expire and has no badge. You fix the copy in the browser without regenerating in the tool, and every save is a version you can restore. You can make the page Private or Email-gated and see who opened it and which sections they read. A form stores its responses in an inbox, emails you each one, and can redirect to a thank-you page from the Responses tab.
Unless the export is a framework project: then Vercel for v0, Lovable's publish or Vercel or Netlify for Lovable, and bolt.host or Netlify for Bolt. Unless nothing rides on the page: then the tool's own preview link, or Claude's Publish button, is fine. Unless you need a custom domain, which Hostus does not offer; GitHub Pages does it free for a static file.
Good to know before you switch
Hostus has no custom domain: the link is always your-slug.v.hostus.io. It hosts single HTML files, optionally with a folder of images, video and fonts, not React, Next.js, Vite or TanStack Start build output and not PDFs; a build folder can be uploaded but there are no server routes. Free is 20 documents, 2 MB of HTML in total and 100 form responses a month; paid is $9.99 a month or $49.99 a year for unlimited documents, 200 MB and unlimited responses. No team seats or co-editing, and the in-browser editor is desktop only.