How do you share an HTML file so it opens as a webpage?

Host it at a public URL and share the link. The web server tells the browser to render the file as HTML, which is the step that a file attachment, a cloud-drive link, or a chat upload cannot perform.

Why does a shared HTML file show code instead of a page?

Because whatever is serving the file is sending it as plain text rather than as HTML, or the recipient is opening it in an editor. Browsers render HTML based on the content type the server declares, so serving matters as much as the file itself.

Can you share an HTML file through Google Drive?

You can share the file, but Drive will not render it as a page. It shows a preview or prompts a download, because Drive serves files for storage rather than as a web server would.

Is there a way to share an HTML file without a hosting account?

Some tools accept an upload with no account and return a temporary link. The tradeoff is usually that the link expires, you cannot update it, and there is no way to collect feedback on the page afterwards.

What about HTML files with images and CSS in separate files?

Those need to be shared together with their folder structure intact, normally as a zip that the host unpacks. Sharing only the HTML file leaves every relative path broken and the page will render unstyled.

How to Share an HTML File Online

Sharing an HTML file sounds like sharing any other file, and it is not. The recipient needs a browser to render it, which means something has to serve it as a web page rather than hand over the bytes. This guide covers the options that actually work, the ones that look like they should, and how to choose.

The Problem

An HTML file is not a document. It is a set of instructions that a browser executes, and it usually depends on other things — stylesheets, scripts, images, fonts.

That produces two failure modes that catch almost everyone:

The file arrives but shows as code. The recipient sees <!DOCTYPE html> and a wall of tags. This happens when the file is served as plain text, or opened in an editor rather than a browser.
The file arrives and renders wrong. The page loads but has no styling and no images, because the CSS and assets were left behind. The HTML referenced ./styles.css, and there is no styles.css next to it.

Both are the same underlying issue: an HTML file is only meaningful in context. Move it without its context and it degrades.

Upload the file to a host, get a URL, send the URL. The recipient clicks and sees the page, fully interactive, on any device, with nothing to install.

This is the only option that reliably delivers a working page, because a web server is the thing that declares the file as HTML so the browser renders it rather than downloading it.

Undraft is built for this case specifically: upload a single .html file or a .zip of a whole static site, get a link, and — the part hosting alone does not give you — let people leave comments pinned to elements on the live page. If the file exists so that other people can react to it, the reaction needs somewhere to go.

Email it as an attachment (usually fails)

Mail providers treat HTML attachments as a security risk, because an HTML file can contain scripts. Depending on the provider, the attachment is stripped, quarantined, flagged with a warning, or delivered in a way that opens as text. Even when it survives, the recipient has to download it, find it, and open it in the right application.

Do not build a workflow on this. It works often enough to seem viable and fails often enough to cost you a day.

Cloud drive link (renders as a file, not a page)

Google Drive, Dropbox, and OneDrive are storage, not web servers. Share an HTML file and the recipient gets a preview panel or a download prompt. There is no reliable way to make these services render arbitrary HTML as a live page, and the workarounds that once existed have been closed — the reason is a security one, covered in why HTML files don’t render in Google Drive or Dropbox.

Useful for handing over source files. Useless for showing someone a page.

Chat upload (Slack, Teams, WhatsApp)

Same as email, with an extra problem: chat clients often show a preview of the raw text. The recipient sees markup. On mobile, they frequently cannot open it at all.

Code sandboxes (works, wrong context)

CodePen, JSFiddle, and similar tools will render your HTML and give you a link. Good for sharing a technique with another developer. Wrong for showing a client or stakeholder a finished page, because the editor chrome surrounds the work and the audience ends up commenting on the tool.

Single File vs Multiple Files

Single self-contained file. Everything inline: styles in <style>, scripts in <script>, images as data URLs or hotlinked. Share the one file and it works anywhere. This is the format generated pages usually arrive in, and it is the easiest thing in the world to host.

A folder. An index.html plus styles.css, app.js, and /images/. All of it has to travel together with the structure intact. Zip the folder — with index.html at the top level, not nested inside a second folder — and upload that.

The most common mistake here is zipping the parent directory, so the host finds my-site/index.html instead of index.html. Some hosts handle it; many serve a directory listing or a 404. For the full test of which format you have, see single HTML file vs zip.

Examples

Before

You attach report.html to an email.
The provider flags it.
The recipient downloads it anyway, opens it in a text editor, and sees markup.
You explain how to right-click and open with a browser.
It opens unstyled, because report.css was never attached.

After

You zip the folder with index.html at the top level.
You upload it and get a link.
You paste the link into the same email.
The recipient clicks it and sees the page, styled, interactive, on their phone.
They click the section they have a question about and leave a comment on it.

Summary

Host it and send a link — this is the only method that reliably produces a rendered page rather than a downloaded file.
Check that assets travel with the file — if CSS, JS, or images are separate, zip the folder with index.html at the top level.
Avoid email attachments and cloud-drive links — providers strip HTML attachments, and storage services will not render a page.

Next: the step-by-step guide to share an HTML file, and what it looks like to comment on a webpage once it is live.