How browser-only PDF tools work (and why your file never gets uploaded)
Most online PDF tools upload your file to their server, process it there, and send it back. For a contract, a passport scan or a bank statement, that's a lot of trust. It doesn't have to work that way. Modern browsers c
Most online PDF tools upload your file to their server, process it there, and send it back. For a contract, a passport scan or a bank statement, that's a lot of trust.
It doesn't have to work that way. Modern browsers can do most PDF work on your own device. That's the idea behind ShamsPDF, a free set of 40+ PDF tools.
What runs in the browser
- Merge, split, rotate, reorder, delete pages: pdf-lib reads the PDF, moves pages around and writes a new file, all in memory.
- Previews and thumbnails: pdf.js renders each page to a canvas.
- Compress, sign, watermark, page numbers: also local. The download is created with a Blob URL, so nothing leaves the tab.
You can check this yourself: open DevTools β Network, run Merge, and you'll see no file upload.
What needs a server (and how it's handled)
Some jobs need heavy software:
- Word, Excel and PowerPoint to PDF (LibreOffice)
- PDF to Word
- OCR for scanned pages
For these, the file is sent over HTTPS, processed in a temporary folder, and deleted right after download (within 10 minutes at most). Files are virus-scanned before processing. The site says clearly which tools are browser-only and which use the server.
One feature I haven't seen elsewhere: Smart Arrange
If you scan a 20-page document and the pages come out in the wrong order, Smart Arrange reads the page numbers (OCR for scans), turns upside-down pages, and drops blank and duplicate pages. Then it puts everything back in order.
Try it
It's free, needs no sign-up, and works in 12 languages. If you find something broken or missing, I'd love to hear it in the comments.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.