The first thing that confuses people about WSL is files: you open the Linux terminal, type ls, and your photos and documents are nowhere to be seen. They’re not gone — Linux just starts you in its own home directory, and your Windows files live one short path away. Once you know how the two file systems connect, every WSL tool can work on your real files directly.
This is the piece that makes the task guides usable, so it’s worth getting straight. If WSL isn’t installed yet, see the WSL install guide.
Your Windows files live under /mnt
WSL mounts your Windows drives under /mnt. The drive letter becomes a folder:
C:→/mnt/cD:→/mnt/d
So a path like C:\Users\YourName\Pictures is reached with:
cd /mnt/c/Users/YourName/Pictures
lsNow ls shows your actual photos, and any Linux tool you run here reads and writes them in place — output saved right beside the originals.
Windows path to WSL path
| C:\\Users\\You\\Pictures | /mnt/c/Users/You/Pictures |
|---|---|
| C:\\Temp\\file.jpg | /mnt/c/Temp/file.jpg |
| D:\\Media\\clip.mp4 | /mnt/d/Media/clip.mp4 |
The rule: replace the drive letter with /mnt/<letter> and flip backslashes to forward slashes.
Finding the right path fast
Typing long paths is error-prone. Two shortcuts:
- Copy the path from File Explorer’s address bar, then convert it with the rule above.
- Let WSL do the conversion with
wslpath:
wslpath "C:\Users\YourName\Pictures"That prints the /mnt/c/... version, ready to paste into a cd.
Going the other way: Linux files in Windows
It works in reverse too. From any WSL folder, open it in File Explorer with:
explorer.exe .The . means “the current folder.” To browse your whole Linux file system from Windows, type this into the Explorer address bar:
\\wsl$(On newer builds, \\wsl.localhost does the same.) You’ll see your installed distributions; inside each, your Linux home directory is under /home/<username>.
The performance gotcha
Here’s the one thing worth knowing before you do heavy work: crossing between the two file systems has a cost. Tools running on files under /mnt/c are slower than the same tools running on files inside the Linux file system.
For a one-off conversion or a small folder, the difference is irrelevant — just work in /mnt/c. But if you’re processing hundreds of large files or running something repeatedly, copy them into your Linux home first, work there, then copy results back:
cp -r /mnt/c/Users/YourName/BigBatch ~/work
cd ~/work
# ...run your heavy processing here...
cp -r ~/work/output /mnt/c/Users/YourName/BigBatch/A practical routine
For most everyday jobs, this is all you need:
Working on your files in WSL
- cd into the folder under /mnt/c
- Run the tool's command on the files there
- Output appears next to the originals
- For big repeated jobs, copy into ~ first for speed
- Use explorer.exe . to jump back to Windows
Wrapping up
Accessing your files across WSL is two ideas: Windows drives appear under /mnt (so C: is /mnt/c), and your Linux files show up in Windows via \\wsl$ or explorer.exe .. Convert paths by swapping the drive letter for /mnt/<letter> and the slashes, or let wslpath do it. The only catch is performance — work inside your Linux home for heavy, repeated jobs, and /mnt/c for everything casual.
With the file bridge clear, the task guides drop into place. See 10 useful things you can do with WSL and the tools worth installing first.
