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.
Last updated: August 2026
1MB
Target
JPEG, WebP
Output
Live Recompress
Adjust Anytime
Private
No Uploads
Drop image here to compress to 1000KB
JPEG, PNG, WebP, AVIF, HEIC. All processing stays in your browser.
Already have a result and want a different size or format? Just change the target field or click JPEG or WebP, no need to drop the file in again.
Drop or select your image
JPEG, PNG, WebP, AVIF or HEIC. Nothing is uploaded, it stays on your device.
Checks your file size
Already under 1MB? Download the original, no unnecessary compression.
Finds the highest usable quality
Binary search runs in a background worker, so the tab doesn't freeze.
Fine-tune without restarting
Change the target or format, it recompresses automatically.
Download your compressed image
Preview and size stats appear, click download to save the file.
Common reasons people compress to 1MB
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 checks quality 100 first, and for most phone photos a full quality 100 encode already fits comfortably under 1MB, so that's what you get with no search needed at all. Only if quality 100 overshoots does it narrow down to the highest quality that fits, with no ceiling below 100. In the rare case where even a low quality setting can't reach 1MB without looking visibly bad, the tool also trims the pixel dimensions slightly rather than deliver a poor result, though at a 1MB target this almost never triggers.
That repeated search loop, trying one quality level after another, runs in a background Web Worker rather than on the page itself. For a large or high-resolution photo that means the browser tab stays responsive while compression happens, it doesn't lock up or stop scrolling. And because the tool keeps the decoded image cached after the first pass, changing the target size or switching between JPEG and WebP afterward triggers a fresh compression automatically, there's no need to drop the file in again to try a different setting.
JPEG has no alpha channel, so a transparent PNG or WebP compressed with JPEG selected has its transparent areas filled with a solid color instead. If the tool detects transparency in your source image and JPEG is selected, it shows a warning explaining this along with a one-click button to switch to WebP, which keeps transparency intact.
Uploading a HEIC file directly to a CMS
Most WordPress installs and CMS platforms reject HEIC silently. Convert to JPEG first, or let this tool handle conversion and compression together in one step.
Ignoring the transparency warning and staying on JPEG
If a transparent PNG or WebP is compressed with JPEG selected, the tool warns that the transparent areas will be filled with a solid color. Use the one-click switch to WebP in that warning if the transparency matters.
Re-dropping the file just to try a different target or format
That's no longer necessary. Changing the target size field or clicking JPEG or WebP after a result already appears recompresses automatically using the same cached image.
Assuming 1MB is overkill and always reachable at full quality
For most phone photos it is, but a very high-resolution or highly detailed image can occasionally need a small dimension reduction to stay under 1MB without dropping quality too far. Check the result panel if this happens.
Compressing an already-optimized image again
If an image is already under 1MB, this tool skips compression and offers the original file directly rather than needlessly re-encoding it.
Not checking whether the platform's real limit is different
1MB is a common default, but some CMS installs configure a lower or higher limit. Confirm the actual number before assuming 1MB is safe.
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, HEIC and HEIF are all supported as input. The output is JPEG or WebP only, this tool never outputs PNG. JPEG is the safest choice for submission portals as it is universally accepted, WebP is worth choosing if you specifically need to preserve transparency.
Yes. The tool keeps the decoded image cached, so adjusting the target size field or clicking JPEG or WebP after a result already appears triggers an automatic recompress rather than asking you to drop the file in again. Typing a new target waits briefly until you stop typing before it recompresses, switching format applies right away.
No. The binary search that repeatedly tries different quality levels runs in a background Web Worker rather than on the page's main thread, so the tab stays responsive and scrollable while a large or high-resolution photo compresses.
JPEG has no alpha channel, so if a transparent PNG or WebP is compressed with JPEG selected, the tool shows a warning explaining that the transparent areas will be filled with a solid color, along with a one-click button to switch to WebP, which does support transparency.
Almost never at this target. 1MB is a generous budget for most photos, so quality adjustment alone is nearly always enough to hit it. Dimensions are only reduced as a last resort if quality would otherwise have to drop low enough to look genuinely bad, which is uncommon at 1MB.
The target size field accepts anything from 1KB up to 10,000KB, roughly 10MB. For a 1MB target this is mostly relevant if you're comparing this tool against the exactly-1MB or under-500KB pages elsewhere on the site.
No. The image is decoded to raw pixels and re-encoded during compression, so EXIF metadata, including GPS location and camera details, does not carry over to the output file.
No. All compression happens entirely in your browser, including the background worker that runs the encoding loop. Your image never leaves your device. You can verify this by disconnecting from the internet after the page loads, the tool still works.
This page compresses one image at a time. For batch compression across multiple files, use the main image editor on the homepage.
No sign-up. No uploads. Drop your image above and download the compressed version in seconds.