Compress any image to under 500KB entirely in your browser. A popular limit for email attachments, social media uploads, and cloud services.
Last updated: August 2026
500KB
Exact Target
JPEG, WebP
Output
High Quality
Search
Private
No Uploads
Drop image here to compress to 500KB
JPEG, PNG, WebP, AVIF, HEIC. All processing stays in your browser.
Want to compare against a different limit? Change the target field above, no need to drop the file in again.
Five steps is all it takes. Everything runs in your browser so there is no waiting for an upload or server processing.
Set your target
The target is pre-set to 500KB. Adjust it to any value if your platform has a different limit.
Drop your image
Drag and drop a JPEG, PNG, WebP, AVIF, HEIC or HEIF file onto the tool. No upload happens, the file stays on your device.
Quality check, usually resolved fast
Quality 100 is tried first, and at 500KB it often already fits. Runs in a background worker either way, so the tab stays responsive.
Fine-tune without starting over
Change the target or switch between JPEG and WebP afterward and the tool recompresses automatically.
Download the result
Preview and size stats appear. Download the compressed file immediately.
The 500KB limit is common for email systems with attachment recommendations, social profile photo uploads and general web platform image requirements. At 500KB, images retain full visual quality in nearly all cases.
Email attachment compression
Many email clients recommend keeping individual image attachments under 500KB to avoid delivery issues.
Social media profile photos
LinkedIn, professional networks and some social platforms cap profile and header images at 500KB.
Cloud storage and sharing platforms
Some cloud storage services and shared drive systems impose a 500KB limit on embedded or shared images.
Website and blog image uploads
CMS platforms and blog systems may enforce a 500KB upload limit on images through their media manager.
500KB sits comfortably above the point where JPEG compression starts producing visible artifacts for typical photographs. Research into perceptual image quality generally puts the threshold for visually lossless JPEG somewhere in the upper quality range for photographic content, depending on the image. Because 500KB is such a generous budget, the tool's fast-path check, a full quality 100 encode tried before any search happens, very often already fits for a typical phone photo. In that case there's no trade-off at all, the output is genuinely the maximum quality the format can produce, and it finishes almost instantly since no search was needed.
This is also where the tool is fastest. At a tight target like 20KB or 50KB, the search has to work through several quality levels to find the highest one that fits. At 500KB, the fast-path check alone frequently resolves it, so compression at this target is typically quicker than compressing the same image down to a much smaller size.
Where 500KB does require meaningful compression is large PNG source files. A screenshot at high resolution saved as PNG might easily be several megabytes. A photograph exported as PNG from a photo editor can be even larger. Converting these to JPEG or WebP and targeting 500KB still involves genuine compression work because the source has so much pixel data. Screenshots and UI images in particular require more care at 500KB than photographs do, because JPEG can produce visible ringing around high-contrast text and sharp edges at whatever quality setting is needed to reach the target. If your source is a screenshot or a document image with sharp text, checking the output before submitting is worth the extra few seconds.
If the platform you are uploading to is a social network or CMS that will recompress your image anyway on their end, the quality of your input file matters more than hitting an exact byte count. Uploading a clean, pre-compressed file under 500KB gives the platform's encoder cleaner input to work with than uploading a platform-recompressed version of a multi-megabyte original. For social media specifically, pre-compressing before upload tends to produce better final results than letting the platform handle the full reduction from an unoptimized original. If you need to go further down than 500KB for a stricter platform limit, the compress to 200KB tool applies the same approach at a tighter target while keeping quality as high as the limit allows, and switching between the two just means changing the target field, no need to start over.
Choosing JPEG for a transparent screenshot
If the source PNG has a transparent background, JPEG will fill it with a solid color. The tool warns about this and offers a one-click switch to WebP, which keeps transparency.
Not checking sharp text after compressing a screenshot
JPEG can produce visible ringing around high-contrast text and UI edges at the quality settings a screenshot might need to hit 500KB. Check the result before submitting, or use PNG-friendly workflows for text-heavy screenshots.
Expecting visible quality loss at 500KB
For most phone photos there isn't any. 500KB is generous enough that the fast-path quality-100 check frequently succeeds outright and finishes almost instantly.
Assuming the tool will pad a file up to 500KB
It won't. Compression only ever reduces size. If your image is already under 500KB, the tool detects that and offers the original for download rather than processing it further.
Re-dropping the file just to compare a different target
That's no longer necessary. Changing the target size field after a result already appears recompresses automatically using the same cached image.
Uploading a large uncompressed original when the platform will recompress anyway
If a social platform or CMS recompresses on their end regardless, feeding it a clean, pre-compressed 500KB file usually looks better than letting the platform work from a multi-megabyte original.
500KB is enough space to store an excellent quality photograph at typical web display resolutions. The limit is common on platforms that want to prevent very large unoptimised uploads while still allowing high quality images.
Compressing a phone photo to 500KB almost always produces a result that is visually identical to the original at screen viewing sizes. 500KB is a very generous target for most photographs.
It checks quality 100 first. Because 500KB is a generous budget, a full quality 100 encode often already fits under it for a typical phone photo, in which case that's what you get with no further searching needed and the whole process finishes almost instantly. If quality 100 overshoots, the tool binary searches downward to find the highest quality that still fits under 500KB.
Essentially never for a typical photograph. Where it can still take real work is a large PNG source, a screenshot or a photo exported from an editor as PNG can be several megabytes before compression, since PNG isn't designed for photographic content. Converting it to JPEG or WebP and targeting 500KB usually resolves through quality reduction alone, dimension scaling stays a fallback reserved for much tighter targets like 10KB to 30KB.
JPEG, PNG, WebP, AVIF, HEIC and HEIF are all supported as input. The output is JPEG or WebP depending on your selection, never PNG. JPEG is the safest choice for submission portals as it is universally accepted.
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.
No. The quality check and any search that follows both run in a background Web Worker rather than on the page's main thread, so the tab stays responsive even while a large source photo or PNG screenshot compresses.
JPEG has no alpha channel, so a transparent PNG compressed with JPEG selected has its transparent areas filled with a solid color instead. If the tool detects transparency and JPEG is selected, it shows a warning with a one-click button to switch to WebP, which keeps transparency intact.
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 compressed file.
No. Decoding uses the Canvas API, or a dedicated decoder for HEIC and HEIF files, and the compression itself runs via WebAssembly in a background Web Worker. All of this 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.
No, this tool handles one image at a time. For a batch of email attachments or profile photos, run each one through individually.
No sign-up. No uploads. Drop your image above and download the compressed version in seconds.
