Why does this portal require images under 1MB?
1MB is a web-optimised image size that balances quality and load performance. The limit is common because images above 1MB significantly slow down web pages, particularly on mobile connections.
Compress any image to under 1MB entirely in your browser. A 1MB limit is common for CMS uploads, website builders, and general file size restrictions.
1MB
Exact Target
Any Format
Input Support
Precise
Compression
Private
No Uploads
Drop image here to compress to 1000KB
JPEG, PNG, WebP, AVIF, HEIC. All processing stays in your browser.
The 1MB limit is a practical threshold for web-optimised images. Modern phone cameras produce 3 to 12MB photos by default, which exceed this limit. Compressing to 1MB prepares images for websites, CMS platforms and sharing systems.
CMS and WordPress media uploads
WordPress and other CMS platforms often have configurable upload limits, with 1MB being a common default cap.
Website image optimisation
Serving images under 1MB is a web performance best practice for faster page load times.
E-commerce product photos
Product image upload systems in e-commerce platforms frequently enforce a 1MB limit per image.
Forum and community platform uploads
Online communities and forum software often restrict image attachments to 1MB to manage storage costs.
Your phone's camera has no idea what you're going to do with the photo it just took. So it saves everything. A modern iPhone or Android shoots JPEG files anywhere from 3MB to 12MB depending on the scene, the lighting, and how much detail it decides to preserve. That's great for printing. Not so great when a website, CMS, or platform is waiting on the other end with a 1MB cap.
The 1MB threshold isn't arbitrary. It became a web standard because HTTP Archive data consistently shows that images are the single largest contributor to page weight, making up roughly 45% of the average webpage's total size. Platforms that set a 1MB limit are essentially saying: give us an image that's already optimised for the web, and we won't have to mangle it ourselves. It's a reasonable ask when you understand where it's coming from.
Here's what surprises most people. Going from a 6MB phone photo down to 1MB sounds like you're throwing away 83% of your image. But visually, you're barely touching it. The reason is that a huge chunk of a raw phone photo's file size comes from metadata, colour profile data, and redundant pixel information that your eyes never register on screen. A well-compressed 1MB JPEG at 1920 pixels wide looks essentially identical to its 6MB original when you're viewing it on a monitor or website.
The place where you'd actually notice quality loss is in extreme crops or if you're printing the image at poster size. For a website hero image, a product photo, or a CMS upload, 1MB is genuinely enough. The compression isn't hurting anything that matters for your use case.
If you're on an iPhone and your photos aren't uploading at all, the file size might not even be the main issue. iPhones save photos in HEIC format by default, which most websites, WordPress installs, and CMS platforms simply don't accept. The portal rejects it silently, and you're left wondering what went wrong.
The fix is to convert to JPEG first, then compress. This tool handles both steps together. Drop in your HEIC file and it converts and compresses in one pass, outputting a standard JPEG under 1MB that any platform will accept. If you want to do it separately, the HEIC to JPG converter handles the format conversion on its own.
Most online compressors guess. They apply a fixed quality setting like 75% or 80% and hope the output lands under your target. If your image is already small, that's fine. If it's a dense 10MB RAW export, the fixed quality approach often still misses the mark.
This tool uses a binary search algorithm instead. It sets an initial quality, checks the output size, then adjusts up or down based on whether it overshot or undershot. It keeps narrowing until it lands as close to 1MB as possible without going over. The whole process runs in your browser in a few seconds, and your image never touches a server at any point.
1MB is a web-optimised image size that balances quality and load performance. The limit is common because images above 1MB significantly slow down web pages, particularly on mobile connections.
Compressing a phone photo to 1MB almost always produces a visually identical result. The quality reduction needed to reach 1MB from a typical 3 to 8MB phone photo is minimal and imperceptible at normal screen sizes.
JPEG, PNG, WebP, AVIF and HEIC are all supported as input. The output is JPEG or WebP depending on your selection. JPEG is the safest choice for submission portals as it is universally accepted.
No. All compression happens entirely in your browser. Your image never leaves your device. You can verify this by disconnecting from the internet after the page loads, the tool still works.