Also, it seems disingenuous to have “locally” in the title when your default is cloud inference providers and I don't see you naming a recommended LLM that could be hosted locally and is proven to work well for this task. You list “Your files” under “Stays on your machine” and then require an API key for a cloud provider.
Worth noting there’s also textsnap if you want something that’s actually local end-to-end via ONNX on CPU, no GPU, no API key, nothing leaves your machine. https://github.com/kouhxp/textsnap
https://github.com/amitxm/AIDocPrep is the one I built that is true local OCR. I made sure there is NO internet use, even accidentally. Also, added redaction.
I built a free tool(https://mdpdf.net), based on the fast PDF conversion library (https://github.com/firecrawl/pdf-inspector). It runs entirely in the user’s browser. In my view, the biggest pain points when converting PDF to Markdown are whether it can properly handle content like tables and code blocks, as well as OCR. Current OCR approaches don’t seem very effective unless you use an LLM.
21 comments
[ 3.8 ms ] story [ 10.7 ms ] threadAlso, it seems disingenuous to have “locally” in the title when your default is cloud inference providers and I don't see you naming a recommended LLM that could be hosted locally and is proven to work well for this task. You list “Your files” under “Stays on your machine” and then require an API key for a cloud provider.
And you could even try it online in browser (no any data sent to server): https://docling-project.github.io/docling.rs/