Sync Clipboard Between Local and Remote Mac

Published November 11, 2026 • Figment editorial team

Pasting a snippet from your local editor into a remote Mac's terminal should take one keystroke. Over a VNC session it usually can, but only when the client, the server, and the guest OS all agree on what the clipboard carries. This guide explains what RFB clipboard messages actually transport, gives you a short worksheet to test your own setup, and shows which Figment plan matches the amount of pasting you do.

How VNC Clipboard Messages Work

The RFB protocol defined in RFC 6143 carries clipboard text in two messages: ClientCutText (type 6, client to server) and ServerCutText (type 3, server to client). Each has a one-byte message type, three padding bytes, a four-byte unsigned length field, and a byte array of text. The base specification states that the text is ISO 8859-1 (Latin-1) and that there is no base-protocol way to transfer text outside that character set.

Several later VNC implementations negotiate extensions that can carry UTF-8 or additional formats, so you cannot assume every session is Latin-1-only, and you cannot assume every session carries emoji and CJK either. The only reliable test is to paste a benign multilingual sample through the actual client and server you plan to use and look at what arrives.

A few more facts from the RFC that shape the workflow:

There is no base field for images, files, or styled text. Anything that appears to paste a picture is a client extension, not base RFB.
The length field is 32-bit, but every real client and server caps clipboard updates far below 4 GiB. TigerVNC's viewer and Xvnc server, for example, default MaxCutText to 262144 bytes (256 KiB).
Clipboard sync depends on the VNC server integrating with the guest OS clipboard. If that integration is absent, a client-side toggle will not create one.

A Short Acceptance Worksheet For Your Own Setup

Rather than trusting a how-to for one specific viewer, run this acceptance worksheet against the client and server you actually use. The documented clipboard options differ by product: TigerVNC exposes AcceptClipboard, SendClipboard, and SendPrimary (all default on); RealVNC exposes SendCutText and AcceptCutText on both sides; Remmina has a "Turn off clipboard sync" checkbox inside each VNC profile. Start from the help page bundled with your installed version so you are not mixing parameters between products.

Connect and open a plain-text editor on the remote Mac. Copy a short ASCII string from your local machine and paste it in. Confirm it arrives byte-for-byte.
Copy the same ASCII string on the remote Mac and paste it locally. If only one direction works, the asymmetric toggle is set wrong on that end.
Paste a benign multilingual sample such as café — 日本語 — 😀 and record exactly what arrives. Silent dropping, replacement characters, or truncation tells you the negotiated encoding is Latin-1 and you will need a UTF-8-capable client or an out-of-band transfer for non-Latin-1 text.
Paste a 2 KB block, then a 200 KB block. If the larger one truncates, you are hitting a MaxCutText cap on the viewer or the server rather than a bug.
Clear the clipboard on both ends when you finish so stale content does not leak into the next session.

For anything larger than a comfortable text paste, move the payload over an authenticated outbound transfer the Mac initiates to storage you control, such as your own object store, artifact service, or a Finder Cmd-K connection to sftp://user@your-server/. A VNC session with a browser console does not include a file-upload channel; use an outbound transfer when the clipboard is the wrong tool.

Universal Clipboard Is Not A Substitute

Apple's own Universal Clipboard requirements list the same Apple Account on both devices, Wi-Fi, Bluetooth, Handoff, and a 10 m (30 ft) proximity window. A rental Mac in a data centre meets none of those, so Universal Clipboard will not reach it. VNC clipboard is the right mechanism for a rented Mac, and anything larger than text belongs on a file transfer you authorise and audit.

Pick A Figment Plan For Your Paste Workflow

Figment rents Macs; how reliably clipboard sync behaves depends on the plan you choose and the client you bring.

$29/month virtual Intel macOS (2 vCPU, 8 GiB RAM, 80 GiB disk). Access is a browser console to the guest. Guest clipboard integration on this image is not independently verified end-to-end, so plan to manually type anything short that must land exactly, and use an authorised outbound transfer for anything bigger. A good fit for Intel-compatible toolchains and Xcode 26 or earlier cross-compilation.
i3 physical Mac from $49/month and M-series physical Mac from $95/month. Supply is request-based. If clipboard sync is central to the job, ask in your quote for a specific client-and-server pair the team has tested, and confirm it in an evaluation before purchase. The $95 M-series entry is an unspecified starting configuration, not a confirmed M4/16 GiB/256 GiB spec; the exact chip, RAM, and disk are set in the quote.
Managed Build Mac $249/month. One M-series Mac with CI setup, backups, monitoring, and 30 minutes of monthly support included.
Managed Mac Team $999/month. Two M-series Macs, two CI runners, team setup, backups, monitoring, and one hour of monthly support included.

Ready to connect? Browse options at /mac-hosting or request a configuration at /mac-hosting/start.

Related guides: