中文版本： 《远程会话中怎么传文件》
You're remoted into a colleague's machine to debug a bug. They have a log file you need on your laptop. How do you get it across? There are four common patterns, with very different tradeoffs.
Pattern 1: Clipboard
The simplest. Copy a file in the remote machine's file manager, paste in your local one. Works for small files (most tools cap at 10-50 MB for clipboard transfers).
Best for: Quick sharing of small files, single items.
Watch out for:
- File size limits vary by tool.
- Some tools transfer file contents through the relay (not E2EE) even when the session itself is.
- Permission-sensitive transfers — check whether the transfer is logged.
Pattern 2: Drag-and-Drop
Drag from the remote window directly onto your local desktop or file manager. The tool handles the actual transfer underneath.
Best for: Visual workflows, one-off transfers.
Watch out for:
- Performance: dragging large files through the remote display protocol is slower than dedicated file transfer.
- Behavior varies: some tools require both ends to use the same OS for drag-and-drop to work cleanly.
Pattern 3: Mounted Drive
The tool exposes your local drive as a network share on the remote machine (and vice versa). Files appear in the remote machine's file manager as if they were on a USB drive.
Best for: Sustained file work — editing a document remotely that lives on your local machine, or vice versa.
Watch out for:
- Latency: every file open is a network round trip. Don't compile code from a mounted drive — it'll be 10× slower than copying first.
- Security: a mounted drive can give the remote OS more access than you intend. Verify which directories are shared.
Pattern 4: Dedicated Transfer Panel
The tool has a separate "file transfer" UI, often a side panel or modal. You queue files, they transfer in the background with progress bars.
Best for: Large files, batches, anything where reliability matters more than convenience.
Watch out for:
- Look for resume-on-failure for very large transfers.
- Check whether transfers compete with screen-share bandwidth or use a separate channel.
Which to Use When
| Scenario | Pattern |
|---|---|
| "I need this 200 KB config file" | Clipboard |
| "Drop this design file over there" | Drag-and-drop |
| "I'm going to edit these docs for an hour" | Mounted drive |
| "Move this 5 GB project archive" | Dedicated transfer panel |
| "Move a folder of 10,000 small files" | Dedicated transfer (or zip first) |
Security Considerations
File transfer is the biggest pre-attack surface in remote desktop. A few guardrails:
- Disable file transfer for support sessions unless explicitly needed for that ticket.
- Log every transfer — what file, who, when, in which direction. For compliance.
- Scan transferred files for malware on the receiving side. Don't trust the remote machine.
- Set per-session size limits for support sessions to prevent data exfiltration.
For more, see Remote Desktop Security Best Practices.
A Common Mistake
People copy a 2 GB file through the clipboard, watch it fail at 50%, and conclude "the tool is broken." It's not — they used the wrong pattern. Clipboards are not transfer protocols. Use a dedicated transfer for anything you wouldn't email.
What to Read Next
- Setting up for a team: How to Set Up Remote Desktop Access for Your Team
- Security baseline: Remote Desktop Security Best Practices
- Compliance angle: Is Your Remote Desktop HIPAA / SOC 2 Compliant?