Can You Use a Local Clipboard Shelf Over Fullscreen RDP?

A local clipboard shelf that hovers on the edge of your physical monitor cannot see anything you copy inside a Remote Desktop fullscreen session. The moment the RDP window goes fullscreen, the remote machine has its own clipboard, its own Win+V history, and its own clipboard-watching processes. Your local shelf is watching an empty clipboard. This guide explains why the boundary exists, what RDP's clipboard redirection actually does, and the practical workflows that work around it.

For related multi-monitor context, see virtual desktops and always-on-top shelves and clipboard tools on multi-monitor Windows setups.

The two-clipboard problem

Every Windows machine has exactly one clipboard per session. A local session has a local clipboard. A remote session, when RDP clipboard redirection is on, has its own clipboard. RDP's clipboard redirection does not unify the two clipboards into one — it relays changes between them, with restrictions.

When you copy text inside the RDP session:

1. The remote machine's clipboard gets the text.
2. The remote rdpclip.exe process notices the change and sends it to the RDP client over the virtual channel.
3. The local RDP client (mstsc.exe) receives the data and places it on the local clipboard.
4. The local clipboard watcher (your shelf, Win+V, Ditto, etc.) sees the change and records it.

When you copy text outside the RDP session:

1. The local clipboard gets the text.
2. The local RDP client sends it to the remote rdpclip.exe.
3. The remote clipboard gets the text.

The relay is symmetric, but it is not free and it is not transparent. Several things break the relay:

• The RDP window is fullscreen. A fullscreen RDP session captures the keyboard, so local hotkeys (including your shelf's hotkey and Win+V) go to the remote session, not the local one. The local shelf cannot be opened by hotkey while RDP is fullscreen.
• The RDP window is not fullscreen but is focused. Local hotkeys go to whatever has focus. If the RDP window has focus, Win+V opens the remote clipboard history, not the local one.
• Clipboard redirection is disabled in the RDP file. The .rdp file or the Local Resources tab in mstsc.exe controls whether clipboard redirection is on at all.
• The clipboard format is not on the redirection whitelist. RDP redirects text, HTML, and a few other formats by default; files are redirected through drive redirection, not the clipboard channel.

What "live" means

The question "which clipboard is live?" has a precise answer: the clipboard of the session that currently has keyboard focus. If the RDP window has focus, the remote clipboard is live and Win+V opens the remote history. If a local window has focus, the local clipboard is live and Win+V opens the local history.

A hover-activated local shelf has an additional problem: the shelf is drawn on the local desktop, but the cursor is inside the fullscreen RDP session. The shelf cannot be hovered because the cursor is not on the local desktop. Even if the shelf is set to always-on-top and z-orders above the RDP window, the cursor never reaches the local screen edge.

Workarounds

Run the shelf inside the remote session

The cleanest answer is to install the clipboard manager inside the remote session and treat it as the remote clipboard manager. It watches the remote clipboard, opens with the remote hotkey, and works exactly as it would on a local machine. The cost is that the remote machine needs the manager installed and configured, which is not always possible (locked-down corporate machines, shared jump hosts).

Use a windowed RDP session

A windowed RDP session leaves the local desktop partially visible, so the local shelf can be hovered. The local shelf sees only what the local clipboard contains, which is whatever RDP has relayed from the remote session. The relay is one-way at any given moment — copies inside RDP reach the local clipboard within a second or two, but the local shelf cannot see copies that the remote session has not yet relayed.

Use the RDP hotkey to release the mouse

Ctrl+Alt+Break toggles RDP between fullscreen and windowed. Ctrl+Alt+End sends Ctrl+Alt+Del to the remote session. These are the standard RDP hotkeys that work even in fullscreen. Releasing fullscreen briefly to interact with the local shelf is workable but clumsy.

Disable clipboard redirection and use a side channel

Some workflows disable clipboard redirection entirely for security reasons and use a side channel — a shared folder, a chat application, or a password manager — to move text between local and remote. This is common on locked-down jump hosts where clipboard redirection is disabled by Group Policy. In that case, the local shelf and the remote clipboard are completely separate, and the user manages two histories.

What the OS actually syncs

RDP clipboard redirection, when enabled, syncs the formats on the redirection whitelist. The exact list varies by Windows version but typically includes:

• Plain text (CF_UNICODETEXT)
• HTML (CF_HTML)
• Bitmap (CF_DIB, CF_DIBV5)
• A handful of private formats used by Office

Files are not synced through the clipboard channel. To copy a file between local and remote, you need drive redirection (the "Local drives" checkbox under Local Resources → More) or you copy the file's path as text and open it from the remote session over a UNC path.

For the deep troubleshooting discussion of RDP clipboard failures, see remote desktop copy-paste not working and RDP files paste but text does not (or the reverse).

Multi-monitor RDP

RDP supports multi-monitor fullscreen ("Use all my monitors for the remote session" on the Display tab). In this mode, the remote session covers all local monitors, and the local desktop is entirely hidden. The local shelf is unreachable — there is no local screen edge to hover.

The workaround is to leave one local monitor outside the RDP session, which is not possible when "Use all my monitors" is checked. The alternative is to run the manager inside the remote session, where it can be hovered against the remote session's virtual screen edges.

For the broader multi-monitor discussion, see clipboard tools on multi-monitor Windows setups and virtual desktops and always-on-top shelves.

Honest positioning

Edge-Drop, the Windows hover-activated clipboard shelf, is a local tool. It cannot see inside a fullscreen RDP session, and the shelf does not run inside the remote session unless the user installs it there (which requires the remote machine to be a Windows machine where installation is permitted). The shelf's SHQueryUserNotificationState check suppresses hover when a fullscreen app is detected, which includes fullscreen RDP — so the shelf correctly stays out of the way during an RDP session rather than fighting for pixels it cannot use. The honest recommendation for users who spend most of their day in RDP is to run a clipboard manager inside the remote session, not to try to use a local shelf through the RDP boundary.

A worked case: the jump-host chain

Consider a common corporate pattern: a local laptop running a windowed RDP session to a locked-down jump host, which in turn RDPs into a production server. The clipboard chain is now three layers deep — laptop, jump host, production — and each hop relays only the formats on its own whitelist. A copy from the production server reaches the laptop only if both hops allow clipboard redirection, and only the formats common to both whitelists survive the trip. Files almost never make it; they require drive redirection at every hop, which is usually disabled on jump hosts for security reasons.

The practical answer is to run the clipboard manager on the jump host, where it can see both directions of the relay, and to treat the laptop's local shelf as a separate tool for local copies only. Trying to make one shelf cover all three sessions leads to duplicated items, missing formats, and false confidence that a copy actually landed.

What to check

If your local shelf is not seeing copies made inside RDP, work through these:

1. Is the RDP session fullscreen? If yes, the local shelf cannot be hovered; use a hotkey or run the shelf inside the remote session.
2. Is clipboard redirection enabled? (mstsc.exe → Local Resources → Clipboard.)
3. Is rdpclip.exe running on the remote machine? (Task Manager on the remote; if not, restart it via Task Manager or taskkill /f /im rdpclip.exe followed by restarting it.)
4. Is the format you are copying on the redirection whitelist? (Files are not; try plain text first.)
5. Is there a Group Policy disabling clipboard redirection? (Look for "Do not allow clipboard redirection" in the remote machine's Group Policy.)

Most failures are item 1, 2, or 3. For the full troubleshooting tree, see remote desktop copy-paste not working.

Related reading

• Virtual Desktops and Always-On-Top Shelves
• High Refresh Pointers and Hover Dwell Times
• Clipboard Tools on Multi-Monitor Windows Setups
• Win+V Not Working on Windows 11: 9 Fixes

Sources

• Microsoft Learn — Remote Desktop Services clipboard redirection — official documentation of the RDP clipboard redirection channel and its format whitelist
• Microsoft Support — Copy and paste between local and remote desktop — official guidance on enabling clipboard redirection in mstsc.exe
• Microsoft Learn — rdpclip.exe — Microsoft reference for the rdpclip process that handles clipboard relay on the remote side
• Microsoft Learn — RDP Group Policy settings — official reference for the "Do not allow clipboard redirection" policy and its scope
• Microsoft Learn — Terminal Services shortcut keys — official list of RDP shortcut keys including Ctrl+Alt+Break and Ctrl+Alt+End

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support