Guides / Publish HTML

Publish HTML online and share a live HTTPS URL

Publish HTML online for free, host an HTML file, or turn HTML into a public HTTPS URL for AI pages, reports, prototypes, and static build output.

Updated 2026-10-26Practical deployment guide

Answer First

To publish HTML online, upload a single .html file, paste the HTML source, publish Markdown, or deploy a static build output folder from React, Vue, Vite, Next static export, Astro, Svelte, or plain HTML/CSS/JS. PreviewShip hosts the browser-ready artifact and returns a public HTTPS URL that you can share with clients, teammates, or an AI agent workflow.

Try without signing up Read full docs

Deploy build artifacts, not source-code zips.

If you upload a zip, build the project first and zip the static output folder such as dist, build, out, or public with index.html and assets. Do not zip raw React/Vue/Next source folders with package.json and node_modules. Single .html, .md/.markdown, and .pdf files are supported directly by console upload, CLI, MCP, and the VS Code/Cursor extension.

PreviewShip upload page for publishing an HTML, Markdown, or static build and getting a shareable URL — The no-signup upload page accepts a file, pasted HTML, or pasted Markdown and returns a public preview link.

Key takeaways

Best for AI-generated HTML, one-page prototypes, reports, dashboards, Claude HTML artifacts, and small landing pages.

Works without Git, CI/CD, server setup, or a production hosting account.

Supports direct .html upload, pasted HTML, Markdown, build-output folders, CLI deploys, MCP deploys, and editor deploys.

For React/Vue/Vite/Next or other multi-file projects, build first and deploy the static output folder with index.html and assets.

Recommended workflow

Create or export your HTML file from ChatGPT, Claude, Cursor, a design tool, or a local editor.

Open the try page and upload the .html file or paste its full source. For a terminal workflow, authenticate the CLI and run npx previewship deploy ./page.html.

Name the project and start the deployment.

Copy the live URL and share it with reviewers.

Comparison snapshot

Question	PreviewShip	Traditional hosting
Input	HTML file, Markdown file, pasted HTML, or build output	Usually FTP, Git, or server files
Setup	No server or CI setup	Often requires DNS, hosting, or repo setup
AI workflow	MCP and CLI friendly	Usually human-dashboard first
Best use	Fast review and sharing	Production site operations

Why HTML needs a public URL

AI tools now generate complete HTML pages for landing pages, research reports, calculators, dashboards, and small prototypes. The output is useful, but a local file is hard to review on another device.

Publishing HTML online gives the artifact a link other people can open. Reviewers can test it in a browser and send feedback through their usual email, chat, or review tool. PreviewShip does not add a built-in comment system.

What PreviewShip accepts

PreviewShip supports three common inputs: a single .html/.md/.markdown file, pasted HTML source, or a built static output folder. The first two are ideal for AI-generated one-page artifacts. The third is ideal for React, Vue, Vite, Next static export, Astro, Svelte, and other framework builds.

If your zip contains package.json, src, and node_modules, it is probably source code rather than deployable static output. Build it first and deploy dist, build, out, public, or another folder that contains index.html.

Make an HTML file into a website: a final check

For a self-contained page, upload the file or paste the complete document. Use the local static preview to inspect its layout, then publish and open the returned link. The local preview disables scripts and external resources; the hosted page is where you check interactions and remote dependencies.

Check the page title, mobile viewport, images, links, and client-side behavior. Replace local file paths and remove private API keys. If the page needs CSS, JavaScript, or images stored beside the HTML, upload the complete static output instead of only the entry file.

Preview pasted HTML before publishing Package a file with its local assets

Choose the shortest path for the artifact you have

Use direct upload or paste for one complete HTML file. Use a built static folder for local assets or framework output. Use CLI or MCP when the deploy step belongs inside a repeatable developer or agent workflow.

See what the current Free preview plan includes

Official sources

Product and workflow facts were verified against these official pages on 2026-10-26.

PreviewShip: current product facts and limits

FAQ

Can I publish one HTML file without zipping it?

Yes. PreviewShip supports direct .html upload and pasted HTML source in the console, plus single-file deploys from CLI, MCP, VS Code, and Cursor.

Can I publish HTML online for free?

Yes. No-signup previews last 24 hours; Free account previews last 3 days. Use an active Pro subscription when a project needs continuous hosting.

Does PreviewShip preserve my HTML meta tags?

PreviewShip deploys the HTML artifact as static output. Any title, meta description, Open Graph tags, and JSON-LD that are inside the HTML remain part of the page.

Can I publish HTML generated by ChatGPT or Claude?

Yes. Save the generated code as a .html file, paste it into the console, or let an MCP-compatible agent deploy it directly.

Is this the same as production hosting?

PreviewShip is optimized for fast preview sharing. Use it for reviews, demos, prototypes, and temporary public links rather than full production hosting workflows.