How it works
Select JPG, PNG or WebP files, choose your settings, then process and download the results. PixelKit performs the image operation in your browser. The crop tool edits one image at a time.
Your files stay private
Image contents are not sent to a PixelKit file-processing server. Closing or refreshing this page clears the current queue.
Changing language opens the equivalent page and clears the current image queue. Only your language preference is stored; selected images are never stored in browser storage.
Practical limits
The 20-file cap is not a memory guarantee. On phones, start with 3–5 large photos per batch; split the queue if PixelKit shows a memory warning. Keep the tab open while processing. Files that cannot be decoded are reported instead of silently changed.
Guides that use this tool
- How to choose between JPG, PNG and WebP
- How to compress images without losing visible quality
- Work through a batch of images without losing track
- Where your images actually go in a browser tool
Frequently asked questions
Does compressing change the pixel dimensions of my image?
No. Compression changes how the pixels are stored, not how many there are. Use the resize tool when you need smaller dimensions as well.
What happens when the target size cannot be reached?
The tool keeps the smallest result the browser produced and shows the size it actually reached, instead of reporting a target it did not meet. Resizing first usually gets you closer.
Is my image uploaded while it is compressed?
No. Your browser decodes and re-encodes the file locally, and there is no upload step in the tool.