How to convert path separators
Windows separates folders with a backslash while Linux, macOS, Git and most web tooling use a forward slash. Pasting a path copied from Windows Explorer straight into a terminal or a config file is therefore one of the most common reasons a file cannot be found. This tool walks through the text line by line and rewrites only the separators, keeping the number of lines and their order intact so you can convert a whole list at once.
The scope is deliberately narrow and stated up front. A leading double separator is recognised as a UNC network prefix and preserved. A drive letter such as C: is left untouched, because turning it into the WSL path /mnt/c or a macOS mount point depends on your machine; when such lines appear, a note tells you so. Collapsing repeated separators is off by default and, when enabled, merges duplicate separators everywhere except the UNC prefix.
One caveat matters: text copied out of source code. An escaped double backslash inside a string literal is read here as two separators, so converting it leaves two slashes behind. Turn the collapse option on for that case, or paste the raw path instead. The result panel reports how many lines were processed and how many separators actually changed, so you can confirm the conversion did what you expected.
Frequently asked questions
Yes. A leading double separator is treated as a UNC prefix and kept, and the result tells you how many lines were affected. Collapsing repeated separators never merges that prefix while the option is on.
Only the separators change, so C: stays exactly as it is. Rewriting it to a mount path such as /mnt/c depends on your environment, so the tool leaves that decision to you.
Every backslash is treated as a separator, so an escaped double backslash becomes two separators. Turn on the collapse option to merge them, or paste the raw path instead of the code literal.