Regex to Match Unix File Paths

This regex validates absolute Unix/Linux file paths. Here is the token-by-token breakdown:

^ — Anchors the match at the start of the string.

(?: — Opens a non-capturing group for each path segment.

/ — Matches a literal forward slash, the Unix path separator.

[\w.-]+ — A character class matching one or more valid path segment characters. \w matches word characters (letters, digits, underscore), and we also allow dots (for file extensions and hidden files like .bashrc) and hyphens (common in directory and file names). The + requires at least one character per segment, preventing consecutive slashes.

)+ — Closes the non-capturing group and repeats it one or more times. This matches one or more path segments, each starting with a slash.

/? — Matches an optional trailing forward slash. Unix paths can optionally end with a slash to indicate a directory.

$ — Anchors the match at the end of the string.

This pattern matches paths like /usr/local/bin, /home/user/file.txt, /var/log/, and /etc/nginx/nginx.conf. It requires an absolute path starting with / and does not match relative paths like ./config or ../parent.

The pattern does not allow spaces in path names. If you need to support spaces, add a space to the character class: [\w. -]+. It also does not match the root path / by itself, since the group requires at least one character after each slash. For a more permissive pattern, you could add the root as an alternative.