Everything between a file and a link someone can open — making HTML self-contained, sizing it, viewing it online, choosing it over PDF, and sending it to one person.
The hard part of an HTML deliverable should be building it. In practice, a surprising amount of friction lives in the last step — getting the finished file to render, as a page, on someone else's screen. Almost all of that friction traces back to two things: whether the file is self-contained, and whether you're sending a file or a link.
This guide is the map. Each section links the deep dive.
A portable HTML file inlines everything it needs — styles in a <style> block, scripts in a <script> block, images as base64 or data URIs — so there's no separate stylesheet to lose and no asset folder to forget.
If you already have the folder and just want the one file, the fastest route is to let something do the inlining for you: combine an HTML, CSS, and JS folder into one file runs in the browser, takes the folder, and hands back a single self-contained .html — nothing uploaded, nothing to install.
If you'd rather understand the mechanics or do it by hand, how to inline all CSS and JavaScript in an HTML file walks through it; for AI-produced output, making a Claude artifact self-contained is the export checklist.
Self-contained has a cost: inlined images and chart libraries add weight. When the file outgrows what email allows, the answer isn't to compress harder — it's to send the URL. Sending a 50MB HTML file when email refuses covers where the real limits are and what to do past them.
"View this HTML online" usually means get a URL that renders the file as a page, not just open it locally. Deciding who should be able to open it covers the fork that step really is — a findable address or an unguessable one — and why most tools pick for you.
The format is a decision, not a default. Why HTML beats PDF for deliverables in 2026 covers the three axes where HTML wins — interactivity, weight, and not leaving stale copies in everyone's Downloads — and the cases where PDF is still the right shape.
Once the file is self-contained and right-sized, the handoff is the easy part — if the channel matches. Sharing an HTML report with a client compares the channels; what your client sees opening a private link walks the receiver's experience; and sharing one link with multiple stakeholders covers the short-list case without losing the audit trail.
Self-contained file → right-sized → hosted at a link → sent to the people you choose. Each step removes one reason the page might not render on the other end. The link layer is the last mile: an unguessable URL, hidden from search by default, with optional password and expiry — the privacy free on every tier.
See the full set in the How-to & formats archive.
Cursor builds projects as folders of linked files, not one shareable artifact. Three reliable ways to collapse a Cursor build into a single self-contained HTML you can drop on a private link — and the one case where you deploy instead.
Email providers cap attachments around 20-25MB. The fix when the file is bigger isn't to compress harder — it's to send the URL instead.
Three formats people reach for by habit, built for three different jobs. A job-by-job map of when Markdown, HTML, or PDF is the right shape — and why they work best as a pipeline, not a choice.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.