🔒 Your images never leave this browser.
Choose the 200 KB JPG preset for a JPG upload limit, or set Target KB for another size or output format. Check the result before uploading; a valid result may not be possible within your constraints.
When to use this Set a target size in KB or use the 200 KB JPG preset. Check the saved file’s format, byte count, and minimum width and height.
🔒 Your images never leave this browser.
Use one static JPG, PNG or WebP image. Choose Quality presets to keep the format and pixel dimensions, or Target KB when an upload has a byte ceiling. Size optimization is separate from metadata cleanup.
These examples describe constraints and expected decisions. They are not measured compression results or promises that a target will be reached.
| Setting example | Expected behavior or limit |
|---|---|
| Target 100 KB; minimum 600 × 600 px | The target is 100,000 bytes. A valid result must meet the byte cap and both minimum dimensions; no result is guaranteed. |
| Source 500 × 500 px; minimum 600 × 600 px | The minimum exceeds the source. Upscaling is disabled; obtain a larger source or lower the minimum only if allowed. |
| Transparent PNG; output JPG | Explicit white-background permission is required. Use PNG or WebP if transparency must remain and the recipient accepts it. |
| Same-format source already below target | Original bytes may be returned, including their existing metadata. |
| Quality presets with PNG | PNG does not use the lossy quality setting. A preset that does not reduce size can return the original file. |
Compare exact bytes, format, width and height. Target KB searches quality and then smaller dimensions while respecting both minimums. Inspect small text, edges, direction, color and important detail: a smaller file can lose detail or pixels. Meeting the target does not guarantee another website accepts the upload.
A successful message or an optimized filename does not certify metadata removal. Original-retained files keep their metadata. Byte-identical files necessarily retain the same embedded information; changed bytes alone do not prove sensitive fields are absent. Use a supported privacy workflow and inspect the final upload copy independently when cleanup is required. Operating-system Properties may show only some fields.
The byte ceiling and minimum dimensions may conflict with acceptable detail. No download is offered when no valid result is found. Change only constraints the recipient allows: raise the cap, lower minimum dimensions or try another accepted format. If the conflict remains, keep the original and ask for another upload route.
Quality presets keep pixel dimensions and the original format. If the encoded file is no smaller, the original may be offered. PNG does not respond to a lossy quality setting like JPEG.
Target KB rejects animated inputs and may refuse files under conservative memory checks; those checks do not measure a device’s actual maximum memory. Its JPEG EXIF orientation check rejects values other than 1; the parser does not check PNG orientation metadata. Verify actual display direction rather than assuming all formats are normalized.
No sanitization guarantee is made. Presets and same-format Target KB can return original bytes. Re-encoding is not proof of all-format metadata removal. EXIF orientation and ICC information affect appearance, and removing metadata does not remove faces, names or addresses visible in pixels. Stop sharing if cleanup fails or verification is unavailable.
Use Cancel during Target KB processing, or Reset for a fresh input. Keep the original until the final copy has been checked.