Path Case Converter — Text to path/case Online
Convert text to path/case — words joined with forward slashes for file paths and URL segments. Free, instant, client-side path case converter.
🔒 100% Client-Side Processing
Your data is processed entirely in your browser and never transmitted to any server.
Input
getUserProfile Output
get/user/profile camelCase boundaries are split automatically — no need to insert spaces first. Hyphens and underscores work the same way.
Common Use Cases
Designing URL routes
Convert a feature name such as "user profile settings" into the user/profile/settings segment structure before wiring it into a router or a static site generator.
Creating folder structures
Turn a description of a document hierarchy into the slash-separated directory path to create, ready to hand straight to mkdir -p in a terminal.
Building object storage keys
S3 and similar object stores have no real folders, only slash-delimited keys that display as folders in a console, and this produces exactly that shape.
Laying out documentation paths
Derive the nested path for a documentation page from its title, so the published URL mirrors the navigation hierarchy that readers already see in the sidebar.
Frequently Asked Questions
- What is path/case used for?
- File system paths, URL segments, and object storage keys — words lowercased and joined with forward slashes, so "user profile settings" becomes user/profile/settings. Anywhere a name needs to express nesting that a filesystem, router or bucket will interpret, the slash is the separator that does it.
- Does it handle camelCase input?
- Yes, automatically. Case boundaries are treated as word breaks, so getUserProfile becomes get/user/profile with no manual spacing required. Hyphens, underscores and punctuation are handled the same way, and accented characters fold to ASCII first, so "Café Menu Items" becomes cafe/menu/items.
- Is the result an absolute path?
- No. There is no leading slash, so what you get is a relative path — user/profile/settings rather than /user/profile/settings. Add the leading slash yourself if you need an absolute filesystem path or a root-relative URL route, since which one you want depends entirely on where it is going.
- Can I use this output as a filename?
- No. A forward slash is the path separator, so it can never appear inside a single filename — the output is a directory structure, not a name. For one safe filename segment, use Slugify or the Kebab Case Converter, both of which join words without introducing a separator character.
- Does this work on Windows?
- Mostly. Windows APIs and Node's path module accept forward slashes almost everywhere, and browsers and web servers always do. The exceptions are shell commands and some older tooling that still expect backslashes, so convert the separators at that boundary rather than assuming they will pass through unchanged.
- Is my data private when I use this tool?
- Yes. This tool runs entirely in your browser using client-side JavaScript — nothing you type is transmitted to, logged by, or stored on any server. You can safely process confidential text, tokens, or code.