What is wrong with just emailing the .html file to a client?

Most email providers block .html attachments as a phishing precaution, so it may never arrive. When it does, the client sees a download prompt instead of a working page, and has to know to open it in a browser, which non-technical clients often do not. Either outcome reads as an unfinished deliverable rather than a polished one.

Does it matter if the HTML came from an AI tool (Claude, ChatGPT, Gemini)?

Not for the delivery problem itself, that is identical either way. What changes is the starting point: you are copying HTML out of a chat interface rather than opening a file you built by hand. Either way, the file needs a URL before a client can see it properly.

How do I make the link look like it belongs to me, not a random host?

On LiveSend, Pro accounts can set a custom slug under their own username, so the link reads yourname/project-name instead of a random string. A branded, readable path is one of the small details that makes a deliverable look finished rather than thrown together.

Can I control who sees it and for how long?

Yes. LiveSend lets you add a password if the content is confidential, set an expiration date so the link stops working after a project ends, and toggle the document off at any time. None of that is available with a plain file attachment.

What if the client asks for a change after I already sent the link?

Edit the document inline or upload a new version, the URL the client already has stays the same. There is no "resend the corrected file" email, and no risk they open an outdated copy from an old attachment.

Guide

How to send an HTML file to a client

Turn the HTML into a hosted link and send that, never the raw file. A client who receives a .html attachment either cannot open it (email blocks it) or gets a download prompt that reads as unfinished work. Paste the file into a host built for one-off HTML (LiveSend), get a permanent URL, and send the link instead. It opens in any browser with no download, no plugin, and no explanation needed.

A client judges the delivery, not just the work

By the time an HTML file is ready to send, whether it is a prototype, a proposal, a one-page tool, or a mockup, the hard part is done. What happens next still shapes how the work is received. An attachment that gets blocked, or a download prompt on a file the client does not recognize, reads as unfinished, even when the content itself is good. The fix is a link, not a file.

The three-step version

Upload or paste the HTML into LiveSend. No account setup beyond email and password.
Optionally set a custom slug (Pro) so the URL reads with your name or agency, not a random string.
Send the link in an email or message. It opens directly in the browser, nothing to download.

What a client-ready link needs, beyond just opening

Sending a working link clears the bar for "it opens." For paid client work, a few details separate a finished deliverable from a thrown-together one:

A branded URL reads as prepared for that client specifically, not a generic upload.
Confirmation it was opened. For a proposal or a time-sensitive deliverable, knowing whether the client actually looked at it changes your follow-up.
The ability to fix a typo without a resend. Inline edits on the same URL avoid the awkward "ignore the last email, here is the corrected version" message.
A password, if the content is sensitive. Financial figures, pricing, or anything under NDA should not sit behind a guessable link alone.

What not to do

Do not attach the raw .html file (email blocks it, or the client gets a download prompt). Do not paste it into Google Drive or Dropbox (both serve it as a download, not a page). Do not screenshot it if the file has any interactivity, filters, forms, or navigation, the client is judging the actual product, not a flattened image of it.

New to turning a file into a link? See the shortest path, no hosting knowledge required.

Frequently asked questions

What is wrong with just emailing the .html file to a client?
Most email providers block .html attachments as a phishing precaution, so it may never arrive. When it does, the client sees a download prompt instead of a working page, and has to know to open it in a browser, which non-technical clients often do not. Either outcome reads as an unfinished deliverable rather than a polished one.
Does it matter if the HTML came from an AI tool (Claude, ChatGPT, Gemini)?
Not for the delivery problem itself, that is identical either way. What changes is the starting point: you are copying HTML out of a chat interface rather than opening a file you built by hand. Either way, the file needs a URL before a client can see it properly.
How do I make the link look like it belongs to me, not a random host?
On LiveSend, Pro accounts can set a custom slug under their own username, so the link reads yourname/project-name instead of a random string. A branded, readable path is one of the small details that makes a deliverable look finished rather than thrown together.
Can I control who sees it and for how long?
Yes. LiveSend lets you add a password if the content is confidential, set an expiration date so the link stops working after a project ends, and toggle the document off at any time. None of that is available with a plain file attachment.
What if the client asks for a change after I already sent the link?
Edit the document inline or upload a new version, the URL the client already has stays the same. There is no "resend the corrected file" email, and no risk they open an outdated copy from an old attachment.

Related guides

Want to try the LiveSend approach?

Paste your HTML, get a permanent link. Free for the first 3 documents.

Get started free