Upload an HTML file online and share it as a public link
Upload one finished HTML file and turn it into a browser link for review or sharing. No ZIP is required when the page is self-contained.
Answer First
Upload a complete .html file, paste its source, or deploy a browser-ready static build and PreviewShip returns a public HTTPS URL. A self-contained page needs no ZIP; pages with local CSS, JavaScript, images, fonts, or framework assets should be uploaded as a complete static folder or ZIP after the project is built.
From HTML to a link you can share
- Upload your .html file. Include local images and styles in a static ZIP when needed.
- Publish, then open the HTTPS link and check the page.
- Share the link; create an account to save and update the project.
No-signup previews last 24 hours, with uploads up to 15 MiB. Claimed projects follow your plan: 3-day previews on Free, or continuous hosting with an active Pro subscription. Claiming an expired project does not republish it.
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.
Key takeaways
Recommended workflow
Save the complete page as a .html file, copy the full HTML source, or build the framework project into static output.
Open PreviewShip and choose direct HTML upload, paste HTML, a browser-ready ZIP, CLI, MCP, or an editor workflow.
Enter a project name, deploy the artifact, and wait for the Ready result.
Open the returned HTTPS URL, verify the page and its local assets, then share that same project link.
Comparison snapshot
Choose the right upload input
Use direct .html upload or paste HTML when the page is self-contained or only references reachable external assets. This fits generated landing pages, reports, dashboards, calculators, and design proofs.
Use a ZIP or static folder when index.html references local images, CSS, fonts, JavaScript, or nested routes. For a framework project, run its production or static-export build first and upload the generated output.
Example: turn a report folder into a website
For a page that uses local files, put index.html at the root of the static ZIP alongside styles.css and an assets folder. If the HTML contains src="./assets/chart.png", the ZIP must contain assets/chart.png with the same spelling and capitalization.
Include the finished page and the assets it uses. Do not upload only index.html from a framework build, because its JavaScript and CSS bundles are needed to render the page. A directory named public is suitable only if it is already the complete browser-ready output.
Upload without FTP, DNS, or a repository
Traditional upload-to-website workflows often involve FTP, cPanel, a Git repository, a hosting dashboard, or DNS. Those steps are unnecessary when the immediate goal is a review link for an artifact that already runs in a browser.
PreviewShip keeps this handoff narrow: select the browser-ready artifact, deploy it, open the generated URL, and share the verified link.
Troubleshoot a blank page or missing assets
A blank result usually means the uploaded artifact was not browser-ready. Confirm that index.html is at the expected entry point, open the build locally, and check that every stylesheet, script, image, and font path still exists after packaging.
If the page came from a framework, do not upload the source project. Run the build, deploy the generated output, and compare the exact filename case and relative path for any asset that still returns 404.
Preview sharing is different from production hosting
A PreviewShip URL is a fast way to review a finished static artifact. Choose a production platform when the site needs durable release operations, custom domains, backend services, databases, server rendering, or production uptime commitments.
Official sources
Product and workflow facts were verified against these official pages on 2026-10-26.
FAQ
Can I preview an HTML file before publishing it?
Yes. The HTML input offers a local static preview for checking layout before you publish. Scripts and external resources are disabled there. Use the published link to verify JavaScript, remote fonts, images, and APIs; a local layout check does not test those dependencies.
What happens to the uploaded HTML or Markdown filename?
A single HTML upload is published as index.html so the project root opens the page. Markdown is rendered through a generated HTML reader while its source is retained.
Can I upload an HTML file online for free?
Yes. A no-signup preview lasts 24 hours with an upload limit of 15 MiB. Free account previews last 3 days. Pro adds higher limits, continuous hosting while subscribed, and password access.
Can the HTML include JavaScript?
Yes. Client-side JavaScript can run on the published static page if the browser and external dependencies allow it. The local HTML preview before publishing is a static layout check with scripts disabled; test interactions on the hosted result.
Can I update the same project later?
You can deploy a new version under the same project workflow and keep the fixed project URL pointing at the latest deployment.
Do I need FTP, a domain name, or a Git repository?
No. PreviewShip returns a hosted preview URL, so a browser-ready HTML artifact can be shared without FTP, DNS, a custom domain, or a repository.
Should I upload framework source code or built output?
Upload browser-ready output. Build the project first, then deploy dist, build, out, public, or a ZIP that contains index.html and all referenced static assets.