Path Format Converter

Features

• All four forms at once: Windows (backslashes), portable (forward slashes), WSL (/mnt/c) and Git Bash (/c)
• Recognises drive letters, /mnt/c, /c, UNC network paths (\\server\share) and relative paths, and says which it read it as
• ⚠️ The trailing slash is preserved and re-applied with the target notation’s own separator (the Windows form gets a backslash, never C:\a\b/)
• UNC and absolute Unix paths with no equivalent say so in words rather than inventing something
• Multiple lines supported, grouped per line
• Optional collapsing of repeated separators
• Deliberately does not “replace every backslash with a forward slash”: on Linux a backslash is a legal filename character, so character-by-character replacement points at a different path

How to use

1. Paste one path per line
2. Turn on “collapse repeated separators” if you want it
3. The result gives all four forms per line, with the reasoning

FAQ

What is the difference between /mnt/c and /c?

They are two different locations. `/mnt/c` is the WSL mount convention pointing at Windows drive C; Git Bash does not understand it. `/c` is the Git Bash (MSYS2) form, also pointing at drive C — but inside WSL, `/c` is an ordinary directory named c at the root. Pasting one into the other environment does not raise an error; it creates a folder in the wrong place. So this tool gives both and lets you pick the right one.

Why not just strip the trailing slash?

Because it changes what the command means. `cp -r src/ dest` and `cp -r src dest` behave differently when the destination does not exist, and `node scripts/` makes some tools treat it as a directory. So it is preserved — and re-applied with the target notation’s own separator: a backslash for the Windows form, a forward slash for the rest.

Why is there no Unix form for a UNC path?

The server part of `\\server\share\dir` is a host on the network, and it maps to no local mount point. WSL and Git Bash can each mount a network share, but in different ways — there is no universal form derivable from the path itself. So this says “no equivalent” rather than inventing a plausible-looking path that would appear usable.

Why not replace every backslash with a forward slash?

Because on Linux a backslash is a legal filename character: a file named `a\b` really can exist. Replacing its backslash points at a different (nonexistent) path, and nothing errors. So the reading is based on the shape of the whole path — is there a drive letter, is there a `/mnt/` — not on character-by-character replacement.