Edit any HTML file visually — no code required

No. The file is read by your browser and stays on your device. There is no server involved in the editing at all — you can disconnect from the internet and the editor keeps working.

In Chrome and Edge, yes — open the file with the Open HTML File button, grant access once in the file dialog, and Save writes straight back to it with no further prompts. Brave ships with that API turned off by default for privacy, and Firefox and Safari have not implemented it, so on those browsers Save downloads an edited copy instead. The editor tells you which of the two will happen before you press Save.

That means the editor has no write access to your original, so it is falling back to a download — and your browser is set to ask where downloads go. Two things cause it: opening the file by dragging it in rather than using the Open HTML File button, or a browser that blocks file writing altogether. The line under the filename in the sidebar tells you which one applies.

Scripts are deliberately disabled inside the preview. An HTML file you open is untrusted, and letting its JavaScript run on this site would give it access to your browser storage for this domain. Static pages render exactly as they will look; pages that build themselves with JavaScript will appear incomplete.

You will see a warning. Those pages generate their content from JavaScript at runtime, so text you edit in the saved HTML is usually regenerated and lost the next time the page runs. The editor is designed for plain static HTML.

Yes. Add a data-edit attribute to any element in your HTML, and only elements carrying that attribute become editable — everything else stays locked. This is useful when handing a page to a client to update.

Static HTML that someone else built and you now have to keep current: a landing page from a template marketplace, a brochure site, an emailed HTML newsletter, a course or portfolio page, a one-file report. The common case is a page where the text is wrong or a photo is out of date, the person who built it is unavailable, and the change is genuinely five words long. Opening that in a code editor means finding the right line among a thousand; opening it here means clicking the words.

It does not reformat. The document you save is your document with the parts you edited changed and everything else — indentation, comments, attribute order, the script tags it refused to run — left exactly as it was. Everything the editor injects while you work is prefixed so it cannot collide with your own class names, and all of it is stripped again on save. A file you open and save without touching anything comes back essentially unchanged.

Links are edited in the side panel rather than by clicking through them, so you can change where a button points without the preview navigating away from you. Images can be replaced with a file from your device or an address. What you cannot do is restructure the page — this is an editor for changing content in place, not a page builder, and a tool that let you drag sections around would have to rewrite the markup it is trying to preserve.

Because developer tools change the page in memory and forget everything the moment you reload. It is the right tool for checking whether a change would look good and the wrong one for making it permanent. This editor holds a real link to the file on your disk, so pressing Save changes the file rather than the view of it.

It turns the whole thing into a locked-down editor for one specific page. Put data-edit on the three elements a client is allowed to change and nothing else on that page responds to a click, so there is no way to accidentally overwrite the navigation or delete a footer while updating a price. Hand over the file and the tool, and the worst outcome is that the price is wrong.

That is exactly why scripts are blocked in it. An HTML file is executable content, and a page whose JavaScript ran inside this site could read anything this site has stored in your browser. The preview is rendered with scripting disabled and no access to this origin, so the worst a malicious file can do is look wrong. The cost is that pages which build themselves with JavaScript appear incomplete — which is also the honest signal that they are not the kind of page this tool can edit.

Your changes are saved to your browser as a draft while you work. Reopen the same file and the editor offers to restore them.