The essentials

Quick reference

One focused task per row. Jump to the related section for complete, working examples.

UseSyntaxExamples
List volumeslist volumeView examples
Select a volumeselect volume 7View examples
Inspect the selected volumedetail volumeView examples
List supported filesystemsfilesystemsView examples
Full-format NTFSformat fs=ntfs label="Data"View examples
Quick-format NTFSformat fs=ntfs label="Data" quickView examples
Quick-format exFATformat fs=exfat label="Exchange" quickView examples
Quick-format FAT32format fs=fat32 label="EFI" quickView examples
Quick-format ReFSformat fs=refs label="Data" quickView examples
Use 64 KB NTFS clustersformat fs=ntfs unit=64k label="Database" quickView examples
Use recommended settingsformat recommended label="Data" quickView examples
Enable default NTFS compressionformat fs=ntfs label="Archive" compress quickView examples
Force dismount for formatformat fs=ntfs label="Data" quick overrideView examples
Assign a letterassign letter=RView examples
Verify the resultdetail volumeView examples
Scan the new NTFS volumechkdsk R: /scanView examples

DiskPart format creates a new filesystem on the selected volume and destroys access to its previous filesystem data. Select and verify the volume by disk, partition, size, label, and mount points before formatting. Use filesystems to discover what the current host supports, prefer default allocation units unless a workload has tested requirements, and remember that formatting is not media sanitization.

Step by step

Detailed examples

01

Resolve the volume back to its physical disk

A drive letter or old label is not enough identity. List volumes, select the candidate, inspect detail volume, and correlate its disk and partition with detail disk and list partition. Formatting the wrong volume is immediately destructive. Stop services and unmount application workloads before proceeding.

Volume format preflight
list volume
select volume 7
detail volume
attributes volume
rem Stop unless disk, partition, size, label, paths, and owner all match approval.
Back to quick reference ↑
02

Ask the host what the selected volume supports

The filesystems command reports the current filesystem and format choices for the focused volume. Availability varies with Windows edition, volume role, size, sector format, and media. Do not assume a filesystem is supported merely because DiskPart recognizes its name.

Inspect format choices
select volume 7
detail volume
filesystems
help format
Back to quick reference ↑
03

Match the filesystem to the workload

NTFS is the general Windows choice and supports permissions, compression, encryption, and many Windows roles. FAT32 is required for EFI system partitions and some devices but has a 4 GB individual-file limit. exFAT targets interoperable removable storage without NTFS security semantics. ReFS availability and supported roles vary; verify the specific Windows edition and workload documentation.

Prepare an approved NTFS data volume
select volume 7
detail volume
filesystems
rem DANGER: formatting destroys the selected volume's prior filesystem.
format fs=ntfs label="Data" quick
Back to quick reference ↑
04

Choose quick or full format for the right reason

Quick format recreates filesystem structures but skips a full surface scan. A non-quick format takes longer and checks the volume, but neither mode is a guaranteed secure erase process. Use storage health diagnostics for suspected hardware failure and approved sanitization methods for disposal. Override forces dismount and can abruptly invalidate open file handles.

Full-format a new approved NTFS volume
select volume 7
detail volume
rem This may take a long time and destroys existing filesystem data.
format fs=ntfs label="Archive"
Back to quick reference ↑
05

Keep defaults unless measurements justify tuning

Allocation unit size affects space efficiency, compression support, and application behavior. Default settings are appropriate for general use. A 64 KB unit is common for some database workloads only when vendor guidance, backup tooling, and performance tests agree. NTFS compression is unavailable above certain allocation sizes and should not be combined blindly with database or already-compressed data.

Review a workload-specific format plan
select volume 7
detail volume
filesystems
rem Validate application and backup support before using 64 KB clusters.
format fs=ntfs unit=64k label="Database" quick
Back to quick reference ↑
06

Verify filesystem, mount, and application behavior

After format, inspect detail volume and list volume, assign only an approved free letter or mount point, and run the filesystem's validation tools. Then test permissions, expected capacity, backup discovery, and application access. A successful format does not prove the selected allocation or filesystem is suitable for the workload.

Post-format validation
detail volume
assign letter=R
list volume
exit
chkdsk R: /scan
Back to quick reference ↑

Sources and further reading

References

Authoritative documentation used to verify and expand this cheat sheet.

  1. Microsoftdiskpartlearn.microsoft.com
  2. Microsoftfilesystemslearn.microsoft.com
  3. Microsoftformatlearn.microsoft.com
  4. MicrosoftFile system functionality comparisonlearn.microsoft.com

Help us improve

Found a typo or missing example?

Tell us what would make this cheat sheet clearer, more complete, or more useful.

Share feedback