Question 1

Do inline styles and embedded images in my HTML file come through correctly?

Accepted Answer

Yes. dochost serves the file as uploaded, so anything baked into the HTML itself — inline CSS, base64-encoded images, data URIs, and any src attributes pointing to public CDN URLs — renders in the viewer’s browser just as it would locally. We do not strip or rewrite styles. The only thing that will not work automatically is content that requires a separate file we did not receive, such as an external stylesheet you left in a /css folder next to the HTML.

Question 2

Is there a file-size limit for the HTML file I upload?

Accepted Answer

There is a per-file ceiling that comfortably fits a typical single-file HTML export — even one with a handful of base64-encoded images baked in. If your file is unusually large because it contains heavy embedded assets, consider hosting those images externally and referencing them by URL instead; that also makes the page load faster for whoever clicks your link. Paid accounts allow larger uploads — see the pricing page for the current figures.

Question 3

Does the link show a viewable webpage or let people download the raw file?

Accepted Answer

It shows a viewable webpage. When someone opens the link, their browser renders the HTML just like any other website — they see the page, not a download prompt. There is no download button shown to viewers by default. This is intentional: the whole point is to give someone a URL they can tap and read, not an attachment they need to save and open locally. If you specifically need to share the raw source, you can copy it somewhere else.

Question 4

What happens to images that use a local file path like ../images/logo.png?

Accepted Answer

They will not load. A local path like ../images/logo.png only makes sense on your own machine, where that folder actually exists. Once the HTML is served from our servers, the browser follows that path and finds nothing. Before uploading, replace local image references with public URLs — upload the images to an image host or use your own CDN — or embed them directly as base64 data URIs. Most email export tools inline images automatically, so this usually is not an issue for exported email files.

Question 5

How do I share an HTML file as a link instead of an attachment?

Accepted Answer

Upload it here and send the URL you get back. That is the whole difference. No mail client renders an .html attachment inline — the recipient gets a file to download, and then has to find something on their device that will open it, which is exactly where it breaks. On a phone that download has nowhere to go; on a managed work laptop the file may not open at all; and plenty of corporate mail gateways strip HTML attachments before they arrive. A link asks them to tap instead. Nothing is downloaded, the browser they already have does the rendering, and you send one URL to five people instead of re-attaching the file five times. There is a longer walkthrough on share an HTML file online.

HTML file to link converter

Upload your HTML file

How to convert an HTML file to a shareable link

A real example

Questions about HTML file to link converter

Keep your links forever

Related use cases