DeepSeek-OCR

pxpipe reflows text into ~1928px columns (~92,000 chars/page ≈ 4,761 vision tokens) and only converts where the math beats ~19 chars/token, claiming a 59–70% lower end-to-end bill. It's explicitly lossy: imaging a 12-char hex string recalled correctly only 13 of 15 times.

Commenters call it a token-accounting loophole, not efficiency. Gemini already OCRs PDFs and doesn't charge for the extracted text; a developer who tried the same trick last year got MORE completion tokens and a bigger bill.

Baidu open-sourced Unlimited-OCR, which parses long documents in one pass instead of chopping them into pages and gluing the text back. The trick (R-SWA): keep the full document image always in view, but cap memory of the model's own output to a small sliding window so the KV cache stops growing.

It openly credits DeepSeek-OCR and PaddleOCR for the ideas. The thread's skeptics ask the obvious thing: how is this better than just feeding one page at a time?