Questions
Short answers about privacy, offline use, and what happens when a file won't process.
Are my files private?
Yes, structurally rather than by promise. Every tool runs in your browser, so your files are never sent anywhere. There is no server that could store them, and no operator who could read them. You can verify this yourself: open your browser's network tab while using a tool and you'll see no upload.
Do I need an internet connection?
Only for the initial page load. Once the processing libraries are in your browser you can disconnect and keep merging, splitting, compressing and editing. Two exceptions: OCR downloads a language model the first time you use it, and web fonts load from Google Fonts.
Are there file size or usage limits?
No artificial ones — no page caps, no daily quotas, no premium tier. The real limit is your device's memory and CPU. A 500-page scan being OCR'd will take a while on a modest laptop, because the work is happening there rather than on rented hardware.
Is my activity tracked?
No. There is no analytics script, no telemetry, and no cookies set by this app. The only outbound requests the page makes are for its own assets and the Google Fonts stylesheet.
Why did my PDF fail to process?
Usually one of three causes:
- The file is password-protected. Run it through Decrypt PDF first.
- The file is a dynamic XFA form, which most tools here cannot read.
- The file is corrupt or doesn't follow the PDF specification closely enough.
If none of those apply, the document may simply be large enough to exhaust the tab's memory — try splitting it first.
What is this built on?
Chiefly pdf-lib and PDFKit for writing PDFs, PDF.js for rendering them, and Tesseract.js for OCR — all compiled to run in the browser via WebAssembly. That is what makes server-grade processing possible without a server.