Motionix / Your workspace
Compress images. Keep control.
Reduce a photo's file size without guessing what changed. Choose balanced compression, a size ceiling, or a percentage of the original, then compare the result before downloading.
Three steps. One result to inspect.
Pick the real constraint
Check whether the destination limits file bytes, image dimensions, or both. A smaller pixel frame and a different file format solve different problems.
Set and inspect
Choose your target, then inspect text, faces, transparent edges, and the reported dimensions. A percentage target means a share of the original bytes.
Save a separate copy
Download a result only when it meets your needs. Keep the original and use it for another attempt rather than repeatedly recompressing the previous JPEG.
How to compress a JPEG below 200 KB
Read the upload rule first. Some services use decimal KB while this workspace uses 1024-byte KiB. A strict 200,000-byte ceiling is lower than 200 KiB; a 195 KiB target equals 199,680 bytes. Compare the actual output size, not a promised percentage. The compressor searches quality and can reduce dimensions when needed. A difficult target may fail rather than produce a misleading success. A minimum-size requirement is different: this tool is not a guarantee that a file falls within every minimum/maximum window.
Compress an image without resizing: know the trade-off
A balanced export may reduce bytes without changing dimensions, but a strict target can require smaller pixels. Read the result dimensions before uploading. JPEG is lossy, so repeated recompression can soften text and facial detail. PNG uses lossless encoding, but resizing a PNG still changes its pixels. The original may already be smaller than a fresh encoding; keeping it in that case is more honest than calling a larger file an improvement. No fixed saving or visually identical result is promised.
Compress a PNG while keeping transparency
A normal PNG workflow keeps an alpha channel. Native PNG quality is not controlled by a JPEG-style quality slider, so reducing a large PNG to a strict byte target may reduce its dimensions. Fixed-JPEG preset workflows instead flatten transparency onto white. Inspect logos on a contrasting background and choose the format the destination accepts. WebP supports transparency, but changing formats is not a guarantee of smaller output or metadata removal.
Why an image can still exceed an upload limit
The destination may reject a format, require different dimensions, or count bytes differently. Check all three rather than lowering quality repeatedly. Unsupported or oversized files should produce an error; successful previous results remain distinct from new settings. Processing does not require an image upload, but browser limits and initial site requests still apply. This tool can retain the original if no smaller same-format output is found, so do not assume it strips metadata. Keep a backup when metadata or color fidelity matters.
Your files, with explicit choices
Image processing does not require an upload. The site and processing assets use the network. Results are not automatically backed up. Download your result and keep the original.
Frequently asked questions
Can every image be compressed below 100 KB or 200 KB?
No. An achievable size depends on the source, format, quality, and dimensions. A strict target may shrink the image or fail. Check exact bytes and the receiving service's requirements.
Does 60% mean a 60% reduction?
No. A target of 60% means at most 60% of the original byte count, equivalent to at least a 40% reduction if the target is achieved. It does not describe visual quality.
Will compression preserve every pixel and all metadata?
No universal preservation claim is possible. JPEG and the chosen WebP encoding are lossy; target mode may resize. The original may be returned when a same-format re-encoding is not smaller, so metadata removal is not guaranteed either.
Can I compress HEIC or several images at once?
This workspace processes one JPEG, PNG, WebP, or browser-decodable AVIF at a time. Convert HEIC with the dedicated HEIC-to-JPG tool first. It is not a batch compressor.
Why is the original kept?
If balanced same-format re-encoding would not save bytes, keeping the original avoids making it larger. That is not proof of universal optimization; another target may change the quality or dimensions.
Sources and the limits of this page
Sources checked
- MDN image format guide
Lossy/lossless formats and alpha support.
- MDN canvas toBlob()
Quality parameters apply to lossy encoders, not native PNG quality.
- Google WebP container specification
WebP can contain metadata; its extension alone does not imply removal.
These references explain formats or published requirements. They do not represent a partnership or an inspection of your file. Check the current requirements before using an export.