Two hundred kilobytes is a comfortable ceiling for many web photos, which is why it appears in marketplace rules, email guidelines and CMS upload forms. To compress a JPG to 200KB without visible loss, start with sensible dimensions and keep the highest quality that stays under the cap. The catch is that “without visible quality loss” depends on dimensions and content: a 1600px product photo at 200KB can look clean, while the same 200KB spent on a 4000px file forces obvious mush.
Part of the image compression guide. Resize in the image compressor and resizer, convert formats in the image format converter, and use the exact-pixel resize method when a slot has fixed dimensions.
What 200KB buys at different sizes
Bytes per pixel is the useful mental model. A 200KB file spread across 1080×1080 pixels has more room for detail than the same 200KB spread across 3000×3000 pixels. That is why a photo can look excellent at 1200px wide and mediocre at 3000px wide even though both files are under the limit. If the image will display at 1200px, there is no reason to keep 3000px of detail and then crush the quality to pay for it.
For a typical photograph, 80–85% JPEG quality is a sensible starting range. At 1200–1600px wide, that range often lands under 200KB. At 1920px or larger, detailed scenes may need 75% or a modest downscale. Highly textured subjects such as foliage, crowds and fabric cost more bytes than a plain wall or a studio background.
| Placement | Export pixels | Starting quality | Notes |
|---|---|---|---|
| Blog inline | 1200 wide | 80–85% | Usually well under 200KB |
| Blog hero | 1600×900 | 80% | 200KB is a workable ceiling |
| Marketplace square | 1500×1500 | 85% | Product detail needs the higher setting |
| Email photo | 1000 wide | 80% | Email clients may recompress again |
| Full-width banner | 1920 wide | 75–80% | Tight for detailed scenes; resize if needed |
Treat the table as a starting point. The correct quality is the highest one that stays under the limit while surviving a 100% zoom check.
Resize before you compress
If a 4032px photo will appear at 1600px, discard the extra pixels first. Compressing the full-size image and then resizing it spends quality on detail that disappears. The compressor's maximum-width field handles this for aspect-correct images: set it to the display width and the height follows. When both dimensions are fixed, use the resize view, then convert the PNG output to JPEG if the destination requires JPEG.
Do not upscale a smaller image to reach a target. Enlarging adds no detail and makes the file larger for no visual gain. Crop instead when the composition does not fit the slot. A 4:3 photo forced into a 16:9 frame by stretching will look wrong no matter how carefully you compress it; the resize guide covers crop-before-resize in more detail.
Quality passes without visible loss
Start at 85% and compare the result with the original at 100% zoom. If the file is under 200KB, stop. There is no prize for landing exactly on the ceiling; a 150KB file at 85% is usually a better deliverable than a 199KB file at 70%. If the file is over, drop five points and run another pass. Each pass should be judged on the exported file, not on the preview thumbnail.
If quality reaches the low 70s and the file is still over 200KB, reduce dimensions before cutting further. Going from 1920px to 1600px often saves more bytes with less visible damage than dropping from 80% to 60%. Keep the aspect ratio locked and resize once; repeated resizes soften edges cumulatively. For images with text, try 90% first and accept a larger file if the destination allows it, because text shows JPEG artifacts sooner than skin or scenery does.
A byte target is a ceiling, not a quality setting. Stop as soon as the file is comfortably under it and the image still looks right at its display size.
Two worked examples with byte outcomes
Example 1: a landscape photo for a 1600px-wide slot. The source was a 4032×3024 JPEG at 5.2MB. The slot was 1600px wide, so the compressor was set to a maximum width of 1600 and produced a 1600×1200 file. At 85% the file was about 255KB. At 80% it was about 190KB, with no obvious change in the foliage or building edges at 100% zoom. The 80% export was used. Dropping to 75% produced roughly 150KB, but the extra savings bought nothing visible.
Example 2: a product photo for a marketplace listing. The source was a 3000×3000 JPEG at 4.4MB. The listing wanted a square image, so no crop was needed; the file was resized to 1500×1500. At 85% it was about 225KB. At 80% it was about 175KB, and the product label stayed legible. A plain background helped; a textured set would have produced larger files at the same settings. The 80% version cleared the limit without touching the dimensions again.
These numbers are illustrative, not guarantees. A noisy phone photo, a detailed pattern or a different browser encoder can move the result by tens of kilobytes in either direction.
What visible loss actually looks like
JPEG divides the image into small blocks and compresses each one. At aggressive settings, smooth skies develop blocky patches, high-contrast edges pick up a faint halo, and fine texture turns into mush. Saturated reds and blues can shift first because JPEG spends fewer bits on colour detail than on brightness. Text and logos show ringing around letters, which is why screenshots and graphics often need a different format rather than a lower slider.
Judge the export at 100% on the screen where it will be viewed. Fit-to-window previews hide artifacts, and phone screens can make them look worse than a desktop monitor or the reverse. Compare the compressed file with the original side by side, then look at the areas a viewer will notice: faces, product labels, headline text and the centre of the frame.
Format choice and honest limits
For the web, WebP often produces a smaller file than JPEG at a similar visual quality, and it can keep transparency. Some marketplaces and government portals still accept only JPEG, so check the rule before converting. The format converter here handles JPEG, PNG and WebP. It does not read HEIC files from iPhones, does not write AVIF, and does not convert SVG; export those to JPEG or PNG in the source app first.
A PNG screenshot converted to JPEG may fit under 200KB at 90% quality, but small text may soften. If the destination accepts PNG and the file is already under the limit, keep PNG. If it accepts WebP, test the result in the actual upload preview rather than assuming every platform renders it. Conversion does not resize, so set the dimensions first and convert second.
Verify and preserve the master
Check the exported file's byte count, pixel dimensions and extension before uploading. Open it at 100%, then check the upload preview if one is offered. Keep the original camera file or design export untouched; re-compressing an already-compressed JPEG adds artifacts and can push the file over a different limit later. Re-encoding also drops EXIF metadata, including GPS, which is helpful for privacy but means you should archive the original separately.
Name the accepted file clearly, such as product-1500-175kb.jpg, so the next person does not have to guess which export was approved. If a second destination needs a different size, start from the master rather than from the compressed copy.