Privacy
Where your files go (nowhere)
The short version: your PDF stays on your machine. The whole conversion runs locally, in your browser, so the file is never uploaded and I never receive it. There is nothing to trust me with, because nothing reaches me.
Most PDF tools want you to upload your document to their server first. Some of what I work with is sensitive, and I never liked the idea of my files sitting on someone else’s machine. So this one was built the other way around. Below is exactly what happens to your file, and an honest answer on the questions people keep asking: open source, self-hosting, and private deployment.
What actually happens to your file
- Your file never leaves your device. The PDF is read and converted by code running in your own browser tab. It is not uploaded to a server, because there is no server in the loop for the conversion.
- No account, no sign-up. You do not create an account or hand over an email to use it. Open the page, pick a file, get Markdown back.
- Nothing for me to see. Since your file is parsed locally, I never receive it. There is no copy on my side to store, log, or leak.
- Works without a connection. Once the page has loaded, the conversion itself does not need the network. You can disconnect and it still runs.
- Verify it yourself. Open your browser’s DevTools, watch the Network tab, and convert a file. You will not see your PDF go out.
One honest caveat: the tool loads a few things over the network the normal way a web page does (the app code, fonts, and a built-in sample file if you try it). What it does not send is your PDF. That part stays local.
Open source & self-hosting
I’ll be straight about where this stands, rather than dress it up. The code is not open source today, and there is no official self-host build yet. Both come up a lot, and both are on my “considering” list, but I’d rather not promise a date I can’t keep.
The good news is that privacy here doesn’t depend on either one. The conversion already runs on your own device, so you get the “my files stay mine” part today, without waiting for a self-host release. If a self-host or open-source version is the thing that would actually make this work for you, that is exactly what I want to know.
One thing I’ll leave the door open on: some hard jobs (heavy OCR, big batches) are tough inside a browser tab, so down the road there may be an optional server-side path, and a paid tier to go with the bigger stuff. If that ever happens it’d be a clearly-marked choice, never the default. The free, in-browser tool you’re using now stays local and private either way.
Need self-hosting, a private deployment, or a Pro version?
I’m trying to figure out who actually needs what here, so I can build the right thing instead of guessing. Tick whatever matters to you and, if you like, leave a word on why. Email is optional, only fill it in if you want me to follow up.
Got it, thank you 🧡 This goes straight onto my list. If you left an email, I’ll reach out when there’s something to share.
— Jerome
Questions people keep asking
Do my files get uploaded to a server?
No. The conversion runs entirely in your browser, on your own device. Your PDF is never sent to a server, and there is no cloud API in the loop.
Is pdfmarkdown.app open source?
Not yet. The code is not public today. Open-sourcing it is something I am considering, but I am not promising a date I cannot keep.
Can I self-host or run it offline?
There is no official self-host build today. That said, the conversion already runs locally in your browser, so once the page has loaded you can convert files with the network disconnected. A proper self-host option is on the “considering” list, not a commitment.
Do you store or log my documents?
No. Because your file is processed locally and never reaches me, there is nothing on my side to store or log. I cannot see your documents.
I have a private deployment or enterprise need. What now?
Email me at hey@pdfmarkdown.app and tell me what you need. I am collecting these to figure out whether a self-host or private-deployment option is worth building, and what it should do.
That’s the privacy story: convert in your browser, keep your file, hand over nothing. If you want to see where the rest of the tool is heading, the roadmap lays out what works, what’s rough, and the maybe-someday server-side option.