Compress PDF without uploading
Everything happens in your browser tab. Nothing is sent to any server. Watch the byte counter at the bottom — it stays at zero.
↑ 0 B of your file sent·↓ 0 B (page + engine)
Common questions (5)
How can a PDF compressor work without uploading my file?
Modern browsers can run real compression code directly via WebAssembly. fits.tools downloads a small compression engine on your first visit (about 3 MB, cached for next time), then runs it on your file inside the same browser tab. No file ever leaves the tab.
How do I verify nothing is uploaded?
Open your browser’s Developer Tools → Network tab, then drop a PDF on the page and run the compression. You’ll see asset fetches for the page and engine, but no upload of your PDF. The site’s Content-Security-Policy header also blocks any cross-origin upload attempt at the browser level.
Why do other "free PDF compressors" require uploading?
Historically, browsers couldn’t run heavy compression code fast enough, so tools sent files to a server to do the work. WebAssembly (since 2017) and browser-side PDF libraries changed that. Most major compressors haven’t caught up — fits.tools is built around the new model from day one.
Is fits.tools really free, or is "free" the bait?
It’s free. There’s no signup, no daily limit, no watermark, no upsell. fits.tools has no document-handling server, which means almost zero cost-per-use to run — that’s what makes "free" actually free here.
What about confidential documents — passports, contracts, medical records?
Compressing them with fits.tools is exactly as safe as opening them in your own PDF viewer: the data stays on your device. No copy is made anywhere we control. That makes fits.tools appropriate for documents where the upload-then-trust model of other tools would be a non-starter.