Your files never leave your browser
The short version: MakeItMarkdown is a static website. When you convert a document, the parsing happens inside your own browser. Your file is never uploaded, transmitted, or seen by us — there is no server that could receive it.
How conversion works
The site ships JavaScript parsers to your browser. When you drop a file, your browser reads it from your disk into its own memory, converts it to Markdown locally, and shows you the result. No network request carries your file or its contents anywhere.
You can verify this yourself in two ways:
- Go offline. Load the page once, disconnect from the internet, and convert a file. It works — because the conversion never needed a network.
- Watch the network tab. Open your browser's developer tools while converting. The only requests you'll see fetch the site's own code and fonts from our static host — never your document.
What is stored on your device
A few things are kept in your browser's local storage, on your device only, to make the tool nicer to use:
- Recent conversions — up to five converted results (Markdown text and the fidelity report, without embedded images) so you can reopen them. Remove them any time with the Clear button on the start screen, or by clearing the site's data in your browser settings.
- Theme choice — whether you picked light or dark mode.
- Offline cache — the site's own code and fonts, cached by a service worker so the tool loads fast and works offline. This cache contains our files, never yours.
None of this is visible to us. It lives in your browser, and clearing the site's data removes all of it.
What we don't do
- No accounts, no sign-in, no email collection.
- No analytics or tracking scripts at the time of writing.
- No cookies of our own. The only cookies that can appear on this site are advertising cookies, described in the next section — and in regions that require it, you are asked before any are set.
- No third-party requests during conversion — every library and font the converter uses is self-hosted, so converting a file doesn't ping anyone else's servers. Ad serving (below) is the one separate exception, and those requests never contain your files.
Advertising
To keep the project free, this site uses Google AdSense to serve advertising on its pages. (Ad units appear only after Google's review completes — until then the reserved spaces stay empty.) Two things hold regardless:
- Ads never see your files. Conversion is local, with or without ads on the page. Ad requests carry no part of your documents, and blocking ads does not break the converter.
- Ads never stand between you and your result — no popups, no overlays, no full-screen formats.
Cookies and identifiers. Third-party vendors, including Google, use cookies and device identifiers to serve and measure ads. Google's advertising cookies enable it and its partners to serve ads based on your visits to this site and/or other sites on the internet. How Google uses data when you visit a partner site is described at policies.google.com/technologies/partner-sites.
Your choices.
- Opt out of personalized advertising in Google Ads Settings, or opt out of many third-party vendors' advertising cookies at aboutads.info/choices (EU: youronlinechoices.com).
- If you visit from the EEA, the UK or Switzerland, a consent banner (a Google-certified consent management platform) asks before any advertising cookies are set. You can decline — non-personalized ads, which don't use cookies for personalization, may be shown instead — and you can change or withdraw your choice at any time through the banner's settings.
GitHub is the exception — by your choice
If you report a bug on our GitHub issue tracker and attach a sample file there, that attachment is uploaded to GitHub and visible to anyone who can see the issue. That is a deliberate act on GitHub's platform, separate from this site — strip anything confidential from samples first. Nothing you do inside the converter itself ever creates such an upload.
Changes
If this policy changes, the date at the top changes with it, and material changes will be called out in the site's public commit history. Questions? See contact.