a Unix-style path
Matches a Unix-style path. It is anchored at both ends, so the whole string has to match. There are no capture groups.
Pattern
/^/(?:[^/\0]+/)*[^/\0]*$/- Match scope
- the whole string
- Capture groups
- 0
- What it catches in the first example
- /usr/local/bin
Try it yourself
Type any text and the parts this expression catches are highlighted. It runs in your browser and is never sent anywhere.
/usr/local/bin
1 match
Examples that match
- /usr/local/bin
- /
Examples that do not match
- usr/local
- C:\\Windows
Other expressions in this group
^[a-z][a-z0-9_]{2,15}$a username that starts with a letter^[a-z0-9]+(?:-[a-z0-9]+)*$a URL slug^[^\\/:*?"<>|]+\.[a-z0-9]+$a file name with an extension^.+\.(?:jpe?g|png|gif|webp|avif|svg)$an image file extension^[A-Za-z]:\\(?:[^\\/:*?"<>|]+\\)*[^\\/:*?"<>|]*$a Windows path^</?[a-z][a-z0-9]*(?:\s[^<>]*)?/?>$a single HTML tag^\.-?[_a-z][_a-z0-9-]*$a CSS class selector^M{0,3}(?:CM|CD|D?C{0,3})(?:XC|XL|L?X{0,3})(?:IX|IV|V?I{0,3})$a Roman numeralHow to read this
- With ^ and $ around it, the whole string must match; without them the match can sit anywhere. Always anchor an expression you use for validation.
- Round brackets ( ) capture what they wrap. When you only need grouping, write (?: ) so the numbering of later groups does not shift.
- Every expression here is checked against its examples. Even so, "looks like an email" and "is a real inbox" remain different questions.
- Nested open-ended repeats such as (a+)+ can blow up on certain inputs. Look for that shape before pasting someone else’s expression into your code.
Frequently asked questions
Q. What is the regex for a Unix-style path?
^/(?:[^/\0]+/)*[^/\0]*$.
Q. Which strings match?
Text like /usr/local/bin matches; text like usr/local does not.
Q. Does the whole string have to match?
Yes. It is wrapped in ^ and $, so nothing but a full match passes.
Q. How do I use what it caught?
There are no capture groups, so only the whole match (match[0]) comes back. Wrap the part you need in brackets to capture it.