After you flash an image to a large card, Windows often shows only a small drive, and the rest of the card seems to have vanished. Nothing is wrong. The image carried its own partition layout, sized for the original card or image, and the unused space on your larger card is simply unallocated. Expanding the filesystem assigns that space to the main partition so the system can actually use it.
This guide is for anyone who flashed a Raspberry Pi image, or another Linux-based image, and now sees a card that reports far less space than its label promises. It explains why the card looks small, how Raspberry Pi OS handles expansion automatically, and what to do when expansion does not happen on its own. It also explains the Windows case, where the answer is different, so you do not chase a Linux solution for a Windows problem.
A warning first: expanding a filesystem changes partition boundaries, so back up anything important on the card before you resize it. The operation is routine and usually safe, but a power loss during a resize can corrupt the filesystem. Work on a copy if the card holds irreplaceable data, and never resize a card while the device using it is running from that card unless the tool you are using is designed for online expansion.
Before you start
- Back up the card with Win32 Disk Imager Read before resizing, if the data matters. A resize is low-risk, but a backup makes it no-risk.
- Do not expand a partition into space that belongs to another partition. Check the layout first, in the Pi itself or in a partition tool, so you know what is free and what is already used.
- On Windows, do not expect to expand a Linux ext4 partition with Disk Management. Windows cannot read ext4, so it will show the partition as unknown, and that is normal, not a fault to fix in Windows.
Understanding the layout helps everything else make sense. A typical Pi image has a small FAT boot partition that Windows can see, and a larger Linux root partition that Windows cannot read. After flashing, Windows shows the boot partition’s size and hides the rest, which is why a 64 GB card can appear as a 256 MB drive. The space is not lost; it is in partitions Windows does not display, plus unallocated space the image never assigned.
Step by step
1. Check whether expansion already happened
Boot the Pi, open a terminal, and run df -h to see the size of the root filesystem. If the root partition is close to the card’s full capacity, expansion already happened and you do not need to do anything. If it is close to the original image size, for example 2 GB on a 32 GB card, then manual expansion is needed. Checking first avoids resizing a filesystem that is already correct.
2. Use raspi-config on Raspberry Pi OS
On Raspberry Pi OS, run sudo raspi-config, choose Advanced Options, then Expand Filesystem, and reboot when prompted. This is the supported method, and it handles the partition and filesystem resize together. After rebooting, run df -h again to confirm the root filesystem now fills the card. If raspi-config reports that the filesystem is already expanded, trust that result and look elsewhere for your missing space.
3. Expand manually with a partition tool if needed
For images without raspi-config, boot the Pi from a different card, or use a Linux system, and resize with a partition tool such as GParted. Select the card, resize the root partition into the free space, apply, and then check the filesystem. Do not resize the boot partition unless you have a specific reason, and do not move the start of a partition, because moving a partition start is slower and riskier than extending its end.
4. If you only use Windows, use a Linux live system
Windows Disk Management cannot expand an ext4 partition, and third-party Windows tools that claim to do so should be used cautiously and only after a backup. The reliable route is a Linux live USB, GParted, or a second Pi booted from another card. That sounds like extra work, but it is safer than a Windows tool silently mishandling a filesystem it cannot read.
5. Verify the result and test the card
After expansion, boot the Pi from the resized card and confirm with df -h that the space is available. Copy a test file, reboot, and confirm the system still boots cleanly. If the Pi fails to boot after a resize, restore your Read backup to a spare card and retry the resize, because a failed resize is easier to recover from with a backup than without one.
Frequently asked questions
Why does my 64 GB card show only a few hundred megabytes in Windows?
Windows shows only the small FAT boot partition it can read. The Linux partitions and unallocated space are hidden from File Explorer, but they are still on the card.
Does Raspberry Pi OS expand automatically?
Yes, normally on first boot it expands its root filesystem to fill the card and may reboot once. Manual expansion is only needed if that step did not happen.
Can I expand the filesystem in Windows Disk Management?
Not for a Linux ext4 partition. Windows cannot read ext4, so use raspi-config on the Pi, or GParted from a Linux system, after backing up the card.
For the full set of guides, see the Tutorials hub, and get the program from the download page. Related guides include: flash raspberry pi os win32 disk imager, raspberry pi wont boot after flashing, how to back up sd card to img — each one covers one job in the same plain style as this guide.