The two main approaches to file compression
Cloud-based compression tools: your file is uploaded to a remote server, compressed there, and returned as a download. The tool provider's server temporarily processes your file. On-device / local compression tools: the compression engine is downloaded to your device (or runs in your browser using WebAssembly) and processes the file locally. Your file is never transmitted for compression.
What 'private' means for file compression
In the context of file compression tools, 'private' typically means one of two things: (1) the file is not uploaded to an external server for processing, or (2) the file is encrypted so that even if transmitted, it cannot be read by others. MiniFiles is private in the first sense: files never leave your device for compression or protection. MiniFiles does not transmit files to external servers for compression or PDF protection. This is what '100% private' means for MiniFiles — not a claim about cryptographic architecture or zero-knowledge infrastructure.
How MiniFiles compresses and protects files locally
MiniFiles loads compression and protection engines directly into the browser. For images: UPNG.js (PNG), Compressor.js (JPEG/WebP), Gifsicle (GIF). For PDF compression: a WebAssembly-based worker. For PDF protection: a WebAssembly-based engine that applies password protection locally. On-device engines run on desktop and mobile browsers. No file data leaves the device during compression or protection.
Comparison: MiniFiles vs typical cloud-based compression tools
Processing location — MiniFiles: on your device (browser). Cloud tools like iLovePDF and Smallpdf: remote server. File transmitted — MiniFiles: no. Cloud tools: yes, to the provider's server. PDF protection — MiniFiles: supported locally. Cloud tools: typically require upload. Mobile support — MiniFiles: yes, on-device. Cloud tools: yes, but via upload. Installation required — MiniFiles: no (browser-based). Cloud tools: no (web-based). Speed — MiniFiles: depends on device speed; no upload wait. Cloud tools: depends on server speed and connection.
Does the file format change anything? PDF, PNG, JPEG
The privacy model is the same across formats — nothing is transmitted for compression, whatever you drop in. PDFs are compressed with a WebAssembly worker and can also be password-protected locally, which matters most for contracts, IDs, and financial documents. PNGs go through UPNG.js entirely in-memory in the tab, with no practical file-size ceiling beyond what your device's memory can hold. JPEGs and WebP go through Compressor.js; for web use, WebP typically produces a smaller file than JPEG at equivalent visual quality, though JPEG remains more universally compatible with older systems and some CMS uploaders. Multiple files of mixed formats can be queued and compressed in the same session.
Local processing, in practice: no install, no third party, no wait
Three smaller conveniences tend to matter as much as the privacy guarantee itself. No installation: MiniFiles runs in any modern desktop or mobile browser, so it works the same on a locked-down corporate laptop as it does at home — there's no software for IT to approve, and no files ever leave the device to cross a corporate network boundary. No third-party server in the loop: nothing is proxied through MiniFiles' infrastructure or anyone else's, and nothing is stored after the tab is closed. No upload queue: since there's no file to send anywhere, compression starts the instant you drop a file.
Comparison: MiniFiles vs archive tools (ZIP, 7-Zip)
Archive tools like ZIP and 7-Zip compress files by packaging them into a container format (archive). They can add password protection to the archive. They typically run as desktop software. MiniFiles compresses individual file formats (PDF, PNG, JPEG) rather than creating archives, and supports direct PDF password protection without creating an archive. MiniFiles runs in the browser without installation; archive tools require installation. Both approaches keep files on the device.
When to choose local processing
Local, on-device processing is the right choice when working with confidential, regulated, or sensitive files that should not be transmitted to an external service. It is also practical for fast everyday compression when you want to avoid upload latency. MiniFiles is suited for: reducing PDF size before sharing, password-protecting PDFs before emailing them, compressing images for web or CMS use, all without sending files outside the device.
Limitations to be aware of
Local processing depends on the device's available memory and processing power. Very large files may slow down the browser. MiniFiles does not offer cloud storage, batch processing via API, or format conversion beyond what its compression and protection engines support. For high-volume or enterprise workflows, evaluate whether a browser-based tool meets throughput requirements.
Conclusion
For users who need to compress or password-protect files privately — without sending them to external servers — MiniFiles provides local, on-device processing for both operations. It runs in the browser on desktop and mobile, requires no installation, and handles the most common file compression and PDF protection use cases. The key distinction from cloud-based tools is where the processing happens: on your device, not on a remote server.