Path Validator
Paste a list of file paths and check them against real Windows, macOS, and Linux filesystem rules before you deploy, sync, or commit them.
How to use Path Validator
- Use these example values as a starting point: src/components/Header.jsx docs/CON.md assets/images/photo final.jpg src/Utils.js src/utils.js.
- Set the inputs and options shown here: File paths (one per line), Max path length.
- Run the tool with Validate Paths.
- Review the results, then choose an output control: Export Report.
Catching filesystem problems before deployment, not after
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.
Why case-only collisions matter even on Linux
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.
What are the Windows reserved names?
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.
What's a safe max path length to check against?
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.
Does this check if the paths actually exist?
No — it validates path strings against filesystem naming rules only; it doesn't check anything against a real filesystem.