A 1 MB cap is common on forums, help desk systems, older content management systems, school and government portals, and some email setups, and it is the limit most likely to reject a straight-from-the-phone photo of 3 to 8 MB. Unlike stricter targets, 1 MB rarely requires any loss you can see. This page opens with the target set to 1 MB. The tool first tries a high JPG quality and lowers it only as much as needed; for most phone photos that alone is enough, so the full resolution is kept and the file simply gets more efficient encoding. Very large or very detailed images, such as 48 or 108 megapixel shots, may also be scaled down, and the new dimensions are shown next to the result. Screenshots and graphics saved as PNG are often the files that exceed 1 MB unexpectedly; converting them to JPG here usually fixes that, although text edges look slightly softer in JPG than in PNG. The target is counted as 1,000,000 bytes, so the file is under the limit whether the site means 1,000,000 or 1,048,576 bytes. Several photos can be compressed in one go. For a stricter limit see Compress Image to 500KB, and to also change the format use Image Format Converter.
Image compression is one of the highest-impact performance optimizations for most websites. Images typically account for 50 to 80 percent of a page's total download size, and unoptimized images are the most common cause of poor Core Web Vitals scores, particularly Largest Contentful Paint (LCP). A JPEG compressed to 75 percent quality is visually indistinguishable from the original for photographic content in most contexts, but can be 60 to 70 percent smaller. The human eye is much more sensitive to sharpness and color accuracy in certain areas (faces, text in images, sharp edges) than in others (smooth backgrounds, sky, blurred backgrounds). Lossy compression algorithms exploit this by applying heavier compression in less sensitive areas. For PNG files, lossless compression reorders pixel data and uses more efficient encoding tables. PNG compression level (1-9) trades CPU time for file size: higher levels take longer to encode but produce smaller files. For web use, both JPEG and PNG should be served at their maximum practical compression level (JPEG 75-85, PNG level 9) since the decompression time is negligible but the smaller network transfer size benefits every user. The recommended modern workflow for web image delivery is: optimize your original image with this tool, then serve it in WebP format for Chrome and Safari 14+ users with a JPEG fallback for older browsers using the HTML picture element with source type="image/webp".
Read our guide: In-depth guide for Compress Image to 1MB