How to Copy Text From a Remote Desktop or Citrix Session When the Clipboard Is Broken

Here's how to copy text from a remote desktop to your local Mac when the clipboard won't. You're working in a Citrix or Remote Desktop session. An error pops up with an IP address, a return code and a ticket number you need to paste into an email. You press ⌘C, switch to your Mac, press ⌘V, and nothing. The clipboard isn't crossing the session boundary.

The problem

Remote sessions pass the clipboard between the remote machine and your Mac through a "clipboard redirection" channel. It fails for two reasons:

• It's turned off on purpose. Many companies disable it so data can't leave the remote environment.
• It's broken. The clipboard service in the session hangs, especially after sleep or reconnecting.

Either way you end up retyping long codes by hand, which is exactly where typos creep in.

Practical fixes, in order

1. Rule out a stuck clipboard

Disconnect and reconnect the session. In Microsoft's Windows App (formerly Remote Desktop), check the connection's clipboard setting. In Citrix Workspace, check the session's preferences or ask IT. If it works after reconnecting, you're done.

2. Read the text off the screen

If copying is disabled, the text is still displayed on your Mac, as pixels in the session window. OCR reads it locally:

1. Make the dialog or text visible in the remote window, the bigger the better.
2. Press ⌘⇧7 in Screenshot Text and drag a box around just the text.
3. Paste it into your email, ticket or notes.

The free alternative is a screenshot (⌘⇧4), then open it in Preview and select the text with Live Text.

Our test: an error dialog in a compressed session

Remote sessions are usually scaled and compressed, which is hard on OCR. We simulated that with an SAP error dialog in a Citrix-style window, scaled down and saved as a low-quality JPEG:

Capturing just the dialog in Normal mode returned:

Error: Connection to partner 10.42.7.19:3299 broken
Return code: NIECONN REFUSED (-10)
Transaction ID: 5F3A9C210B44D7A
Contact the IT Service Desk on ext. 4417 and quote ticket INC0482216.

It looks perfect, but it isn't:

• The transaction ID lost a character. 5F3A9C21E0B44D7A became 5F3A9C210B44D7A, with the E gone. Normal mode's language correction "smoothed" the string.
• The underscore became a space: NIECONN_REFUSED became NIECONN REFUSED.

The IP address, port, extension and ticket number were all correct.

With Optimize for code on, which reads characters literally before tidying, the transaction ID came back correct. The underscore was still a space. So for dialogs full of codes, literal reading helps, but nothing replaces a quick check.

What OCR does and doesn't solve

Situation	Helps?
Error messages, IDs, ticket numbers to report	Yes. Check every character of long codes
Short passages to quote in an email	Yes
Commands or config shown in the session	Yes. See copy text from a VM for code tips
Moving files or large documents out of the session	No. That's what the clipboard policy blocks; ask IT
Getting around a data-loss-prevention rule	No, and you shouldn't

Checklist

• Reconnect once to rule out a stuck clipboard
• Zoom or enlarge the remote window before capturing
• Capture only the dialog, not the whole desktop
• Re-check long IDs, IPs and underscores against the screen
• Follow your company's rules for sensitive data

The same capture works on anything else on your screen: see how to extract text from a screenshot on Mac.