Updated September 2026
Because this tool runs entirely inside your browser rather than as installed software, there's no separate "Windows version" or "Mac version" to download — the same compressor works anywhere a modern browser does. Here's what to expect on each platform, and the handful of things that genuinely differ.
The compression engine is WebAssembly — code that runs inside the browser tab itself, at near-native speed, on any operating system the browser supports. There's no installer, no admin permissions needed, and nothing OS-specific about the compression logic. If your browser can run modern web pages, it can run this.
Works in Chrome, Edge, or Firefox on Windows 10 or 11 with no special setup. Drag-and-drop from File Explorer works directly onto the drop zone, or use "choose files" to browse. No admin rights are needed since nothing installs — useful on a locked-down work laptop where installing desktop PDF software isn't an option.
Works the same way in Safari, Chrome, or Edge on macOS. Drag-and-drop from Finder works the same as Windows Explorer. If you're used to macOS's built-in Preview app for basic PDF viewing, this tool is a useful complement for cases Preview doesn't handle well — batch compression across many files at once, in particular.
Safari on iOS supports the same WebAssembly engine, so single-file compression works the same way — tap "choose files" to pick a PDF from Files, iCloud Drive, or wherever it's stored, or from a share sheet if you're compressing something you just scanned with the Notes or Files app scanner. Drag-and-drop between apps works on iPad in split-screen; on iPhone, use the file picker instead. Very large scanned PDFs can be slower to process than on a desktop, simply because phones generally have less available memory — for a big multi-page scan, expect it to take a bit longer rather than fail outright.
Chrome on Android handles this the same way as desktop Chrome — pick a file from your device storage or Downloads folder. As with iOS, large files may process more slowly on lower-memory devices; if a very large scan seems stuck, giving it more time (rather than force-closing the tab) usually finishes the job.
Any Linux distribution running a modern Chromium- or Firefox-based browser works identically to Windows and Mac — there's no OS check anywhere in the tool, since the browser is the only thing that matters.
The practical ceiling on file size isn't tied to Windows vs. Mac vs. mobile as such — it's tied to how much memory your specific browser tab has available. A desktop or laptop with several gigabytes of free RAM will comfortably handle very large scanned PDFs; an older phone with many other apps open might struggle with the same file. If a compression seems to hang on a mobile device, closing other tabs and apps first, or switching to a desktop for that one large file, usually resolves it.
The WebAssembly engine downloads once (a few megabytes) the first time you load the page, then the tool keeps working even without an internet connection — useful on a flight, in an area with poor signal, or anywhere you'd rather not rely on connectivity to get a file compressed. This is also indirect proof of the privacy claim: a tool that needed to upload your file to a server couldn't possibly keep working offline.
A desktop PDF utility has its own advantages, but it also means an install, permissions, and keeping it updated across every machine you use — a laptop, a work desktop, a family iMac. A browser-based tool skips all of that: the "install" is just visiting the page once, and it's immediately the same tool on the next device, with no separate license or download per platform.
Do I need to install anything? No — it's a website, not an app. Nothing to download from an app store, nothing to keep updated.
Does the compression result differ by device? No — the same MuPDF-based engine and the same two-pass logic run identically regardless of platform; see how compression works for the exact process.
Does the batch feature work the same on mobile? Yes — the batch unlock and compression flow work identically on any device with a browser; a large batch will simply take longer on a lower-memory phone than on a desktop.