Upload a .html file from your computer and get a clean, shareable URL in seconds — no server setup, no attachment headaches.
Drop a .html file here and get a shareable link. No account needed to start.
When you have a finished HTML file sitting on your desktop, sending it as an email attachment is a bad idea. Recipients on phones cannot open it, and most email clients block local file downloads outright. If you have been wondering how to share an HTML file as a link instead of a dead attachment, this is it: dochost acts as a straightforward HTML file to link converter — you upload the file, we host it, and you get back a URL anyone can open in a browser. No account required to start. Free links stay live for seven days. If you need the link to stick around permanently, a paid plan keeps it online indefinitely. The file renders exactly as it would in a browser — inline styles, embedded images, all of it.
Click the upload area or drag your .html file onto the card above.
dochost reads the file and generates a hosted URL — usually within a few seconds.
Copy the link and share it. Recipients open it in any browser, on any device; free links expire after 7 days, or upgrade for a permanent URL.
Maya is a freelance email designer. She has spent two days building a promotional newsletter for a skincare brand: animated GIF header, product grid with inline table layout, a footer with unsubscribe copy. Her email tool exports the finished design as a single file, campaign.html, with all styles inlined and every product image pointing to the brand’s CDN. The client needs to approve the visual before Maya loads it into their ESP.
Sending the raw .html file as an attachment is useless — the client’s marketing manager reviews everything on her iPhone, and iOS Mail will not render a local HTML attachment the way a real browser would. A screenshot will not cut it either; the client specifically wants to scroll through the email at actual size.
Maya opens dochost, drags campaign.html onto the upload card, and gets a URL in about three seconds. She pastes it into her approval message on Slack. The client taps the link on her phone, sees the newsletter rendering correctly — GIF playing, product images loading, fonts intact — and replies with a green light. Maya never had to spin up a staging server or zip anything. The link is live for seven days, which is more than enough time to get sign-off and send the campaign.
This search is four different jobs wearing the same words, and they do not all end on this page. Pick the one that matches what is actually on your screen.
There is a file on your desktop and you want a URL for it.
This page, and the card above. Drag the file in, get a link back in a few seconds, send the link. Nothing is installed and no account is needed to start. This is the case the rest of the page is written for.
You have markup in your clipboard — from an AI chat, an editor, or a snippet — and never saved it.
Do not save it to disk first just to upload it. Paste the markup straight in and you get the same hosted URL, skipping the file entirely. This is the usual shape when the HTML came out of ChatGPT or Claude, where there was never a file to begin with.
Paste HTML and generate a linkIt is a real project directory — index.html plus /css, /js and /images.
This is the branch that does not end here, and pretending otherwise would waste your time. The uploader takes one file, so a folder loses its stylesheet and its images: the page still renders, just unstyled, which is worse than an honest failure. Either inline the assets into a single self-contained HTML file first, or use a host built for directory deploys.
Hosting a multi-file appIf the project came out of an AI builder, ask it for a single self-contained HTML file — most will produce one on request, and then this page works.
The link is going somewhere permanent — a CV, a README, a business card.
Then the seven-day free link is the wrong product and you should know that before you paste it somewhere permanent, not after it expires. A paid plan keeps the URL online indefinitely, and you can also extend a page you already published before it lapses.
Plans that keep the linkYou have a URL and you want the HTML or Markdown out of it.
That is the reverse job and it has its own tool — fetch the page and get clean Markdown back, rather than trying to make a link out of something that already is one.
URL to MarkdownYes. 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.
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.
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.
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.
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.
Los enlaces gratuitos duran 7 días con una cuenta gratuita. Con un plan de pago, cada página que publiques se queda online de forma permanente.
Ver precios