View an HTML file online.

No. The viewer reads the file in your browser and renders it there, so it never leaves your machine. The file is never sent to a server and nothing about it is logged.

Yes. Embedded CSS applies and JavaScript executes, so the page behaves the way it was built to. The frame is sandboxed, so modal dialogs like alert() are suppressed and the file cannot redirect the page around it.

Files referenced by a relative path, like styles.css or img/logo.png, have nothing to resolve against once the page is read out of its folder. Anything linked by a full https:// address, including CDN libraries, loads normally. A folder of files that belong together is better hosted as a ZIP, which serves the whole project with its paths intact.

The render is sandboxed on a separate origin with no access to this page, its cookies, or your NudgeHost account, which contains what the file can do here. Knowing where an unfamiliar file came from is still worth doing before you run it anywhere else.

Up to 2MB. A bigger file is refused with a message giving its size, and none of it is read.

Yes. Open Or paste markup instead and paste the code. The frame redraws a moment after you stop typing, so you can edit it in the box and watch the result. Whichever you used last, the file or the box, is what the frame shows.

Files ending in .html or .htm. Anything else that holds markup can go in the paste box instead.

They show, but submitting one does nothing, because the viewer's frame doesn't allow form submission. A hosted HTML page does allow it, so a form there sends its data wherever it points.

Not in the viewer. The frame blocks pop-ups and new windows, so a link set to open in a new tab does nothing. A hosted page allows them.

No. The frame has no origin of its own, so it can't read or set cookies or use local storage, and a page that depends on them may show an error or an empty state.

Only from a service that accepts requests from any origin, since the frame has none of its own. Anything that needs a login or your cookies won't answer.

Yes, once the page has loaded. Anything the file pulls in from a web address, such as a font or a script from a CDN, still needs a connection.

UTF-8. A page saved in another encoding can show stray characters where accented letters should be, and re-saving it as UTF-8 fixes that.

Browsers are forgiving with markup, so the frame shows whatever the code produces, missing tags and all. The viewer doesn't check or correct it.

So the page can't push the rest of this one around. A longer page scrolls inside the frame.

Yes. There's no account, no limit on how many files you open, and nothing to pay.

The page and the file's contents go with it. Nothing was stored, so there's nothing to delete.

No. The viewer stores nothing about the files you choose or the markup you paste.

Yes. A hosted HTML file opens in a sandboxed frame that allows scripts, forms and pop-ups, and keeps the page away from NudgeHost's own pages and your cookies.

Yes, a free one, made with an email address or Google and no card. You can pick the file first. It waits in your browser while you sign up and goes live in the new account. Whoever opens the link needs no account.

On the free plan, 14 days. On Pro and Studio it stays up until you delete it, and any account can give it an earlier end date.

No. The page opens under the viewer's slim header with its filename, and no plan adds a bar to the page itself.

Yes, on any account plan. Upload the new version over the old one and the same link shows it, with the view count and any settings kept.

Not by name. A hosted link counts its opens on every account plan, and Pro and Studio add the time and country of each one, with a CSV export.

Yes, on Pro and Studio. Anyone who opens the link enters the password before the page appears. A password-protected site doesn't serve on a custom domain, so pick one or the other.

A NudgeHost card with an HTML label and the page's title, or the file name when the page has no title. A password-protected link shows the standard NudgeHost card instead.

No. The page behind a hosted file link asks search engines not to index it, so it reaches the people you send it to.

No. It reads the file and never writes to it, so the copy on your disk stays exactly as it was.

No. The page exists only in your tab, so there's no address to send anyone. Hosting the file is the step that gives it one.

Only once it's saved as an HTML file. The viewer opens files from your computer and has no box for a web address.

Yes, if your computer's file picker can reach it. The viewer reads whatever file you choose, wherever it's stored.

Yes, when the media is inside the file or linked by a full web address. Whether it starts on its own follows your browser's usual rules.

The viewer opens a file you already have. The HTML tester in the dev tools is an editor for writing markup and watching it render as you type.

Yes, as long as your browser can open this page. Nothing gets installed, and the file stays on the machine it came from.

No. Choosing a new file replaces the one in the frame, and nothing from the first one is kept.

The viewer shows the rendered page rather than the code. Paste the markup into the box and it stays visible above the frame, or open the file in a text editor.

No. The viewer reads only the file you choose, and the page inside the frame can't open anything else on your disk.

No. The frame doesn't allow downloads, so a button in the page that would save a file does nothing.

No. The frame isn't allowed to take over the screen, so a full-screen button in the page does nothing.

No. The frame isn't granted those permissions, so the page can't ask you for them.

A build that fits in one file runs, since its script sits inside the page. A build split across several files needs the others beside it, which is what a zipped site is for.

Yes, as long as it's saved as a .html or .htm file. Images the email loads from a web address appear, and images that were attachments to the email don't, because they aren't in the file.

Yes. The viewer itself is a script running in this page, and it's what reads the file and fills the frame.

Yes, on every plan. Name the link in the upload card on the homepage before you drop the file, and it reads like nudgehost.com/launch-page instead of a random string.

No. There's no visitor cap on any plan, so the link keeps working however many people open it.

Not a single file. A custom domain attaches to a zipped site, on a subdomain, and comes with Pro and Studio.

It stops opening straight away. Anyone who follows the link afterwards lands on a page saying there is no file there.