The honest answer to which apps compress images is that two kinds do. Deliberate compressors like ImageOptim, Squoosh, and the tool on this site shrink a photo because you asked. Platforms like Discord, WhatsApp, and Instagram re-encode your uploads because it saves them bandwidth. This hub measures both, app by app.
I build image compressors, so I did the boring part. I read each app's own documentation, used the popular ones, and ran my own file through this site's engine to get numbers I can stand behind. Here is the map, starting with the apps you actually choose, then the platforms that choose for you.
Which apps compress images on purpose?
The apps built to compress images on purpose fall into three groups: phone apps, desktop software, and web tools you open in a browser. All three do the same core job, which is to re-encode your photo so the same picture takes fewer bytes, and they differ mainly in where they run, whether they handle a whole folder at once, and what they cost.
The three groups map to how you work. A phone app compresses photos where most photos are born, in your camera roll, with no trip to a computer. Desktop software chews through folders of images and fits into an editing workflow you already have. Web tools need nothing installed and behave the same on any operating system, which is why a browser compressor is usually the fastest route for a one-off file.
There is a fourth answer most listicles skip: you may not need to install anything at all. A browser does the job for the majority of single photos, and that is where the real comparison starts.
Do you even need an app to compress a photo?
Usually not. A browser compressor does the same job as an installed app with nothing to download, no account, and no ads, which is why it is the first thing I reach for on a single photo or a small batch. The compressor on this site is our own, and it converts between JPG, PNG, WebP, and AVIF on output. You can drop up to 30 images at once, 25 MB each, with no signup.
Two things happen on the way through that you would otherwise want an app for. EXIF data, the hidden metadata your camera writes into every file including GPS coordinates and the exact time of the shot, is stripped by default. And the copy you upload is deleted from our storage within the hour, swept out by a job that runs every fifteen minutes. When you want to compress the photo in your browser instead of trusting a platform to do it later, that is the whole transaction.
The measured before and after
Here is what the engine did to two real files in July 2026, measured, not estimated.
| File | Before | After at quality 80 | Result |
|---|---|---|---|
| Phone photo, JPEG | 4.5 MB | ~900 KB JPEG | ~80% smaller |
| Home page demo, JPG | 497 KB | 214 KB WebP | 56.9% smaller |
The phone photo landed at the top of the typical 60 to 80 percent range because camera JPEGs are saved at a quality far above what any screen shows. Quality 80 is the default here because it is visually lossless for a photograph. If a form needs the file even smaller, you pull the quality slider down and watch the after size drop; re-running the same image never costs you anything.
The one thing this tool does not do is hit an exact kilobyte target for you automatically. There is no target-size mode; you move the slider and read the number. If you need an app to reduce image size in KB to a hard number without touching a slider, a couple of the phone apps below do exactly that, and so does the command-line route on desktop.
The best apps to compress images on your phone
On a phone the fastest route is still the browser, but if you want a dedicated app, both stores carry compressors that batch your camera roll and, on the Android side, compress to a target size in KB or MB. Whichever you pick, the same rule holds: compress once from the original, because a second lossy pass over an already-compressed photo shows.
Compress images on iPhone
To compress images on iPhone, you can use the browser compressor above, a native route, or an App Store app. The most popular App Store compressors shrink JPEG and PNG files and let you keep or clear metadata, which is handy, though most of the free ones are ad-supported, and some carry tracking labels worth reading before you install. The App Store's own privacy labels tell you which. For the native levers Apple builds in, the Share sheet resize, Mail's automatic sizing, and a Shortcuts action, the iPhone guide walks each one with measured results.
The best free app to compress photos on Android
On Android, the best free app to compress photos for most people is one of the batch resizers that can target an exact file size, such as the widely used Photo Compressor and Resizer, which compresses to a chosen KB or MB. That target-size feature is the one real reason to prefer a phone app over the browser. The catch is the usual one on free store apps: ads, and sometimes tracking. Android's own built-in routes, including resizing on share, are covered in the Android guide.
Desktop and web compressors, compared
On a desktop you have more power and more choices: a free open-source app like ImageOptim on a Mac, an image compressor app for PC on Windows, the export settings already inside Photoshop or GIMP, or a web tool that runs in the browser on any machine. Each suits a different habit.
Mac: ImageOptim
ImageOptim is the Mac answer most people land on, and for good reason. It is free and open source, you drag a folder onto it, and it bundles best-in-class encoders while stripping the invisible junk. It removes EXIF, GPS, color-profile, and comment metadata as part of the optimization, which cuts bytes and, as a side effect, cleans up the privacy exposure your camera left in the file (ImageOptim preferences). It is lossless by default and does not resize, so pair it with a resize step when the pixels are the problem.
Windows and Linux desktop compressors
Windows and Linux do not ship a one-click compressor, but free tools fill the gap. RIOT and Trimage are the usual open-source picks, giving you a quality slider and metadata stripping without a subscription. For a pure resize, Paint on Windows will drop the pixel dimensions and re-save, which is a blunt instrument but fine when losing pixels is acceptable. The any-device guide covers the built-in routes operating system by operating system.
Photoshop and GIMP export
If you already own Photoshop or run GIMP, the compressor is built in. Export As and the older Save for Web give you a quality slider and a live preview of the resulting file size, which is exactly the lossy re-encoding a dedicated app performs, just inside your editor (web.dev on image performance). GIMP's export dialog does the same for free. These are the right tool when the image is already open on your canvas.
Web tools with nothing to install
The web category is where the no-install answer lives. Squoosh, Google's open-source tool, is notable for processing images locally in your browser, so the file never leaves your machine. iLoveIMG and Adobe Express run bulk compression and conversion in the cloud. The compressor on this site sits here too, and it is the one whose numbers I can vouch for byte for byte.
How do these apps compare on batch, target size, and privacy?
Here they are side by side. I scored each on where it runs, whether it handles a folder at once, whether it can hit an exact file size, and how it is funded, compiled from each tool's own listing and my own use in July 2026.
| Tool | Where it runs | Batch | Compress to a target KB | Cost model |
|---|---|---|---|---|
| This site | Web, any OS | Yes, 30 free | No, slider only | Free tier, Pro $12/mo |
| ImageOptim | Mac app | Yes, drag a folder | No | Free, open source |
| Squoosh | Web, local in browser | One at a time | No | Free, open source |
| Photo Compressor and Resizer | Android app | Yes | Yes, KB or MB | Free, ad-supported |
| Compress Photos and Pictures | iPhone app | Yes | Yes | Free, ad-supported |
| Photoshop or GIMP | Mac, Windows, Linux | Via export or scripts | No | Paid or free |
Read the table by the problem you have. If you compress folders, batch support is the column that matters, and the desktop apps and this site win it. If an upload form demands an exact number, the target-KB column is decisive, and there the phone store apps and the command line lead, because most browser and desktop compressors, this one included, give you a slider rather than a number box.
Privacy is the column people forget, and it splits on where the compression actually happens.
| Tool type | Where your image is processed | Metadata |
|---|---|---|
| Browser tool (this site) | Uploaded, processed, deleted within an hour | EXIF stripped by default |
| Local web tool (Squoosh) | In your browser, never uploaded | Depends on settings |
| Installed app | On your device | Varies; some keep EXIF, some clear it |
| Platform upload (Discord, and the like) | On the platform's servers | Usually stripped |
The honest tradeoff for this site is right there in the table. A local tool like Squoosh never uploads your file, which is the stronger privacy story; this site does upload, processes on a server, then deletes the copy within the hour and strips the EXIF on the way through. Both are defensible. If never-uploading is your hard requirement, use a local tool; if you want the smallest file with the metadata gone and no install, the browser route here is built for it.
Which apps compress your images without asking?
Most messaging apps, social networks, and some cloud services do. They re-encode your uploads to save bandwidth and storage, and it is the same optimization I would build in their position. The levers are consistent: downscale the pixels to the size the image will actually display, re-compress to a lossy target at an automatically chosen quality, sometimes convert the format to WebP, and usually strip the metadata.
The economics explain each move. Serving an image at its displayed size instead of its shot size, and picking the most efficient format the requesting browser supports, are documented, running infrastructure; Cloudinary, the image CDN behind a large slice of the web, describes both its automatic format selection and its automatic quality selection in its optimization docs (Cloudinary image optimization). Format conversion pays off because WebP comes in 25 to 35 percent smaller than a JPEG of the same visual quality, per Mozilla's format guidance (MDN image file types), which is why so many platforms hand you back a WebP file you never created.
The trouble is that almost none of them publish the numbers. Discord is the best-documented consumer app, and even its File Attachments FAQ only tells you part of the story: non-Nitro uploads cap at 10 MB, a file over that limit is shared as a download instead of shown inline, and mobile Data Saving Mode sends images in lower quality over cellular (Discord File Attachments FAQ). Whether an in-limit image gets re-compressed on the way through is not stated. That silence is the pattern everywhere, and the behavior moves without announcements, so the only trustworthy number is one from a dated test.
That is why each platform gets its own page in this hub, built around a real upload test with a date on it. Pick the app in front of you.
Messaging and chat:
- Does Discord compress images? covers the 10 MB cap and what happens inside it.
- Does WhatsApp compress images? tests the most aggressive pipeline most people use daily.
- Does Slack compress images? tests the workday uploader.
- Does Teams compress images? does the same for Microsoft's side.
Social platforms:
- Does Instagram compress images? tests the platform photographers complain about most.
- Does Facebook compress images? measures the feed pipeline.
- Does LinkedIn compress images? checks what happens to your professional graphics.
- Does Bluesky compress images? tests the newer network.
- Does Imgur compress images? covers the image host itself.
- Does Twitter (X) compress images? separates the copy X stores from the one it serves.
- Does Pinterest compress images? tests what survives into the feed.
Photos and cloud storage:
- Does Google Photos compress images? tests the Storage saver question.
- Does Google Drive compress images? answers whether plain file storage touches your files.
- Does Dropbox compress images? tests the sync model.
Email:
- Does Gmail compress images? tests attachments against inline images.
- Does Outlook compress images? covers the resize prompt and what it does.
Documents and design tools:
- Does Word compress images? tests what happens inside a .docx.
- Does Google Slides compress images? checks presentation uploads.
- Does PDF compress images? answers the format question people mean when they ask it.
- Does Canva compress images? tests the design tool's export path.
- Does Figma compress images? does the same for the design canvas.
How to stop an app from wrecking your photos
Compress the photo yourself before you upload it. A platform's pipeline hits hardest when you hand it a huge, never-compressed original, because there is a lot to squeeze and the platform picks how. Hand it a small, already-optimized file instead and its pass has almost nothing left to take, and what it does take, you already chose.
The numbers make the case. A 900 KB upload sails under every cap in this hub, uploads faster on a phone, and gives the platform's re-encoder almost nothing to bite on. The compound case is what you are avoiding: a photo that goes phone to WhatsApp to a group chat, gets saved, gets posted to Instagram, then screenshotted, has been through four or five lossy re-encodes, and it looks like it. Compress Images Without Losing Quality covers why repeated lossy saves stack up and how to stay ahead of them.
Two habits close the loop. Keep your originals somewhere that does not re-encode them, and treat every copy inside a chat app or social feed as a lossy duplicate, because pulling your own photo back out of a thread gets you the platform's version, not yours. And strip the metadata yourself rather than depending on each platform to do it. For the specific size caps and formats each destination wants, Compress Images for Email, Web, Docs and Uploads lays them out side by side, and the broad how-to lives on the main compress an image hub.