Reduce File Size for Transfer: Quick Compression Guide
Reduce file sizes before transferring without losing quality. Quick tips for compressing images, videos, PDFs, and documents for faster sharing.
To reduce a file before sending it, pick the right codec for the format: H.265 or AV1 for video, WebP or AVIF for images, linearized PDF with downsampled images, and 7-Zip with LZMA2 for mixed archives. A 4K MP4 can drop from 8 GB to 1.2 GB without visible quality loss, and a 300 MB scanned PDF often shrinks to 40 MB once its embedded images are resampled from 600 DPI to 150 DPI. The codec matters more than the compression level.
Why file size dictates transfer time
A 100 Mbps upload line transfers roughly 12.5 MB per second in theory, and closer to 9 MB per second after TCP overhead, TLS handshakes, and the realities of residential ISPs. That means a 10 GB master file needs about 18 minutes under ideal conditions, and often more than an hour on consumer fiber during peak hours. Shaving a file down to 3 GB isn't cosmetic; it's the difference between a transfer that finishes before your meeting and one that doesn't.
Every major transfer service sets a ceiling. WeTransfer caps free users at 2 GB, Smash removes size limits but throttles aggressively past 2 GB, Dropbox Transfer free tier sits at 100 MB. If your file is bigger than the ceiling, compression isn't optional, it's mandatory.
Video: the biggest wins happen here
Video files are almost always the largest thing you need to send, and the most compressible. The default export settings in Premiere Pro, Final Cut, and DaVinci Resolve tend to be generous because they optimise for quality headroom, not transfer.
Re-encode with HandBrake or FFmpeg using H.265 (HEVC) at CRF 23 for a near-visually-lossless result. For ultra-small sizes at web-delivery quality, AV1 through SVT-AV1 at CRF 30 cuts another 30 to 50 percent compared to H.265. A one-liner that works: ffmpeg -i input.mov -c:v libx265 -crf 23 -preset medium -c:a aac -b:a 128k output.mp4. Expect a 5 GB ProRes file to land around 600 MB.
Skip the temptation to export at 4K when 1080p will do. Downsampling resolution before encoding is far more effective than cranking up the bitrate cap.
Images: format beats resolution
A 12 MP photo saved as uncompressed TIFF runs 36 MB. The same image at WebP quality 85 sits near 1.8 MB with no visible degradation. AVIF goes lower still, often under 1 MB, and Safari, Chrome, Firefox, and Edge all support it natively now.
For raw batches headed to a client, convert DNG or CR3 files to JPEG XL (.jxl) or progressive JPEG at quality 90. A shoot folder of 200 RAWs at 1.2 GB becomes roughly 90 MB without losing detail anyone will notice on a normal monitor.
Tools that don't require a download: Squoosh in the browser handles WebP, AVIF, and MozJPEG individually. For batches, ImageMagick's magick mogrify -format webp -quality 85 *.jpg processes a folder in seconds.
PDFs: strip the embedded bulk
Most oversized PDFs are carrying embedded image scans at print resolution. Acrobat's "Reduce File Size" command downsamples embedded images to 150 DPI and re-encodes them with JBIG2 for text scans and JPEG2000 for photos. The same job is free through Ghostscript: gs -sDEVICE=pdfwrite -dCompatibilityLevel=1.5 -dPDFSETTINGS=/ebook -sOutputFile=out.pdf in.pdf.
A 300 MB contract with 40 scanned signature pages typically drops to 35 MB this way. If you're sending PDFs for e-signature workflows through DocuSign or Dropbox Sign, this matters because their upload limits sit around 25 MB per document.
For born-digital PDFs exported from Word or Google Docs, use the "Print to PDF" virtual printer set to "Standard" quality rather than the default "High." The difference is often 10x.
Documents and spreadsheets
A bloated .docx or .xlsx is almost always bloated because of pasted-in images or embedded spreadsheet ranges. Word's Compress Pictures command (File > Options > Advanced > Image Size) targets 150 PPI for email. Excel files ballooning past 20 MB usually contain formatting across empty cells; the "Clear All" on unused rows often recovers 90 percent of the size.
For older formats, saving a .doc as .docx cuts size by 30 to 60 percent because the modern XML-based format uses zipped storage by default.
Archive smartly: 7z beats ZIP on mixed content
When you're bundling a mix of documents, code, and a few images, 7-Zip with LZMA2 at the "Ultra" level typically hits 20 to 40 percent better ratios than standard ZIP. The tradeoff is compression time, which can matter for 10 GB archives. For already-compressed content (MP4, JPG, ZIP), don't bother, the savings are under 2 percent and you just burn CPU.
Tar + zstd (tar --zstd -cf archive.tar.zst folder/) is the sweet spot for Linux and macOS users moving codebases; zstd decompresses 5x faster than gzip at similar ratios.
Avoid RAR unless your recipient has WinRAR or 7-Zip installed. ZIP and .7z are safer defaults for external recipients.
When compression hurts more than it helps
Don't re-compress files that are already at web-delivery quality. Running HandBrake on a YouTube download or an already-H.264 MP4 at CRF 23 will either not shrink it meaningfully or will introduce generation loss artefacts. Check the source bitrate with ffprobe file.mp4 first; if it's already under 5 Mbps for 1080p, leave it alone.
Similarly, encrypted archives (password-protected ZIP, 7z with AES-256) become incompressible, so compress first and encrypt second, not the other way around.
Send big without the shrink
Sometimes compression isn't worth the time, especially for one-off sends of video masters or design deliverables where the recipient needs the original quality. A service that accepts large raw files end-to-end is simpler than a round of re-encoding. HexaTransfer handles up to 10 GB per transfer with AES-256-GCM encryption and no account, which covers most "I can't compress this any further" scenarios.
Try it at hexatransfer.com — free, no account, 10 GB max.
Send large files securely with end-to-end encryption
Transfer files up to 10 GB for free with end-to-end encryption. No account required. Your files are encrypted in your browser before upload — no one else can read them.
Send a file