CONVERT Command Guide - Convert FAT/FAT32 Volumes to NTFS in Windows

The convert command is a Windows Command Prompt utility that converts FAT or FAT32 volumes to NTFS file system without data loss. Use convert volume /fs:ntfs to upgrade file systems while preserving all existing files, directories, and data. The conversion is one-way and irreversible—NTFS volumes cannot be converted back to FAT32 using convert.

Whether you're upgrading legacy systems to support modern security features, enabling file compression and encryption, or preparing drives for files larger than 4GB, mastering convert enables seamless file system upgrades. IT professionals rely on this command for standardizing enterprise storage, migrating workstations to NTFS, and enabling advanced NTFS features without reformatting.

This comprehensive guide covers convert syntax, prerequisites, practical examples for different scenarios, conversion process details, troubleshooting tips, alternative methods, related commands, and frequently asked questions. By the end, you'll confidently convert file systems from the command line for system administration, storage upgrades, and infrastructure modernization.

What Is the Convert Command?

The convert command has been part of Windows since Windows NT 4.0, providing a safe, in-place mechanism for upgrading FAT and FAT32 volumes to NTFS. Unlike reformatting, convert preserves all existing data, making it the preferred method for file system upgrades on drives with existing content.

NTFS (New Technology File System) offers significant advantages over FAT32:

Large file support – Files larger than 4GB (FAT32's limit)
Advanced permissions – File and folder-level security (ACLs)
Encryption – EFS (Encrypting File System) support
Compression – Built-in NTFS compression
Reliability – Journaling for crash recovery and data integrity
Quotas – Disk space management per user
Large volumes – Support for volumes over 2TB efficiently

The command works in Command Prompt (CMD) with administrator privileges and is available in Windows 11, Windows 10, Windows 8, Windows 7, Windows Vista, Windows XP, and all Windows Server editions. Convert requires exclusive access to the volume—if the target is the system drive, conversion happens at next boot before Windows loads.

System administrators use convert during Windows migrations, storage standardization projects, and when deploying applications that require NTFS features. Common scenarios include upgrading workstation operating system drives, converting data volumes for large file storage, and enabling security features on file servers.

Convert Command Syntax

The basic syntax for the convert command is:

convert volume /fs:ntfs [/v] [/cvtarea:filename] [/nosecurity] [/x]

Parameters and Switches

Parameter	Description
`volume`	Drive letter (followed by colon), mount point, or volume name to convert
`/fs:ntfs`	Specifies conversion to NTFS file system (required)
`/v`	Verbose mode—displays detailed progress and file names during conversion
`/cvtarea:filename`	Specifies contiguous placeholder file in root directory for NTFS system files
`/nosecurity`	Removes security attributes—all files accessible to everyone after conversion
`/x`	Force dismount volume if necessary (closes open file handles)

Critical note: The volume parameter is required and must specify which drive to convert. Always verify the correct drive letter before executing—conversion is irreversible.

Important Conversion Requirements

Before running convert, ensure these prerequisites are met:

Administrator privileges – Must run Command Prompt as Administrator
Sufficient free space – At least 15% free space for conversion process
Backup recommended – While convert preserves data, backups are essential insurance
System drive conversion – Requires restart (conversion happens before Windows boots)
Non-system drive conversion – Can happen immediately if volume is not in use

Understanding FAT to NTFS Conversion

Why Convert to NTFS?

Organizations and users convert to NTFS for several critical capabilities:

Large file support – FAT32 has a 4GB maximum file size. NTFS supports files up to 16EB (exabytes) theoretically, 256TB practically on modern Windows.
Security – NTFS provides file and folder permissions (ACLs), enabling granular access control. FAT32 has no built-in security features.
Reliability – NTFS uses journaling to track changes, allowing recovery after crashes or power failures. FAT32 is more susceptible to corruption.
Encryption – EFS (Encrypting File System) requires NTFS. FAT32 cannot encrypt individual files.
Compression – NTFS built-in compression saves disk space transparently. FAT32 has no compression capabilities.
Quotas – Track and limit disk usage per user on NTFS. FAT32 has no quota support.

What Happens During Conversion

The conversion process involves several stages:

Pre-conversion analysis – Windows checks free space, file system integrity, and calculates requirements
Volume lock – Exclusive access acquired (system drive: scheduled for next boot)
File system metadata creation – NTFS structures created (MFT, system files, journal)
Data migration – Existing files moved to NTFS structures without modification
Directory structure conversion – FAT directory tables converted to NTFS B-tree structure
Security application – Default NTFS permissions applied (unless /nosecurity specified)
Cleanup – FAT structures removed, space reclaimed

Time estimate: Conversion typically takes 5-30 minutes depending on volume size, file count, and disk speed. System drive conversions require one additional reboot.

Limitations and Considerations

One-way conversion: Convert only works FAT → NTFS, not NTFS → FAT. To reverse, you must back up data, reformat as FAT32, and restore files.

Free space requirement: Convert needs approximately 15% free space for temporary structures and NTFS metadata. Volumes over 85% full may fail conversion.

Fragmentation: Converted volumes may be more fragmented than native NTFS volumes. Consider defragmenting after conversion.

Cluster size preservation: Convert maintains the cluster size from the original FAT volume. Native NTFS installations may use different (more optimal) cluster sizes.

Boot sector changes: System drive conversions modify boot sectors. Ensure boot configuration is correct before converting system volumes.

Converting Drives to NTFS

Convert Non-System Drive (Immediate)

To convert a data drive to NTFS immediately:

convert D: /fs:ntfs

Output:

The type of the file system is FAT32.
Enter current volume label for drive D: DATA

Convert will take place automatically the next time the system restarts.
Converting file system
Conversion complete

If the volume is not in use, conversion happens immediately. Close all open files on the target drive before running convert.

Enterprise use case: Convert external drives, USB drives, and data volumes to NTFS for large file support and security features.

Convert System Drive (Requires Restart)

To convert the Windows system drive (typically C:):

convert C: /fs:ntfs

Output:

The type of the file system is FAT32.
Enter current volume label for drive C: WINDOWS

WARNING: All data on drive C: will be converted.
Convert will take place automatically the next time the system restarts.
Do you want to force a dismount on this volume? (Y/N) Y
Conversion complete

After confirming, restart the computer. During boot, before Windows loads, conversion runs. This ensures exclusive access to the system volume. The process is automatic and may take 10-30 minutes depending on drive size.

Critical: Do not interrupt power or force restart during system drive conversion. Interruption can leave the volume in an inconsistent state requiring recovery.

Convert with Verbose Output

To see detailed progress during conversion:

convert E: /fs:ntfs /v

Verbose mode (/v) displays:

File names as they're converted
Directory structures being migrated
Detailed progress percentages
Metadata creation steps

Useful for monitoring large conversions and diagnosing issues if conversion fails.

Convert and Remove Security

To convert without applying NTFS security (all files accessible to everyone):

convert F: /fs:ntfs /nosecurity

The /nosecurity switch prevents NTFS ACLs from being applied. All files remain accessible to all users. Rarely used except for specific legacy compatibility scenarios or publicly accessible data drives.

Security warning: Only use /nosecurity when you explicitly want no file-level security. After conversion, you can apply security manually with icacls or Windows Explorer.

Force Dismount and Convert

If files are open on the target volume:

convert G: /fs:ntfs /x

The /x switch forces the volume to dismount, closing all open file handles. Use with caution—applications with open files may lose unsaved data. Safer approach: close applications manually, then convert without /x.

Convert with Custom NTFS System File Placeholder

For advanced scenarios, specify where NTFS creates system files:

convert H: /fs:ntfs /cvtarea:ntfssys.dat

The /cvtarea switch specifies a contiguous placeholder file in the root directory. Convert uses this space for NTFS metadata. Rarely needed—let convert choose automatically unless you have specific fragmentation concerns.

Pre-Conversion Checklist

Verify Drive Letter and Volume Label

Before converting, confirm the correct drive:

vol D:

Output:

Volume in drive D is DATA
Volume Serial Number is 1234-5678

Double-check the volume label and drive letter match your intended target. Conversion is irreversible.

Check Free Space

Ensure at least 15% free space on the volume:

dir D:

Look at the last line showing free space. If less than 15% is available, delete unnecessary files or move data temporarily to create space.

Check File System Type

Verify current file system:

fsutil fsinfo volumeinfo D:

Look for "File System Name : FAT32" to confirm the volume is FAT or FAT32. NTFS volumes don't need conversion.

Backup Critical Data

While convert is designed to preserve data, always back up before file system changes:

robocopy D:\ImportantData E:\Backup /mir /r:3 /w:10

This creates a mirror backup of critical directories. Insurance against unexpected issues during conversion.

Close Open Files and Applications

Prevent conversion failures by closing applications accessing the target drive:

Save and close all documents on the target drive
Exit applications that may have open files (Office, databases, IDEs)
Stop services accessing the drive
Check Task Manager for processes with open handles

Disable Scheduled Tasks

Pause scheduled tasks that might access the drive during conversion:

schtasks /query /fo LIST | findstr "Task Name"

Temporarily disable tasks accessing the target volume to prevent interference.

Common Use Cases

Upgrade System Drive to Enable BitLocker

Convert the system drive to NTFS as a prerequisite for BitLocker encryption:

convert C: /fs:ntfs

BitLocker requires NTFS. After conversion and restart, enable BitLocker through Control Panel or Group Policy.

Convert USB Drive for Large File Storage

Upgrade USB drives to store files larger than 4GB (videos, ISOs, databases):

convert E: /fs:ntfs

Enables storage of large video files, disk images, and virtual machines on portable drives. Note: NTFS may have reduced compatibility with non-Windows devices (Linux, macOS, media players).

Standardize File Server Volumes

Convert legacy FAT32 data volumes to NTFS for consistent security:

convert D: /fs:ntfs
convert E: /fs:ntfs
convert F: /fs:ntfs

Standardize file systems across file servers to enable unified permission management, auditing, and quotas.

Enable EFS Encryption on Data Drive

Convert to NTFS before enabling folder encryption:

convert D: /fs:ntfs
cipher /e D:\Confidential

EFS requires NTFS. Convert first, then use cipher to encrypt sensitive directories.

Prepare Drive for SQL Server Database Files

Convert data drives before SQL Server installation:

convert D: /fs:ntfs

SQL Server strongly recommends NTFS for database file storage due to security, reliability, and performance features.

Migrate Legacy Windows XP Systems

Upgrade older Windows XP installations from FAT32 to NTFS:

convert C: /fs:ntfs

Modernizes legacy systems to support current security practices and application requirements.

Convert External Archive Drives

Upgrade external hard drives used for backups and archives:

convert G: /fs:ntfs /v

Use verbose mode to monitor progress on large external drives. Enables compression for space savings on archive data.

Enable Disk Quotas on User Drives

Convert user data volumes to enable per-user disk quotas:

convert E: /fs:ntfs
fsutil quota enforce E:

After conversion, configure quotas to limit user storage consumption on shared volumes.

Tips and Best Practices

Always Backup Before Converting

Even though convert is designed to preserve data, hardware failures, power outages, or bugs can cause data loss. Maintain complete backups before converting any volume, especially system drives.

Verify Free Space Requirements

Conversion requires at least 15% free space. Check with dir or File Explorer before converting. If space is insufficient, temporarily move files to another drive or delete unnecessary data.

Use Verbose Mode for Large Volumes

Include /v when converting volumes over 100GB. Verbose output confirms the process is progressing and helps diagnose issues if conversion stalls.

Convert During Maintenance Windows

Schedule system drive conversions during planned downtime. The conversion reboot and process can take 30-60 minutes on large, fragmented drives.

Don't Interrupt System Drive Conversions

Power failures or forced restarts during system drive conversion can corrupt the file system. Ensure reliable power (UPS) and allow the process to complete.

Consider Reformatting Instead of Converting

For empty drives or when you can restore from backup, reformatting to NTFS is preferable to converting. Reformatting creates a cleaner, less fragmented NTFS volume with optimal cluster sizes.

Test on Non-Critical Volumes First

If you're new to convert, practice on non-critical data drives before converting system drives. Gain familiarity with the process and typical completion times.

Check for Disk Errors Before Converting

Run chkdsk to verify file system integrity before conversion:

chkdsk D: /f

Fix any errors before converting. Converting a volume with existing errors can lead to data loss.

Document Volume Labels

Record volume labels before converting. The convert process prompts for the current label as a safety check—you must enter it correctly to proceed.

Update Boot Configuration on Multi-Boot Systems

On systems with multiple operating systems, converting a shared data partition may affect boot configuration. Document boot settings and have recovery media available.

Defragment After Conversion

Converted volumes may be fragmented. Schedule defragmentation after conversion completes:

defrag D: /u /v

Improves performance on converted volumes, especially mechanical hard drives.

Understand NTFS Compatibility Limitations

While NTFS is standard on Windows, compatibility with other platforms varies. Linux supports NTFS (with ntfs-3g), but macOS has limited NTFS write support. Consider portability needs before converting external drives.

Troubleshooting Common Issues

"Cannot Lock the Drive" Error

Problem: Convert fails with "Cannot lock the drive. The volume is still in use."

Cause: Open files or applications accessing the target drive prevent exclusive lock.

Solution:

Close all applications and documents on the target drive
Check Task Manager → Details → find processes accessing the drive
Stop services that may access the drive
Use /x to force dismount: convert D: /fs:ntfs /x
For system drive, conversion will automatically schedule for next reboot

Prevention: Before converting, close all applications and check for open files.

"Insufficient Disk Space" Error

Problem: Convert fails with "Insufficient disk space for conversion."

Cause: Less than 15% free space on the target volume.

Solution:

Check free space: dir D:
Delete temporary files, downloads, or unnecessary data
Move large files temporarily to another drive
Empty Recycle Bin
Run Disk Cleanup: cleanmgr /d D:

Prevention: Ensure at least 20% free space before converting (buffer above 15% minimum).

"Volume Label Is Incorrect" Error

Problem: Convert prompts for volume label but rejects the entered label.

Cause: Entered label doesn't match the actual volume label (case-sensitive).

Solution:

Check exact label: vol D:
Enter label exactly as shown, including spaces and case
If volume has no label, press Enter without typing anything

Prevention: Run vol first to see the exact label; copy it accurately.

System Drive Conversion Fails to Complete

Problem: System drive conversion scheduled for reboot but fails or hangs during boot.

Cause: Disk errors, bad sectors, insufficient space, or interrupted conversion.

Solution:

Boot into Safe Mode or Windows Recovery Environment
Run chkdsk C: /f /r to repair file system and bad sectors
Retry conversion: convert C: /fs:ntfs
If repeatedly failing, back up data and reformat to NTFS

Prevention: Run chkdsk before converting; ensure UPS or reliable power during conversion.

Conversion Takes Extremely Long

Problem: Convert runs for hours without completing.

Cause: Heavily fragmented volume, slow disk, or millions of small files.

Solution:

Monitor progress with /v verbose mode
Check disk health with wmic diskdrive get status
Allow conversion to complete—large volumes can take 1-2 hours
If truly stalled (no disk activity for 30+ minutes), force reboot and run chkdsk

Prevention: Defragment FAT32 volumes before converting; expect 1-2 hours for heavily used 500GB+ drives.

"The Convert Command Cannot Run Because the Volume Is Being Used By Another Process"

Problem: Convert fails even after closing all visible applications.

Cause: Background processes, services, or hidden applications with open file handles.

Solution:

Use Resource Monitor (resmon) → Disk tab to identify processes with open handles
Stop services: net stop servicename
Close hidden applications (antivirus, backup, sync tools)
Use /x to force dismount
Boot to Safe Mode and retry conversion

Prevention: Stop unnecessary services and close all applications before converting.

Related Commands

diskpart – Advanced Disk Partitioning

While convert changes file systems on existing volumes, diskpart creates, deletes, and manages partitions. Use diskpart to create new NTFS partitions; use convert to upgrade existing FAT/FAT32 volumes to NTFS.

format – Initialize File Systems

format erases volumes and creates new file systems. Use format when you can afford data loss or have backups; use convert when you must preserve existing data during file system upgrade.

chkdsk – File System Verification

chkdsk checks and repairs file system errors. Always run chkdsk before converting to ensure volume integrity. After conversion, run chkdsk to verify NTFS structures are healthy.

fsutil – File System Utility

fsutil provides low-level file system information and operations. Use fsutil fsinfo volumeinfo to check current file system type before converting, and to verify NTFS features after conversion.

defrag – Disk Defragmentation

defrag reorganizes files to improve performance. Run defrag after conversion to optimize file placement on converted NTFS volumes, especially on mechanical hard drives.

icacls – NTFS Permissions

icacls manages NTFS access control lists. After conversion, use icacls to configure granular file and folder permissions—a key NTFS advantage over FAT32.

Frequently Asked Questions

What does convert C: /fs:ntfs do?

convert C: /fs:ntfs converts the C: drive from FAT or FAT32 file system to NTFS without data loss. For system drives, conversion is scheduled for the next reboot and completes before Windows loads. All existing files, folders, and data are preserved during conversion.

Will convert delete my files?

No, convert is designed to preserve all existing data during file system conversion. However, always maintain backups before converting—hardware failures, power outages, or bugs can cause data loss in rare cases. Convert is safe but not risk-free.

Can I convert NTFS back to FAT32?

No, the convert command only works one direction: FAT/FAT32 → NTFS. To reverse, you must back up all data, reformat the volume as FAT32 (using format or Disk Management), and restore files. This is destructive and time-consuming.

How long does convert take?

Conversion time varies by volume size, file count, and disk speed. Typical ranges: small volumes (10-50GB) take 5-15 minutes; medium volumes (100-250GB) take 15-30 minutes; large volumes (500GB+) can take 1-2 hours. System drive conversions add one reboot cycle.

Do I need administrator privileges to run convert?

Yes, convert requires administrator privileges. Right-click Command Prompt and select "Run as administrator" before executing convert. Without elevation, the command will fail with "Access denied" errors.

What happens if power fails during conversion?

Power failure during conversion can corrupt the file system, potentially causing data loss. The volume may be left in an inconsistent state requiring recovery tools or reformatting. Always use UPS (uninterruptible power supply) for laptops and desktops when converting system drives.

Can I convert external USB drives?

Yes, convert works on external drives formatted as FAT or FAT32. However, NTFS has reduced compatibility with non-Windows devices. Linux supports NTFS well, but macOS has limited write support, and many consumer devices (TVs, media players) don't support NTFS at all. Consider portability needs.

Is it better to convert or reformat to NTFS?

Reformat is preferable if you can afford to restore from backup. Reformatting creates a cleaner NTFS volume with optimal cluster sizes and no fragmentation. Convert is necessary when you must preserve existing data in place without backup/restore cycles.

Why does convert require volume label?

The volume label prompt is a safety check to prevent accidental conversion of wrong drives. You must enter the correct current volume label to proceed. This ensures you're converting the intended volume, not accidentally targeting another drive.

Can I cancel convert after it starts?

On non-system drives, you can press Ctrl+C to cancel before conversion begins. Once conversion starts writing NTFS structures, cancellation is not safe—interruption can corrupt the file system. For system drive conversions scheduled for reboot, you must allow conversion to complete.

Does convert work on SSD drives?

Yes, convert works on SSDs and supports TRIM after conversion to NTFS. SSDs benefit from NTFS features like compression, security, and journaling. However, ensure sufficient free space (15%+) before converting—SSDs with low free space perform poorly.

Will convert affect dual-boot systems?

Converting a shared data partition may affect boot configuration on dual-boot systems. Linux can read and write NTFS (with ntfs-3g), so converted volumes remain accessible. However, converting the Windows system partition on a dual-boot setup requires careful boot configuration management.

Quick Reference Card

Command	Purpose	Example
`convert D: /fs:ntfs`	Convert drive D: to NTFS	Standard conversion
`convert C: /fs:ntfs`	Convert system drive (requires restart)	Upgrade Windows volume
`convert E: /fs:ntfs /v`	Convert with verbose output	Monitor progress
`convert F: /fs:ntfs /x`	Force dismount and convert	Override open files
`convert G: /fs:ntfs /nosecurity`	Convert without security	Public access volume
`vol D:`	Check volume label	Verify target drive
`fsutil fsinfo volumeinfo D:`	Check file system type	Confirm FAT/FAT32
`chkdsk D: /f`	Check disk errors before converting	Pre-conversion safety

Try Convert in Our Simulator

Want to practice using the convert command without affecting your system? Try our interactive Windows Command Simulator to experiment with file system conversion operations in a safe, simulated environment. Practice conversion syntax, see simulated output, and understand the process before running commands on your actual system.

For more disk management commands, browse our comprehensive Commands Reference with over 200 Windows commands, syntax guides, and practical examples.

Summary

The convert command provides safe, in-place conversion of FAT and FAT32 volumes to NTFS file system while preserving all existing data. By upgrading to NTFS, you gain large file support (over 4GB), advanced security features (ACLs), encryption (EFS), compression, quotas, and improved reliability through journaling.

Key takeaways: Use convert volume /fs:ntfs to upgrade file systems. Always back up critical data before converting. Ensure at least 15% free space on the target volume. System drive conversions require a restart and happen before Windows loads. Non-system drive conversions can happen immediately if the volume is not in use.

Conversion is one-way and irreversible—NTFS cannot be converted back to FAT32 without reformatting. Consider compatibility needs before converting external drives, as NTFS has limited support on non-Windows platforms. When possible, reformatting is preferable to converting because it creates cleaner, less fragmented NTFS volumes with optimal cluster sizes.

For system administrators, convert is essential for standardizing file systems across enterprise environments, enabling security features, and migrating legacy systems. Implement conversion during maintenance windows, verify prerequisites, and monitor progress to ensure successful upgrades.

Master the convert command to modernize file systems, enable advanced NTFS features, and prepare storage infrastructure for current and future Windows capabilities—all without data loss or lengthy backup/restore cycles.