RedpandaCompress Blog

WhatsApp caps every video you send in a chat at 16MB — and if your clip is even slightly over that, the app quietly re-encodes it for you. The result is usually blockier, blurrier, and worse than if you’d compressed it yourself first. Here’s exactly what WhatsApp’s limits are in 2026, why its automatic compression looks the way it does, and how to get a video under 16MB without wrecking the quality.

WhatsApp’s Actual Video Size Limits (2026)

WhatsApp enforces different limits depending on how you send a video, and it’s easy to hit the wrong one by accident:

• Chat media (photo/video attach button): 16MB per video, on iOS, Android, and WhatsApp Web alike. Roughly 90 seconds to 3 minutes of footage depending on resolution and how much motion is in the frame.
• Status: 16MB per clip, with a hard 30-second duration cap regardless of file size.
• Sent as a document (attach → document instead of photo/video): up to 2GB. This skips WhatsApp’s automatic compression entirely, but the recipient loses the inline preview and autoplay — they have to tap to download and open it.

Most people hit the 16MB wall without realizing it: a 30-second clip shot in 4K on a modern phone routinely lands at 150–300MB straight out of the camera roll — ten to twenty times over the limit.

Why WhatsApp’s Own Compression Looks Bad

When your video is over 16MB, WhatsApp doesn’t reject it — it silently re-encodes the file to squeeze it under the cap before sending. The problem is that this re-encode uses one aggressive, one-size-fits-all bitrate target regardless of what’s actually in your footage. A slow, static shot and a fast action clip get squashed to roughly the same data budget, so anything with motion — a kid running, a pan across a room, low light — ends up visibly blocky, with smeared detail and banding in shadows.

Compressing the video yourself before sending gives you control WhatsApp doesn’t: you can choose the resolution and bitrate combination that keeps the parts of the frame that matter — faces, text, motion — looking sharp, while trimming the data elsewhere. The file WhatsApp receives is already under 16MB, so it passes through untouched instead of getting recompressed a second time.

How Big Is a Video, Really?

Rough file sizes for a 30-second clip at different settings — this is what determines whether you’ll land under WhatsApp’s 16MB cap:

Resolution / Bitrate	Approx. Size (30 sec)	Fits 16MB Chat Limit?
4K, camera default (~50 Mbps)	180–220 MB	No — needs heavy compression
1080p, camera default (~20 Mbps)	75–90 MB	No
1080p, compressed (~3.5 Mbps)	13–15 MB	Yes, tight
720p, compressed (~2.5 Mbps)	9–11 MB	Yes, comfortable

720p at a moderate bitrate is the sweet spot for WhatsApp: on a phone screen, the difference between 720p and 1080p is barely visible, but the file is roughly half the size — giving you headroom to stay under 16MB even for slightly longer clips.

How to Compress a Video for WhatsApp Yourself

The fastest way is a browser-based compressor rather than a phone app: drop the file in, let it target a size under 16MB, and download the result — no install, no account.

1. Open RedPandaCompress, which has a WhatsApp preset that targets a safe size under the 16MB limit automatically.
2. Drop in your video. Compression runs entirely inside your browser tab — the file is never uploaded to a server, so anything personal in the clip stays on your device the whole time.
3. Compare the generated versions and pick the smallest one that still looks right at normal viewing size (you rarely need the largest option for a phone screen).
4. Download the result as H.264 MP4 — the format every phone, and WhatsApp itself, plays without any conversion step.
5. Send it as a normal video attachment. Since it’s already under 16MB, WhatsApp passes it through without re-encoding it a second time.

Worked Example: A 45-Second Birthday Video

Say you shoot 45 seconds of a birthday cake and candles at your phone’s default 4K setting. The clip lands at 240MB — nowhere close to WhatsApp’s 16MB cap. Attach it directly and WhatsApp force-compresses it down, and the result is noticeably soft, with the flame highlights blown out and blocky edges around faces in the candlelight.

Run the same clip through a compressor targeting 720p at roughly 2.3 Mbps instead, and it comes out around 13MB — under the limit with room to spare. Because you chose the settings deliberately rather than letting WhatsApp’s blanket algorithm decide, the faces and candle flames stay recognizably sharp, and the file passes straight through to your group chat without a second automatic re-encode.

When to Use “Send as Document” Instead

If you genuinely need the original quality — a wedding video, drone footage, anything where compression artifacts would actually matter — send it as a document instead of a media attachment. You get up to 2GB with no forced re-encoding, at the cost of the inline preview: the recipient sees a file icon and has to tap to download rather than watching it play inline in the chat. For anything you want someone to actually watch without extra taps, compressing to fit the 16MB media limit is almost always the better experience.

FAQ

Does WhatsApp always compress my videos automatically?

Only when a video exceeds the 16MB media limit. If your file is already under that size, WhatsApp sends it as-is without touching the quality.

Why does my video look blurry after I send it on WhatsApp?

WhatsApp’s automatic compression uses one fixed, fairly aggressive bitrate target for anything over 16MB, regardless of the footage. Motion, low light, and fine detail all suffer more under that one-size-fits-all approach than they would if you chose the resolution and bitrate yourself before sending.

What’s the maximum length for a WhatsApp Status video?

30 seconds per clip, and it also needs to stay under 16MB. Longer recordings get automatically split into multiple Status segments.

Is there a way to send a large video on WhatsApp without any size limit?

Sending as a document raises the cap to 2GB with no forced compression, but the recipient has to download and open it manually — there’s no inline video preview. For anything meant to autoplay in the chat, staying under 16MB is the better option.

Whether it’s a WhatsApp clip, a Discord upload, or an email attachment, the same free tool at RedPandaCompress handles the compression entirely in your browser — private by default, with H.264 MP4 output that plays everywhere.

Scan a stack of paper into your phone or a flatbed scanner, and you’ll often end up with a PDF that’s 40, 80, even 150 MB — for what might be a dozen pages of black text on white paper. That’s because a “scanned PDF” usually isn’t text at all. It’s a sequence of full-resolution photographs, one per page, stitched together in a PDF wrapper. This guide explains why scanned PDFs balloon in size, how to shrink them without turning your text into mush, and what settings actually matter.

Why Scanned PDFs Get So Large

A typed Word document saved as PDF stores text as text — a few kilobytes for an entire page, because letters are drawn from font outlines, not pixels. A scanned page is the opposite: every pixel of the page, including all the white space, gets recorded as image data. A single US Letter or A4 page scanned at 300 DPI in full color can weigh 5–15 MB uncompressed, and scanning apps rarely compress aggressively by default, since they’re optimized for legibility over file size.

Multiply that by a 20-page contract, and you’ve got a file too big to email, too big for some upload forms, and slow to open on a phone. The fix isn’t to scan at a lower quality — it’s to compress the PDF intelligently after the fact, so the text stays sharp while the redundant image data shrinks.

What Actually Controls Scanned PDF Size

Three settings determine how big a scanned page ends up being, and only one of them meaningfully affects whether your text stays readable.

• Resolution (DPI): Higher DPI means sharper text but a bigger file. 300 DPI is the print-quality standard; 150 DPI is plenty for on-screen reading and archiving.
• Color mode: Full color triples the data of grayscale for the same DPI. Most scanned documents — receipts, contracts, forms — have no meaningful color information to preserve.
• Image compression level: This is where most of the size reduction happens, and it’s the one setting that doesn’t require re-scanning anything. A good compressor re-encodes the existing page images at a lower bitrate without touching resolution or color mode, so text edges stay crisp longer than you’d expect.

Scan Settings vs. File Size: A 10-Page Document

Rough numbers for a typical 10-page text document (letter or A4), scanned from paper:

Settings	Approx. Size (10 pages)	Good For
300 DPI, full color, uncompressed	80–150 MB	Archival masters only
300 DPI, grayscale, uncompressed	30–50 MB	Rarely worth it — same DPI, less data
300 DPI, color, compressed	3–8 MB	Printing, sharp scans with color
150 DPI, grayscale, compressed	0.5–1.5 MB	Email, forms, everyday reading

Notice that compression — not lower DPI — does the heavy lifting. A 300 DPI color scan compressed properly can end up smaller than an uncompressed grayscale version at the same resolution, with no visible loss in legibility.

Worked Example: A Signed Contract

Say you scan a 12-page signed contract on your phone at the default “high quality” color setting. The resulting PDF is 64 MB — too big for most email attachment limits (typically 20–25 MB) and awkward to send over messaging apps that cap file size. Running it through a PDF compressor set to a “text document” or “standard” profile typically brings that down to 3–5 MB: every page still crisp enough to read every clause and signature, but now small enough to email, upload to a portal, or send over chat without hitting a size wall.

How to Compress a Scanned PDF

The simplest approach is a browser-based compressor like RedPandaCompress’s PDF tool: drop in the scanned file, and it generates a few compressed versions at different quality levels so you can pick the smallest one that still looks right. Two things matter more for scanned documents than for typical file compression:

First, privacy. Scanned PDFs are disproportionately likely to contain something sensitive — a signed lease, a passport photo page, a medical form, a tax document. RedPandaCompress compresses entirely inside your browser tab; the file is never uploaded to a server, so a document you’d never want sitting on someone else’s storage never leaves your device in the first place. That’s a meaningfully different privacy posture from most “upload and download a link” PDF tools.

Second, output flexibility. Because scanned documents range from “needs to look perfect” (contracts, IDs) to “just needs to be readable” (meeting notes, receipts), getting several compressed versions to compare — rather than one fixed result — makes it much easier to find the smallest file that still does the job. The same underlying tool also handles everyday video compression and format conversion to universally compatible H.264 MP4, if paperwork isn’t the only large file you’re dealing with this week.

What to Avoid

• Don’t over-compress dense text or fine print. Aggressive image compression can introduce blotchiness around small serif fonts. If a page has fine print (contracts, legal documents), compare before and after at 100% zoom.
• Don’t rescan at lower DPI to save space. You lose quality permanently and still may not save as much as proper compression would.
• Watch out for tools that convert scans to searchable text (OCR) as a side effect. That’s a useful feature in the right context, but it changes the document from an image-based PDF to a text-layer PDF — not the same thing as compression, and not always desirable if you need the scan to look exactly like the original.

FAQ

Will compressing a scanned PDF make the text blurry?



At reasonable compression levels, no — the loss is concentrated in fine color gradients and background noise, which your eye doesn’t register as text quality. Extreme compression settings can eventually blur small fonts, so it’s worth comparing a couple of output levels rather than always grabbing the smallest file.

What’s the best DPI for scanning documents I plan to compress anyway?

300 DPI if you might ever need to print it or zoom into fine print; 150 DPI is fine for anything that’s purely digital reading. Either way, compress after scanning rather than lowering DPI upfront — you keep the option to go back to a sharper version later if you kept the original scan.

Is it safe to compress PDFs that contain personal or financial information?

It depends entirely on the tool. Anything that uploads your file to a server means that document now exists somewhere outside your control, even briefly. A browser-based compressor that processes the file locally — never sending it anywhere — avoids that exposure entirely, which matters a lot more for a passport scan or bank statement than for a vacation video.

Why is my scanned PDF bigger than the original paper document, size-wise?

Paper doesn’t have a file size — the comparison that matters is against a typed, text-based PDF of the same content, which would be a fraction of the size. A scan is fundamentally a photograph of a page, not a re-creation of the text, so it inherits all the overhead of image data even when the page itself is simple.

Whether it’s a single signed contract or a folder of scanned receipts, compressing your scanned PDFs is usually a two-minute fix for a problem that otherwise blocks emails, uploads, and shares. Try it on your next scan before you resign yourself to a 60 MB attachment.