Compress an image to 500 KB in your browser
500 KB suits wide article headers, portfolio images, and high-resolution previews. The image is re-encoded in this tab, not on a server.
Open target-size mode, enter 500 KB, and keep the native resolution when the layout displays a large image. The encoder finds a quality level that fits while preserving most of the detail.
Half a megabyte is generous for a web image. At this ceiling you can keep a 1600 pixel photo looking clean on a large display, provided the content does not rely on very fine texture or high-contrast edges.
The file is still heavy for mobile users. Pair a 500 KB source with smaller responsive variants so a phone downloads only what it can display, and let the browser choose the appropriate file.
How to hit the target
- 1
Switch to target size
Open the image compressor and choose target size.
- 2
Enter 500 KB
Type 500 as the ceiling. Keep original dimensions for large displays.
- 3
Use WebP for detail
WebP preserves more detail at 500 KB than JPEG in most photographs; AVIF is an option when encoding support exists.
- 4
Inspect at display size
Compare the preview at the size the page will use, then download the result.
What to check at 500 KB
Do not ship it to phones
A large file needs a responsive source set. Otherwise mobile visitors pay for pixels their screen cannot show.
Keep gradients smooth
Skies and backgrounds reveal banding first. Lower the target slightly or keep a higher quality if the gradient becomes visible.
Check the format pair
If the destination expects JPG, using a WebP source may break the upload. Convert to the required format after compressing.
Common questions
When is 500 KB acceptable?
When the image is a large hero or portfolio piece and the page still meets its performance budget. Pair it with responsive sizes so phones do not download the full file.
Why not just use the original?
The original may be several megabytes and slow down first paint. A 500 KB target keeps most of the visual quality while cutting transfer size substantially.
Should I choose AVIF at 500 KB?
AVIF can preserve more detail at the same size, but encoding is slower and support varies. WebP is a safer default; offer AVIF as a second source when your stack supports it.