Skip to content
TidyByte

Image compression

Image compression for iPhone.

Re-encode the photos that are larger than they need to be, choose the quality, and see exactly how many megabytes each one returned.

Free forever No ads, no subscription Core cleanup runs on-device

TidyByte cleanup tools screen showing the Photo Compression tool among the cleanup options.
Photo compression sits alongside the deletion tools.

Why photos end up bigger than they need to be

A 12-megapixel photo taken with the High Efficiency setting is usually one to four megabytes, which is already efficient. The oversized ones come from somewhere else: imported camera files, screenshots of high-resolution documents, images saved from the web at their original size, ProRAW captures at 20 to 30 MB, and photos edited and re-exported at maximum quality.

There is a second category that rarely gets mentioned: photos that were already compressed badly. Re-saving a JPEG at high quality repeatedly makes it larger without making it better. A compression tool that reports the real before and after size is the only way to spot those.

Compression is not deletion. You keep the image, you lose bytes that no screen was going to show you, and you can choose how aggressive to be per batch.

Compression without sending photos to TidyByte

Search for “compress images” and you land on websites that ask you to upload your pictures. For a single screenshot that is fine. For a family library it means handing your photos to a server you know nothing about, often in exchange for a file-size limit and a queue.

TidyByte re-encodes selected iPhone-library images locally with Apple’s image frameworks; those images are not sent to TidyByte. This avoids third-party upload time and works offline for images already on your device. The optional Google Photos source is separate and connects directly to Google in builds where it is enabled.

What happens to the file

  • Re-encoded at the quality preset you choose
  • Compared against the original size, and skipped if it would not shrink
  • Saved to your library with date, location and album placement intact
  • Logged in the on-device history so you can see what was processed

Choosing a quality setting that holds up

Every compression setting is a trade, and the right point on the curve depends on the image. Photographs of people and landscapes tolerate aggressive settings because the eye forgives softness in natural detail. Screenshots, documents, receipts and text-heavy images do not: they are the first to show artefacts, because sharp edges and small type are exactly what compression damages.

  1. Start moderate and check the reported saving. If it is small, the file was already efficient and there is little to gain.
  2. Exclude screenshots and documents from aggressive batches, or run them separately at a lighter setting.
  3. Judge on the device, at the size you will actually view the photo, rather than by zooming to 100%.
  4. Keep the originals until you are satisfied; deletion is a separate, reversible step.

Compress, convert, or delete?

Delete

For duplicates, screenshots you have used, and shots you never wanted. Nothing is gained by shrinking a file you do not need.

Convert

For Live Photos: dropping the motion clip usually saves more than compression, and the still is untouched.

Compress

For photos you are keeping but that are larger than the job requires: imports, ProRAW captures, web images saved at full size.

Used together, the three moves cover everything in a library, and all of them run on-device, for free, without an account.

How it compares

Image compression compared
  TidyByte iOS Mail or Shortcuts Web image compressors
Sends photos to a TidyByte server No, processed on-device No Uploads to the service
Batch a whole selection Yes, with per-file progress One image at a time Sometimes, by upload
Verifies real size reduction Yes, per file No No
Keeps EXIF data and album placement Date, location and album preserved Often stripped Usually stripped
Shows a history of what was compressed Yes, on-device ledger No No
Cost Free Free Ads or paid tiers
  • Free forever

    No subscription, no in-app purchases, no ads.

  • Private by design

    No TidyByte account, backend, analytics SDK, ads, or tracking.

  • On-device only

    iPhone-library cleanup runs locally; optional Google Photos connects directly to Google.

  • Open source

    MIT licensed on GitHub, so every claim is auditable.

Frequently asked questions

How do I compress images on my iPhone?

Open TidyByte's Photo Compression tool, select the images, and pick a quality preset. Each photo is re-encoded on-device, the new file size is compared against the original, and the result is saved into your library. You then choose whether to keep the original or let it go.

Will compressing photos make them look worse?

Compression always removes some data, but at moderate settings the difference is invisible at normal viewing sizes. Screenshots and text-heavy images lose crispness first, which is why TidyByte reports the actual saving per file so you can stop before the trade stops being worth it.

Does compressing a photo delete the original?

No. The compressed version is written to your library first and verified, and the original is only offered for removal once that succeeds. If the re-encode comes out larger than the original, the app reports that and leaves everything as it was.

Can I compress images in bulk?

Yes. Select as many photos as you like and the batch runs with per-item progress and a cancel option. Items that would not shrink are reported as skipped with the reason, rather than quietly disappearing from the list.

Is there a limit on how many images I can compress for free?

No. There is no daily cap, no credit system and no paid tier, because the work happens on your own device and costs nothing to run. The app is free with no in-app purchases and the source is MIT licensed.

Every cleanup tool, in one free app

Make big photos small.

Download TidyByte Free and re-encode oversized images without sending them to a TidyByte server.