Why Your Files Are Bigger Than They Need to Be

Email has a 25-megabyte limit. A single phone photo is 5-12MB. A one-minute 4K video is 400MB. These numbers don't fit together. Compression is matching the file to its context.

Email has a 25-megabyte attachment limit. It has had a 25-megabyte attachment limit for over a decade. Gmail, Outlook, Yahoo. All of them. Twenty-five megabytes.

A single photo from a modern phone camera is 5 to 12 megabytes. A short screen recording is 30 to 80 megabytes. A one-minute video from an iPhone at 4K is roughly 400 megabytes. A ten-page PDF with embedded images can easily reach 15 megabytes.

These numbers don’t fit together. The files we create have grown dramatically. The channels we use to send them haven’t. The result is a daily friction that most people solve by reaching for a cloud link (Google Drive, Dropbox, WeTransfer) which works, but quietly shifts the paradigm from “I’m sending you a file” to “I’m giving you permission to access a file I’ve stored on someone else’s server.”

For plenty of situations, that’s fine. For anything confidential, time-sensitive, or going to a recipient who doesn’t have a Google account (they exist), it’s not.

The alternative is compression. Making the file smaller so it fits through the channels that already exist.

Compression gets a bad reputation because people associate it with quality loss. And for some formats and some settings, that’s accurate. But the relationship between file size and perceptible quality is non-linear. A 50% reduction in file size does not mean a 50% reduction in quality. For most files, significant size reductions are possible with no visible or audible difference.

A photo at 8 megabytes and the same photo at 800 kilobytes can look identical on a screen. The difference is data that was there for the camera sensor’s benefit, not yours. Colour precision beyond what your display can render. Resolution beyond what the viewing context requires.

A PDF at 14 megabytes and the same PDF at 2 megabytes often contain the same readable content. The difference is embedded fonts at full weight instead of subsetted, images at print resolution instead of screen resolution, metadata layers that add nothing to the reading experience.

A video at 400 megabytes and the same video at 40 megabytes can be indistinguishable in a browser window. The difference is bitrate headroom that only matters on a cinema screen.

The point isn’t that quality doesn’t matter. It’s that most files are larger than their destination requires. A photo going into a Slack message doesn’t need print resolution. A PDF going as an email attachment doesn’t need embedded full fonts. A video going to Instagram is getting re-compressed by Instagram anyway.

Compression is matching the file to its context. And it’s something that should happen in seconds, on your device, without uploading the file somewhere first.

Because here’s the other thing about cloud transfer links: they expire. They require the recipient to click, load a page, maybe sign in, maybe see a cookie banner, maybe wait for a download. An attached file is just there. In the email. Ready. No dependencies, no expiration, no third-party infrastructure required.

Sometimes the simplest solution is the smallest file.