How to compress an image to 500KB or a target file size

Start with the actual upload limit

Check whether the destination limits file size, image dimensions, or both. The steps for compressing an image to 500KB, 200KB, or 100KB are the same, but smaller targets usually require a greater trade-off among detail, pixel dimensions, and format.

Burger Compress processes media on your computer. Test one representative original first. Check text, edges, transparency, and color before using the same settings for batch image compression.

File size is not pixel size

KB and MB measure storage size. Pixel width and height describe image dimensions. A photograph, screenshot, and flat-color graphic can all be 1920 × 1080 yet have very different file sizes.

If an upload form sets both a file-size limit and minimum dimensions, you must satisfy both. Do not shrink an image until its content becomes unreadable just to reduce the file.

Set a target: a 500 KB example

Import an image into Burger Compress and select compression. Choose an output format with target-size controls. Availability for JPG, WebP, AVIF, and other formats follows your computer's capability checks and the app's explanations.

1. Select the image and choose Target size under Strategy in its image settings.
2. Enter 500 and confirm that the unit is KB. Leave a little headroom if the receiving platform has a strict limit.
3. Check the output dimensions and destination, then start processing.
4. Inspect the actual file size and visual detail, and test the result on the receiving platform.

What changes at 100KB, 200KB, or 500KB?

These are not three different compression methods. Enter the required number in Target size (KB). If a platform says the image must not exceed 500KB, set a slightly lower target to leave room for file variation and the platform's calculation.

Pushing the same image from 500KB toward 100KB will usually remove more detail. If that result is not acceptable, consider smaller pixel dimensions or a supported format better suited to the content. Do not repeatedly recompress the previous output.

Choose for the content and recipient

Do not choose a format just because it sounds newer. Confirm support at the destination, then compare outputs made from the same original.

• Photographs: JPG is a practical starting point. Compare WebP or AVIF when the recipient supports them.
• Transparent logos or artwork: do not simply switch to JPG if you need transparency. Check the output format and transparency settings.
• Screenshots and line art: inspect text edges closely. A lossless format may be appropriate, but not necessarily smaller.
• Animation: confirm that Keep animation is available. Exporting the first frame or choosing a frame produces a still image.

What if the target is too small?

Decide whether the output needs its original pixel dimensions. For screen viewing, smaller dimensions may be reasonable if the content remains clear. Printing, editing, and strict dimension requirements may need more resolution.

Without a hard size limit, use a quality preset or quality value and compare gradually. Higher quality generally retains more detail, but 100 is not the same as lossless. Quality numbers also are not directly comparable across formats.

Target size, KB/MB, and downward tolerance

Burger Compress uses 1024 bytes per KB and 1024 KB per MB. If a destination defines 500KB as 500,000 bytes, the app's 500 KB means 512,000 bytes. In that case, start with 480 KB (491,520 bytes), then check the actual output against the destination's limit.

Downward tolerance describes how close an output should preferably be to the target. For 500 KB and 10%, the preferred range is 450–500 KB; a smaller valid output can also be used. It does not permit exceeding the upper limit or add padding merely to fill the budget.

Why did a JPG get larger, or a target-size task fail?

A small original, a higher output quality, a lossless output format, or changed content can make a quality-mode result larger. Check whether Target size is selected; changing an extension alone does not guarantee savings.

Target-size mode verifies its upper limit. If it cannot meet the target, follow the failure message rather than treating an oversized file as successful. Work from the original and adjust the target or permitted dimensions and format. Target-size control adjusts quality; resizing is a separate setting.

Check the target-size image

Create each new result from the original, keep that original for later adjustments, and inspect one sample before batch image compression.

• Does its actual byte size meet the destination's upper limit?
• Are dimensions, orientation, and text correct?
• Were transparency and animation handled as intended?
• Does the receiving application or website accept the format?