ManyScreens is remote desktop software for your own computers. You install it once, on the Mac, Windows PC or Linux machine you want to reach; from anywhere else you need nothing but a browser — a phone, a tablet, a laptop you are not allowed to install anything on. Screen, mouse, keyboard, sound and clipboard travel straight between the two machines over WebRTC. Nothing to forward on your router, no per-seat price, and nobody checking whether your use looks commercial.
macOS · Windows · Linux. On a phone or tablet you only need the browser you are holding.
The pieces of a remote desktop you actually use, without the parts you have to set up.
The viewer is a web page. Any current browser is enough, Safari on an iPhone included. Bookmark it and you are in.
On the same network the picture never leaves the building. Elsewhere it goes out on port 443 like any website and comes back the same way. Nothing to open on your router.
Pick the monitor you want. Or open a window per screen and put them side by side, the way they sit on the desk.
Hear the remote machine. Copy on one side, paste on the other. Drop a file on the window and it lands in Downloads over there. Send the keys the browser would keep for itself, ⌘⇥ and alt‑tab included.
Pinch to zoom, two fingers to scroll, a look‑or‑control switch so nothing gets clicked by accident, and a row of the keys a phone does not have.
An optional service reaches the login window itself, so a machine that rebooted at three in the morning is not lost until someone walks over to it. On a Mac it carries Apple’s own Screen Sharing; on Linux it needs an X11 login screen. Off until you switch it on, and it asks for the administrator password.
A code appears on your screen. You read it out, they type it in, and you say yes at the machine. Ten minutes to use it, gone after that. No account needed on their side.
The app goes on the machine you want to reach. Everything else is a browser.
Download ManyScreens on the computer you want to reach. It lives in the menu bar or tray and can start with the computer.
Create an account in the app’s window and click Share this computer. Takes a minute, happens once.
Sign in from any browser and click the computer. Mouse, keyboard, sound and clipboard are yours.
For the computer you want to reach. The side you watch from needs only a browser. Updates install themselves.
Windows 10 or newer, 64‑bit. The installer is not code‑signed yet, so Windows will warn about an unknown publisher — More info, then Run anyway.
Download .exeAppImage, 64‑bit. X11, or Wayland on GNOME and KDE. On Ubuntu 24.04 install libfuse2t64 first.
Download .AppImageRemote access you cannot see is the kind you should not trust. Here the machine being watched says so, every time.
Free is for a few computers on your own network. Pro is for living on it. One price for all your computers — there is no per‑seat and no per‑technician pricing, and nothing checks whether your use looks commercial.
Short answers, and the honest ones where the answer is no.
No. The ManyScreens viewer is a web page, so any current browser will do — Chrome, Safari, Edge or Firefox, on a computer, an iPhone or an Android phone. You only install the app on the computer you want to reach.
No. The ManyScreens agent connects outward to the server, and the browser does the same; WebRTC then builds a direct path between them. Where a direct path is impossible the picture goes through a relay on port 443, like any HTTPS site. There is nothing to change on your router.
Screen, sound and input travel as a WebRTC peer connection secured with DTLS-SRTP between your two machines. When the relay is needed it forwards packets it has no key for. The ManyScreens server brokers the connection and never sees the picture. The one exception is a macOS login window.
No. ManyScreens has no commercial-use detection and no session timer. Your own computers are your own business. The limits on Free are three computers, one screen at a time, and lower quality when a session has to go through the relay.
Until 1 January 2027 every account has every Pro feature free, with no card. After that you keep Free automatically — three computers, full quality on direct connections, no time limit — and choose Pro only if you want unlimited computers, any quality setting through the relay, up to 60 fps, a window per screen and system audio.
Yes. Open manyscreens.com in Safari, sign in and tap the computer. ManyScreens draws a touch interface: a switch between looking and controlling, pinch to zoom, two fingers to scroll, press and hold for a right click, and a row of the keys a phone keyboard does not have. There is nothing to install, and no app in the App Store yet; one is on the way, and the waitlist is at the end of this page.
It has to be switched on and online, but it need not be logged in. Switch on Start at login and the ManyScreens app comes back whenever you log in and updates itself; an optional service reaches the login window after a restart on macOS and on Linux machines with an X11 login screen.
Yes. The screen is captured once and every viewer gets its own encode at its own size and bitrate, so a second window does not spoil the first. The computer being watched lists each connection and can end any of them.
ManyScreens shows a code on the screen of the machine being shared. It lives ten minutes, works exactly once, and the person sitting at that machine still has to say yes when the guest arrives. The helper needs no account. Refusing spends the code.
Usually, yes. Signalling runs over WSS on 443, the relay speaks TURNS on 443, and if a proxy kills WebSockets the ManyScreens viewer falls back to ordinary HTTPS requests by itself. Once you are signed in, a check page tells you in about ten seconds what a given network allows.
Pro plays the remote machine’s system audio, off until you ask for it and sent only to the viewer who asked. Clipboard text goes both ways. Drop a file on the window and it lands in Downloads over there; fetch one back by picking it in a dialog on the far side.
ManyScreens has a send-keys menu for the combinations the local browser or OS keeps for itself, and in full screen it uses Keyboard Lock to capture them directly. Ctrl+Alt+Del cannot be sent.
No. ManyScreens needs an email address and a password, nothing else, and there is no browser extension. Passwords are hashed with argon2 and every signed-in browser is a session you can revoke on its own.
The ManyScreens signalling server runs in Berlin and the relay in Frankfurt, both in Germany. The site loads no analytics, no trackers and no third-party fonts; the only foreign scripts are Paddle’s checkout on the Pro page and Cloudflare’s bot check on the sign-in page.
Yes. With two-factor sign-in switched on under Settings → Account, ManyScreens asks for a six-digit code from an authenticator app at every sign-in, and eight single-use recovery codes cover a lost phone; a password reset by email does not get around it. Around that: an argon2-hashed password, revocable session tokens, a question about whether a browser is yours, and a host that shows every connection and can cut it.
No to both. ManyScreens is a hosted service. If running your own infrastructure is the requirement, RustDesk and MeshCentral are built for that and ManyScreens is not.
No. ManyScreens is for working on your own computers. A browser WebRTC viewer will not match Parsec or Moonlight on controller latency, and it does not try to.
One developer, working in Germany and Austria, who uses it every day to reach a Mac, a Linux box and a PC. There is no company behind it and no investor pushing the price up.