About All Markdown

I built this because I kept needing it and could not find it. It is made by one person, Aleksandar Simov, at Simov Studio LTD — a small company registered in Cyprus. No funding, no accounts, no uploads, and no plans for any of the three.

Why it exists

There is no shortage of Markdown tools. That was the problem. Every time I needed one — open a .md file someone had sent me, turn a Word document into Markdown, get a clean PDF out of a README — I would find something that did that one job, and only that job, and usually with a sign-up wall in front of it or an upload I did not want to make.

The ones that did not ask me to sign in tended to be worse in a different way: a text box and a preview pane, no tabs, no way to open a file, a layout that fell apart on a phone. I never found one where everything was right at once — easy to start using, no login, a genuinely good editor, plenty of features, and still a clean interface. Most tools get one of those right. Very few get two.

So I made the one I wanted, and then I used it. 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 — accounts, syncing between your devices, collaborating with someone else in real time — is not here and cannot be, in this form. Those are real features and other tools have them. This one has the other thing.

What it does not do

• No account, so no password to lose and no profile to delete.
• No uploads, so no file of yours is on a machine I 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.

Who "we" is

Mostly it is "I". Aleksandar Simov — some people write it Aleks — building and maintaining this through Simov Studio LTD, registered in Cyprus. The company is how invoices and terms work; the site is one person's project.

This matters for one practical reason: when you email hello@simov.studio, you are writing to the person who wrote the code. There is no support queue and no first-line script. 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 sanitised 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.