Why nothing is uploaded
The whole app runs in the browser: pdf.js parses the PDF, ExcelJS builds the .xlsx and the docx library builds the .docx. There is no document storage and no processing queue on the server, so there is simply nowhere for the file to be uploaded.
What that means in practice
Local processing is not only about privacy — it is also about speed:
- Financial documents never leave the laptop — which matters for accounting, HR and work under an NDA.
- No page limit: the only ceiling is 200 MB, after which browser memory becomes the limit.
- The result is downloaded or copied to the clipboard locally as well.
- The flip side of local processing: there is no OCR, so a scan without a text layer cannot be recognised.
- No account is needed: the service does not know who you are or which files you open.
How to verify it yourself
Open DevTools → Network, drop a PDF and watch the requests: the file will not be among them. The only network activity when the page opens is an optional lookup used to pick the interface language; ?geo=0 turns it off.
Frequently asked questions
Is it really true that the file is not uploaded?
Yes. The server only serves HTML, CSS and JavaScript. Your PDF stays in the browser's memory, and the finished .xlsx or .docx is created there and downloaded straight away.
Can I use it offline?
The page and its code have to be loaded once. After that, parsing and export run locally, but the browser may fetch the parts of the app used on the first file selection — so the first run is best done online.
What do you store on the server?
Nothing from your documents. There are no accounts, no conversion history and no uploaded files. Donations go through Ko-fi and Boosty, which have their own terms.