A raw .img backup is as large as the whole card it came from, because Win32 Disk Imager Read copies every sector, including empty space, and does not compress anything. A 64 GB card therefore produces roughly a 64 GB file, which is awkward to store, slow to copy, and wasteful when most of that space was empty. Compressing the image with 7-Zip solves most of that problem, often shrinking a sparse system image to a fraction of its raw size.
This guide is for anyone who has a folder full of large .img files, or who is about to make a backup and wants a storage plan that will last. It covers installing 7-Zip, choosing a format, compressing correctly, verifying the archive, and decompressing before a restore.
One rule governs the whole guide: never delete the original .img file until you have verified the compressed archive and, ideally, tested a restore from it. Compression is reliable, but a backup you have never decompressed is a promise, not a proven copy. Keep the original until the compressed copy has earned your trust.
Before you start
- Check free disk space before compressing. You need room for both the original .img file and the archive until you verify the archive and delete the original.
- Do not compress an image while Win32 Disk Imager is still writing or reading it. Wait for the operation to finish completely.
- Use a clear archive name that matches the image name, with the date and device, so you can find the right backup months later.
- Remember that a compressed archive must be decompressed back to a plain .img file before Win32 Disk Imager can write it. Win32 Disk Imager does not write directly from a .7z or .zip archive.
Why do .img files compress so well, when they are already exact copies? Because empty sectors are highly repetitive: long runs of zeros compress to almost nothing. An image of a system that uses 4 GB on a 64 GB card is mostly empty space, so it compresses dramatically. An image of a card filled with photos, videos, or encrypted data compresses poorly, because that data is already dense or random. Both outcomes are normal, and the compression ratio tells you about the contents, not about whether you did something wrong.
Step by step
1. Install 7-Zip
Download 7-Zip from its official site, install the version matching your Windows system, and confirm it appears in the File Explorer right-click menu. You do not need any other compression tool for this guide, and you should avoid obscure tools that promise extreme ratios, because a backup format you cannot open in five years is worse than a slightly larger archive you can open anywhere.
2. Right-click the .img file and choose Add to archive
In File Explorer, right-click the .img file, choose 7-Zip, then Add to archive. This opens the compression settings dialog, where you choose the format and level. Do not simply choose Add to .zip from the quick menu if you want the best compression, because the dialog gives you control over format and level that the quick option does not.
3. Choose .7z format and a sensible level
Set Archive format to 7z and Compression level to Normal or Maximum. Normal is faster and already captures most of the saving on a sparse image; Maximum squeezes a little more at the cost of much longer compression time. For a one-off backup, Normal is the practical choice. Leave the other settings at their defaults unless you have a specific reason to change them, such as splitting the archive for storage on smaller media.
4. Compress and wait without interrupting
Click OK and wait for compression to finish. For a 64 GB image, this can take many minutes, even on a fast computer, because the tool must read the whole file. Do not put the computer to sleep, and avoid heavy disk work at the same time. When it finishes, note the archive size and compare it with the original, so you know how much you saved and whether the ratio looks plausible for the image’s contents.
5. Verify the archive before deleting the original
In 7-Zip, use Test archive on the new .7z file, or open it and confirm the .img file inside has the expected size. Only after that test passes should you consider deleting the original .img file to reclaim space. If you have room, keeping both for a while is even safer, and for irreplaceable backups, keeping the original on a separate drive is worth the space.
6. Decompress before you restore
When you need the backup, decompress the archive back to a plain .img file first, then write that file with Win32 Disk Imager as usual. Do not try to point Win32 Disk Imager at the .7z file, because it expects a raw image. After decompressing, check the file size against your notes, write it to a spare card for testing if the original is still working, and only then restore over a failed card.
Where to keep the backup
A backup only helps if it survives the card it came from, so copy the finished .img file off the computer you flashed from. A dedicated backup drive (Sponsored) works well for large images, and you can also keep a second copy in cloud storage such as pCloud if you want an off-site copy. Label every file with the device, date, and contents before you upload it.
Frequently asked questions
Can Win32 Disk Imager write a .7z file directly?
No. Decompress the archive back to a plain .img file first, then write that file with Win32 Disk Imager. The program expects a raw image, not a compressed archive.
Why did my image barely shrink when compressed?
Because the card was nearly full of dense data, such as photos, video, or encrypted files, which compress poorly. Sparse system images shrink dramatically, while full data cards do not.
Should I delete the original .img after compressing?
Only after you test the archive with 7-Zip Test archive and confirm the file inside has the expected size. For irreplaceable backups, keep the original on a separate drive as well.
For the full set of guides, see the Tutorials hub, and get the program from the download page. Related guides include: how to back up sd card to img, restore img backup to sd card, win32 disk imager allocated only read — each one covers one job in the same plain style as this guide.