Citrix and VDI Clipboard Redirection

When citrix clipboard not working shows up as a help-desk ticket, the cause is almost never the Windows clipboard itself. It is policy on the Citrix layer, bandwidth on the ICA clipboard virtual channel, or the file-versus-text split that Citrix draws explicitly and most other clipboard stacks do not. This guide walks through the policy and bandwidth limits, the difference between text and file redirection, where RDP fits in, and where Win+V stops crossing the VDI boundary.

For related topics, see iPhone to Windows paste: what works in 2026 for the consumer cross-device case, VM guest clipboard integration broken for the workstation hypervisor case, and the general Win+V not working on Windows 11: 9 fixes and Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11 references.

What is in scope

VDI clipboard redirection covers three product families in 2026:

• Citrix Virtual Apps and Desktops (CVAD) reached via the Citrix Workspace app on the endpoint. Clipboard flows over an ICA virtual channel named Clipboard.
• Microsoft Remote Desktop Services (RDSH or AVD) reached via mstsc.exe or the Remote Desktop client. Clipboard flows through rdpclip.exe and the Local Resources → Clipboard toggle.
• VMware Horizon reached via Blast or PCoIP. Clipboard is governed by a Horizon policy and a Blast channel.

This article focuses on Citrix and the RDP fallback. For the workstation-VM case (VMware Workstation, VirtualBox, Hyper-V Enhanced Session), see VM guest clipboard integration broken.

What does not cross the VDI edge

Several things users expect to cross do not:

• Win+V history. Windows clipboard history is local to whichever machine opened Win+V. It does not flow over ICA or RDP. If you copy on the endpoint and paste in the session, the most recent clipboard item crosses; the 25-item history does not.
• Pinned items. Pinned Win+V entries stay on the machine they were pinned on.
• Cloud sync. Win+V cloud sync is PC-to-PC and does not extend to a VDI session, even if both are signed into the same Microsoft account.
• Third-party clipboard managers. Ditto, CopyQ, or Edge-Drop running on the endpoint see only the endpoint's clipboard. They do not see what is happening inside the VDI session unless the underlying OS clipboard has been redirected into the session.

This is the same boundary covered in clipboard sync says on but devices disagree, but applied to enterprise remote sessions.

Citrix clipboard redirection policy

Citrix exposes clipboard behaviour through policies configured in Citrix Studio or Citrix Cloud Web Studio. The relevant settings:

• Client clipboard redirection — Allow, Prohibit, or Prohibit explicitly. The default in many secured environments is Prohibit.
• Clipboard redirection allowed formats — a whitelist of clipboard formats that can cross. Common defaults include CF_TEXT, CF_UNICODETEXT, and CF_OEMTEXT. HTML, bitmap, and file-drop formats are typically removed.
• Client clipboard write allowed formats — companion to the read side; restricts which formats the session can write back to the endpoint.
• Restrict clipboard transfer between client and session — older policy name still seen on some sites; superseded by the per-format list above.

When a user reports "citrix clipboard not working", the first check is whether policy explicitly forbids it. A quick test: launch a session with a temporary policy that allows all formats both directions, then verify the user can copy text both ways. If yes, the original policy is the cause. The Citrix product documentation on ICA policy settings lists the verbatim policy names; do not invent policy names not documented there.

Bandwidth limits on the ICA clipboard channel

The ICA clipboard channel is bandwidth-limited. A few practical effects:

• Large text (a 1 MB log) crosses slowly. The session appears to hang briefly while the transfer completes.
• Bitmaps cross slowly and can saturate a low-bandwidth link.
• Files either do not cross at all (default in many policies) or cross via a separate file-transfer channel that has its own limits.
• HTML and rich formats are usually stripped, so pasting into Word inside the session lands as plain text even if the source was rich.

Citrix's clipboard virtual channel also has a default cap on the size of a single clipboard transfer. The cap is configurable but is usually around 4 MB to match the Windows clipboard item limit; content above that is dropped silently. For more on the per-item 4 MB cap and the 25-entry history limit, see Windows clipboard settings, line by line.

File versus text redirection

Citrix splits clipboard content into two categories:

• Text and bitmaps flow through the standard clipboard virtual channel.
• Files flow through Client Drive Mapping (CDM) and the file-copy semantics layered on top of it.

A user copying a file in Explorer on the endpoint and trying to paste it inside the session is using CDM, not the clipboard channel. If CDM is disabled by policy, file paste fails even when text clipboard redirection is on. The same applies in reverse: copying a file inside the session and pasting on the endpoint needs CDM enabled both directions.

This split is the most common cause of "sometimes it works, sometimes it does not" reports. Text works, files do not, and the user assumes the clipboard is broken.

RDP fallback: rdpclip and Local Resources

When Citrix is not in scope but a user reaches a Windows VM or RDSH session over RDP, the clipboard stack is different. The clipboard flows through rdpclip.exe on the session side and a paired component on the endpoint side. The toggle is in the Remote Desktop client:

• Open mstsc.exe.
• Click Show Options.
• Switch to the Local Resources tab.
• Under Local devices and resources, tick Clipboard.
• Click More… to enable drive redirection if file paste is also needed.

If rdpclip.exe hangs, the symptom is that clipboard works in one direction but not the other, or stops mid-session. The standard fix is to restart rdpclip.exe in Task Manager on the session side, or to log off and back on. For the full sequence, see remote desktop copy paste not working and RDP files paste but text does not, or the reverse.

UAC and integrity level mismatches

A second RDP and VDI clipboard failure mode is integrity level. A process running elevated (admin) and a process running at medium integrity cannot exchange clipboard data in all configurations, and this applies inside a VDI session too. If a user copies from a non-elevated app on the endpoint and tries to paste into an elevated app in the session, the paste can fail silently.

The fix is to launch the destination app at the same integrity level as the source. This is a Windows integrity boundary, not a VDI boundary; it applies on a single machine too.

Two clipboard managers, one session

A common failure pattern: a clipboard manager runs on the endpoint (Ditto, Edge-Drop, CopyQ) and another runs inside the VDI session (Ditto, or Win+V with history on). The two managers race for clipboard notifications, and the user sees duplicate entries, dropped entries, or stale content.

The fix is to run clipboard management on one side only — usually the endpoint, where the user's actual workflow lives. Inside the VDI session, leave Win+V off or pinned to a short history. The same conflict applies on a single machine; see can you run two clipboard tools at once.

Edge-Drop, the Windows clipboard shelf, is one option on the endpoint side. It does not attempt to bridge into a VDI session; it sees what the endpoint sees, which is the redirected clipboard.

Troubleshooting checklist

• Confirm Citrix policy allows clipboard redirection both directions for the user's delivery group.
• Confirm the allowed formats list includes the format the user needs (text, HTML, bitmap).
• If file paste fails but text works, check Client Drive Mapping, not the clipboard channel.
• If only one direction works, restart rdpclip.exe (RDP) or reconnect the session (Citrix).
• If both directions stop working mid-session, log off and back on. Persistent failure indicates policy or network.
• Confirm the user is not running a second clipboard manager inside the session that is racing with the endpoint manager.
• Check that the endpoint and session integrity levels match when pasting into elevated apps.

What to avoid

• Inventing a policy name. Citrix policy names are listed in the Citrix product documentation. If a setting is not there, it does not exist.
• Trying to forward Win+V across the session. Win+V history does not cross the VDI edge; it is local to whichever machine opened it.
• Enabling cloud sync as a workaround. Win+V cloud sync is PC-to-PC and does not extend to a VDI session.
• Treating the VDI session as a clipboard-storage location. Session state is destroyed at logoff; nothing in the session clipboard persists.

Related reading

• VM Guest Clipboard Integration Broken
• Windows Sandbox Has No Lasting History
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Support — Using the clipboard on Windows — official statement of the 25-item, 4 MB, text-HTML-bitmap limits and the optional cloud sync that does not extend to VDI sessions
• Microsoft Learn — Remote Desktop Services — RDS documentation covering Local Resources, rdpclip.exe, and the difference between clipboard and drive redirection
• Microsoft Learn — mstsc command reference — official mstsc options including the Local Resources flags relevant to clipboard and drive redirection
• Citrix Product Documentation — Citrix Virtual Apps and Desktops — authoritative source for the ICA clipboard policy names and the per-format redirection list
• Microsoft Learn — Windows Information Protection — explains the enterprise policy layer that can additionally restrict clipboard flow between work and personal contexts

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