Show HN: CPU-only fast OCR for screenshots, images, PDFs, webpages

3 pointsposted 7 hours ago
by mrkn1

5 Comments

atmanactive

4 hours ago

Nice, thanks! After reading the whole Github ReadMe, it's not clear to me how is the clipboard handled: if I have an image in my clipboard and I run textsnap with no arguments, where is the OCR text stored, back in the clipboard (that would be ideal)? Unrelated, I wish textsnap would look for it's model files not only in the well-known operating system's dir, but also next to itself (portable mode), as that would enable me to copy/move textsnap directory together with the model files to any computer and just use it from there without any setup steps necessary. The --model-dir is useful, but it is also cumbersome for day to day use. In other words, it would be great if --model-dir is understood to be wherever textsnap executable is, by default. Thanks.

PeterStuer

3 hours ago

I've been using docling-serv on one of my machines with a modest gpu. How does this compare?

freakynit

7 hours ago

Cool tool... but, did you just vibe-coded this on similar lines as yapsnap? I sense an eerie similarity between the two. Yapsnap also was on frontpage today itself.

https://news.ycombinator.com/item?id=48214399

Nevertheless, very useful.

Thanks..

mrkn1

7 hours ago

thanks! yapsnap is audio to text, and textsnap is image to text. Both have been daily use cases for me for a while. And yes, the feedback on yapsnap encouraged me to also release textsnap on github

freakynit

4 hours ago

Oh.. I didnt even notice it earlier.. you are also the author of yapsnap.. hence the similarity...

I loved the simplicity in both. They both work, without the bloat.