Format an SD Card to FAT32 for CCTV and Security Cameras
This site is an independent, unofficial resource and is not affiliated with any camera maker or RidgeCrop Consultants. FAT32 GUI Formatter (guiformat) version 1.01 is a Windows-only portable program. It formats an existing partition to FAT32. It does not create or resize partitions, and it does not install anything.
A CCTV or home security camera shares the dashcam’s hardest storage job: continuous or motion-triggered recording that overwrites old footage, day after day, often outdoors and often without anyone watching the card’s health. That loop-recording workload is why this post and the dashcam post point to the same endurance buying guide, and why the overlap is stated explicitly rather than hidden. An endurance-rated microSD card is built for repeated overwrites, while an ordinary card can fail early under the same workload, with corrupted clips, a card error, or gaps in coverage that are only discovered after an incident. Format is important, but it cannot turn an ordinary worn card into an endurance card.
Does YOUR camera actually need FAT32?
Check your camera manual for your exact model, because CCTV cameras do not share one file-system rule. EZVIZ support guidance checked here gives a clear split by capacity: the file format should be FAT32 for capacities below 64GB, and exFAT for capacities of 64GB and above, with a Class 10 or UHS-1 rating, and with the card initialised in the EZVIZ app before use. That split is a useful example of why capacity alone does not decide format: a 32GB card and a 128GB card for the same brand can correctly use different file systems.
Other cameras are stricter or more permissive. Some models accept FAT32 or exFAT at a given capacity, some are FAT32-only at the capacities they support, and some require in-camera initialisation regardless of how the card was formatted on a PC. The dashcam manual pattern in this cluster shows the same variation, with some models FAT32-only and others allowing exFAT or FAT32. Do not copy a dashcam rule to a CCTV camera, or a CCTV rule to a dashcam, even though their endurance needs overlap. The card type overlaps; the file-system rule does not automatically overlap.
| Source checked here | Rule | What to do |
|---|---|---|
| EZVIZ support, microSD FAQ | FAT32 below 64GB, exFAT at 64GB and above; Class 10 or UHS-1; initialise in the app | Follow the capacity split for EZVIZ models it covers, and initialise in the app |
| Your camera model | Check your device manual | Do not assume the EZVIZ split applies to another brand or model |
The FAT32 single-file limit still applies where FAT32 is used: a single file cannot exceed 4GB on FAT32. Security cameras usually record in segments, so the limit rarely blocks a clip, but check your device manual if your camera records very long single files or if you export long clips to a FAT32 card for transfer.
Why endurance matters for CCTV loop recording
Loop recording means the card is always writing. Continuous recording writes constantly; motion recording writes in bursts, but over months those bursts add up to the same wear pattern. An endurance-rated card is designed for that pattern, with higher tolerance for repeated writes. This post does not invent a lifespan in months or a write-cycle count for your camera, because those numbers depend on capacity, bitrate, resolution, temperature, and recording mode. Check your device manual and the endurance buying guide linked below for card types by name.
Before you format: back up footage you need
Formatting erases everything on the selected card or partition. Double-check the drive letter before you press Start. For a security camera, that warning includes event clips that may be evidence or simply irreplaceable. Copy important footage to another drive before formatting, using the camera app or a card reader, and confirm the copies play before you format. Loop recording will eventually overwrite unprotected footage on its own, so do not leave important clips only on the camera card while deciding whether to format.
Format in the camera or with guiformat
Formatting or initialising in the camera or its app is the preferred first choice when your camera offers it, because the camera then creates exactly the layout it expects and marks the card as initialised or normal in its status screen. EZVIZ guidance, for example, tells users to initialise the card in the app and to format again through the app if the status shows abnormal or uninitialised, after backing up important files. Use that route for routine maintenance.
Use guiformat on Windows when the camera cannot format the card, when a FAT32 camera needs a larger card forced to FAT32, or when a deep PC format is needed after in-camera formatting fails. Windows graphical tools will not offer FAT32 for a volume over 32GB. The Windows command line can also do a quick format, for example format E: /FS:FAT32 /Q with your verified drive letter, and newer Windows 11 builds raise the command-line FAT32 limit to 2TB. Disk Management’s graphical interface still stops at 32GB. Guiformat does not create or resize partitions, and it does not make an exFAT-only camera accept FAT32, or vice versa. If your camera’s rule is exFAT at 64GB and above, do not force FAT32 on a large card for that camera just because guiformat can.
- Copy important footage off the card and confirm the copies play.
- Remove the card safely, confirm its drive letter and capacity in File Explorer on Windows, and close any program using it.
- Open guiformat only if your camera’s rule calls for FAT32 for this card size. Select the card, confirm the capacity matches, and set the allocation unit size from your camera manual, or check your device manual if it names no value.
- Select Quick Format for a healthy card, press Start, confirm the erase warning, wait for completion, and eject safely.
- Insert the card in the camera, initialise or format it in the camera or app if it asks, and confirm the status shows normal and recording starts before relying on it for coverage.
Frequently asked questions
Does every CCTV camera need FAT32? No. EZVIZ guidance checked here uses FAT32 below 64GB and exFAT at 64GB and above, while other models have different rules. Check your device manual for your exact model.
Should I format in the camera or on a PC? In the camera or app first, for routine use, because it creates the layout and status the camera expects. Use guiformat on a PC when a FAT32 rule needs a larger card forced to FAT32 or the camera cannot format the card itself.
Why does endurance matter if I only record on motion? Motion recording still writes repeatedly over months, and the card still overwrites old events. An endurance-rated card is built for that repeated-write pattern, while an ordinary card can wear out early.
Why does my camera keep asking to format the card? The usual causes are a worn card, a file system that does not match the camera’s rule for that capacity, a card over the model’s limit, a card never initialised in the app, or removal during writing. Back up footage, try a clean format, and replace a worn card with an endurance-rated type if the problem returns.
Related device guides
- Best microSD card for dashcam endurance — endurance cards overlap explicitly with CCTV use: loop recording wears dashcam and CCTV cards in the same way, so the same endurance card types apply.
- Format an SD card to FAT32 — the general Windows walkthrough.
- Format an SD card to FAT32 for a dashcam
- Format an SD card to FAT32 for Raspberry Pi
- Download FAT32 GUI Formatter