Blog

How to share an HTML file: 5 ways compared

Email attachment, cloud folder, PDF, GitHub Pages or Visushare: how to share an HTML file so it opens as a finished page for the recipient.

Published

Contents

An HTML file only reaches your recipient as a finished page if they open it in a browser through a link. If you're a developer, a hosting platform such as GitHub Pages or Netlify does the job; for everyone else, Visushare, which publishes HTML files directly as a link, is the simpler route. Email attachments and cloud folders often show only the source code or force a download, and a PDF is mainly useful as an archive copy.

Quick overview: what are the ways to share an HTML file?

The table compares the five options on the criteria that matter most.

Option Displays correctly for the recipient Effort Link stays the same after changes Access protection Technical skills needed
Email attachment Uncertain, only after downloading Low No, there is no link No No
Cloud folder (Google Drive, OneDrive, Dropbox) Usually not, often source code or a download Low Yes, if you replace the file with a new version Yes, through sharing settings No
PDF export Yes, but without interactivity Low No, there is no link Optional PDF password No
Developer hosting (GitHub Pages, Netlify) Yes Medium to high Yes Depends on platform and plan Yes, the basics
Visushare Yes Low, account required Yes Yes, password or email verification No

An HTML file is a text file with instructions for a browser, which turns it into a page with layout, images and interactive elements. So the key question is: does the recipient open the file in a browser, or just in a preview?

Can you send an HTML file as an email attachment?

Yes, but it arrives as a file, not as a page. The recipient has to download it and open it in a browser, which works better on some email clients and devices than others.

Gmail on the web shows HTML attachments as raw code in its preview, a change Google made for security reasons. The file only renders once it's downloaded and opened in a browser, which is awkward on a phone.

HTML attachments are also a common phishing vehicle, so some companies filter or block them, and cautious recipients may not open them.

Pros: no extra service, sent in seconds.

Cons: download required, unreliable display, attachments may be filtered. Every correction means another email with another file.

Good fit if the recipient is technically confident and wants to keep working on the file locally anyway.

Do Google Drive, OneDrive and Dropbox display HTML files as web pages?

Generally not. Cloud storage services treat HTML files as documents, not as websites. A shared link usually leads to a preview of the source code or to a download.

  • Dropbox states in its help center that shared links don't render HTML content in a web browser.
  • Google Drive shows HTML files as source code in its preview, just like Gmail.
  • SharePoint and OneDrive for Business prompt users to download HTML files instead of opening them in the browser, according to Microsoft, for security reasons. Microsoft is expanding HTML previews in OneDrive, but you shouldn't count on scripts and interactive elements working there.

Pros: many people already have an account, and sharing with specific people is easy. Replace the file with a new version and the share link usually stays the same.

Cons: the recipient rarely sees the finished page and has to download the file, just as with an attachment.

Good fit if you're handing the file to someone who will edit it, such as a colleague on your team.

Is a PDF a good alternative to an HTML file?

A PDF looks the same everywhere, but it's a snapshot. Everything that makes an HTML page interactive is lost: calculators, toggles, expandable sections, animations. The layout can shift too, because a web page is built for screens and a PDF for printed pages.

You can create a PDF straight from your browser: open the page, choose "Print" and select "Save as PDF".

Pros: opens on any device and is easy to archive, print and sign. You can protect a PDF with a password.

Cons: no interactivity, and the layout often changes. Each correction creates a new file, and soon "final" and "final-v2" are circulating side by side.

Good fit if you need a fixed record, for example for your files or as an attachment to a contract. A PDF still does that job well alongside any of the other options.

How do you publish an HTML page with GitHub Pages or Netlify?

A developer hosting platform turns your HTML file into a real website with its own address, displayed exactly as you built it.

GitHub Pages requires a GitHub account and a repository, which is a project folder with version control, according to the GitHub docs. The entry file is index.html. On the free GitHub plan, the repository has to be public. Just as important: GitHub notes that Pages sites are publicly available on the internet, even if the repository is private.

Netlify offers several routes, according to the Netlify docs: a Git repository that deploys automatically on every change, the command line, or dragging and dropping a folder. A deploy is the act of publishing a new version of the site. You can try Netlify Drop without an account, but you'll need to log in to manage the site and push updates later. Password protection is available, depending on your plan.

Pros: full control, correct display, a stable address, and custom domains are possible.

Cons: you need to understand repositories or deploy workflows, and GitHub Pages has no built-in access protection. For a single page sent to a client, that's a lot of overhead.

Good fit if you already work with Git or want to publish a complete website with several pages.

Use Visushare. We built it for exactly this situation: your AI has created a good HTML page and you want to show it to someone, without hosting, without code and without making the recipient download a file first. You upload the file and get an address that opens in any browser like a normal web page, on a laptop or a phone.

Visushare is designed for pages that AI tools such as Claude or ChatGPT create: quotes, programmes, questionnaires, reports, small tools. Everything the page can do also works for the recipient, including animations, expandable sections and calculators.

Here's how it works:

  1. Ask your AI to create the page as an HTML file.
  2. Upload the file to Visushare.
  3. Share the link by email, chat or QR code.

What you get on top:

  • The same link for every version: you replace the page, and the link in emails, chats or QR codes you've already shared leads to the new version. You keep earlier versions and can find them again.
  • Not visible to everyone: protect the page with a password or email verification.
  • You know it arrived: see how often and when the page was opened.
  • Secure and in Switzerland: pages are served over HTTPS and hosted in Switzerland.
  • A PDF is still possible: ask your AI to add a "Save as PDF" button to the page so the recipient can file a copy.

Pros: no code, no hosting, correct display with all interactive elements, the same link for every new version.

Cons: you need an account. The free plan is meant for trying things out; a custom address comes with the Solo plan, and email verification with the Standard plan. For your records or as a contract attachment, a PDF is still worth keeping.

Good fit if you regularly send AI-generated pages, such as quotes, itineraries or reports, to clients or guests. The use case: quote as a link instead of a PDF shows an example.

Which option is right for you?

It comes down to who opens the page and what happens next.

  • The recipient needs to edit the file: email attachment or cloud folder.
  • You need a fixed record for your files: PDF.
  • You work with Git or are publishing a whole website: GitHub Pages or Netlify.
  • You want to share, protect and later update a finished page without any technical setup: Visushare.

Two options often work together: the link shows the current version, the PDF records what was agreed. More examples are in our use cases.

Frequently asked questions

Why does my HTML file look different for the recipient?

Usually the recipient opens it in an email or cloud preview that only shows the source code, not in a browser. Missing images, fonts or scripts that sat next to the file on your computer also break the layout. Opened through a link in a browser, the page looks the way it does for you.

How do I send someone an HTML page they can just open?

Send a link instead of the file. Put the page online with GitHub Pages or Netlify, or upload it to Visushare. A link opens with one click or tap in any browser, including on a phone, whereas an attachment has to be saved first and then opened in a browser.

How do I share an HTML page without making it public?

You need a service that checks access before it shows the page. Netlify offers password protection depending on your plan, and Visushare lets you protect a page with a password or email verification. GitHub Pages sites, by contrast, are always publicly reachable, and cloud folder sharing protects the file but usually won't display it as a page.

How can I put an HTML page online for free?

GitHub Pages and Netlify can be used at no cost, but they require some technical know-how. Visushare has a free plan for trying it out that needs no code. Check each service's current terms before using it with clients.

How do I update an HTML page I've already sent?

With an email attachment or a PDF, all you can do is send a new file in a new email. With a hosting platform or with Visushare, you replace the page and the link stays the same, even in emails you've already sent. If you also need a fixed record, save the agreed version as a PDF.

Read next

  • Use cases

    Quote as a link instead of a PDF

    Send your quote as a web page with a link instead of a PDF: clients pick options, see the timeline and can still save a PDF for their records.

    Agencies & creatives