Why can't I just email an HTML file as an attachment?

Gmail, Outlook, and most corporate mail systems block or quarantine .html attachments because they can contain scripts. Even if the file gets through, clients often open it from their Downloads folder — external assets like stylesheets or images fail to load because the relative paths resolve to nothing outside a server. The result is a broken page that doesn't represent your work.

How do I share an HTML file so a client can comment on it?

Host the file on any static server to get a URL, then use a tool that wraps that URL in a comment layer — or use a tool like Drafty that hosts and annotates in one step. The key is that comments should be pinned to a specific element, not sent in a separate email, so you know exactly which part of the page the feedback refers to.

Can a client comment on an HTML file without creating an account?

Yes — most annotation tools designed for client review let guests leave comments with just a name, no signup. Drafty guests authenticate with a one-time code so comments are attributed, but there is no account to create or maintain.

How do I share a local HTML file online for free?

Netlify Drop is the fastest free option: drag your file to app.netlify.com/drop and get a public URL instantly, no signup needed for the first deploy. For something more permanent, GitHub Pages is free for public repos.

What happens when I update the HTML — does the link change?

On Netlify, you can redeploy to the same site and the URL stays the same. On GitHub Pages, any push to the configured branch updates the live URL. If you want version history alongside the same link, tools like Drafty keep every version accessible so clients can compare before and after.

How do I share an HTML file with a client who isn't technical?

Give them a plain URL that opens the rendered page in their browser — not a .html file to download. Any of the hosting options above produce such a link. The shorter and cleaner the URL, the less likely they'll have trouble with it. Avoid links that contain long query strings or hash fragments, which can get mangled when copy-pasted from email.

drafty

How to share an HTML file for feedback

Quick answer

To share an HTML file for feedback, host it somewhere your client can open it in a browser — email attachments don't work reliably because Gmail and Outlook often block or mangle .html files. The fastest options are a free static host (Netlify Drop, GitHub Pages, or CodePen), a one-click hosting tool, or a shared link your client can annotate directly without downloading anything.

Step 1

Netlify Drop — drag, drop, get a URL

Go to app.netlify.com/drop, drag your HTML file (or a folder with its CSS and images) onto the page, and Netlify gives you a live URL in seconds — no account required for a first deploy. The link works on any device and renders exactly like a browser would locally. When you have a revision, drag the updated folder onto the same site in your Netlify dashboard to get the same URL with new content. One gotcha: if your HTML references local CSS or image paths, the files must be in the same folder you drop. A single self-contained .html file with inline styles works best.

Step 2

GitHub Pages — right for iteration-heavy projects

If your HTML file is already in a Git repo, GitHub Pages is a clean option: push your file to a branch named gh-pages (or configure Pages under Settings → Pages → Source), and GitHub publishes it at yourusername.github.io/repo-name. Every git push updates the live URL automatically, so iteration is just commit-and-push rather than re-uploading. The tradeoff: it takes a few minutes to propagate on the first publish, and clients who click the link before the DNS resolves see a 404. Better suited to ongoing projects than one-off reviews.

Step 3

CodePen or similar — for self-contained snippets

CodePen, JSFiddle, and StackBlitz let you paste HTML, CSS, and JS into separate panels and share a live preview link. These work well for component reviews or isolated UI snippets — not for multi-page builds or files that load external assets from a local path. Create a new Pen, paste your markup, and share the Pen URL. CodePen's free plan lets you share any number of public Pens. Your client opens the link and sees the rendered output with no downloads. The preview URL is permanent as long as the Pen exists.

Step 4

When the feedback itself is the hard part

Hosting solves the viewing problem, but not the feedback problem. Once a client can see your HTML, they still have to describe what they mean: "the blue button on the second row" or "can you move that section up?" usually arrives in an iMessage or buried in an email thread. The comment ends up detached from the element it refers to, and you spend ten minutes re-reading the markup to figure out where they meant. The next section covers a faster path for collecting pinned, element-level feedback.

The faster way

If your client needs to mark up the actual page — not just view it — drop the HTML into Drafty and share the link. They click the exact heading, button, or paragraph they mean and leave a comment anchored right there, no account needed. You see every note in one thread tied to the element, reply in context, and push a revised version to the same URL. No "the thing in the top right" guessing games.

Open a live demo

Questions

Why can't I just email an HTML file as an attachment?: Gmail, Outlook, and most corporate mail systems block or quarantine .html attachments because they can contain scripts. Even if the file gets through, clients often open it from their Downloads folder — external assets like stylesheets or images fail to load because the relative paths resolve to nothing outside a server. The result is a broken page that doesn't represent your work.
How do I share an HTML file so a client can comment on it?: Host the file on any static server to get a URL, then use a tool that wraps that URL in a comment layer — or use a tool like Drafty that hosts and annotates in one step. The key is that comments should be pinned to a specific element, not sent in a separate email, so you know exactly which part of the page the feedback refers to.
Can a client comment on an HTML file without creating an account?: Yes — most annotation tools designed for client review let guests leave comments with just a name, no signup. Drafty guests authenticate with a one-time code so comments are attributed, but there is no account to create or maintain.
How do I share a local HTML file online for free?: Netlify Drop is the fastest free option: drag your file to app.netlify.com/drop and get a public URL instantly, no signup needed for the first deploy. For something more permanent, GitHub Pages is free for public repos.
What happens when I update the HTML — does the link change?: On Netlify, you can redeploy to the same site and the URL stays the same. On GitHub Pages, any push to the configured branch updates the live URL. If you want version history alongside the same link, tools like Drafty keep every version accessible so clients can compare before and after.
How do I share an HTML file with a client who isn't technical?: Give them a plain URL that opens the rendered page in their browser — not a .html file to download. Any of the hosting options above produce such a link. The shorter and cleaner the URL, the less likely they'll have trouble with it. Avoid links that contain long query strings or hash fragments, which can get mangled when copy-pasted from email.

Keep exploring

Review a website Website feedback tool BugHerd alternative Annotate a PDF

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo