Why won't my HTML attachment open on the client's phone?

On a phone, tapping an .html attachment often shows the raw source code, downloads a file the person cannot open, or does nothing. HTML also depends on fonts and scripts that may not be present on their device, so even when it opens it can look broken.

Why might a client never receive an HTML attachment at all?

Many corporate mail filters strip HTML attachments because they are a known phishing vector. The message can arrive with the attachment silently removed, so the client never sees it and you never get told.

What is the most reliable way to send an HTML document to a client?

Send a link instead of a file. A hosted link opens in one tap on any device, renders as designed, and cannot be stripped by a mail filter the way an attachment can.

Are there free ways to host an HTML file as a link?

Yes. GitHub Pages, Netlify Drop, Cloudflare Pages and Tiiny.host all host a single HTML file for free. Most give you a hosting subdomain and do not produce a preview card when the link is pasted into a chat app.

Guide

How to send an HTML file to a client (so it actually opens)

You have a report, a proposal or a one-pager as an HTML file — maybe an AI tool wrote it — and you want to get it to a client. The obvious move is to attach the file to an email. It is also the move most likely to fail. Here is why, and what to do instead.

Why attaching a .html file usually fails

An HTML file is not a self-contained document like a PDF. It is a set of instructions a browser follows, and it often depends on fonts and scripts that are not inside the file. Hand it to someone else and three things go wrong.

It does not open on a phone. Most clients read email on a phone first. Tapping an .html attachment there commonly shows a wall of source code, downloads a file the person has no app to open, or simply does nothing.
It may never arrive. Plenty of corporate mail filters strip HTML attachments outright, because a live HTML file is a known phishing vector. The email lands with the attachment quietly removed, and nobody is told.
It looks suspicious. Even when it does get through and does open, an unfamiliar .html attachment from an outside sender reads as risky to a non-technical client. A meaningful share of people never click it.

So the file that looked perfect on your screen can arrive as source code, as nothing, or as something the client is wary of touching.

The usual fallbacks, and what they cost

Faced with this, most people reach for a PDF or a screenshot. Both are reasonable in the right situation, and both lose something.

Printing to PDF is the safe-looking choice that fails quietly. Interactive charts can flatten to empty boxes, and a wide table that scrolled on screen simply loses its right-hand columns on paper — the numbers vanish with nothing to show they were ever there.
Screenshotting always displays, but the text stops being text: it cannot be searched, copied, quoted back, or translated, and on a phone the client is pinching and zooming a picture.

There is a fuller breakdown of each failure mode in the deeper guide on why HTML breaks in transit. For client work, the practical takeaway is short: use a PDF when the client needs to file or sign something, and otherwise reach for a link.

The reliable answer: send a link, not a file

A hosted link sidesteps every problem above. There is nothing to download, a mail filter has nothing to strip, and it opens in one tap in whatever browser the client already has. You do not need to pay for this — several genuinely free options exist.

GitHub Pages. Free and reliable if the document belongs in a repository. The URL looks technical and the setup is a few steps, but it works well.
Netlify Drop or Cloudflare Pages. Drag a folder in, get a URL. Free and dependable; you get a hosting subdomain rather than anything branded.
Tiiny.host. Upload a single HTML file and get a link in a couple of clicks. The free tier is enough for the occasional document.

All of these host the page. What most of them do not do is produce a proper preview card when you paste the link into WhatsApp, Slack or email — the client sees a bare subdomain URL rather than your title — and they give you no clean path to a PDF or Word copy if the client later asks for one.

What SendPage adds for client work

SendPage is aimed at exactly this case: sending a document to a client and having it land well. You paste the HTML and get a link. When you send that link, it previews as a card with your name and title in WhatsApp and email rather than a bare URL, and the client taps once to read the document as designed on any phone.

Because exports come from a real browser render, you can hand over a clean PDF or Word copy when a client asks, without the flattened charts or cut-off columns. And if you spot a typo after sending, you can fix it without issuing a second link — the client opens the same URL and sees the corrected version. It is free for three documents a month, with no signup.

How to send it as a link, step by step

Paste the HTML. Open SendPage and paste the full HTML of your document into the box. No signup for the first three documents a month.
Get a link. SendPage hosts the page and hands back a single link. The page renders exactly as designed — nothing is flattened or cut off.
Send the link. Drop it into your email, WhatsApp or Slack message. It previews as a card with your title, and the client opens it in one tap.

If the document came out of Claude, you can skip the copying entirely: connect SendPage to it and the link is produced in the same conversation that wrote the page.