What I Learned From Compressing a 10 MB Photo

A few months ago, I was putting together a new landing page. I had just taken a stunning landscape shot on my phone while hiking—a perfect, golden-hour photo of a mountain range. I AirDropped it to my laptop, dropped it into the website builder, and hit publish.

Then I tried to load the page on my phone.

I watched the progress bar inch across the screen. I watched the mountain render line by agonizing line, like a dial-up modem struggling to download a picture in 1998. Frustrated, I checked the file properties.

The photo was 10.4 MB.

I had dumped ten megabytes of data onto a simple landing page. To put that into perspective, an entire paperback novel is about 1 MB of text. I was forcing every visitor to download the equivalent of ten novels just to look at a mountain for two seconds before scrolling past it.

I knew I needed to compress it. But honestly? I was hesitant. I loved how crisp the photo looked. I didn’t want to ruin the subtle gradients in the sunset or introduce those ugly, blocky artifacts you see on badly compressed memes.

But I forced myself to run the photo through a compressor anyway. The process completely changed how I think about digital images. Here is exactly what I learned when I shrank that 10 MB behemoth down to a web-friendly size.

Lesson 1: You Are Hoarding Useless Pixels

My first realization had nothing to do with compression algorithms. It was entirely about dimensions.

My phone had taken a photo that was roughly 4000 by 3000 pixels. That is 12 million pixels. It’s a massive amount of visual data, completely necessary if I wanted to print the photo on a large canvas and hang it in my living room.

But this photo was going on a website. The maximum width of the text column on my landing page was 800 pixels.

Even if a user was viewing the site on a high-resolution Retina display, the absolute maximum width the image would ever be displayed at was 1600 pixels.

I was sending 4000 pixels of data to a screen that could only physically display 1600 of them. The browser was downloading millions of pixels just to immediately throw them in the trash before rendering the page. It was incredibly wasteful.

Before I even touched a compression slider, I resized the physical dimensions of the photo down to 1600 pixels wide. The file size instantly plummeted from 10.4 MB down to 2.1 MB.

I hadn’t lost a single drop of visual quality on the screen, and I had already deleted 80% of the file size.

Lesson 2: The “Quality” Slider is Psychological

Even at 2.1 MB, the image was still far too heavy for a fast website. Now I had to actually use lossy compression.

If you have ever used photo editing software, you know the export screen. There is usually a slider labeled “Quality” that defaults to 100%. Moving that slider to the left feels inherently wrong. Why would anyone intentionally choose to make their work lower quality?

I dragged it down to 80%. I expected the image to turn into a blurry, pixelated mess. I exported the file and opened it next to the original 10 MB version.

I literally could not tell the difference.

I zoomed in 200%. I stared at the sharp edges of the mountain peaks. I looked for color banding in the sky. Nothing. To my human eyes, the two images were completely identical. But the file size told a different story. The 80% quality version was now sitting at a mere 450 KB.

Here is what was actually happening: my camera captured millions of incredibly subtle color variations that my monitor couldn’t perfectly display and my eyes couldn’t actually perceive. The compression algorithm simply went through the image, found clusters of slightly different pixels, and averaged them out. It threw away data I was never going to see in the first place.

Lesson 3: The Format Changes Everything

At 450 KB, I had already won. The image was loading instantly. But I decided to push it a little further to see what would happen if I abandoned JPEG entirely.

For decades, JPEG has been the undisputed king of photographic compression. It does an excellent job. But modern web browsers support a newer format developed by Google called WebP. WebP was designed specifically to beat JPEG at its own game, offering smaller file sizes at the exact same visual quality.

I took the resized image and ran it through a WebP converter. I set the quality to 80% again.

The resulting file was 180 KB.

Let that sink in. I started with a 10.4 MB file. By resizing the dimensions to match my layout, applying reasonable lossy compression, and using a modern web format, I had reduced the file size by 98%.

When I put the 180 KB WebP next to the 10.4 MB original on my phone screen, they looked identical.

The Takeaway

We have been conditioned by marketing departments to believe that bigger files mean better photos. We buy phones advertising 48-megapixel sensors and 8K video recording, and we assume that all of that massive data needs to be preserved at all costs.

But digital screens have limits, and human eyes have limits.

If you are a professional photographer archiving your portfolio, keep your massive RAW files. But if you are building a website, sending an email, or uploading a profile picture, you have to stop hoarding pixels.

A heavy, slow-loading website ruins the user experience far more than a slightly compressed sunset ever could.

The next time you are staring at a massive file and worrying about ruining it, don’t overthink it. Check the physical dimensions first. If you need to hit a specific file size for a rigid upload portal, use a tool like our MB to KB image converter to force it down to the exact size you need. And if you just want to make your website faster, run your hero images through our free image compressor and watch the megabytes disappear.

Trust me. Your eyes won’t miss the deleted data, but your users will definitely notice the speed.