Choose a KB limit. Quality and dimensions are reduced only as much as needed.
Private batch compression
Image CompressorSmaller files. Same visual confidence.
Reduce JPG, PNG, and WebP file sizes for websites, email, forms, and social media. Set a target size and process up to 20 images without uploading them.
Images stay in this browser
IMAGE COMPRESSOR
Compress images to the size you need
BatchTarget KBLocal
01
Source images
Drop images to compress
JPG, PNG, WebP, SVG, and browser-readable HEIC images
Up to 50 MB each and 20 images at a time02
Batch preview
Your image queue appears here
Add one or more images to compare original and compressed sizes.
Images to Compress0 images
Apply one setting to as many as 20 images and download each result.
Compression runs locally and the images never leave your device.
Try a documented 100 KB example
Use Try Sample, JPG, and a 100 KB target. A recorded run produced 99.7 KB from a displayed 171 KB source; your browser can produce different sizes. Check the output dimensions and small text as well as the size.
Read the example, samples, and exact rules →Choose compression settings for the destination, not just the smallest number
A useful compressed image must still look right where it will be used. Start with the delivery requirement, keep an untouched original, and compare the result at normal viewing size before replacing a source file.
Step by step
- Define the destination
A website hero, marketplace photo, email attachment, and application upload all tolerate different dimensions and file sizes. Record the required pixel dimensions and maximum KB before compressing.
- Add the original files
Batch files that share the same purpose so one target and format choice makes sense. Mixed logos, screenshots, and photos usually need separate passes.
- Set a realistic target
Use a preset or enter a KB target. OmniKit adjusts quality first and may reduce dimensions only when quality changes alone cannot reach the target.
- Compare before downloading
Inspect edges, small text, gradients, and transparent areas. Keep the original when the saving is small or the result introduces visible artifacts.
Decision guide
- JPG
- Best for photographs without transparency and broad compatibility. Repeated exports can accumulate artifacts.
- WebP
- Usually smaller than JPG at similar visual quality and suitable for modern websites and apps.
- PNG
- Keeps transparency and sharp interface graphics, but browser PNG encoding is lossless and may not reach a strict size target.
- Target KB
- Useful when a form or platform enforces a hard upload limit. Leave a small safety margin below that limit.
Important limits
- Compression cannot recreate detail already lost in a previously compressed source.
- A very small target can force both lower quality and smaller dimensions.
- PNG photographs often remain larger than JPG or WebP because PNG is optimized for lossless graphics.
- Processing happens in browser memory; very large batches can be limited by the device, so split them when the page becomes slow.
04 · Common questions
Common questions
Why is my PNG still larger than the target?
PNG export is lossless in this browser workflow. Convert a photographic PNG to WebP or JPG when transparency is not required.
Does a smaller file always mean lower quality?
Not necessarily. Removing inefficient encoding can save space with little visible change, but aggressive targets eventually reduce quality or dimensions.
Should I delete the original after compression?
No. Keep an original or master file so you can create a different size later without compressing an already compressed result.
Compress JPG, PNG, and WebP images online
Use the target size presets for profile pictures, application forms, email attachments, product images, and faster websites. JPEG and WebP quality is adjusted first; when a strict target cannot be reached, OmniKit progressively reduces dimensions.
PNG uses lossless browser encoding, so some PNG files may remain larger than the selected target. Choosing WebP or JPG usually produces a smaller result, while PNG is useful when transparency must be retained.
Image compression questions
Are my images uploaded?
No. Your browser decodes and re-encodes each image locally. OmniKit never receives the source image or the generated result.
Can every image reach the exact target size?
Not always. Very detailed images or lossless PNG files can remain above the target. The result card clearly states when the browser compressed an image as much as possible.
Does compression remove metadata?
Yes. Exported images are newly encoded pixel data, so common EXIF fields such as GPS location, camera model, and capture time are not copied.