Compress PDF on Linux

It runs a comparable optimization pipeline with a graphical interface. Ghostscript gives you four coarse -dPDFSETTINGS presets; this adds an exact target-size search and shows the resulting size immediately. For scripted batch jobs on a server the CLI remains the right tool — for interactive one-off compression, this is considerably faster.

Firefox, Chrome, Chromium, Brave, Vivaldi and Edge for Linux all work. Any browser with WebAssembly support is fine. Chromium-based browsers tend to be somewhat faster on very large documents due to their memory allocation behaviour.

Yes, and that is the main advantage on a managed system. There is no package to install, no dependency to resolve and no root access required — useful on shared workstations, university lab machines or hardened corporate Linux builds.

No. Compression runs entirely inside your browser using WebAssembly. Your PDF is read into local memory, processed on your own CPU and written straight back to your downloads folder. No network request ever carries the file.

Yes, and this is usually desirable. Author names, the originating software, revision history, comment threads and XMP blocks are stripped. That reduces file size and removes information you may not want to share — a genuine privacy benefit when sending documents externally.

Yes. The interface is fully responsive and the engine runs on iOS and Android. Bear in mind that mobile devices have less memory, so very large files (over roughly 50 MB) may be slow or fail on older phones.

Very well, because the file itself is never transmitted. Only the page and the compression engine are downloaded, once, and they are then cached. Uploading a 100 MB PDF to a server-based tool would consume 100 MB of your data allowance; here it consumes none.

Yes. Bookmarks, the table of contents, internal cross-references, hyperlink annotations and interactive form fields all survive compression. Only the encoding of images and content streams is altered — the document's structural and navigational layers are preserved.

Yes. Drop in as many files as you like — they are queued and processed one after another so memory stays under control. Each file gets its own progress bar and download button, plus there is a Download All option.

Rarely, and it is usually counterproductive. The first pass already removes structural waste and downsamples images; a second pass mostly re-encodes already-degraded JPEGs, which loses more quality for negligible gain. Prefer a stronger preset on the original file instead.