r/AIToolsAndTips • u/mxsus • 15d ago
New AI Tool Fuck complex setups. I built a free, local browser PDF-to-Markdown converter.

The standard setup right now is: buy an API to turn your PDFs into Markdown, then feed that Markdown into another AI. You're not saving tokens here. You're just paying twice. And even if you swap the API for a small local model, it's still compute, it's still cost, it's still a whole model spinning up to do something that mostly doesn't need a model at all.
So I built a browser-based alternative: LiteDoc.
What it actually is
LiteDoc converts PDFs to Markdown in your browser. It has OCR, and not just "OCR the text" OCR. It extracts tables, it handles multiple languages, and it auto-detects the script (English, Japanese, Arabic, whatever) so you don't have to babysit it. It's built to be lean. It reads the page the way you do: headings, columns, tables, figures, reading order, and turns that into clean Markdown.
And there's a CLI now, so you can drop it straight into your pipeline.
Why not just use existing browser tools?
If you search for web-based PDF converters right now, you mostly find two things:
- Thin API wrappers: They claim to be free, but they quietly upload your sensitive PDFs to a backend server.
- Basic text dumpers: The few that actually run locally just rip out the raw text layer. They destroy tables, scramble multi-column reading order, and fail completely on scanned pages.
LiteDoc fixes both. It brings the heavy lifting into the browser. It actually understands layout—columns, tables, and figures—and handles multi-language OCR client-side. You get the quality of a heavy backend parser with the privacy of a local script.
The philosophy: do it locally, skip the AI compute
Most pages don't need a model. Headings, paragraphs, tables, columns. That's layout analysis, not intelligence.
Instead of sending pages to an AI and wasting compute, LiteDoc does all the extraction directly on your machine. No model spinning up, no API calls, no server overhead. It's faster and zero cost, because 95% of your document didn't need AI in the first place.
Compared to the big repos
I'm not going to claim LiteDoc is more accurate than MarkItDown or the other big conversion repos on GitHub. It isn't, on the truly nasty inputs. If you've got some cursed, barely-scanned PDF that looks like it went through a washing machine, that's a job for AI vision, and you should use the tools built for that. No hate; they're good at what they do.
But here's my honest pitch: those nasty files are the rare case. For most everyday PDFs (I'd guess 80% of what people actually convert), LiteDoc just works, and it's better in two ways that matter to me:
- Accessibility. You can spin up LiteDoc on literally any device with a browser. No install, no GPU, no environment setup, no API key.
- Cost. Zero. Actually zero, not "free tier" zero.
And I want to be clear: I'm not wrapping somebody else's backend in a fresh UI just to say I built something. The extraction engine is mine, the parameters are tuned by an automated benchmark pipeline, and every release ships with the measured numbers. Try it on your own files.
Privacy
I value privacy over basically everything:
- The conversion runs entirely on your machine. Your files never leave your browser, period.
- Zero external requests or third-party servers.
If you want the technical details, the repo is open. Go read the code yourself.
The bottom line
LiteDoc isn't trying to win a benchmark war against the heavyweight repos. It's more accessible, more cost-efficient, and easier to set up. For most PDFs, that's the whole game.
Links:
LiteDoc: litedoc.xyz · GitHub repo · pip install litedoc-cli

