Updated July 19, 2026
Truly lossless compression — the kind that preserves every single pixel — only adds 5–10% savings. The approach that actually works is visually lossless compression: the algorithm discards details the human eye cannot distinguish, shrinking file sizes by 2–5x. Here's how it works, real benchmark numbers, and how cloud-based compression compares to tools like TinyPNG and Squoosh.
How Much Space You Actually Get Back: Live Engine Benchmarks
We ran the Cloudiet engine on a test photo at 1100×500 pixels (293 KB — a typical size for a phone-compressed image) and measured all 9 combinations of compression modes and output formats. The numbers below come from real code, not theoretical calculations.
| Mode | Output format | Before | After | Savings |
|---|---|---|---|---|
| Lossless | Keep as JPEG | 293 KB | 293 KB | 0% — photo already optimized |
| Visually lossless | Keep as JPEG | 293 KB | 243 KB | -17% (83% of original) |
| Aggressive | Keep as JPEG | 293 KB | 199 KB | -32% (68% of original) |
| Visually lossless | WebP | 293 KB | 214 KB | -27% (73% of original) |
| Aggressive | WebP | 293 KB | 185 KB | -37% (63% of original) |
Key takeaways: (1) Lossless mode on an already-optimized JPEG yields nothing — it's for cases where pixel-perfect accuracy is required. (2) Visually lossless + WebP is the best balance: -27% storage, with a difference invisible to the naked eye. (3) Aggressive + WebP gives -37%, though on a single small photo the impact seems modest — the real payoff comes when you process thousands of shots.
On real photo archives the effect is dramatic. A recent example: 145 images from a corporate website — 21.4 MB before, 2.2 MB after (-90%). A typical smartphone photo runs 3–5 MB; after compression it's 0.7–1.2 MB. Across 10,000 photos, that's 25–35 GB freed — more than the free storage tier on Yandex Disk.
Where the Savings Come From: Three Mechanisms
Transcoding to a modern format. JPEG was invented in 1992. WebP and AVIF pack the same image 1.5–3x more efficiently at equivalent quality.
Intelligent quality tuning. Phone cameras typically save images at unnecessarily high quality — it's simpler for manufacturers that way. Dropping quality from 98 to 82–85 is visually indistinguishable, yet the file can shrink by half or more.
Stripping embedded metadata. Photos carry hidden payloads — thumbnails, color profiles, duplicate metadata entries — adding hundreds of kilobytes per file.
Compression Modes: Which One to Choose
Cloudiet offers three modes, and the logic is straightforward. Light compression is for photos you plan to print large or edit in post — expect around 30–40% savings. Medium is the sweet spot for a family archive: 2–3x smaller with no visible change even on a large screen. Aggressive is for screenshots, receipts, documents, and anything you'll only ever view on a phone (4–5x smaller).
Three Mistakes That Actually Damage Photos
Re-compressing an already compressed file. Every pass adds artifacts. Good services track which files have already been processed and skip them — Cloudiet does this automatically.
Downscaling instead of compressing. Many "optimizers" simply resize images to 1920 pixels. You'll save space, but you won't be able to print the shot or zoom into any detail. Cloudiet never touches the resolution.
Compressing without a backup. Even a perfect algorithm can't restore the original. That's why Cloudiet's free plan always keeps the original: it stays in place until you choose to delete it yourself.
Which Tool to Use: An Honest Comparison
| Tool | Where it works | Strengths | Limitations |
|---|---|---|---|
| TinyPNG | Website, manual upload | Simple for a couple of images | File size and batch limits; you'd have to download your cloud archive and re-upload it |
| Squoosh | Browser, one file at a time | Fine-grained manual controls, visual before/after comparison | One file at a time — not practical for an archive of thousands |
| Desktop apps (ImageOptim and similar) | Your computer | Batch processing of local folders | You have to download your entire cloud archive first |
| Cloudiet | Directly inside Yandex Disk and Mail.ru Cloud | Folders of any size without downloading, automatic backups, tracks already-processed files | Works with cloud storage only, not local folders |
Bottom line: for a handful of images on a website, use TinyPNG or Squoosh. For a photo archive that already lives in the cloud, use a tool that works inside the cloud.
How to Compress Photos Directly in the Cloud — No Downloading Required
The classic approach — download your archive from the cloud, run it through a local tool, upload it back — takes an evening for a 50 GB archive and doubles your bandwidth usage. Cloudiet works directly with Yandex Disk and Mail.ru Cloud: you pick a folder and a mode, and the service processes every file in place. For more on reclaiming space in specific cloud services, see our dedicated guides: Yandex Disk and Mail.ru Cloud.
Frequently Asked Questions
Why not just keep everything as-is?
You can — while storage is free. After that, the choice is between paying for extra storage every month or compressing your archive once and forgetting about it for a couple of years.
Will print quality suffer?
For prints up to A4 size, Medium mode is plenty. For photo books or posters, choose Light compression or enable the backup-original option.
Can I do this with video too?
Yes, and the savings are even more dramatic: transcoding to H.265 cuts video file sizes in half or more. Video compression is available on the Pro and Unlimited plans.
Connect your cloud storage and compress your first folder right now — free, no credit card required, with a backup of every file. You'll see results within minutes.
Compress Photos in the Cloud