After flashing an image, Windows shows your 32 GB or 64 GB card as only a few hundred megabytes, or a few gigabytes. It looks as if flashing shrank the card. In almost all cases it did not. The image created one or more small partitions, Windows can only read the first small FAT partition, and the rest of the card sits unallocated and invisible in Explorer. The capacity is still there; it just needs to be reclaimed or expanded.
This is a direct consequence of how Win32 Disk Imager works. It copies a whole device sector by sector, and a Read copies the full device size with no compression. An image built from, say, a 4 GB card therefore contains a 4 GB partition layout even when you write it to a 64 GB card. The extra space is not lost and not overwritten with data; it is simply not yet assigned to any partition. The same logic explains why a backup image file is as large as the whole card, not just the files on it — see allocated partitions and empty images for the related Read-side behaviour.
Why the card looks smaller
- The image partition layout is smaller than the card. The image’s partitions end well before the end of the larger card, leaving unallocated space.
- Windows only mounts what it understands. A Raspberry Pi image, for example, has a small FAT boot partition that Windows shows, plus Linux partitions Windows does not assign letters to. Explorer therefore reports only the small visible partition.
- Disk Management tells the truth. Open Disk Management and you will usually see the small partitions plus a large block labelled Unallocated. That block is your missing space.
- A fake card is the exception. If Disk Management shows the card itself as much smaller than printed, or a capacity test fails, the card may be counterfeit rather than merely partitioned small. See how to test a fake card before assuming a partition fix will help.
Fixes, cheapest and quickest first
- On a Raspberry Pi, expand the filesystem from the Pi itself. Boot the Pi, run raspi-config, choose Advanced Options, then Expand Filesystem, and reboot. This is the intended fix for Pi images and it preserves your system.
- On Windows, extend the visible partition only if it is a Windows-readable partition you own. In Disk Management, right-click the partition immediately before the unallocated space and choose Extend Volume if Windows offers it. Do not delete a partition you do not recognise to make room.
- Use a partition tool for Linux partitions. If the unallocated space follows a Linux partition, a tool such as GParted (from a live USB) can resize that partition into the free space. Back up the card image first — resizing can go wrong.
- Re-image from scratch if you do not need the current contents. If the card holds nothing you need, you can repartition the whole card in Disk Management (delete all partitions, create one full-size FAT32 or exFAT volume) to prove the full capacity is present, then flash again and expand as above.
- Verify full capacity before trusting the card. After reclaiming space, check that Disk Management shows the full size and, for a new or suspicious card, run a full write-and-verify test.
Do not format the card in Windows as a first step if the card contains a system you want to keep, such as a Pi installation. Formatting the visible partition will not reclaim the unallocated space and may destroy the boot partition. Expanding is the fix; formatting is only appropriate when you are deliberately wiping the card to reuse it as plain storage.
If you need a fresh copy of the tool, use the download page. For other post-flash surprises, the troubleshooting hub and write succeeded but won’t boot guide cover the next most common cases.
When to stop and switch tools
Stop trying partition fixes if Disk Management shows the physical device itself as far smaller than the printed size, if the card reports different sizes on different PCs, or if a full capacity test fails. Those are signs of a fake or failing card, not a partition layout issue, and no partition tool will create real capacity that is not there. Replace the card. Likewise, if expanding repeatedly corrupts the filesystem, stop and take a fresh backup image first, then expand on a copy — a card that corrupts on resize is telling you it is unreliable.
FAQ
Did flashing shrink my SD card permanently?
No, in almost all cases. The card still has its full capacity; Windows is only showing the small partition that the image created. Re-partitioning restores the rest.
Is it safe to expand the partition on a Raspberry Pi card?
Yes, if you use the Pi’s own expand option or a trusted partition tool and you have a backup. Expanding does not erase the system partition when done correctly, but back up first anyway.
Why does the image not fill the whole card?
Because an image is a fixed-size snapshot. It was built for a smaller card or a fixed partition layout, so it only creates partitions of that size, leaving the rest unallocated.