How to Transfer Files Over Remote Desktop in Windows: 5 Easy Methods

If you’ve ever connected to a remote PC and then wondered how to actually get a file from your computer onto it (or vice versa), you’re not alone.

Remote Desktop Connection doesn’t make this obvious. There’s no drag-and-drop icon staring you in the face, and one wrong clipboard setting will make it look like file transfer simply doesn’t work.

The good news: it does work, and once you know where the settings live, it takes under a minute to set up.

Quick answer: The fastest way to transfer files over Remote Desktop is to enable Clipboard and Drive redirection under Show Options → Local Resources before you connect. Once connected, you can copy-paste or drag-and-drop files between your PC and the remote session, or browse your local drives from inside the remote session via This PC → Redirected Drives.

Below, I’ll walk through five methods, from the built-in RDP tricks to third-party tools for Windows Home users, plus the fixes for the errors people run into most often.

Before You Start: What You Need

• Remote Desktop Connection (RDP) works out of the box only if the remote PC is running Windows 10/11 Pro, Enterprise, or Education. Windows Home can’t host an incoming RDP connection (more on the workaround below).
• You’ll need the remote PC’s IP address or hostname and a username/password with access to it.
• Both machines should be on the same network, or connected through a VPN/port-forwarding setup if you’re connecting over the internet.
• A stable connection matters more than people expect. If your Wi-Fi keeps dropping mid-transfer, it’s worth confirming your network doesn’t have IP configuration issues before you start moving large files.

Method 1: Copy and Paste (Fastest for a Few Files)

This is the method most people actually want. Here, there is no drive mapping, no third-party software, just Ctrl+C and Ctrl+V between your local machine and the remote session.

1. Open Remote Desktop Connection (press Windows + R, type mstsc, hit Enter).
2. Click Show Options in the bottom-left corner.
3. Go to the Local Resources tab and make sure Clipboard is checked.
4. Connect to the remote PC as usual and sign in.
5. On the source computer (local or remote), select the file, right-click, and choose Copy (or press. Ctrl + C).
6. Switch to the destination computer’s window, right-click where you want the file, and choose Paste (or Ctrl + V).

Good for: a handful of documents, images, or small files you need right now.

Watch out for: Microsoft’s clipboard redirection silently fails on any single file larger than 2 GB. The copy will appear to do nothing, and you won’t get an error message. If that happens, switch to drive redirection (Method 3) instead.

Method 2: Drag and Drop

If Clipboard redirection is already enabled, you can also drag files directly between the local desktop and the remote session window, the same way you’d drag a file between two folders.

1. Confirm Clipboard is enabled under Show Options → Local Resources (same as Method 1).
2. Arrange your local File Explorer window and the Remote Desktop window so both are visible, side by side works best.
3. Click and hold the file in one window, drag it across, and release it in the destination window.

This works well for one or two files, but gets clunky fast with dozens of files or nested folders. For bulk transfers, drive redirection is more reliable.

Method 3: Drive Redirection (Best for Bulk Transfers)

Drive redirection mounts your local drives inside the remote session, so you can browse and copy files exactly like you would locally. It’s the most robust of the built-in methods and the only one that handles files over 2 GB without issue.

Step 1: Enable Remote Desktop on the host PC

1. Right-click the Start button and choose Settings.
2. Click System.
3. Select Remote Desktop from the left pane.
4. Turn on the Remote Desktop toggle and click Confirm.

Step 2: Find the remote PC’s IP address

On the remote computer:

1. Open Settings → Network & Internet.
2. Click Wi-Fi or Ethernet, then click your active connection.
3. Note the IPv4 address and the username of that PC; you’ll need both.

Step 3: Connect and share your local drives

1. Search for Remote Desktop Connection in the Start menu and open it (running as administrator avoids some permission issues).
2. Click Show Options → Local Resources → More.
3. Expand the categories and check the boxes for the drives or folders you want available during the session.
4. Click OK, then go to the General tab and enter the remote PC’s username and IP address.
5. Click Connect, confirm the prompt, and enter the remote PC’s password.

Step 4: Access your files from inside the session

1. On the remote desktop, open File Explorer.
2. Click This PC.
3. Your shared drives will appear under Redirected Drives and Folders.
4. Copy and paste files between the redirected drive and the remote PC’s local storage as needed.

Transfer speed depends on both machines’ specs and your internet or LAN speed, so expect it to run a bit slower than a local copy-paste. That’s normal, not a sign that anything is broken.

If you’re regularly moving large files or working with limited local storage, keeping a fast external SSD like the Samsung T7 portable SSD (view on Amazon) on hand makes it easy to stage files locally before an RDP session instead of waiting on a slow redirected-drive transfer.

Related: Is Your Hard Drive Clicking? Here’s What You Need to Know

Method 4: FTP or SFTP (Best When Drive Sharing Is Blocked)

Some networks, especially corporate ones, disable the clipboard and drive redirection entirely for security reasons. If that’s the case for you, FTP (File Transfer Protocol) or SFTP (Secure FTP) works independently of Remote Desktop’s built-in features.

1. Install an FTP or SFTP server on the remote system (Windows includes a built-in SFTP-compatible option via OpenSSH Server, which you can add under Settings → Apps → Optional Features).
2. On your local machine, connect using an SFTP client. Windows’ File Explorer supports basic SFTP connections, or you can use a dedicated client for more control.
3. Enter the remote PC’s IP address and credentials to connect.
4. Drag and drop files between the local and remote file panes, just like a normal file manager.

Good for: networks where RDP drive/clipboard redirection is locked down by policy, or when you need a persistent, always-on way to move files that doesn’t depend on keeping an RDP session open.

Trade-off: standard FTP sends data unencrypted, so stick to SFTP unless you’re on a fully trusted, isolated network.

Method 5: Third-Party Remote Desktop Tools (Best for Windows Home)

If the remote PC runs Windows 10 or 11 Home, it can’t accept incoming RDP connections at all. Microsoft reserves that feature for Pro, Enterprise, and Education.

Third-party remote access tools fill that gap, and most include a dedicated file-transfer panel that’s more visual than dragging files through an RDP window.

AnyViewer is one option built specifically around this use case:

1. Download and install AnyViewer on both the local and remote computers.
2. Sign up for a free account and log in on the local PC.
3. Log in to the same account on the remote PC. This links both devices automatically.
4. On the local PC, open the Device tab, select the remote computer, and click File Transfer.
5. In the File Transfer window, select your files and use the arrow buttons to move them in either direction.

Free accounts are typically capped on transfer speed and thread count; paid tiers raise those limits along with the maximum file size per transfer.

Other tools in this category worth knowing about, useful if AnyViewer’s account-based model isn’t for you, include lightweight, link-based remote access apps that skip account creation entirely and connect through a one-time session link instead.

Good for: Windows Home users, anyone supporting non-technical family members remotely, or situations where you want a visual file browser instead of drive redirection.

Related: How to Block Specific Devices from Your WiFi Router

Comparison: Which Method Should You Use?

Common Mistakes to Avoid

• Forgetting to enable the Clipboard before connecting. It has to be turned on before you connect. Toggling it mid-session won’t retroactively fix a stalled transfer.
• Trying to copy a file over 2 GB with clipboard redirection. It fails silently with no error message. Use drive redirection instead.
• Assuming Windows Home can host RDP sessions. It can only initiate outgoing connections, not accept incoming ones. You need Pro/Enterprise on the host side, or a third-party tool.
• Not checking drive redirection separately from the clipboard. They’re two different checkboxes. Clipboard alone only moves plain text and small files. Full drive browsing needs drive redirection enabled, too.
• Ignoring firewall or antivirus prompts the first time you connect, which can silently block redirected drives from appearing.

Troubleshooting: Fixing Common RDP File Transfer Problems

Copy-paste isn’t working at all

1. Confirm Clipboard is checked under Show Options → Local Resources on the client.
2. On the remote machine, open Task Manager, end the rdpclip.exe process, then relaunch it (Run → rdpclip.exe). This resets a stalled clipboard channel without ending your session.
3. If it still fails, log off the remote session completely and reconnect. This clears most clipboard sync issues.

Redirected drives aren’t showing up under “This PC”

• Double-check that you selected the correct drives under Local Resources → More before connecting. This setting doesn’t apply retroactively to an active session.
• On managed or work networks, drive redirection may be disabled by Group Policy. Check with your IT administrator if you don’t see the option at all.

A large file transfer fails with no error message

• This is almost always the 2 GB clipboard-redirection limit. Switch to drive redirection, which has no such cap.

File transfer works, but is extremely slow

• Transfer speed is bound by the slower of your two internet/LAN connections. If both machines are on solid connections but speeds are still poor, check your Wi-Fi channel settings. Channel congestion is a common, overlooked cause of sluggish remote sessions.

Expert Tips for Smoother Remote File Transfers

• Enable only the drives you need. Sharing your entire C: drive when you only need one folder slows down the session’s initial handshake and clutters the redirected-drives list.
• Use a wired connection on at least one end if you’re transferring large batches of files. Wi-Fi instability is the most common cause of stalled or corrupted transfers.
• Run Remote Desktop Connection as administrator on the local machine if you notice drive redirection permissions behaving inconsistently.
• Compress folders before transferring if you’re moving many small files. A single zipped archive transfers noticeably faster than thousands of individual files over RDP.

If your remote sessions regularly involve large file batches, a reliable Ethernet cable like the Jadaol Cat 6 Ethernet Cable on Amazon for the host machine can meaningfully cut transfer times compared to relying on Wi-Fi alone.

Myth vs. Fact

Security Considerations

Remote Desktop is generally considered safer than routing sensitive files through cloud storage, since the data moves directly between the two machines rather than sitting on a third-party server. That said, a few habits matter:

• Only enable RDP access when you need it, and turn it off afterward if the PC is on a shared or public network.
• Use a strong, unique password on any account with RDP access. This is the single most common way RDP sessions get compromised.
• If you’re connecting over the internet rather than a local network, use a VPN rather than exposing port 3389 directly.

Related: Is Guest WiFi Safe? How to Create a Secure Guest Network

Conclusion

Moving files over Remote Desktop isn’t complicated once you know the two settings that actually matter: Clipboard and Drive redirection, both tucked under Show Options → Local Resources.

For quick, small transfers, copy-paste or drag-and-drop gets the job done in seconds. For bulk transfers or files over 2 GB, drive redirection is the more reliable choice.

And if the remote PC runs Windows Home, a third-party tool like AnyViewer, or an SFTP setup if you want something account-free, closes that gap entirely.

Whichever method fits your situation, the setup takes a couple of minutes and saves you from routing sensitive files through cloud storage just to get them from one PC to another.

Frequently Asked Questions