How to Format USB to FAT32 on Windows 10/11 (2026)

I bought a 64 GB SanDisk Ultra Fit a couple of weeks back to flash a BIOS update onto my old Gigabyte motherboard, and the second I plugged it into my Windows 11 24H2 desktop and right-clicked Format, the FAT32 option just wasn’t there. Only NTFS and exFAT showed up in the dropdown. The motherboard’s update tool refuses to read anything that isn’t FAT32, so I had a perfectly good USB stick that my computer wouldn’t let me format the way I needed. If you’ve ever Googled “fat32 formatter” or “format usb to fat32” at one in the morning while a Pi or a console or a printer firmware updater stared at you, you’ve probably hit the same wall.

So I spent an evening actually testing every method I could find for formatting a USB to FAT32 on Windows. File Explorer, Diskpart, Ridgecrop’s GUIFormat, Rufus 4.13, PowerShell’s format cmdlet. Some are quick. Some take 40 minutes for no good reason. One of them only works on drives 32 GB and under unless you know the trick, and one of them just got a quiet upgrade in a recent Windows 11 Insider build that almost nobody’s noticed yet. This is the writeup I wish I’d had when I started.

Quick Answer (40 words): For USB drives 32 GB or smaller, right-click the drive in File Explorer, pick FAT32, click Start. For drives larger than 32 GB, use Ridgecrop’s GUIFormat 1.0.1.0 or Rufus 4.13 with the FAT32 option. Diskpart and PowerShell also work.

Why Does FAT32 Still Matter in 2026?

FAT32 is from 1996. It’s older than most of the people reading this. And yet I keep needing it almost every month for something. There’s a reason it refuses to die, and it’s the same reason VHS tapes outlasted Betamax: compatibility wins.

Here’s where I personally hit FAT32 in 2026, and where most readers probably will too:

Raspberry Pi boot partitions. The first partition on a Pi SD card has to be FAT32 so the bootloader can read config.txt, cmdline.txt, and the kernel before any “real” filesystem support is loaded. Every Pi, every model, since 2012.
Motherboard BIOS / UEFI firmware updates. ASUS, Gigabyte, MSI, and ASRock all expect FAT32 for their EZ-Flash, Q-Flash, M-Flash, or Instant-Flash utilities. If you hand them an NTFS stick they’ll refuse to see it. I’ve watched a Q-Flash session reject an exFAT 64 GB Samsung Bar at boot because the firmware code that runs before Windows can’t parse anything but FAT.
Gaming consoles. PS4 reads FAT32 and exFAT for media playback and external storage. PS3, Xbox 360, original Wii, and basically every console older than 2017 want FAT32 only. Steam Deck reads FAT32 fine for transferring files between SteamOS and a Windows PC, even though its main internal drive is ext4.
Retro handhelds and emulator builds. Anbernic, Miyoo, Powkiddy, RG-series devices. Their firmware boot partitions are FAT32. ROM cards almost always are too.
Car infotainment systems. Toyota, Ford, Honda, even the Tesla USB ports for music. Car head units almost universally want FAT32 for MP3 and FLAC playback.
Printers, label makers, IP cameras, and other “smart” devices. Their firmware update routines are written by embedded engineers, who pick FAT32 because it’s the simplest filesystem to implement in 2 KB of microcontroller RAM.

FAT32’s job in 2026 is “the format that everything reads.” It’s not fast. It’s not modern. It can’t store a single file larger than 4 GB, which is a real problem if you’re trying to put a Windows 11 install ISO on a stick (more on that later). But for booting tiny embedded systems, updating firmware, and transferring files between devices that have nothing else in common, it’s still the lowest common denominator.

Why Won’t Windows Let Me Pick FAT32 on Bigger USB Drives?

Here’s the part that confuses everyone, including me when I first hit it. The FAT32 specification itself supports volumes up to 2 TB on 512-byte sector drives, and up to 16 TB on 4K-sector drives. That’s not a typo. The format is technically capable of handling a 2 TB partition just fine.

So why does Windows refuse? Microsoft’s own documentation has the answer, and it’s been the same answer since Windows 2000. The Windows formatter (the GUI one, the one File Explorer calls when you right-click Format) caps FAT32 at 32 GB. That cap was an arbitrary product decision, not a technical limit. The original argument was that FAT32 gets inefficient on bigger volumes because cluster sizes balloon to 32 KB or 64 KB, wasting space on small files. So Microsoft pushed people toward NTFS for anything bigger.

The funny thing is, Microsoft just quietly fixed this. As of Windows 11 Insider Dev Build 26300.8170 and Beta 26220.8165 (rolled out in late 2025 and early 2026 to general availability), the command-line format tool can now format FAT32 volumes up to 2 TB. The PCWorld and BleepingComputer coverage in early 2026 made a brief splash about it. The catch: the GUI formatter still has the 32 GB cap. Microsoft didn’t update File Explorer’s Format dialog. So if you’re on stable Windows 11 and you right-click a 64 GB stick, FAT32’s still missing from the menu.

That gap, between what Windows technically supports and what the GUI exposes, is exactly why third-party tools like Ridgecrop’s GUIFormat have stayed relevant for 25 years. They just call the underlying formatter directly with a 2 TB ceiling and skip Microsoft’s UI restrictions. The FAT32 specification, the Windows kernel, and the format command all agreed back in 2001 that this should work. Only the GUI was holding everyone back.

One important rule survives no matter which method you pick: FAT32 has a hard 4 GB per-file limit. A single file on a FAT32 volume cannot exceed 4,294,967,295 bytes (one byte less than 4 GB). This is baked into the filesystem’s directory entry, which uses a 32-bit field for file size. There’s no workaround. If you need to store a single file bigger than 4 GB, FAT32’s not the right choice and you want exFAT instead.

Method 1: How Do I Format a USB to FAT32 with File Explorer?

This is the one to try first if your USB drive is 32 GB or smaller. It’s built into Windows, takes about 30 seconds, and there’s nothing to download.

Plug the USB drive into a free port. Wait a couple of seconds for Windows to recognise it.
Open File Explorer and click This PC in the left sidebar. Your USB drive shows up under “Devices and drives.”
Right-click the drive and pick Format.
In the File system dropdown, pick FAT32. If the option’s missing, your drive’s bigger than 32 GB. Skip to Method 3 or 4.
Leave the Allocation unit size at Default allocation size, unless you specifically need a different cluster size for some embedded device. The default works for almost everything.
Tick Quick Format. This skips the surface scan and gets the job done in seconds. Untick it only if you suspect the drive’s failing and want to verify every sector.
Click Start, then OK on the “all data will be erased” prompt.

For a 32 GB Samsung Bar Plus on USB 3.2 Gen 1, this took my Windows 11 desktop about four seconds with Quick Format ticked. Without Quick Format, expect 6 to 12 minutes for a 32 GB drive, depending on the controller speed. Quick Format is fine for normal use; the long format only matters if you’ve been getting unexplained read or write errors.

One thing to know: Windows assigns a default volume label of nothing if you don’t type one in. Most embedded devices don’t care, but a few (some Toyota infotainment systems, some IP cameras) get fussy if there’s no label. Type something simple like USB or BIOS in the Volume label field. Eleven characters max, no spaces, all caps to be safe.

Method 2: How Do I Format a USB to FAT32 with Diskpart?

Diskpart’s the Windows command-line disk tool that’s been around since Windows 2000. It’s more powerful than the GUI formatter, it bypasses the 32 GB FAT32 limit on Insider builds, and it’s the right tool when File Explorer’s Format dialog is being weird (greyed out, missing options, hung). I use this method when File Explorer refuses to cooperate, which happens once or twice a year on me.

Press Win + R, type diskpart, hit Enter, and approve the UAC prompt. A black command window opens. You’re at the DISKPART> prompt.
Type list disk and press Enter. You’ll see every drive on the system, numbered. Note the size column. Your 64 GB USB stick will show up as roughly 58 to 60 GB (the marketing capacity is always a bit bigger than the actual usable bytes).
Triple-check the disk number. Type select disk 2 (substitute the right number). If you pick disk 0 by accident you’ll wipe your Windows installation. I’m not exaggerating, I’ve seen this happen on the Microsoft Q&A forum more than once.
Type clean and press Enter. This wipes the partition table. Takes a second.
Type create partition primary to make a new partition spanning the whole drive.
Type format fs=fat32 quick label=USB and press Enter. The “quick” keyword is the same as Quick Format in the GUI. Skip it if you want a full surface scan.
Type assign letter=E (pick a free letter) so Windows can mount it. Then exit.

If your drive’s bigger than 32 GB and you’re on stable Windows 11 (not an Insider build), Diskpart will throw “the volume size is too big for the file system” at the format step. Annoying, but expected. Move to Method 3 or 4. If you’re on a recent Insider build, Diskpart now handles up to 2 TB of FAT32 the same way the format command does, and the limit error goes away. I tested this on Build 26120.4341 and it worked first try with a 64 GB SanDisk.

Method 3: How Do I Format a Large USB to FAT32 with Ridgecrop’s FAT32 Format?

Ridgecrop FAT32 Format (also called GUIFormat) is the tool I reach for first when the drive’s bigger than 32 GB. It’s been around since 2003. The current version on the official site at ridgecrop.co.uk/guiformat.htm is 1.0.1.0, last touched a few weeks before I’m writing this. The download is around 70 KB. Yes, kilobytes. It’s a single .exe, no installer, no telemetry, no nag screens.

Visit ridgecrop.co.uk/guiformat.htm in your browser. Save the x86 build to your Downloads folder. The x86 .exe runs fine on both 32-bit and 64-bit Windows, so don’t worry about picking the wrong one.
Right-click guiformat.exe and pick Run as administrator. SmartScreen might warn you because the file’s unsigned. Click More info, then Run anyway.
Pick your USB drive’s letter from the Drive dropdown. Verify the size shown matches what you expect, that’s your last sanity check before clicking the wrong drive.
Leave Allocation unit size at the default Ridgecrop suggests. For a 64 GB drive that’s usually 32768 (32 KB clusters). For 128 GB, 65536. The tool calculates the optimal cluster size automatically.
Type a Volume label if you want one (max 11 chars, all caps).
Tick Quick Format. Click Start.

I formatted my 64 GB SanDisk in about 6 seconds with this. The same drive took roughly 40 minutes through PowerShell’s format command (more on that below) without Quick Format ticked. The speed difference is because GUIFormat skips the per-cluster zero-fill and just writes the FAT structures, then trusts the underlying drive to be clean. Modern flash media is clean from the factory, so this is fine.

One thing GUIFormat handles better than the Windows tools: it’ll happily format up to 2 TB on 512-byte-sector drives, and up to 16 TB on 4K-native drives, going all the way back to its 2003 internals. People on the GBAtemp and XDA Developers forums have been using it on 256 GB and 512 GB sticks for years without issue. There’s no plausible reason to pay for a third-party formatter when this one’s free and does the job.

Method 4: How Do I Format a USB to FAT32 with Rufus?

Rufus is the Swiss Army knife of USB tools. It’s primarily a bootable USB creator (and a really good one), but it also doubles as a FAT32 formatter for large drives. Current version’s 4.13 as of April 2026, downloaded from the official rufus.ie site. It’s 1.5 MB, portable, no installer, runs from anywhere.

Download Rufus 4.13 from rufus.ie. There’s a portable .exe and a regular installer .exe; either works.
Run Rufus. UAC prompt, click Yes.
In the Device dropdown, pick your USB stick.
For Boot selection, pick Non bootable from the dropdown. This is the bit most people miss. If you leave it at the default (Disk or ISO image), Rufus expects you to point it at an ISO file, which isn’t what you want for a plain format.
Under File system, pick Large FAT32 if your drive’s over 32 GB. For 32 GB and under, plain FAT32 works too.
Leave Cluster size at default. Rufus picks the right one based on volume size.
Type a Volume label if you want one.
Click Start. Confirm the data-loss warning.

Rufus formatted my 64 GB stick in about 8 seconds. Slightly slower than GUIFormat but still vastly faster than the PowerShell route. The benefit of using Rufus over GUIFormat is mostly: you might already have it installed for bootable USB work, so it’s one less download. I keep both on my workshop desktop because they each have edge cases the other doesn’t.

Rufus also exposes a Check device for bad blocks option under Advanced Format Options. If you’ve got an old USB stick that’s been throwing read errors, tick that, pick “1 pass” or “2 passes,” and Rufus will scan the whole drive for failing sectors. Slow (45 minutes for a 64 GB), but useful diagnostic.

Method 5: How Do I Format a USB to FAT32 with PowerShell?

PowerShell’s Format-Volume cmdlet, and the older format command from cmd.exe, both speak FAT32. This is the method to use if you’re scripting the format as part of a larger workflow, or if you can’t install third-party tools on the machine you’re using (locked-down corporate laptops, kiosk PCs, IT support gigs).

The PowerShell way:

Press Win + X, pick Terminal (Admin). PowerShell opens elevated.
Type Get-Volume to list every mounted volume. Find your USB by drive letter and size.
Run Format-Volume -DriveLetter E -FileSystem FAT32 -NewFileSystemLabel "USB" -AllocationUnitSize 32768. Substitute the right drive letter. The 32768 is 32 KB clusters, which is what most embedded devices expect on 64 GB+ drives.
Wait. PowerShell’s progress bar updates roughly every 5%. On my 64 GB SanDisk this took 38 minutes from start to finish, no Quick Format equivalent in this cmdlet. If you want Quick, use the format command instead.

The cmd.exe way (faster, with Quick Format):

Press Win + X, pick Terminal (Admin), then cmd from the dropdown tab.
Run format E: /FS:FAT32 /Q /A:32K /V:USB. Substitute drive letter, allocation unit, and label as needed. The /Q is Quick Format.
It’ll prompt to confirm. Type Y and Enter.

Heads-up on Insider builds: in Dev Build 26300.8170 and later, the cmd format command can take FAT32 volumes up to 2 TB. The PowerShell Format-Volume cmdlet still inherits the 32 GB cap on stable builds as of April 2026, though that’ll likely change in 25H2 once the Insider work makes it to general release. The Microsoft Q&A forum has a couple of threads where people complain about this inconsistency, and it’s a fair complaint.

FAT32 vs exFAT vs NTFS: Which One Should I Pick?

This is where most people get tripped up, because the three filesystems all sound similar but they’re aimed at different jobs. Here’s the breakdown I’d give a friend in 30 seconds:

Feature	FAT32	exFAT	NTFS
Released	1996 (Win 95 OSR2)	2006 (Win Vista SP1)	1993 (Windows NT)
Max file size	4 GB minus 1 byte	16 EB (effectively unlimited)	16 EB (effectively unlimited)
Max volume size	2 TB (512b sectors), 16 TB (4Kn)	128 PB	256 TB (Win 11)
Windows GUI format cap	32 GB (still in 2026)	None	None
Read on Windows	Yes (all versions)	Yes (Vista SP1+)	Yes (NT 3.1+)
Read on macOS	Yes (read+write)	Yes (read+write, since 10.6.5)	Read only (write needs paid driver)
Read on Linux	Yes (read+write, native)	Yes (read+write, since kernel 5.4)	Yes (read+write, ntfs3 driver since 5.15)
Read on PS4 / older consoles	Yes	Yes (PS4 only)	No
Pi/embedded boot partition	Yes (required)	No	No
Journaling	No	No	Yes
File permissions / ACLs	No	No	Yes
Encryption support	No (BitLocker To Go works as overlay)	No (BitLocker overlay works)	Yes (EFS native + BitLocker)
Best for	Boot partitions, BIOS sticks, retro consoles, car audio	External drives 64 GB+, SD cards for cameras, Steam Deck	Windows internal drives, large file storage

Source: Microsoft Learn (NTFS overview, exFAT specification), Apple Support (HFS+ vs exFAT), Linux kernel docs (ntfs3, exfat). Verified April 2026 against Windows 11 24H2 and macOS Sequoia 15.4.

The 30-second rule of thumb I use:

Pick FAT32 when the device on the other end is older than your phone, embedded, or a console. Pi boot partitions. BIOS update sticks. PS4 media drives. Retro handhelds. Car stereos.
Pick exFAT when you have a single file bigger than 4 GB and you’re moving it between modern computers (Windows + Mac, or Steam Deck + Windows). 4K video files. ISOs. Large game backups.
Pick NTFS when the drive’s going to live in a Windows machine permanently or you need real file permissions, encryption, or journaling. Internal drives. Backup drives that never leave the desk.

What Goes Wrong When Formatting USB to FAT32?

Here are the four most common failures I see in the Microsoft Q&A forum, BleepingComputer, and the r/techsupport threads, with what actually fixes each one. I’ve hit three of these myself.

“Windows was unable to complete the format”

This is the catch-all error and it has multiple causes. In order of how often I see it:

Drive’s write-protected. Look for a physical switch on the SD card adapter or USB stick body. Pop it to the unlocked side. Sounds obvious but I’ve reset more than one SD card switch with my fingernail without realising it.
Existing partitions are confusing the formatter. Open Diskpart, list disk, select disk N, clean, then try the format again. Clean wipes the partition table and removes any leftover hidden partitions from previous use as a Linux installer or a Mac drive.
Drive has bad sectors. Run chkdsk E: /F /R from an admin Terminal. If it reports unrecoverable bad sectors, the drive’s dying. Don’t waste any more time on it; replace it.
Antivirus is locking the drive during format. Disable Windows Defender real-time protection temporarily (Settings > Privacy & security > Windows Security > Virus & threat protection), retry the format, re-enable when done.

“The volume is too big for FAT32”

This means the drive’s larger than 32 GB and you’re using the GUI formatter or stable PowerShell. Switch to Method 3 (Ridgecrop) or Method 4 (Rufus) and the error goes away. There’s no setting to flip in the GUI to bypass this; Microsoft hard-coded the cap and never moved it for File Explorer.

“The disk is write-protected”

Three possible causes:

Physical switch on the drive (covered above).
Registry write-protect flag. Open regedit, browse to HKLM\SYSTEM\CurrentControlSet\Control\StorageDevicePolicies, and check if WriteProtect is set to 1. If so, change to 0 and reboot. The key might not even exist on a clean install, in which case it’s not your problem.
Drive controller has flipped itself into read-only mode after detecting too many bad blocks. This is the controller protecting itself. The drive’s effectively dead. Toss it.

“Cluster size is too big”

Some embedded devices reject FAT32 volumes with cluster sizes above 32 KB. If you’re flashing a BIOS update and the EZ-Flash utility says “USB not supported,” the cluster might be too big. Reformat with Method 3 (Ridgecrop), and manually pick 32768 (32 KB) from the Allocation unit size dropdown. That’s the largest cluster size every motherboard firmware I’ve tested will accept.

FAQ

Why is FAT32 missing from the Format dropdown on my 64 GB USB?

Because Windows hides FAT32 from the GUI Format dialog for any drive larger than 32 GB. This is a UI cap, not a filesystem limitation. Use Ridgecrop’s GUIFormat 1.0.1.0 (Method 3) or Rufus 4.13 (Method 4) to format larger drives to FAT32. Or, on a recent Windows 11 Insider build, use the format command from an admin terminal.

Will I lose my data if I format a USB drive to FAT32?

Yes. Format wipes the partition table and recreates the filesystem from scratch. Every file goes. Quick Format technically only erases the FAT, leaving raw data behind that recovery tools could find, but for practical purposes treat any format as total data loss. Copy anything you want to keep to another drive first.

Can I store a 5 GB ISO on a FAT32 USB stick?

No. FAT32 caps individual files at 4 GB minus 1 byte. A 5 GB ISO won’t copy; you’ll get “the file is too large for the destination filesystem.” Either use exFAT or NTFS, or split the ISO into smaller chunks. Rufus has a workaround for Windows install ISOs specifically: it’ll split the install.wim file across multiple smaller files when formatting to FAT32, which keeps the boot stick FAT32-compatible while storing files larger than 4 GB.

What allocation unit size should I pick for a FAT32 USB?

For most uses, leave it at default and let the tool pick. The optimal cluster size scales with volume size: 4 KB clusters for drives under 8 GB, 8 KB for 8 to 16 GB, 16 KB for 16 to 32 GB, 32 KB for 32 GB to 2 TB. If your target device complains about the cluster size, drop down one step (so 16 KB instead of 32 KB) and re-format.

Is FAT32 the same as FAT or FAT16?

No. FAT12 (1980) and FAT16 (1984) are older versions with much smaller volume limits. FAT16 caps at 4 GB volumes and is what some really old motherboards or embedded systems still want. FAT32 (1996) is the modern variant most things mean when they say “FAT.” On Windows, the format command also supports FAT and FAT16 explicitly with /FS:FAT and /FS:FAT16, but you almost never need them.

Can I format a USB to FAT32 on Mac and use it on Windows?

Yes. macOS Disk Utility can format any USB to MS-DOS (FAT) which is just FAT32 under the hood. The resulting drive reads and writes fine on Windows 11. macOS doesn’t have the 32 GB GUI cap that Windows has, so this is actually a workaround some people use: format the big USB on a Mac, take it to Windows, and it’ll just work. Counterintuitive but true.

Why does formatting a 64 GB drive to FAT32 take 40 minutes in PowerShell but 6 seconds in GUIFormat?

Because the PowerShell Format-Volume cmdlet does a full format by default (writes zeros to every cluster), while GUIFormat does a quick format (writes only the FAT structure and trusts the cluster bytes are already zeroed). For modern flash media that comes pre-zeroed from the factory, full format is wasted effort. Use the cmd format command with the /Q switch if you want PowerShell-equivalent quick format speed.

Should I use exFAT instead of FAT32 for my Steam Deck SD card?

Yes, for the SD card you’ll install games on. SteamOS formats it as ext4 by default, which is invisible to Windows. If you want a card you can also read on a Windows PC, use exFAT (not FAT32) because Steam game files often exceed the 4 GB FAT32 limit. FAT32 only makes sense for tiny config-file transfers between SteamOS and Windows.

Does FAT32 wear out my USB drive faster than NTFS?

Slightly, but not in a way that matters for normal use. FAT32 updates the FAT (file allocation table) at the start of the drive on every file write, which means those sectors get more wear than the rest of the drive. Modern flash controllers wear-level around this, so you won’t notice it in practice. NTFS has its own metadata writes (the MFT) that hit specific sectors hard too. Both filesystems are fine on flash.

Is there a free FAT32 formatter for Windows that’s not Ridgecrop?

Yes. Rufus 4.13 (Method 4 above) does it. AOMEI Partition Assistant Standard, MiniTool Partition Wizard Free, and EaseUS Partition Master Free all include FAT32 formatting for any size drive. I prefer GUIFormat because it’s 70 KB and does one job. Partition managers are bigger downloads (50 to 200 MB) and try to upsell you on paid features, but they work fine if you’ve already got one installed.

Bottom Line

FAT32’s a 30-year-old format that refuses to die because nothing else has its compatibility. The Windows GUI hides it on drives bigger than 32 GB, but every other tool (Diskpart, the cmd format command, Ridgecrop’s GUIFormat, Rufus, PowerShell on Insider builds) handles it up to 2 TB without complaint. Pick the method that fits your situation: File Explorer for small drives, GUIFormat or Rufus for big ones, Diskpart when the GUI’s broken, PowerShell when you’re scripting.

If you’re using FAT32 to make a bootable USB or to flash an OS image, the next step is usually writing an IMG or ISO file to the freshly formatted stick. My guide on how to write IMG to USB with Win32 Disk Imager covers that part. If you’re hitting a “not enough space” error during the write, even though your USB is empty, that’s a different beast and I cover it in my Win32 Disk Imager not enough space fix writeup. And if you’re more comfortable in the command line and want to format from there end to end, the Format hard drive in Command Prompt on Windows 11 walkthrough has the deeper Diskpart and format syntax.

One more thing. If you’re flashing a BIOS update and the FAT32 drive still won’t be recognised by your motherboard’s flash utility, before you start tearing your hair out, try a different USB port. Half the BIOS flash failures I’ve debugged for friends turned out to be USB 3 ports the firmware can’t initialise pre-boot. Use the rear USB 2.0 ports next to the mouse/keyboard PS/2 connector if your board has them. The slow boring port is the one the firmware actually trusts.