What Is a File Compressor and Which to Use
Last reviewed 2026-04-27. All tools below run in the browser on your own device - no file ever leaves your computer or phone.
Why "file compressor" is a search that splits five ways
The phrase "file compressor" sits at the very top of the funnel. Two-thirds of the people typing it into Google have not yet decided what kind of file they need to compress. Some are trying to email a 30 MB PowerPoint. Some are trying to fit a folder of receipts under a 5 MB upload limit. Some are trying to send 200 iPhone photos to a Windows desktop. Some are trying to make a 4 GB drone-footage MP4 small enough to share. The naive answer - "use a free file compressor" - leads each of those five users to the same tool, and four of them get a worse outcome than if they had picked the right specialist tool.
The decision tree is simple once you know it. The hard part is that no search engine reliably distinguishes between the five intents from the phrase "file compressor" alone. So this guide is the disambiguation layer. Read the table, jump to the section that matches your input, and skip the rest.
Decision table - what tool by what you have
| What you have | What to do | Tool | Typical size cut |
|---|---|---|---|
| A folder of mixed files (documents + photos + spreadsheets) | Make a ZIP archive | Zip File | 20-50% |
| Loose JPG / PNG photos | Lower the JPEG quality | Compress Image | 30-70% |
| iPhone HEIC photos that need to open on Windows / Android | Convert HEIC to JPG | HEIC to JPG | compatibility win; size similar |
| Several images for one recipient | Bundle them into one PDF | Images to PDF | 0-20% vs separate (one file, easier to send) |
| Several PDFs for one recipient | Merge into one PDF | Compose PDF | 5-15% |
| One large video / RAW photo / design source | Use a file-transfer link (Drive, Dropbox, WeTransfer) | (host, do not attach) | n/a |
Six kinds of compression, six different math
People say "compress" when they mean any of these. Each uses a fundamentally different algorithm and produces a different size cut for the same input.
- Lossless container compression (ZIP, 7z, RAR). Bundles many files into one archive and compresses the byte stream with DEFLATE / LZMA / LZMA2. Reversible - the extracted files are bit-for-bit identical to the originals. Excellent on text and source code (50-80% cut). Almost no effect on already-compressed media (JPG / MP4 / MP3 / PDF). The right choice when you need to preserve the exact files.
- Lossy image compression (JPEG quality, WebP). Discards visual information the human eye is least likely to notice and re-encodes the result. Drops a 5 MB JPG to 1 MB at quality 80 with no visible difference for most photos. Not reversible - once compressed at quality 60 you cannot recover the original. The right choice when the file is one image and the recipient does not care about pixel-perfect fidelity.
- Image format conversion (HEIC to JPG, PNG to JPG, TIFF to JPG). Changes the encoding format. The size change is a side-effect of moving from a less efficient format to a more efficient one. PNG to JPG cuts a 12 MB photograph to 1 MB; HEIC to JPG keeps the size similar but unlocks every Windows / Android device. The right choice when the file is the wrong format for the recipient.
- Lossy video compression (re-encode at lower bitrate). Re-encodes the video stream at a lower bits-per-second target. Cuts a 1 GB 4K MP4 to 200 MB at 1080p H.264 with acceptable quality. Browser tools handle short clips; long videos go through dedicated software like FFmpeg or HandBrake.
- Lossy audio compression (MP3 / AAC / OGG). Same idea as video but for sound. A 50 MB WAV becomes a 5 MB MP3 at 192 kbps. Browser ZIP does not help; the right move is format conversion.
- Hosting a transfer link. Not technically compression - the file stays the same size, but the recipient downloads it from a service instead of receiving an attachment. This is the only practical answer for files over ~25 MB, the upper bound for most email systems.
What ZIP actually does (and doesn't)
ZIP is the operation that comes to mind first because it has been the universal "compress this for me" verb on Windows since 1997 and on macOS since 2003. It is excellent at one specific job and weak at most others.
What ZIP is good at: bundling many files, preserving folder structure, applying a password to the bundle, compressing text-heavy content (source code, CSV, plain documents) by 50-80%. The output is one .zip file you can attach to an email or upload to a portal that does not let you upload folders. The ZIP File tool handles this in the browser without uploading anything.
What ZIP is weak at: compressing already-compressed media. JPG, PNG, MP3, MP4, HEIC, PDF are all internally compressed already; the DEFLATE algorithm cannot squeeze them further. Zipping a folder of 100 iPhone photos saves typically 1-3% of the total size, not 50%. If your folder is dominated by media files, ZIP is the wrong tool. How to make a zip file smaller covers what to do when ZIP underperforms.
When converting beats compressing
For single files, format conversion often beats compression by a wide margin because the source file was the wrong format for the use case:
- HEIC to JPG. A 3 MB iPhone HEIC opens on Windows only with a paid codec; the JPG copy is 1.5-3 MB but opens everywhere. The conversion is about compatibility, not size. Run it through HEIC to JPG. For more context on HEIC see HEIC vs JPG vs WebP - when to use each format.
- PNG to JPG (for photos). A 12 MB PNG photograph becomes a 1.2 MB JPG at quality 85. PNG is a lossless format intended for screenshots and graphics; using it for photos wastes 90% of the file size. Reserve PNG for transparency, line art, or pixel-perfect screenshots.
- TIFF / BMP to JPG. Both are 5-10x larger than JPG for the same visible content. Convert before sending; recipients on phones often cannot open TIFF at all.
- WAV to MP3. A 50 MB WAV becomes a 5 MB MP3 at 192 kbps. Browser ZIP does not help; the right move is format conversion in dedicated audio software.
Privacy: why "browser-only" matters
Most of the "free file compressor" results upload your files to a server, run the compression in their cloud, and email you a download link. That is fine for cat photos. It is not fine for HR forms, medical records, contracts, source code, or anything subject to GDPR / HIPAA. The five tools listed in this guide all run on your own device using browser-native APIs (the ZIP tool uses the JavaScript Streams + Compression Streams API; the image tools use the Canvas + FileReader APIs; HEIC conversion uses libheif compiled to WASM). Nothing leaves your computer or phone.
For more on this category see free online tools that work without uploading files.
What to do next
Pick the section above that matches your input and click through to the right tool. If you have a folder for email and you want a step-by-step rather than a tool tour, jump straight to how to compress a folder for email. If your input is one file rather than a folder, see how to compress a file online. If you already have a ZIP that is too big, see how to reduce zip file size online.
Why trust these tools
- Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
- Truly in-browser - no upload. Every file-processing tool on this site runs in your browser through modern Web APIs (File, FileReader, Canvas, Web Audio, WebGL, Web Workers). Your photo, PDF, audio, or text never leaves your device.
- No tracking during tool use. Analytics ends at the page view. The actual input you paste, drop, or capture is never sent to any server and never written to any log.
- Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
- Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.