External Drives

How to Move a Folder Between Mac and Windows Without Filename Errors

Audit reserved Windows names, long paths and case collisions before copying a folder from macOS.

Windows may copy the first half of a Mac folder and then stop at a single file. Look underneath the top-level folders for names such as agenda?.pdf or a pair like Cover.png and cover.png. Resolve them in a staging copy before the Windows transfer.

Scan every path component, including the enclosing folder names. Write a list of problematic paths and give each a destination relative path. Use a staging copy for all name changes so an app that still refers to the original tree can continue opening it.

Find names the destination rejects

Microsoft's naming rules reserve characters such as ?, *, : and |. Windows also reserves device names such as CON, NUL and COM1. Adding an extension does not free one of these names. Review names that end in a space or period, which can be rejected by the Windows shell.

Source relative path Staging path Why
notes/agenda?.pdf notes/agenda-review.pdf Reserved punctuation
sessions/CON.txt sessions/console-notes.txt Device name
assets/Cover.png assets/cover-front.png Capitalization conflict
assets/cover.png assets/cover-draft.png Capitalization conflict

A case-sensitive APFS volume can store both image names in the same directory. Assume a case-insensitive destination for routine Windows copies. An app that consumes the folder can also apply its own naming rules, so verify dependent tools during the pilot. After proposing new names, compare them with one another and with all existing targets. Replacing every forbidden character with the same underscore can create collisions of its own.

Try the deepest file first

Length depends on the full destination path and on the application opening it. A file copied to a short root may move successfully and then fail when imported from a nested team folder. Windows software can differ in its support for long paths. For the first test, use the actual Windows application and the real destination root, or a short staging root if the original plan fails.

Pick one file from the deepest folder, one renamed file and one file that has no naming issues. Copy the staged samples and keep the source in place. On Windows verify they open, and check the counts in any folder that had a conflict. Open one project that references a renamed file. Update its relative link and check that a fresh launch can still resolve the asset, since a running editor may have cached the preview. Retain the rename map with the archived original until the copy has been used successfully by whoever receives it.

Build the rename map before copying

List the actual paths under the source, including the names nested well below the top. Look at each folder as well as the file names. Add columns for the proposed relative path, the reason it needs a change and which project uses it. If the source contains a folder named “Phase 1” with a second folder that differs only in capitalization, consider whether their destinations would collide even when the individual files have different names. Resolve folder names first so the descendant paths are clear.

Check names without extensions and those containing invisible trailing space. In the example, adding a suffix might make a reserved file name look plausible without changing the reserved base name in the intended app. Compare the complete names under the destination's rules. Replace problems with names that describe the files. A general punctuation replacement can create two of the same result, so compare all proposed paths together before running the rename. The batch rename rehearsal describes a test set that also accounts for files outside your selection.

Plan how to handle any external references. A design package can link to a photo by relative path or to an audio file in an adjacent folder. A move that passes the operating system's copy check can break an application when a linked path changes. Keep a list of which files need their references updated. Use a duplicate project to test changes while the source can still be opened. A mapping of names without context can be insufficient for a path used in more than one place.

Try the real Windows program on a small set

Use the deepest expected path, one renamed item, and an ordinary file. Copy them to the actual destination root on a test account or test folder you are allowed to use. Open the deepest sample with the application that will consume it. The copy utility and the application may have different support for long paths. If it opens under a short root but fails inside the real folder structure, try shortening a folder name or use an approved shallower destination for the whole project. Record that choice before making one-off changes to every long filename.

A copy failure can leave some files behind even when several folders appear in the new location. Compare expected and actual counts by subtree. Check any file named in the error and whether a different crafted name was already at its proposed path. If you change the name again, update the map and any app reference together. Open the app after a restart so you can see whether it reads the staged project from the correct paths.

Keep a useful record on both sides of the transfer

When the first set passes, choose a relatively small folder for the next batch and compare it using the same checklist. Save a map for the containing folders and for special changed files. If you need to prove exact content transfer, record sizes and hashes for important files and check them on both sides. Those values help confirm equality even when filenames change. Keep the old tree unchanged until you know the new folder works for its intended people and programs.

Give recipients the mapping alongside the delivery. If someone remembers the old “Cover” name, the table can direct them to the front and draft variants. For a multi-platform team, agree on a common naming rule when new files are added. The next copy can then use the same approved names. Retest one nested item and one linked project after moving to a new storage location or changing the Windows application that uses them.

For a transfer through a zip file, run the same check after extracting the archive. A downloaded archive with the expected size can still contain a name the Windows extraction tool cannot create in the chosen folder.

Sources