Choosing a file format a Mac and Windows both accept

A drive gets plugged into a Mac, copied to, unplugged, and handed to someone on Windows. Sometimes everything opens. Sometimes the drive mounts read only, or a 6 GB video refuses to copy, or the folder arrives full of files whose names start with ._, or a name with a colon in it comes back as an error. The search for mac windows file format usually starts after one of those, and it collapses two separate decisions into one phrase. One decision is about the volume. The other is about what gets written onto it. They fail differently and they are fixed in different places.

Two problems wearing one name

The volume problem is a formatting decision made once, before any data exists. It determines the maximum size of a single file, whether a machine can write as well as read, and whether the disk survives being pulled out at the wrong moment. Changing it later means erasing the disk.

The file problem is continuous. Every time a file with an unusual name, an unusual character, or a very long path is written, it becomes a file that may or may not survive the crossing. The volume can be perfect and the transfer can still fail on a name.

Both are worth ten minutes of attention up front, because both produce failures that look like hardware faults and are not.

What Disk Utility will actually create

Apple documents the list, and it is shorter than most comparison articles imply. Disk Utility offers Apple File System in four variants, plus two Windows compatible formats.

MS-DOS (FAT): Use for Windows volumes that are 32 GB or less. ExFAT: Use for Windows volumes that are over 32 GB.

That is from Apple's page on the file system formats available in Disk Utility. The same guide's instructions for formatting a disk for Windows computers repeat the 32 GB line and add a detail that catches people out: the maximum length for the volume name is 11 characters. A name longer than that is silently truncated or rejected at the point of erasing.

NTFS does not appear in that menu at all. A Mac can mount and read an NTFS volume, but Disk Utility will not create one and macOS will not write to one without additional software. That single fact settles most of the argument, because a drive formatted on a Windows machine with default settings is usually NTFS, and the Mac side of the pair is the one that ends up limited.

APFS runs in the other direction. It has been the default for Mac startup disks since macOS 10.13, and Windows has no built in support for reading it. An APFS drive handed to a Windows machine typically prompts to be formatted, which is the offer worth declining.

The comparison, in one table

Format	Read on macOS	Write on macOS	Read on Windows	Largest single file	Journaling
APFS	Yes	Yes	No, without extra software	Very large	Yes, with checksummed metadata
Mac OS Extended	Yes	Yes	No, without extra software	Very large	Yes
ExFAT	Yes	Yes	Yes	2^64 minus 1 bytes	No
MS-DOS (FAT)	Yes	Yes	Yes	4 GiB	No
NTFS	Yes	No, without extra software	Yes	Very large	Yes

The file size figures come from Microsoft's file system functionality comparison, which lists a 4 GiB ceiling for FAT32 and a 2^64 minus 1 byte ceiling for exFAT. That 4 GiB line is the reason a video or a disk image refuses to copy onto an old USB stick while smaller files go across fine.

For a drive that has to be writable from both sides with nothing installed, exFAT is the only entry in the table that qualifies. That is not praise. It is the shape of the constraint.

What exFAT gives up

Journaling is the first thing. APFS and NTFS keep a record of intended changes so that an interruption leaves the volume in a known state. ExFAT does not, which is why the eject step matters more on an exFAT drive than on any other kind. Pulling the cable during a write can lose more than the file being written.

Permissions are the second. ExFAT stores no POSIX ownership or mode bits, so everything on the volume reads as belonging to whoever mounted it. Scripts that depend on the executable bit stop working after a round trip through an exFAT drive, and restoring a backup from one loses the original ownership.

Extended attributes are the third, and this is the source of the mysterious extra files. macOS stores metadata such as tags, quarantine flags, and resource forks in extended attributes. On a volume that cannot hold them, that data is written into a companion file beside the original with a ._ prefix, in the AppleDouble layout. A Windows user sees two files where a Mac user sees one. Alongside those, macOS adds .DS_Store for folder view settings, plus .Spotlight-V100 and .fseventsd at the volume root.

None of this is damage. It is metadata with nowhere better to live. Running dot_clean on a folder before handing over the drive merges those companion files back where possible, and mdutil -i off /Volumes/NAME stops the indexing directories from being recreated.

Doing the reformat without losing the contents

Formatting erases the volume, and Apple's own instructions open with that warning. The order of operations therefore matters more than the choice of format.

Copy everything off first, to a location that is not the drive being erased, and verify the copy by comparing counts and total size rather than by glancing at the folder. A copy that stopped partway through leaves a folder that looks plausible and is short by several files.

In Disk Utility, choose View, then Show All Devices, before selecting anything. Without that, the sidebar shows volumes rather than physical disks, and erasing a volume leaves the existing partition scheme in place. Selecting the physical disk and clicking Erase exposes a Scheme menu alongside the Format menu, and that menu is the part most guides skip. GUID Partition Map is the general purpose choice for drives used with computers. Master Boot Record is the compatible choice for devices with simpler firmware, such as cameras, recorders, and televisions that read a drive but do not run a full operating system.

Then set Format to ExFAT, keep the volume name to 11 characters or fewer, and erase. When it finishes, copy one large file across and open it on the destination machine before trusting the drive with anything else. A drive that was formatted correctly and cabled badly fails on the second gigabyte rather than the first, and finding that out during a handoff is expensive.

One more step is worth building in: leave the original copy in place until the receiving machine has confirmed it can read the files. A transfer is not finished when the copy completes. It is finished when someone else opens the result.

The names that break on the other side

Assume the volume is correct and files still fail. The cause is almost always the name.

Windows reserves nine characters outright and a set of device names inherited from the earliest versions of the system. Microsoft's file naming rules list the reserved characters as < > : " / \ | ? *, and the reserved names as CON, PRN, AUX, NUL, COM1 through COM9, and LPT1 through LPT9, including when they carry an extension. A file called NUL.txt is not a file on Windows. The same page states that a name must not end with a space or a period, and that the traditional path limit is MAX_PATH, defined as 260 characters, with longer paths requiring a registry or Group Policy change.

macOS has a shorter list. A file name cannot contain a colon, cannot begin with a period without becoming hidden, and is limited to 255 characters.

Rule	macOS	Windows
Colon in a name	Not allowed	Not allowed
Backslash, question mark, asterisk, pipe	Allowed	Not allowed
Trailing period or space	Allowed	Not allowed
Name length	255 characters	255 characters per component
Full path length	No practical limit in normal use	260 characters unless raised
Case in names	Two names differing only in case are usually the same file	Same file

The last row is the quiet one. A standard Mac volume treats Report.pdf and report.pdf as the same name, and so does Windows, but an APFS volume formatted as case sensitive does not. A project cloned onto a case sensitive volume and then copied to Windows can arrive with pairs of files that the destination cannot keep apart.

Character normalization is the other quiet one. A Japanese character with a voiced mark can be stored as one code point or as two, and APFS treats both spellings as the same name. Windows does not. A name that was created in the two code point form can therefore look correct on the Mac, sort strangely on Windows, and fail an exact match in a script that was written against the other spelling.

When a shared drive is the wrong answer

A drive is a reasonable choice for a single large handoff. It is a poor choice for anything recurring, because every crossing repeats every risk above.

For recurring transfers, a network share speaks a protocol rather than a disk format, which takes the volume question off the table entirely. Both systems can mount an SMB share, and the file naming rules of the server apply rather than the rules of a disk.

For one off archives, a zip file moves the problem up a layer, and it introduces a different one. Archives created on Windows with a system default encoding produce garbled names when expanded on a Mac, because the archive records the bytes of the name without always recording which encoding those bytes are in. Keeping names to characters that survive on both sides removes the failure mode entirely, which is a cheaper habit than choosing an archive tool per direction.

The habit that pays across all of these is choosing names once, defensively, at creation time: no colons, no trailing periods, no reserved words, and no characters that require an encoding declaration to interpret. Enforcing that by hand across a folder of a hundred files is tedious, which is why bulk renaming with a rule and a preview belongs in the same window as the folder itself rather than in a separate utility. The same goes for the shell commands that clean up companion files before a handoff, which is the arrangement described under Features, and the differences between the tools that offer it are set out in Compared with other file managers.

What to change first

If the drive is being formatted now, choose ExFAT for anything over 32 GB and give it a volume name of 11 characters or fewer. Then fix names at the source rather than after a failed copy, and run dot_clean before handing the disk over. If the deeper cost is switching between a folder window and a shell for every one of those steps, Atriens is built around removing that switch.