TwinPane vs RDP Drive Redirection
Both let users move files between a remote desktop session and a local PC. They take different approaches, work in different situations, and have different blind spots. This page explains where each one is the right answer.
The short version
If you have to pick in 30 seconds:
- Your policies allow drive redirection.
- Users connect from macOS or Linux RDP clients.
- File sizes are small and the LAN is fast.
- You want zero install on host and client.
- Users only need occasional file access.
- Drive redirection is disabled by policy.
- Users run RemoteApp or Citrix published apps.
- File-open speed matters for the daily workflow.
- You want one consistent UX across AVD, RDS, RemoteApp, and Citrix.
- You need centralised licensing, deployment, and reporting.
What each one actually is
A quick refresher so the comparison table makes sense.
RDP drive redirection
A built-in feature of the Remote Desktop Protocol. Local drives are exposed inside the remote session as letters (typically \\tsclient). Files are streamed over the RDP virtual channel as the user reads or writes them. Controlled by the standard RDP Group Policy templates.
TwinPane
A standalone Windows service on the session host plus a lightweight client on the local PC. They pair automatically and stream files over their own encrypted channel — outside RDP. Designed specifically for opening remote files in the user's local applications, plus mirroring local folders into the remote session.
Head-to-head
The points that come up most often in IT decision-maker conversations.
| Capability | RDP drive redirection | TwinPane |
|---|---|---|
| File workflow | ||
| Open remote file in local app | Save & re-open manually | One double-click |
| Mirror local folders into the session | Mapped drives only | Quick Access pins point to local |
| Works in published apps (RemoteApp / XenApp) | No remote desktop to interact with | Designed for published apps |
| Policy & security | ||
| Works with redirection disabled by GPO | Is the redirection | Independent of RDP channels |
| Encryption in transit | RDP TLS | TLS 1.3 |
| Group Policy / ADMX templates | Built into Windows | TwinPane ADMX provided |
| End-user authentication | RDP login | Per-device licence, no extra login |
| Performance | ||
| Performance under heavy RDP load | Shares the RDP pipe | Independent compressed channel |
| Behavior on reconnect | Mapped drives often re-letter or drop | Re-pairs automatically, same paths |
| Reach | ||
| Local PC platforms | Windows / macOS / Linux / web RDP | Windows local PC only |
| Remote-side support | Any Windows host with RDP | AVD, RDS, RemoteApp, Citrix VDA |
| Deployment & cost | ||
| Install required | None — built in | MSI on host + client |
| Intune / SCCM packaging | N/A | Detection rules provided |
| Licensing | Free with Windows | €3 / device / month, 20 min |
| Centralised usage analytics | None | Built into the dashboard |
= strong fit · = not supported · = neutral / depends on context.
The cases drive redirection wasn't built for
Locked-down policy environments
Many enterprises disable client drive redirection by Group Policy or Intune. RDP's built-in answer disappears entirely — TwinPane is purpose-built to operate alongside locked-down RDP policies.
Published-app deployments
RemoteApp and Citrix published apps don't expose a desktop. Drag-and-drop is impossible, and mapped drives feel alien inside an Office open dialog. TwinPane gives users a real local-open from inside any published app.
Large-file workflows
CAD drawings, video, large Office documents. Drive redirection re-streams over the RDP pipe; TwinPane uses a dedicated compressed channel that doesn't compete with screen and input traffic.
Multi-platform fleets
Drive redirection behaves slightly differently on AVD, RDS, RemoteApp, and Citrix. TwinPane is one product with the same UX everywhere.
Reconnect resilience
Mapped drive letters routinely re-letter or drop after lock screens, network blips, and reconnects. TwinPane re-pairs automatically and the user-visible paths stay stable.
Centralised observability
The TwinPane dashboard shows licence usage, active sessions, and file activity across the estate. RDP drive redirection emits no central telemetry.
We are not pretending it's always wrong
RDP drive redirection is built into Windows, free, and genuinely good enough for several common situations. Be honest about which one you're in:
macOS or Linux endpoints
TwinPane requires a Windows local PC. If a meaningful share of your users connect from Mac or Linux RDP clients, drive redirection is the only option that covers them today.
Occasional, ad-hoc file access
If users open a remote file in their local app twice a month, the manual save-and-reopen workflow over a mapped drive is annoying but not broken — and you avoid an MSI rollout.
Small teams, no policy constraints
If drive redirection is allowed by policy and the team is a handful of users on a fast LAN, the speed gap is small and licensing has no payoff.
Single-platform, full-desktop deployments
If you only have AVD full desktops (no RemoteApp, no Citrix) and users always connect via the AVD client on Windows, drive redirection's rough edges are tolerable.
You can run both side-by-side
TwinPane and RDP drive redirection are independent. A common pattern is to leave drive redirection enabled for IT/admin RDP connections that come in from non-Windows endpoints, while deploying TwinPane to the standard end-user fleet for the everyday file-open workflow.
If your policies fully disable drive redirection, TwinPane slots in cleanly without changing any of those policies.
Drill into your specific stack
Each platform has its own quirks around drive redirection. Pick yours for the platform-specific take.
AVD file redirection alternative
How TwinPane fits into Azure Virtual Desktop deployments specifically.
RDS: open remote files locally
TwinPane on Windows Server RDSH multi-session hosts.
Citrix XenApp local file opening
TwinPane on Citrix VDAs (CDM is the Citrix equivalent of drive redirection).
RemoteApp without drive redirection
Published-app file workflows when redirection is policy-blocked.
Frequently asked questions
Can we run TwinPane and RDP drive redirection at the same time?+
Yes. They are independent. Some teams keep RDP drive redirection enabled for occasional admin use while running TwinPane as the everyday file-open path for users. Others keep redirection disabled by policy and use TwinPane exclusively.
Is RDP drive redirection always slower than TwinPane?+
Not always. For small files on a low-latency LAN with a lightly used RDP session, the difference is small. The gap widens with file size, latency, and concurrent RDP load — and disappears entirely if your policies disable drive redirection.
Does TwinPane work on macOS or Linux RDP clients?+
No. TwinPane requires a Windows local PC because it integrates with Windows file associations and Explorer. RDP drive redirection works from macOS and Linux RDP clients — that is one case where drive redirection is the right answer.
Will switching to TwinPane break our existing RDP Group Policy?+
No. TwinPane runs as a separate, signed Windows service. Your existing RDP Group Policy — including disabled drive, clipboard, and printer redirection — keeps working exactly as it does today.
Do users need an account or login to use TwinPane?+
No end-user login. Each Windows client device is activated once with a license key, then auto-pairs with the matching server in the AVD / RDS / Citrix / RemoteApp session.