Installing RealtimeClipboard

RealtimeClipboard runs in a browser on every device you own, and nothing needs installing for that. What installing buys you is one specific thing, on some platforms only: the app noticing what you copied while you were working in a different window.

Start here: do you need to install anything?

Probably not. Open the app on two devices, type the same five-character key on each, and they share a clipboard. Everything below is about one feature — background capture — and whether your platform can do it.

What "background capture" actually means

In a browser, RealtimeClipboard can only read your clipboard while its window is focused. That is not a limitation of this app — it is a rule every browser enforces on every website, because a page that could silently read your clipboard would harvest every password you copy. So the browser version works like this: you copy something, you switch to RealtimeClipboard, and it picks it up as it comes into focus.

A native desktop app is not bound by that rule. The Windows, macOS and Linux app watches the system clipboard continuously, so copying in any application sends it immediately, with no switching.

Which means the desktop app reads every copy you make while it is running — including passwords you copy for unrelated reasons. It is encrypted before it leaves your machine and never written to disk, but that is a real thing to agree to. It ships set to Manual for that reason: nothing leaves the machine until you press send. Turn on Live when you want the automatic behaviour.

Windows

Download the .msi from the download page, or:

winget install RealtimeClipboard.RealtimeClipboard

If Windows SmartScreen warns you about the installer, that is worth taking seriously in general. Check that the publisher matches and that you got the file from the official releases page.

On a work machine: the app needs no administrator rights and installs no driver or service. It makes outbound connections on 443 only, to a single hostname, which is the shape IT departments allowlist. If yours blocks it, the browser version needs nothing at all.

macOS

Download the .dmg, or:

brew install --cask realtimeclipboard

One download covers both Intel and Apple Silicon. macOS needs no special permission to read the clipboard, so there is no prompt to grant — which cuts both ways, and is why the app defaults to Manual.

Linux

flatpak install flathub io.github.akshaynikhare.RealtimeClipboard

Or a .deb, .rpm or AppImage from the releases page, or yay -S realtimeclipboard on Arch.

The Wayland caveat, stated plainly. On X11 the app is told when the clipboard changes and background capture works. On Wayland it depends on your compositor: KDE and the wlroots-based ones expose a protocol for it, and GNOME does not — there is no way for any application to monitor the clipboard on GNOME Wayland. The app detects this and says so in its status bar rather than silently doing nothing, and falls back to capturing on focus, exactly like the browser.

Older distributions. The desktop app needs webkit2gtk 4.1, which means roughly Ubuntu 22.04 or Fedora 36 and newer. On anything older, use the browser or the command-line client.

Android and ChromeOS

There is no Android app, and there is not going to be one. Since Android 10, only the app you are currently using, the active keyboard, or an accessibility service may read the clipboard. A RealtimeClipboard app would therefore be a share-sheet button and an icon — everything else it could do, the installed web app already does.

1. Open the app in Chrome.
2. Tap the menu, then Add to Home screen.

It then has its own icon and window, and works offline. To send something, paste it into the app or use Android's share menu.

iPhone and iPad

Same answer, for the same reason: iOS has never permitted background pasteboard reads, and since iOS 16 it shows a banner every time any app reads the clipboard at all.

1. Open the app in Safari. Chrome and Firefox on iOS cannot install a web app.
2. Tap Share, then Add to Home Screen.

iOS shows no install prompt of its own, so if you are waiting for one to appear, it will not. The Share menu is the whole mechanism.

Servers, SSH sessions and scripts

npx realtimeclipboard D75LV

For machines with no clipboard and no screen. It reads standard input and writes standard output, so it composes with everything else:

echo "deploy key" | npx realtimeclipboard send D75LV
npx realtimeclipboard watch D75LV --once > token.txt

It needs Node 22 or newer. It is not a separate implementation — it imports the same encryption and transport files the browser runs, so a clip sent from a server is indistinguishable from one sent by a laptop.

Running your own relay

The relay passes encrypted clips between your devices. It cannot read them — it only ever sees a room hash and ciphertext — but if you would rather not take that on trust, run it yourself:

docker run -p 8000:8000 ghcr.io/akshaynikhare/realtimeclipboard-relay

Then point the app at it under Settings → Relay. There is a docker-compose.yml with automatic TLS and a Helm chart in the deploy directory.

Ready to install: the download page. Something wrong or out of date here? Open an issue.