Where the 5MB limit shows up
5MB is the unofficial standard for “big but still sendable.” Discord is the headline case: free accounts cap uploads at 10MB, so a photo compressed to under 5MB uploads instantly with headroom to spare — no Nitro required, no failed sends. Portfolio sites and photography marketplaces often suggest 5MB per image as the balance between showcase quality and page speed. Email threads with several attachments stay manageable when each photo is under 5MB, and many CMS media libraries accept 5MB files without complaint. It is the comfortable ceiling: generous enough that a modern phone photo usually keeps 85–95% JPEG quality — effectively indistinguishable from the original — while staying light enough to share anywhere.
How the compressor hits 5MB without hurting quality
The engine works quality-first. It binary-searches JPEG or WebP quality from 90% down to 10% to find the highest quality that lands under 5MB, and only if even the lowest quality cannot fit does it gently shrink the dimensions — never below 320 pixels on the short side. In practice, a 5MB target is so generous that most phone photos settle at high quality with their full dimensions untouched. The exact output size is shown before you download, so you can confirm the file is under the limit yourself. And because everything runs in your browser, there is no queue, no upload, and no waiting on a server.
When 5MB is the wrong target
A target is only right if it matches the job. Sending an avatar, favicon, or forum thumbnail? Our 20KB compressor is the right tool — 5MB would be hundreds of times too big. Facing a strict portal cap? Use the 100KB compressor instead. Need something between? The 2MB compressor covers email-friendly sizes. Archiving precious originals? Don’t compress at all — keep the masters untouched. And if you have dozens of photos to slim down, the bulk compressor processes them all with the same settings in one pass. Pick the number the destination actually asks for, and let the engine do the rest.