A byte limit is a constraint you can measure.
A government form, visa portal, or document handoff can reject an otherwise clear photograph because it is a little too large. This preset treats the limit as an actual encoded-byte constraint. It starts at 200 KB using a conservative decimal interpretation: no more than 200,000 bytes. The original stays on your device, and a download remains locked when the current result does not satisfy that ceiling.
Start with the destination's complete rules
A file-size requirement rarely stands alone. The receiving service may also specify a format, minimum pixel dimensions, portrait composition, or background. Read those conditions together before choosing how to reduce a file. A smaller JPEG can still be unsuitable if it has too few pixels or the wrong subject framing. This preset measures the bytes it creates; it does not certify the photograph, verify a person's identity, or guarantee acceptance by a particular portal.
The preset's cap is 200,000 bytes rather than 204,800 bytes. Both binary and decimal interpretations appear in everyday descriptions of kilobytes, and a conservative decimal ceiling avoids relying on a portal accepting the larger interpretation. Displayed sizes may be rounded for readability, so the download gate uses the underlying integer byte count. A file that looks approximately 200 KB on a rounded label is not automatically allowed through if its actual count exceeds this preset's limit.
Protect dimensions until you choose otherwise
Quality-controlled encoding changes the representation of the image while normally keeping its width and height. That is the first approach here because a portal may require both a small file and a minimum pixel count. The worker makes a candidate, measures it, and refines quality within a bounded number of attempts. Detailed textures or small text may remain expensive to represent, and aggressive quality reduction can damage information that matters even when the final file is technically small enough.
Dimension reduction is a separate opt-in. Enable it only after checking what the destination will accept, then read the reported output width and height alongside the byte count. Reducing a grid can be more effective than further damaging its photographic quality, but it also removes spatial information. PNG targets are handled without quietly quantizing colors: when its unchanged grid is too large, a PNG remains over target unless you allow the tool to reduce the dimensions.
Review the result before you submit it
Use the split divider to compare the original and the current encoded result. Look for readable lettering, clear facial features, ringing around edges, and damaged smooth areas. The quality percentage is an encoder input, not a universal assessment of legibility. A different source photograph, crop, or format can be a better answer than forcing an unacceptable image under the cap. An honest target warning is more useful than a success label that sends an oversized file to a restricted form.
Batch processing applies the same current constraints to each selected image. The queue reports files that are still over target, and this constrained preset keeps individual and all-files downloads locked until their applicable results meet the ceiling. Completed archives are created locally without a remote upload. Keep originals, save compliant delivery copies separately, and check them in the destination's own preview before final submission. Metadata from the source container is not copied into the freshly encoded outputs.
Three steps. A finished file.
Choose the image that needs a 200 KB cap
Select a JPG, PNG, or WebP, or add a batch within the local file budget. The preset fixes the ceiling at 200,000 bytes.
Compare quality while keeping required dimensions
Adjust quality and inspect the split preview. Allow dimension reduction only when the destination's rules permit a smaller grid.
Download only after the cap is met
Check actual output size and dimensions. This preset unlocks a download only for a result within its byte ceiling; batch ZIP waits for the complete queue.
A little clarity.
Does this 200 KB preset mean 200,000 or 204,800 bytes?
It uses the stricter decimal ceiling of 200,000 bytes. That also fits a 204,800-byte interpretation, while avoiding a file that only meets a more generous binary limit.
What if my image cannot fit under 200 KB at the required dimensions?
The result stays visibly over target and its download remains locked on this page. Try another quality, format, crop, or source. Only enable resizing when the receiving service permits it.
Will a file under 200 KB automatically pass a visa or government portal?
No. Byte size is only one condition. The destination can impose its own dimensions, format, composition, and submission rules, which you must check independently.
Related tools
Free online image compressor
Compress JPG, PNG, and WebP images online for free. Compare quality, set a target file size, and download batches. No uploads, sign-up, or added watermarks.
Free online image cropper
Crop, rotate, flip, and resize images online for free. Choose an aspect ratio or exact pixel dimensions and export JPG, PNG, or WebP without uploading files.
Image color picker — HEX, RGB & HSL
Pick colors from an image with an 8× pixel loupe. Copy HEX, RGB, or HSL values and extract a CSS color palette for free. Your image stays on your device.
SVG optimizer
Optimize and minify SVG files online for free. Compare vector previews, preserve viewBox, and export smaller SVG or React components. No uploads required.