Characters Not Allowed in File Names (Windows, Mac, Linux, OneDrive) and How to Fix a Whole Folder
Windows blocks 9 characters in file names. OneDrive blocks more. Here's the exact list for Windows, Mac, Linux and OneDr…
Read article →Paste a list of file paths and check them against real Windows, macOS, and Linux filesystem rules before you deploy, sync, or commit them.
A file path that works fine in development can fail silently (or loudly) once it hits a different operating system — a reserved Windows name like CON.txt, a path over 260 characters, two files differing only by case. Checking a full path list against these real rules before deploying or syncing avoids debugging that failure in production.
Linux filesystems are case-sensitive, so "Report.pdf" and "report.pdf" can coexist there — but the same two files collide on Windows and on macOS's default filesystem, silently overwriting one another during a cross-platform copy or sync.
CON, PRN, AUX, NUL, COM1 through COM9, and LPT1 through LPT9 — using any of these as a filename (with or without an extension) causes errors on Windows specifically.
260 characters is the traditional Windows limit (still relevant for older tools and some network drives); modern Windows can support longer paths if explicitly configured, but 260 is the safest conservative default.
No — it validates path strings against filesystem naming rules only; it doesn't check anything against a real filesystem.
Be the first to share your experience with this tool — your feedback helps others.