Client-side processing, by design

Every tool on Codrenix Toolbox runs entirely in your browser using client-side JavaScript. When you open a file, it is read into your browser's memory and processed by libraries that were downloaded with the page — the same code, running on your device, that other sites run on their servers. There is no upload step because there is nothing to upload to.

No storage, no upload pipeline

We operate no file storage and no upload endpoint. Processed results are saved back to your device by your own browser when you click download. Close or refresh the tab and everything in memory is gone — we could not recover your files even if you asked us to.

Tool by tool

• PDF tools (merge, split, compress, rotate, protect, unlock, sign, watermark, page numbers, OCR, conversions) use in-browser PDF libraries. Password protection uses AES-256 encryption applied locally before the file is saved.
• Image tools (resize, compress, convert) use the browser's canvas API to re-encode images locally.
• Password generator uses your browser's cryptographic random number generator (Web Crypto) — the passwords never exist anywhere outside your tab.
• QR code generator encodes data locally; the generated PNG/SVG is drawn in your browser.
• Unit converter is plain arithmetic in JavaScript — no data involved at all.

No accounts, no tracking of your work

There is no sign-up, no login and no email required, so there is no profile connected to the documents you process. We do not run analytics, we do not use advertising cookies, and we do not see, store or process the contents of your files. See our privacy policy for the full details.

Honest limits

Client-side processing means very large files are limited by your device's memory rather than a server. It also means a malicious or compromised browser extension could in principle read page memory — the same is true of every browser-based tool. If a future tool ever needs server processing, that tool's page will state it clearly before you use it.