You made a page, maybe a report your AI agent wrote as HTML, and sent it to someone. They wrote back with a screenshot of angle brackets, or a file that downloaded and opened with its images missing. The file may be fine. A file preview is different from a hosted page.
Here is what the common apps document about an .html file as of November 2026, and how to share a hosted page instead. We make tossithere, which is one of the fixes, so weigh that.
Why does an HTML file show code instead of the page?
An HTML file shows as code when the app opening it treats it as a document to preview rather than a page to run. A browser renders HTML when it loads it from a web address or opens it from your own disk. Google Drive and Microsoft 365 list HTML among their code previews, and SharePoint can make people download it instead. Those preview lists do not promise to run the page. If a downloaded page refers to local images or scripts that were not sent, those parts will be missing.
Google Drive: why does my HTML file open as code?
Google Drive lists HTML among its "Markup/Code" preview types, next to CSS, JavaScript and Python, in Google's own list of previewable files. That classification suggests a code preview; it does not promise a hosted web page.
Drive used to offer web hosting. Google deprecated web hosting in Drive in 2015 and ended serving content from googledrive.com/host on August 31, 2016, according to its Workspace Updates announcement. That discontinued hosting feature is no longer available.
Microsoft Teams and SharePoint: why does the HTML file download?
SharePoint Online restricts opening HTML files from document libraries in the browser. Microsoft's SharePoint migration guide says the Strict browser file handling setting is enforced in SharePoint Online and can't be changed, so "*.htm and *.html files in document libraries no longer open in the browser. Users are prompted to download the files" (Microsoft Learn).
Files shared in a Teams channel live in that team's SharePoint site (Microsoft Learn). That SharePoint restriction is relevant to HTML files shared in Teams channels. Microsoft's preview list for OneDrive, SharePoint and Teams lists HTML under both "Text and Code" and "Web/Hypertext", but doesn't say a preview runs the page (Microsoft Support).
Slack: can it show an HTML page?
Slack previews files you upload, but its help page on adding files doesn't say it renders HTML as a page, so don't count on the recipient seeing more than a file. Send a link instead, and the page opens in their browser.
What about email?
Email can carry an HTML file: Gmail's list of blocked attachment types doesn't include .html. A recipient may need to download it and open it in a browser. Sending a revised attachment gives them another copy; the attachment itself does not provide a shared comment thread.
How do I fix it?
Put the file on a web host and share the address. Upload the HTML and its assets together, then check that the intended recipient can open the web address.
- Gather the file and anything it loads. If the page uses images, CSS or scripts saved next to it, keep them together in one folder. A single self-contained HTML file is fine on its own.
- Upload it to a host. For a one-off, Netlify Drop, Vercel Drop and Cloudflare Drop take a dragged folder with no account to start, as of November 2026. Claim the site before you send the link: an unclaimed Netlify drop sits behind a temporary password, Cloudflare gives you 60 minutes to claim, and Vercel's temporary deploys expire unless claimed. On Netlify, check the project's visibility after claiming too: on credit-based plans, a team with private-by-default enabled can keep a claimed project private until you make it public. Our guide on how to share an HTML file as a link compares all the options, and tiiny.host alternatives covers the hosts in more detail.
- Paste the link into Teams, Slack, the email or the Drive comment where the file was going to go.
If an AI agent made the page and you expect changes, use a host it can publish to directly, so you don't redo the upload for every version. With tossithere, the agent runs toss report.html and gets a link. A signed-in push is private by default, so share the document with the intended reviewers before sending it. A push without an account is public and expires after 24 hours unless claimed. Reviewers sign in with Google to comment on an element or highlighted text; the agent reads those comments and publishes v2 to the same link. There are setup guides for 23 agents, for example Claude Code, Codex and Cursor. For a comparison of publishing and reviewer access, read Claude Code Artifacts vs tossithere.