Paste HTML or open a .html file and the rendered page appears next to the source, styles and scripts included. Nothing uploads until you decide to publish it.
The rendered page appears on the right, scripts and all. Nothing is uploaded until you publish.
The preview runs the page's own CSS and JavaScript, in an isolated frame with no origin of its own. That last part is why anything using localStorage errors here and works once published — a published page gets its own origin, so its storage is real.
An .html file is the source of a web page, not the page. Open it in a text editor and you get angle brackets; open it in a browser and you get the page — which is fine until the file is an email attachment, a download on a locked-down laptop, or a block of code somebody pasted into a chat. Then there is no obvious way to just look at it.
This viewer is the missing step. Paste the markup or open the file and the right-hand pane renders it the way a browser would, with the CSS applied and the JavaScript running. The file never leaves your machine to do that: the preview is a sandboxed frame in the tab you already have open. If the page turns out to be worth showing someone, the same source publishes to a link in one more click.
CSS applies. Inline <style>, a style= attribute and a stylesheet loaded from a CDN all work, because the frame fetches them exactly as a browser tab would.
JavaScript runs. Buttons, tabs, charts and form validation behave the way they will for a reader. A viewer that quietly stripped scripts would tell you your working page is broken.
Storage does not. The preview frame has no origin of its own, and localStorage throws in that situation. A page that saves state errors here and works once published, where it gets a real origin.
Relative paths do not resolve. src="./logo.png" has nothing to be relative to. Anything pointing at a file next to the original on disk shows as a broken image here, and will do the same for anyone you send the file to.
Nothing is uploaded. The file is read in your browser. The first network request carrying your HTML happens when you press publish.
A recruiter is sent a candidate portfolio as portfolio.html — one self-contained file, exported from a design tool. Her work laptop opens unknown downloads in a policy-managed sandbox that refuses local files, so double-clicking does nothing useful and the preview pane in her mail client shows the first two hundred characters of markup.
She opens this page, clicks Open .html file, and picks the download. The portfolio renders in the right pane: the grid of project cards, the web font, the hover states, and the filter buttons that actually filter because the file’s own script is running. No install, no policy exception, nothing sent anywhere — the file was read by the browser tab she already had open.
Two of her colleagues need to see it before the interview. Rather than forwarding a file that will fail on their machines the same way it failed on hers, she clicks publish and pastes the link into the hiring channel. They open it on a phone and a Windows desktop and see the same page she did.
Paste the code and it runs: the CSS is applied and every script executes, in a sandboxed frame with no access to this site. That is what most people mean by an “online HTML compiler” — here is how it compares with an IDE-style playground.
See a whole page run, JavaScript included
Both execute the page’s own scripts.
Open a .html file from your device
Most playgrounds take pasted code only.
Edit HTML, CSS and JS in separate panes
This viewer takes one document, as a browser does.
Share the running page as a link
Publishing here needs no account; most playgrounds need one to save.
People search for this under a lot of names: an HTML renderer, an HTML reader, an online HTML previewer, an HTML code viewer. They all end in the same place — the markup goes in, the page comes out. Pick the case that is yours.
You have HTML code and want to see the page it draws.
Paste the code into the box above and the renderer draws it on the right, the way a browser tab would: styles applied, scripts running, web fonts and CDN stylesheets fetched. To render HTML online there is nothing to install and nothing to sign up for.
Someone sent you a .html or .htm file and you want to read it as a page.
Use Open .html file and pick it — .htm files work the same way. The file is read by this tab and never uploaded, so it is a safe way to view HTML online when you are not sure what the file contains: its scripts run inside a sandboxed frame that cannot reach this site or your session.
You are writing or fixing HTML and want a live preview while you type.
Edit in the left pane and the preview re-renders as you go, so this doubles as an HTML code viewer and a quick live preview for a colour, a heading or a layout fix. Separate HTML, CSS and JS panes are what a code playground is for — see the table above.
The page looks right and another person needs to see it too.
A preview only exists in your tab. Press publish and the same source becomes a link that renders for anyone, on a phone or a desktop, with no file to open.
Share an HTML file onlineThis one does. Most online viewers render the markup and drop the scripts, which is the wrong default: the reason you are looking at the page rather than the code is usually to check that it works. The preview here is a sandboxed frame, so the page runs its own scripts in an isolated origin — it cannot touch this site or your session, and you still get the real behaviour.
No. Opening a file reads it with the browser’s own file API and renders it locally; the same is true of pasting. Nothing is sent to a server unless you click publish, which is a separate, deliberate action that gives you a link.
Because a file is not a page. Mail clients do not render an HTML attachment inline, phones frequently have no app that will open one, and managed laptops often block local files outright — the file is fine, the delivery method is not. That is the whole problem behind opening an HTML file, and the reliable fix is to send a URL instead of a file.
Yes — the left pane is a plain editor. Type in it and the preview re-renders as you go, which makes it a quick way to try a colour, a heading or a copy change without setting up an editor. It is not a full IDE and does not pretend to be: no file tree, no autocomplete, no saving to disk. Publish when you want the result to persist.
Viewing is for you, right now, in this tab. Hosting puts the page at an address other people can open, which is the part a file cannot do. Publishing here is free and needs no account, and the link lasts seven days unless you extend it — see free HTML hosting for what the hosted version gets you.
Links gratuitos duram 7 dias com uma conta gratuita. Em um plano pago, cada página que você publica fica online permanentemente.
Ver preços