Path Case Converter — Free Online Tool
What is Path Case Converter?
Path Case (path/case) converts text to lowercase words separated by forward slashes, producing output like this/is/path/case. It mimics file system directory paths and URL route structures.
The format naturally represents hierarchical relationships, making it useful for API endpoint definitions, file path templates, and route parameters. This tool converts any input into clean, slash-separated lowercase output.
When to use Path Case Converter?
Use path/case for defining API route segments, file path templates in build tools, URL route parameters in web frameworks, and hierarchical identifiers. js) use path-like patterns for page routes.
If you need dot-separated hierarchy instead, try the Dot Case Converter. For hyphen-separated identifiers, use the Kebab Case Converter.
How to use this tool
- 1Paste your text
- 2Click 'Convert' to get path/case output
- 3Copy for file paths and routes
The tool lowercases all letters, detects word boundaries from spaces, hyphens, underscores, and camelCase transitions, then joins the words with forward slashes.
Examples
| Input | Output |
|---|---|
| Hello World | hello/world |
| user profile settings | user/profile/settings |
| API response handler | api/response/handler |
| my_config_key | my/config/key |
| background-color | background/color |
Rules & Behavior
- All words are converted to lowercase. Every letter in the output is a small letter, matching URL path conventions where paths are case-insensitive by convention.
- Words are separated by forward slashes (/). Spaces, hyphens, underscores, and other separators are replaced with single slashes to create a path-like structure.
- The output represents a hierarchical path structure. Each slash level implies a parent-child relationship, similar to file system directories or URL segments.
Related Tools
Frequently Asked Questions
What is path/case?
path/case uses forward slashes to separate lowercase words, mimicking file system paths or URL routes — like user/profile/settings. It is used for API route definitions, template paths, and hierarchical identifiers where the slash naturally represents nesting or categorisation.
When would I use path/case?
API route segment definitions (/api/user/profile), file path templates in build tools, URL-like identifiers in routing configurations, and hierarchical data references. Web frameworks like Express, Next.js, and Django use path-like patterns extensively for routing.
Is path/case the same as a URL path?
Similar, but URL paths can include query strings, fragments, and encoded characters. path/case is a pure naming convention for creating identifiers that follow a path-like hierarchy. It does not handle URL encoding — for that, use the URL Slug Generator.
Can it handle multiple levels?
Yes. Any multi-word input produces multiple levels of hierarchy. For example, 'user profile settings page' becomes user/profile/settings/page, creating a four-level path structure. There is no limit on the number of levels.
How does it handle existing slashes?
Existing slashes in the input are treated as word separators and preserved in the output. The tool normalises multiple consecutive slashes into single slashes to produce clean path output.