The free online image compressor shrinks a JPG, PNG or WebP with a quality slider or a target size in KB, so a page loads faster or an upload fits a limit. Because it runs in the browser, the images are never uploaded.
Image format work by OnlinePCApps since 2013
A photo straight from a phone or camera is often several megabytes, too heavy to attach, to upload or to load quickly. The free online image compressor brings the size down while the picture still looks right.
A form or an inbox often caps a file at a few megabytes, or a portal asks for a photo under 100 KB. Setting a target size lands the image under the limit on the first try.
Heavy images are the usual reason a page feels slow and scores poorly on Core Web Vitals. On most pages the biggest image is the LCP element, so compressing it cuts the weight and the page paints sooner.
A folder of full-size photos eats disk and cloud space fast. Compressing a batch keeps the pictures usable at a fraction of the size, so far more fit in the same space.
Drop the images on the panel above, or pick them from the device. A single photo or a full set can load together, in JPG, PNG or WebP.
Move the quality slider and watch the size update, or type a target such as 150 KB and let the quality settle to match. A preview shows the result before anything is saved.
Save the lighter image, or take a whole batch as a ZIP. The originals stay as they were, so the source is always ready to compress again at another setting.
To compress an image is to write the same picture into a smaller file. The tool does that on the device.
A lossy pass on a JPG or WebP drops fine detail the eye barely registers, which is where most of the saving comes from. A quality slider sets how far to go, with a live size read-out and a preview to judge the result.
A PNG is repacked without dropping a single pixel, trimming a graphic, logo or screenshot with no quality change at all. The saving is smaller than a lossy pass, so a photo-like PNG does better converted to JPG or WebP.
A target size in KB or MB sets the goal, and the quality settles on its own to land under it. This is the direct answer to an upload that demands a file below 100 KB or a couple of megabytes.
EXIF details such as the camera model and GPS location are removed, which trims a little more size and keeps that data private. The pixels are untouched, so only the hidden tags go.
To compress an image, to reduce a photo's file size and to shrink an image all name the same step. A search for compress PNG, reduce image size or a photo compressor finds the same tool. The source files are kept exactly as they were.
Compression trades file size against detail. These points decide how far it goes and how the result looks.
| The case | Result | What happens and why |
|---|---|---|
| JPG and WebP photos | big saving | A lossy pass drops detail the eye hardly sees, cutting most of the size. |
| PNG graphics | modest saving | A lossless repack keeps every pixel, so the drop is smaller than lossy. |
| Photo saved as PNG | convert instead | A photo in PNG shrinks far more turned into a JPG or WebP. |
| Target size | quality adjusts | A goal in KB is set, and the quality settles to land under it. |
| Over-compression | artifacts | Pushed too far, a JPG shows blocking, blur and banding, so a preview helps. |
| Resizing first | saves more | Shrinking a huge image to its display size cuts more weight than quality alone. |
| Metadata | stripped | EXIF and GPS tags are removed for a little size and more privacy. |
| Transparency | kept | A PNG or WebP keeps its clear background through the compression. |
| Where it runs | on the device | Every picture is processed in the browser, so nothing is uploaded. |
A Smaller File From the Same Picture
Compression reduces the bytes an image takes up without changing what it shows, and it comes in two kinds. Lossy compression, used by JPG and WebP, throws away fine detail the human eye barely notices, which is where the large savings come from. Lossless compression, used by PNG and lossless WebP, rewrites the very same pixels in a tighter way, so nothing is lost but the saving is more modest. Three honest points guide the setting. Lossy compression cannot be undone, so the original is worth keeping, since detail once removed cannot be restored. Pushing the quality too low shows artifacts, the blocking and banding that appear when too much has been thrown away. And a picture kept oversized carries needless weight, so resizing it to the size it will actually be shown at often saves more than the quality slider alone. The references below define the formats and the page-speed goals compression serves.
Both make an image smaller. The trade is real, and a photo is often a personal one.
| Point of comparison | This tool Compressed in the browser On the device | Hosted compressor Uploaded and compressed on a server |
|---|---|---|
| Where the photos go | Never leave the device | Uploaded to a server |
| Price and caps | Free with no file cap | Free tier often capped |
| Camera RAW files | Common web formats here | Server or desktop reads RAW |
| Hundreds of images | A set at a time in the browser | Batch on their hardware |
| A saved size preset | Set each time in the browser | Desktop saves a preset |
The last three rows go to the desktop and hosted routes, since camera RAW, a run of many hundreds and a saved preset each call for more than a browser tab holds. For a set of everyday photos the first two rows are what count. The images stay on the machine, and the compression is free with no cap.
Each picture is recompressed inside the browser using its own canvas, which keeps the job client-side and every photo on the machine that opened it. Nothing is sent to a server to be processed.
A photo can be a personal record, a screenshot, an ID card or a picture that was never meant for an outside server. Many hosted compressors upload each one and promise deletion hours later, while compressing on the device avoids that hand-off completely.
Each of these makes a picture smaller. They differ in effort, in cost and in where the file goes.
Preview, Squoosh and ImageMagick each run on the machine, yet each is either narrow or built for the command line. The online tool here stays local in the same way while adding batch compression and a target size with nothing to set up.
A little context sets how far to push it.
Lossy compression cannot be undone, and detail once removed does not come back. Compressing a copy and keeping the full-quality original means there is always a clean source to start from again.
A photo shown at 800 pixels but saved at 4000 carries weight nobody sees. Resizing to the size it will actually appear at often saves more than the quality slider, with no visible loss.
PNG shines for logos, screenshots and transparency, but a photograph saved as PNG stays large. Converting a photo-like PNG to JPG or WebP shrinks it far more than compression alone.
A set of pictures runs in the browser from memory, which is right for the images at hand. A directory of hundreds, or a full library bound for a website, is a job for the desktop edition, reading from disk and optimising every file in one sweep against a saved preset.
Set it on a folder of pictures and each file is brought down to the target in one sweep, written next to the source.
A preset holds a target size, quality and format, so a repeated job runs the same way each time in one click.
Camera RAW straight off a DSLR and multi-page TIFF are opened and optimised, file types a browser tab cannot decode by itself.
Free and online, with no sign-up and no upload. Bring a picture's file size down in the browser, all on the device.