CristGuard

Bash

Copy Files from Windows to Windows Subsystem for Linux WSL closed

19 September 2026 · 9 min read

Copy Files from Windows to Windows Subsystem for Linux WSL closed

Working between Windows and the Windows Subsystem for Linux (WSL) offers developers a powerful and versatile environment. A common task is needing to copy files from Windows to Windows Subsystem for Linux. This process allows you to leverage Windows’ GUI applications alongside Linux’s command-line tools and development environments. Whether you’re moving code, configuration files, or data sets, understanding the correct methods for file transfer is crucial for a seamless workflow. This guide will walk you through several reliable techniques to efficiently and securely transfer files between the two systems, ensuring you can make the most of both Windows and WSL.

Understanding the Windows and WSL File Systems

Before attempting to copy files from Windows to Windows Subsystem for Linux, it’s important to understand how the file systems are structured and accessed. Windows file systems are typically located under drive letters such as C:\, D:\, etc. WSL, on the other hand, maintains its own separate file system, which is accessed differently depending on the WSL version you are using.

With WSL 1, the Linux file system is stored as a single file on your Windows drive, making direct access somewhat limited. However, WSL 2 introduced a virtualized hard drive, which significantly improves file system performance and allows for more direct access. Understanding these differences is key to choosing the right method for file transfer. It’s also important to consider the security implications and permissions when moving files between the two environments. Incorrect file permissions can lead to errors or security vulnerabilities. According to Microsoft’s documentation, WSL 2 offers a 20x increase in file system performance compared to WSL 1 for certain operations [1].

Knowing the underlying mechanics of file storage in both Windows and WSL will help prevent potential problems when transferring files. For example, be aware of case sensitivity in Linux file systems, which differs from Windows’ default behavior. Also, keep in mind that certain file types, such as symbolic links, might behave differently when moved between the two environments.

Methods to Copy Files from Windows to WSL

Several methods exist to copy files from Windows to Windows Subsystem for Linux. Each method has its own advantages and disadvantages, depending on the size and number of files you are transferring, as well as your comfort level with command-line tools. Here are some of the most common approaches:

  • Using the Command Line (cp and mv): The cp (copy) and mv (move) commands are fundamental Linux tools for file manipulation. These commands can be used within the WSL terminal to copy files from the Windows file system.
  • Using Windows Explorer: Windows Explorer offers a graphical interface for copying and pasting files between the two systems. This method is generally easier for users who are less familiar with the command line.
  • Using Network Shares: Setting up a network share allows you to access files on your Windows machine from within WSL as if they were on a remote server.

The command-line method is often preferred for its speed and flexibility, especially when dealing with large numbers of files or when automating the transfer process. Windows Explorer is best suited for smaller, ad-hoc transfers. Network shares provide a more persistent and integrated solution, but they require more initial setup. Choosing the best method depends on your specific needs and workflow.

For example, if you’re a data scientist needing to transfer a large dataset from a Windows-based storage drive to a WSL environment for analysis using Python, using the command line with tools like rsync (discussed later) would be significantly faster than dragging and dropping files in Windows Explorer. Conversely, if you simply need to copy a single configuration file, Windows Explorer might be the quicker and easier option.

Step-by-Step Guide: Using the Command Line

This section provides a detailed guide on how to copy files from Windows to Windows Subsystem for Linux using the command line. This method involves using the cp command, which is a standard Linux utility for copying files and directories.

To use the command line, you’ll first need to open your WSL terminal. Then, you’ll use the cd command to navigate to the directory where you want to place the copied files within your WSL file system. The Windows file system is typically mounted under the /mnt directory in WSL. For example, your C drive would be accessible at /mnt/c/. From there, you can use the cp command to copy files from your Windows drive to your desired WSL location. For instance, to copy a file named “myfile.txt” from your Windows desktop to your WSL home directory, you would use the following command: cp /mnt/c/Users/YourUsername/Desktop/myfile.txt ~.

Here’s a step-by-step breakdown:

  1. Open your WSL terminal.
  2. Navigate to the destination directory in WSL using the cd command (e.g., cd ~ for your home directory).
  3. Identify the source file in your Windows file system (e.g., /mnt/c/Users/YourUsername/Documents/myfile.txt).
  4. Use the cp command to copy the file: cp /mnt/c/Users/YourUsername/Documents/myfile.txt . (the . represents the current directory).
  5. Verify the file has been copied successfully using the ls command.

A key element of copying files between Windows and WSL is understanding how to access your Windows files from within the WSL environment. The Windows file system is automatically mounted under the /mnt directory in WSL distributions. Each drive letter in Windows corresponds to a directory under /mnt, such as /mnt/c/ for the C: drive, /mnt/d/ for the D: drive, and so on. This mounting allows you to navigate your Windows file system using standard Linux commands like cd, ls, and cp, making file transfer straightforward. Knowing this path is essential for effectively managing files between the two systems.

For more advanced users, rsync and symbolic links offer powerful options for managing files between Windows and WSL. rsync is a versatile file transfer program that is particularly useful for synchronizing files and directories between two locations. It only copies the differences between files, making it much faster than cp for large files or directories that have only been partially modified. Symbolic links, also known as symlinks, are essentially shortcuts to files or directories. They allow you to create links within your WSL file system that point to files or directories on your Windows drive, or vice versa.

To use rsync, you’ll need to install it within your WSL environment using your distribution’s package manager (e.g., sudo apt install rsync on Ubuntu). Once installed, you can use rsync to synchronize files between Windows and WSL. For example, to synchronize a directory named “myproject” from your Windows documents folder to your WSL home directory, you would use the following command: rsync -av /mnt/c/Users/YourUsername/Documents/myproject/ ~/myproject/. The -av options specify that rsync should operate in archive mode (preserving permissions and timestamps) and be verbose (showing the files being transferred).

Infographic here showcasing the different file transfer methods and their pros/cons
Symbolic links can be created using the ln -s command. For instance, to create a symbolic link in your WSL home directory that points to a directory on your Windows drive, you would use the following command: ln -s /mnt/c/Users/YourUsername/Documents/myproject ~/myproject\_link. This creates a link named "myproject\_link" in your WSL home directory that points to the "myproject" directory on your Windows drive. Keep in mind that symbolic links can sometimes behave unexpectedly when crossing file system boundaries, so it's important to test them thoroughly.

FAQ: Common Questions about File Transfer

How do I access my Windows files from WSL?
Your Windows drives are mounted under the /mnt directory in WSL. For example, your C drive is accessible at /mnt/c/.
Can I copy files from WSL to Windows using Windows Explorer?
Yes, you can access the WSL file system from Windows Explorer by typing \\\\wsl$ in the address bar. Then, navigate to your desired WSL distribution and access its files.
What is the fastest way to transfer large files?
For large files, using rsync is generally faster than cp because it only copies the differences between files. Setting up a network share can also be efficient for ongoing transfers.
Are there any security considerations when copying files?
Yes, be mindful of file permissions when copying files between Windows and WSL. Incorrect permissions can lead to security vulnerabilities or access errors. Always verify that the permissions are set correctly after transferring files. According to a report by Snyk, misconfigured file permissions are a common source of security vulnerabilities in Linux environments [\[2\]](https://snyk.io/blog/10-linux-security-best-practices/).
Understanding these common questions and their answers can help you troubleshoot any issues you encounter when transferring files between Windows and WSL.

The ability to seamlessly copy files from Windows to Windows Subsystem for Linux enhances productivity and streamlines workflows. By understanding the different methods available, from the basic command-line tools to more advanced techniques like rsync, you can choose the approach that best suits your needs. Remember to consider file system differences, permissions, and security implications when moving files between the two environments. If you want to explore more about optimizing your WSL environment, check out this detailed guide.

  • Always verify file permissions after transfer.
  • Use rsync for efficient synchronization of large files.

With the knowledge you’ve gained, you’re now well-equipped to manage your files effectively between Windows and WSL. Experiment with the different methods discussed and find the workflow that works best for you. Further enhance your understanding by exploring Microsoft’s official WSL documentation [3] and practicing these techniques. Happy coding!

Question & Answer :

I have enabled developer mode and installed `Bash on Ubuntu on Windows`.

My home directory can be found under %localappdata%\Lxss\home\<ubuntu.username>\, i have created a sub-directory called Pictures such that the full path should be

on windows: C:\Users\<windows.username>\AppData\Local\lxss\home\<ubuntu.username>\Pictures

on bash: /home/<ubuntu.username>/Pictures

if i create a file from bash using the command touch hello.txt i can freely see this file in the windows UI and copy it to my Desktop. However, if i create a new text file from the windows UI and save it in C:\Users\<windows.username>\AppData\Local\lxss\home\<ubuntu.username>\Pictures, even if i restart bash or windows, the file is not visible when i do ls -l.

Why can’t bash see files created from the Windows side in it’s own home directory?

EDIT Using /mnt/c is not a solution, i am trying to understand why it doesn’t see those files and if there is a remedy to that so that it will be able to see UI created files, rather than trying to use the terminal to copy-paste or move files over.

You should be able to access your windows system under the /mnt directory. For example inside of bash, use this to get to your pictures directory:

cd /mnt/c/Users/<windows.username>/Pictures