About All Markdown

The models I use all day hand back Markdown, and reading one of those files meant opening a code editor: a lot of machinery for a document. I wanted it in a browser tab instead, and I wanted it to be a real editor once it was open. That is what this is. It is published by Simov Studio LTD, a company registered in Cyprus, and the free version runs entirely on your device: no account, nothing uploaded.

Why it exists

The files arrive constantly. Every conversation with a model that produces something worth keeping produces a .md file, and so does every README, changelog and page of notes. The usual way to read one is to open a code editor, which works, and which is a strange amount of ceremony for looking at a document.

So the bar was whatever an ordinary day actually asks for: open the file in the browser straight away, with no sign-up; find a real editor rather than a text box once it is open; still have the work there on the next visit; edit the rendered preview directly instead of hunting for the right line in the source; export to PDF, Word, HTML or Markdown; drop in a .docx or paste a web page and get clean Markdown out; and move the interface around until it suits the way you work.

There is no shortage of Markdown tools, and plenty of them do two or three of those things well. I could not find one that did all of them, and the ones that came closest were rough exactly where I spend the most time. So I built the one I wanted to use, and then I used it every day. That last part is most of why it is the way it is.

Most of this was built because I needed it that afternoon

I wrote this site's own documentation in it. Every feature below exists because something was annoying while I was doing that:

• Tabs and folders, because a README, a CHANGELOG and three notes files is a normal afternoon, and one text box is not.
• Editing the rendered document, because switching to the source to fix one word in a table is a silly thing to have to do.
• Version history, because I deleted a section, saved, and wanted it back an hour later, which is well past the end of any undo stack.
• Share links that carry the document, because I wanted to send someone a draft without uploading it anywhere, and it turns out the part of a URL after the # never goes to a server.
• The template library, because I had written the same README skeleton six times and it was time to stop.

That is also the honest reason some things are missing. If I have not needed it, I have probably not built it, which is where an email comes in.

The one rule

Your files never leave your device. Not "we do not look at them", not "we delete them after 24 hours": they are never sent. Everything here, every conversion, every export, every preview, runs in the browser tab you have open.

That is a design constraint rather than a policy, and it is the interesting part of the project. It means there is no server to receive a document, so there is nothing to breach, nothing to subpoena and nothing to quietly change my mind about later. It also means the site works with the network switched off, which is worth trying once because it makes the claim concrete in a way a privacy page cannot.

It costs something, and the cost is worth naming: anything that genuinely needs a server (syncing between your devices, collaborating with someone else in real time) cannot work this way. Those are real features and other tools have them. If any of it is ever built here it will be an optional account you choose to make, sitting beside these tools rather than changing them, because the free version staying on your device is the whole point of it.

What it does not do

• No account, so no password to lose and no profile to delete.
• No uploads, so no file of yours sits on a machine you do not control.
• No ads and no affiliate links.
• No AI features that send your document to a model somewhere.
• No analytics that can see inside a document: page-level and cookieless only. The privacy page names the provider and lists every event it sends.

That is every tool on the site as it stands, and it is what the free version goes on doing whatever else gets built beside it.

Who is behind this

Built by Aleksandar "Aleks" Simov, founder of Simov Studio, building websites since 2012.

He holds a Bachelor of Engineering in Information Technologies from the Faculty of Computer Science and Engineering at Ss. Cyril and Methodius University in Skopje, with design training at the Design Academy at SEDS.

Simov Studio is a web design & development studio: client work and its own independent products. All Markdown is one of them, published through Simov Studio LTD, registered in Cyprus. More about me and my other work is at simov.co.

Elsewhere: LinkedIn, X, GitHub, YouTube.

And when you email hello@simov.studio, it goes to the people who build All Markdown, not to a support queue. A reply might take a day.

How it is built

Static HTML, CSS and JavaScript, served from Cloudflare's edge. No framework in the app itself, no bundler for the code you run, no third-party scripts on the critical path. The Markdown is parsed by marked and sanitized by DOMPurify, both vendored into the site rather than fetched from a CDN, so no other host learns which pages you visit.

It is boring on purpose. Boring survives, and a tool you can rely on for ten years is more useful than a clever one that stops working when somebody's API changes.

Get in touch

hello@simov.studio: bugs, feature requests, a Markdown file that renders wrong, or anything about Simov Studio. A file that reproduces a problem is the most useful thing you can send.