Tomorrowish

Will these file names survive the move?

Drop a folder or paste a file list and get every name that fails on Windows, a Mac, a USB stick, OneDrive, Dropbox or Git, with a safe rename script.

The folder

Drop a folder here (or several). Only the names, folder structure and file sizes are read, never what is inside the files.

Your browser may ask to “upload” the folder: that is its wording for letting this page read the names. Nothing is sent anywhere; this page is not allowed to make network requests.

Where it’s going

Path length and rename options
The rename plan fixes

How it works

Only names. When you drop a folder, the browser hands this page the names, the folder structure and each file’s size. It never opens a file. A pasted list works the same way, so you can check a server or a NAS by pasting the output of find or dir /s /b without copying anything off it.

Ten places, their own rules. Each name is checked against the documented rules of every place you tick, and each result says which place it breaks and why, with the source. Will fail means the copy, sync or checkout refuses or loses the file. Likely trouble means it works in some apps and breaks in others (paths near 260 characters, # in OneDrive, spaces in links). Worth knowing is everything else: hidden files, system files that don’t sync.

Collisions. Windows, Macs, USB sticks, OneDrive, Dropbox and Git checkouts on Windows or a Mac treat Readme.md and README.md as the same name, and Macs also treat é typed as one letter and as e + accent as the same name. Two such files in one folder overwrite each other. Folders that differ only in case are merged into one (a warning), and the files inside them are checked against each other.

The rename plan. Only names that fail somewhere you ticked are renamed; everything else stays exactly as it is. A forbidden character becomes _, a reserved name gets one (CON.txt → CON_.txt), trailing spaces and periods go, too-long names are shortened keeping the extension, and a name that would land on an existing one gets (2), (3). The plan is checked again before it is shown: no new clashes, and a second run plans nothing. Files over 4 GB and over-long paths can’t be fixed by renaming one name, so they stay in the list without a plan.

Path lengths count from the folder you dropped. Windows counts the whole path from the drive letter, and SharePoint counts from the site, so put where the folder will live under Path length and rename options for exact numbers.

Privacy

The page reads the names with your browser and its security policy blocks every network request, so nothing about your files can be sent anywhere. Nothing is stored. No cookies, no analytics on this page.

Questions

Why does the browser say “upload”? That is the folder picker’s standard wording. Dropping the folder onto the box does the same without the prompt.

A phone? Phones can’t hand a web page a whole folder; paste a file list instead.

Is there a free tool that does this already? Command-line ones, yes (detox, PowerShell scripts, OneDrive’s own sync errors after the fact). This one is for checking before the copy, against several places at once, without installing anything.

Every rule it checks

Taken from each vendor’s own documentation (listed under the table). Vendors change their limits; the date each was last checked is at the bottom.

PlaceRuleSeverityRenamed?
WindowsWindows forbids < > : " / \ | ? * in a name.Will failyes
WindowsWindows forbids characters 1 through 31 (tabs, line breaks and other control characters).Will failyes
WindowsCON, PRN, AUX, NUL, COM1–COM9, LPT1–LPT9 and COM¹ COM² COM³ LPT¹ LPT² LPT³ are reserved, also with an extension (NUL.txt = NUL).Will failyes
WindowsWindows Explorer cannot handle a name that ends with a space or a period.Will failyes
WindowsA name can be at most 255 characters (UTF-16 code units) on NTFS.Will failyes
WindowsPaths of 260 characters or more (MAX_PATH, counted from the drive letter, with a final null) fail in Explorer and most programs unless long paths are switched on.Likely troubleno
WindowsWindows treats OSCAR, Oscar and oscar as the same name, so these overwrite each other.Will failyes
WindowsThese folders differ only in upper/lower case; on Windows their contents end up in one folder.Likely troubleno
macOSmacOS shows a : in a name as / in the Finder, and SMB copies to and from Windows mangle it.Likely troublewith “warnings too”
macOSA name longer than 255 characters cannot be created on APFS or HFS+.Will failyes
macOSHFS+ (older Macs, Time Machine and external drives) counts 255 UTF-16 units after splitting accents off (é = e + ´), so this name is too long there.Likely troublewith “warnings too”
macOSMac drives are case-insensitive by default and ignore Unicode normalization (é typed two ways is one name), so these overwrite each other.Will failyes
macOSThese folders are the same name on a Mac (case or accents differ only); their contents end up in one folder.Likely troubleno
macOSNames starting with a period are hidden in the Finder.Worth knowingno
macOS._ files are Mac metadata left behind on non-Mac drives; they are safe to delete.Worth knowingno
macOSIcon followed by a line break holds a Mac folder’s custom icon; other systems show it as a strange file.Worth knowingno
Linuxext4 allows 255 bytes per name; accented letters take 2 bytes, most CJK 3, emoji 4.Will failyes
LinuxPaths longer than 4,095 bytes (PATH_MAX) fail in most programs.Likely troubleno
LinuxA line break or tab inside a name breaks scripts, terminals and file lists.Likely troublewith “warnings too”
LinuxCommand-line tools read a name starting with - as an option; use ./name or -- in commands.Worth knowingno
LinuxThe same letters typed two different ways (precomposed é vs e + ´): Linux keeps both and they look identical.Likely troublewith “warnings too”
USB stick / SD card (FAT32, exFAT)FAT32 and exFAT forbid < > : " / \ | ? * and control characters.Will failyes
USB stick / SD card (FAT32, exFAT)Windows cannot open CON, PRN, AUX, NUL, COM1–9, LPT1–9 (with any extension) on a stick either.Will failyes
USB stick / SD card (FAT32, exFAT)A trailing space or period is dropped or refused on FAT32 and exFAT.Will failyes
USB stick / SD card (FAT32, exFAT)Long names on FAT32 and exFAT max out at 255 characters.Will failyes
USB stick / SD card (FAT32, exFAT)FAT32 and exFAT are case-insensitive, so these overwrite each other.Will failyes
USB stick / SD card (FAT32, exFAT)These folders differ only in case; on the stick their contents end up in one folder.Likely troubleno
USB stick / SD card (FAT32, exFAT)FAT32 cannot hold a file of 4 GiB (4,294,967,296 bytes) or more. exFAT can: format the stick as exFAT, or split the file.Will failno
USB stick / SD card (FAT32, exFAT)A FAT32 folder holds at most 65,536 directory entries, and every long name uses 1 + one per 13 characters.Will failno
USB stick / SD card (FAT32, exFAT)Windows still stops at 260 characters per path on a stick.Likely troubleno
USB stick / SD card (FAT32, exFAT)+ , ; = [ ] are not allowed in old 8.3 short names; long names keep them, but very old devices (car stereos, cameras) may not.Worth knowingno
Git repositoryGit for Windows refuses to check out this path ("invalid path"): Windows forbids its characters, a trailing space or period, or a reserved name like CON.Will failyes
Git repositoryGit keeps both, but a checkout on Windows or a Mac has room for only one: one silently overwrites the other and git status never comes clean.Will failyes
Git repositoryFolders that differ only in case merge on Windows and Mac checkouts; renames there confuse Git.Likely troubleno
Git repositoryGit refuses any path with a .git component (or its Windows short name git~1) inside a repository.Will failyes
Git repositoryThis folder is a repository of its own: the outer repository records it as a link (submodule), not as files.Worth knowingno
Git repositoryWritten in decomposed form (e + ´), the way older Macs store names; without core.precomposeUnicode it shows up as a different file on Linux and Windows.Worth knowingno
Git repositoryGit for Windows fails on paths of 260 characters or more unless core.longpaths is set.Likely troubleno
Git repositoryLooks like a Windows 8.3 short name (ABCDEF~1.TXT); it can clash with the short name Windows makes for another file.Worth knowingno
DropboxDropbox always disallows / and \ in a name.Will failyes
DropboxDropbox: < > : " | ? * and a final period "may cause syncing or display issues, especially on Windows"; the Windows app swaps them for _.Likely troublewith “warnings too”
DropboxDropbox: “Don’t add a space at the end of a file or folder name.”Will failyes
DropboxDropbox: “File paths must be fewer than 260 characters.”Likely troubleno
DropboxDropbox is case-insensitive: one of these is renamed to “(Case Conflict)” when it syncs.Will failyes
DropboxDropbox does not sync desktop.ini, thumbs.db, .ds_store, icon\r, .dropbox and .dropbox.attr.Worth knowingno
DropboxOffice temporary files (~$… or .~…) are not synced.Worth knowingno
OneDrive / SharePointOneDrive and SharePoint do not allow " * : < > ? / \ | in file and folder names.Will failyes
OneDrive / SharePointOneDrive and SharePoint: “You can’t use leading and trailing spaces in file or folder names.”Will failyes
OneDrive / SharePointNot allowed as file or folder names: .lock, CON, PRN, AUX, NUL, COM0–COM9, LPT0–LPT9, desktop.ini, _vti_ anywhere in a name, names starting with ~$.Will failyes
OneDrive / SharePointThe cloud may accept it, but a reserved device name with an extension (CON.txt) still cannot sync to a Windows PC.Likely troublewith “warnings too”
OneDrive / SharePointSharePoint: “You can’t use forms when the folder or file is at the root level of a library.”Likely troubleno
OneDrive / SharePointOneDrive/SharePoint: “Some organizations don’t yet support # and % in names.”Likely troublewith “warnings too”
OneDrive / SharePointThe entire decoded path, including the file name, can’t exceed 400 characters (it counts from the site, e.g. sites/Team/Shared Documents/).Likely troubleno
OneDrive / SharePointOneDrive and SharePoint are case-insensitive: these two can’t sit in the same folder.Will failyes
Google DriveDrive lets two files share one name in a folder; a download or Drive for desktop turns one of them into “name (1)”.Likely troubleno
Google DriveDrive keeps both, but Drive for desktop on Windows or a Mac (case-insensitive) can’t put both in one folder.Likely troublewith “warnings too”
Google DriveDrive for desktop writes names to your disk, which stops at 255 characters.Likely troublewith “warnings too”
Zip fileAPPNOTE 4.4.17: “All slashes MUST be forward slashes”; a \ in a name unpacks as folders on Windows and as one odd name elsewhere.Likely troublewith “warnings too”
Zip fileAn absolute path or a .. component would unpack outside the target folder (“zip slip”); safe unzip tools refuse it.Will failno
Zip fileUnzipping on Windows or a Mac overwrites one of these with the other.Likely troublewith “warnings too”
Zip fileNon-ASCII name: zips made without the UTF-8 flag (old Windows Explorer, some phones) unpack it as garbled text.Worth knowingno
Web server / S3 linksIn a link, a space must be %20, # ends the path, ? starts a query, % starts an escape, & and + are read as query syntax, and " < > \ ^ ` { } | are not allowed at all; links copied by hand break.Likely troublewith “warnings too”
Web server / S3 linksA final period gets dropped by Windows clients and some servers, so the link points nowhere.Likely troublewith “warnings too”
Web server / S3 linksNon-ASCII letters are percent-encoded in links (é = %C3%A9); fine in browsers, but some tools and S3 signatures trip on them.Worth knowingno
Web server / S3 linksWeb servers and S3 are case-sensitive: these are different links, and a link typed in the wrong case is a 404.Worth knowingno

Sources

Rules last checked against these pages on 2026-11-13.