Choosing a file format a Mac and Windows both accept

A drive that has to work on both a Mac and a Windows PC should be formatted as exFAT. Both systems read and write it without extra software, it has no practical limit on file size, and Disk Utility on the Mac can create it in under a minute. The older MS-DOS (FAT) format, which is FAT32, also works on both sides but cannot hold a single file of 4 GB or more. NTFS and APFS each belong to one side. That is the whole answer for most people. The rest of this guide covers what the answer leaves out: what Disk Utility on macOS 27 actually offers, how to reformat without losing what is on the drive, and the file names that copy fine on a Mac and then fail on Windows. Every limit below was checked against Apple's and Microsoft's own documentation on October 8, 2026.

What Disk Utility on macOS 27 will create

Apple's Disk Utility User Guide for macOS 27 lists two Windows-compatible formats, and its instruction is short. Choose MS-DOS (FAT) "if the size of the disk is 32 GB or less". Choose ExFAT "if the size of the disk is over 32 GB". That is a size rule, not a quality rule, and it means nearly every modern USB stick and external drive should get exFAT.

The command line shows the full list. Running diskutil listFilesystems on macOS 27.0.1 returns the formats the Mac can erase a disk to: APFS and its case-sensitive variant, ExFAT, MS-DOS (FAT) with FAT12, FAT16 and FAT32 variants, and four flavours of Mac OS Extended. NTFS is not in the list. A Mac can mount an NTFS drive, but it cannot create one, so a guide that says "format it as NTFS on the Mac" describes something the built in tools do not do.

The same Apple page gives one more limit that catches people. For a disk formatted for Windows, "the maximum length for the volume name is 11 characters". A name like Project Backup 2026 will not be accepted. Pick something short such as SHARED before opening the dialog.

The steps, using the names on screen:

1. Open Disk Utility. If it is not in the Dock, type Disk Utility into Spotlight.
2. Choose View, then Show All Devices. Without this the sidebar shows volumes only, and the drive itself cannot be selected.
3. Select the drive, not the volume indented beneath it.
4. Click Erase in the toolbar.
5. Set Name to something of 11 characters or fewer.
6. Set Format to ExFAT, or MS-DOS (FAT) for a drive of 32 GB or less.
7. Set Scheme. GUID Partition Map suits current Windows PCs. If an older device such as a TV or a car stereo later refuses the drive, Master Boot Record is the scheme to try.
8. Click Erase, then Done.

Formatting from the Windows side instead

The drive can just as well be prepared on the PC. In File Explorer, right-click the drive under This PC and choose Format. The dialog has a File system menu, an Allocation unit size menu, a Volume label field and a Quick Format checkbox. Choose exFAT, leave the allocation unit size at its default, type a short label and click Start. The result is the same exFAT volume a Mac would create, and the Mac mounts it without any prompt.

There is one reason to prefer one side over the other. Whichever machine will write most of the data is the one that should format the drive, because any problem with the result shows up immediately on the machine that made it, where it is easiest to try again. If the drive is mostly filled on a Mac and read on a PC, format it on the Mac. If a Windows workstation produces the files, format it there. Either way, test it on the other machine with a single small file before copying anything large.

The formats side by side

The table puts the numbers that matter in one place. File size and file name limits come from Microsoft's file system functionality comparison. The Mac column reflects what diskutil listFilesystems reports on macOS 27.

Format	Mac	Windows	Largest single file	Journaling	Typical use
exFAT	Read and write, can create	Read and write	2^64 minus 1 bytes	No	Drives shared between both systems
MS-DOS (FAT32)	Read and write, can create	Read and write	4 GiB	No	Small sticks, cameras, older devices
NTFS	Read, cannot create	Read and write, default	2^64 minus 1 bytes	Yes	Drives that stay on Windows
APFS	Read and write, default	Not without extra software	Very large	Copy on write	Drives that stay on Macs

Two rows in that table decide most cases. The 4 GiB file limit is why FAT32 fails the moment someone copies a long video or a disk image. The "cannot create" for NTFS on the Mac is why NTFS is not the shared answer even though Windows treats it as home.

The trade-off with exFAT is the journaling column. Microsoft's comparison lists metadata-only journaling as Yes for NTFS and No for exFAT and FAT32. Without a journal, a drive pulled out in the middle of a write can be left with a damaged directory. On a Mac, always use Eject in Finder before unplugging. On Windows, use Safely Remove Hardware. That one habit removes most of exFAT's reputation for corruption.

Reformatting without losing what is on the drive

Erase means erase. Apple's page carries a warning that formatting a disk or volume erases all the files on it. There is no in place conversion from NTFS or APFS to exFAT in Disk Utility. The safe order is:

1. Copy everything off the drive to another disk.
2. Check the copy opened correctly, by opening a few large files, not just counting them.
3. Erase the drive to exFAT using the steps above.
4. Copy the files back.

Step 2 is the one people skip. A copy can finish with no visible error and still leave out files whose names the destination refused. The next section covers why that happens.

For a drive that already holds a lot, the command line is faster than dragging in Finder and leaves a record of anything that failed:

$ rsync -a --progress /Volumes/OLDDRIVE/ ~/Desktop/olddrive-copy/

The trailing slash on the source copies the contents rather than the folder itself. When the drive has been reformatted, run the same command with the two paths reversed.

Erasing from the command line is possible too, with diskutil eraseDisk ExFAT SHARED GPT diskN, where diskN comes from diskutil list. It is quicker, and it is also the easiest way to erase the wrong disk. Read the diskutil list output twice and confirm the size matches the external drive before pressing Return.

File names that work on a Mac and fail on Windows

A drive can be formatted perfectly and the copy can still fail, because the two systems allow different file names. Microsoft's "Naming Files, Paths, and Namespaces" page lists the rules Windows enforces.

Characters Windows will not accept in a name: < > : " / \ | ? *. The Mac allows most of them. A file called Meeting 10:30.txt or Budget? draft.xlsx is ordinary on a Mac and cannot exist on a Windows PC.

Reserved names: Windows treats CON, PRN, AUX, NUL, COM1 to COM9 and LPT1 to LPT9 as devices. Microsoft notes that adding an extension does not help, since NUL.txt is treated the same as NUL.

Trailing spaces and periods: Microsoft states that the Windows shell does not support names ending in a space or a period, even when the file system underneath could store them. Names like these are easy to create on a Mac without noticing.

Case: exFAT is not case-sensitive. Two files in the same folder called Report.pdf and report.pdf can live side by side on a case-sensitive APFS volume, and one of them will be lost or refused on the way to exFAT.

Finding offenders before copying saves the afternoon. From a Terminal in the folder to be copied:

$ find . -name '*[<>:"\\|?*]*'
$ find . -name '* ' -o -name '*.'

The first finds names with characters Windows rejects. The second finds names that end in a space or a period. Rename what they return, then copy.

The ._ files Windows users see

After a Mac writes to an exFAT or FAT32 drive, a Windows user opening it often sees a duplicate for every file, each starting with ._. These are AppleDouble files. The Mac stores extra information, such as Finder tags and extended attributes, that exFAT has no place for, so it writes that information into a companion file next to the real one.

They are harmless on Windows, and deleting them there does not damage the real files. It only discards the Mac-side extras. To clean a drive from the Mac before handing it over, macOS includes dot_clean. Its manual page describes it as merging ._* files with their corresponding native files:

$ dot_clean -m /Volumes/SHARED

The -m option removes the ._ files after merging. Running it just before ejecting means the Windows side sees only the real files.

When the drive is the wrong answer

A shared drive solves the problem of moving files on foot. If the two machines are on the same network, an SMB share from the Mac (System Settings, General, Sharing, File Sharing) avoids the format question entirely, since each side keeps its own disk format. If the files mostly flow one way and need to arrive somewhere else, a cloud folder may serve better. The shared drive earns its place when there is no network, the files are large, or the drive has to travel.

Keeping the check in the same window as the files

Every check in this guide is a single command run inside a particular folder: find for bad names before copying, rsync for the copy, dot_clean before ejecting. The friction is not the commands themselves. It is opening Terminal, typing cd into the right path on the right volume, and then going back to Finder to see the result.

A file manager with a built-in terminal removes that step, because the terminal opens in the folder already on screen. The Features page shows a terminal tied one to one with each folder, along with zip and unzip built into the window, which is another way to move a folder of awkwardly named files to Windows intact: compress first, then copy one archive. On the Mac it is free with no time limit, as the Pricing page lists. For someone who moves a drive between a Mac and a PC once a year, Finder and Terminal are enough. For someone doing it every week, having the folder and the shell together removes the most error prone part.

What to change first

If the shared drive is over 32 GB, erase it to exFAT in Disk Utility with a name of 11 characters or fewer, after copying its contents somewhere safe. Before the next copy to Windows, run the two find commands above and rename what they return. For the folder and the terminal in one window, see Atriens.