Flamingo Raises $4.5M Seed Round

Skip to content

Updated: October 2026

A new external drive arrives formatted exFAT, and someone asks whether to switch it to NTFS before filling it. The answer depends on where the drive goes next and how it gets unplugged. Here's exFAT vs NTFS for external drives: what each does with your data, what gets lost when files cross between them, and which to pick for backups and shared drives.

exFAT vs NTFS at a Glance

NTFS is the Windows file system: journaled, permission-aware and packed with features. exFAT is the lightweight format built for flash drives and memory cards. Every difference below follows from that split.

exFATNTFS
Journal (repairs its own structure after a crash)NoYes
File permissions (ACLs)NoYes
EFS encryption, compressionNoYes
Mark of the Web on downloaded filesNoYes
BitLocker To GoYesYes
macOSRead and writeRead only
LinuxRead and writeRead and write
TVs, cameras, car stereosUsuallyRarely
Time Machine backupsNoNo
Good home forFiles moving between machinesDrives that live on Windows

The short version: exFAT goes everywhere, NTFS keeps your data in better shape. Pick by which one you need more.

What NTFS's Journal Does That exFAT Can't

NTFS writes down each change to its own records before making it. Microsoft's NTFS overview puts it plainly: after a failure, NTFS uses that log "to automatically restore file system consistency during the next startup." Pull the cable mid-copy and the drive's structure comes back on its own. The file being copied may not.

exFAT has no journal. What it has, per the exFAT specification, is a VolumeDirty flag that gets set before a metadata update and cleared after, plus checksums on the boot region and on each file's directory entries. So exFAT can tell it wasn't finished cleanly. It can't put itself back. That's the "Scan and fix" prompt, and the repair is chkdsk E: /f on Windows or First Aid in Disk Utility on a Mac, walking the whole drive.

A transaction-safe variant called TexFAT exists in the spec, but it shipped on Windows CE devices, not on the desktop.

The top answer in that thread lays out the journaling case well. Then the poster remembers the drive also plugs into a TV, and keeps it exFAT. That trade is the whole exFAT vs NTFS decision in one thread.

What Gets Lost When Files Move to exFAT

Copying from NTFS to exFAT keeps the file contents and timestamps. It drops everything NTFS stores alongside them.

Permissions go first. On exFAT, anyone who plugs the drive in can read every file. EFS-encrypted files get decrypted on the way over, after a warning. Compressed files expand to full size.

The one that surprises people is Mark of the Web. When Windows downloads a file, it tags it as coming from the internet in a hidden alternate data stream, and Office blocks macros in files carrying that tag. Microsoft's own guidance on internet macros says Mark of the Web "only applies to files saved on an NTFS file system, not files saved to FAT32 formatted devices." exFAT has no alternate data streams either. So a macro-laden attachment copied to an exFAT stick and opened from there no longer looks like it came from the internet.

If the data needs protecting on the move, encrypt the whole drive with BitLocker To Go. It works on exFAT and NTFS alike.

Mac, Windows and Linux on One Drive

macOS reads NTFS but can't write to it without third-party drivers. It reads and writes exFAT out of the box. That single fact settles the question for any drive shared with a Mac.

Two Mac habits are worth knowing. macOS leaves hidden ._ companion files and .Spotlight-V100 folders on exFAT drives, which confuse the odd TV or media player. And Time Machine won't use either format. Apple's documentation says Time Machine "can't back up to... a disk formatted for Windows" and prefers APFS. A Mac backup drive gets APFS, and our explainer on FileVault covers encrypting it.

Linux reads and writes both. exFAT went into the mainline kernel after Microsoft published the spec and backed its inclusion on 28 August 2019. NTFS support comes from the ntfs3 driver, which the kernel docs describe as a "fully functional NTFS Read-Write driver."

The r/linux4noobs replies land on a fair split. exFAT has the steadier driver on Linux, and NTFS has the journal. If you go NTFS on a dual-boot drive, do the formatting and repairs from Windows.

Backup Drives: Format for the Restore

A backup drive is judged on the day you restore from it. Format it for the machine that will do the restoring.

For a Windows backup, that's NTFS. The journal protects the drive's structure through a bad unplug, permissions come back with the files, and NTFS works with Volume Shadow Copy for backup apps that snapshot the drive. NTFS also defaults to 4 KB clusters, which suits a backup full of small files. For how the backup chain itself should be built, see our guide to incremental vs differential backup.

exFAT is fine for a drive that carries a copy from one place to another. Don't let it be the only copy of anything.

The same goes for the portable SSD that travels between the office and home. If it only ever meets Windows laptops, NTFS costs nothing and buys the journal. If a Mac or a TV is anywhere on its route, exFAT is the price of admission, and the backup lives somewhere else.

Switching an exFAT Drive to NTFS

There's no in-place conversion. Windows' convert command only handles FAT and FAT32 (our FAT32 vs NTFS guide covers that route), so an exFAT drive has to be emptied, formatted and refilled:

code
robocopy E:\ D:\Holding /E /COPY:DAT /R:1 /W:1
format E: /FS:NTFS /Q /V:BACKUP
robocopy D:\Holding E:\ /E /COPY:DAT /R:1 /W:1

Check the holding copy before you format. Comparing file counts on both sides takes one line:

code
(Get-ChildItem E:\ -Recurse -File).Count; (Get-ChildItem D:\Holding -Recurse -File).Count

If the numbers differ, read the robocopy summary for skipped or failed files before going further. If the exFAT drive is throwing errors, run chkdsk E: /f first so the copy doesn't carry the damage along. In PowerShell, Get-Volume shows which drives are exFAT today.

exFAT or NTFS: Which One to Pick

Pick NTFS if the drive lives on Windows machines, holds backups, or needs permissions. Pick exFAT if it has to be written by a Mac, read by a TV, or shared with Linux without fuss. Either way, eject before you unplug, and keep a second copy of anything that matters.

That's exFAT vs NTFS: exFAT for reach, NTFS for resilience. If you're weighing FAT32 as well, the same logic applies, with a 4 GB file limit on top, and our exFAT vs FAT32 guide covers that pair.

Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

Related Content

Blog Posts

Product Releases

Podcasts

Webinars

Case Studies

Events

Onboarding Guides

Frequently Asked Questions

exFAT vs NTFS

Use NTFS if the drive only meets Windows machines, holds backups or needs permissions, because NTFS has a journal that repairs its own structure after a bad unplug. Use exFAT if a Mac needs to write to it or a TV, camera or car stereo needs to read it.
exFAT has no journal, so a drive pulled mid-write can be left inconsistent and needs a scan with chkdsk or First Aid. NTFS replays its transaction log on the next mount and restores its own consistency. Neither format saves the file that was being copied at that moment.
No. Apple's documentation says Time Machine can't back up to a disk formatted for Windows, and prefers APFS. A drive shared between a Mac and Windows PCs can stay exFAT for moving files, but the Time Machine backup needs its own APFS-formatted disk.
No. Windows can convert FAT and FAT32 volumes to NTFS in place, but not exFAT. Copy the data off, format the drive as NTFS, copy it back and compare file counts before deleting the holding copy.

About OpenFrame

In the cloud, on US soil. Your data stays stateside.
OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.
Both. It's built for MSPs and MSSPs alike.

MSP AI Agents

On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.
Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.