ManyScreens Download

Remote desktop in a browser, with nothing installed where you are

The machine you sit at is often not yours to install things on: a Chromebook, a work laptop under someone else’s policy, a computer in a library or a hotel. ManyScreens needs nothing on that side. You install it once on the computer you want to reach; from anywhere else you open manyscreens.com, sign in and click it.

What you need

• On the computer you want to reach: the ManyScreens app. macOS 12 or newer (Apple silicon or Intel), Windows 10 or newer (x64 or Arm), or Linux as an AppImage (x64 or Arm; X11, or Wayland on GNOME and KDE).
• Where you are: a current browser. Chrome, Edge, Safari and Firefox all work. No extension, no plugin, no download.

Install the app, create an account in its window, click Share this computer, and switch on Start at login in its settings so the machine comes back after a restart. That is the whole setup.

What the browser gets

• The screen you pick. A menu switches between monitors, and the mouse and keyboard follow the screen you are on. Pro can open a window per remote screen to lay them out side by side.
• The shortcuts your own computer would swallow. A send‑keys menu sends ⌘⇥, ⌘Space and Force Quit to a Mac, or Alt+Tab, the Start menu, Alt+F4, Win+L and Win+D to a PC. In full screen, Chrome and Edge also capture most shortcuts directly.
• Clipboard text both ways, and files both ways: drop a file on the window and it lands in Downloads over there; fetch one back and the browser downloads it.
• Several viewers at once. Each browser gets its own picture size and bitrate, so a phone on mobile data does not drag down the laptop on fibre.

On a network that blocks almost everything

Corporate, school and hotel networks often let through web traffic and little else. ManyScreens is built for that. The picture is WebRTC, direct where a path exists and otherwise through a relay that speaks TLS on port 443, like any HTTPS site. The connection to the server is a WebSocket on 443, and if a proxy kills WebSockets the viewer switches to ordinary HTTPS requests by itself after six seconds.

The one thing that needs a WebSocket is the Mac login‑window view, so on such a network you can work on a logged‑in machine but not unlock one.

On a computer that is not yours

After you sign in, ManyScreens asks whether this is a system you trust. Say no and the sign‑in ends when the browser closes, or after 12 hours at the latest. Say yes and it lasts 30 days. Either way, your settings list every signed‑in browser, and each can be signed out on its own or all at once, from anywhere.

Limits worth knowing

• Ctrl+Alt+Del cannot be sent, and the Windows login screen and UAC prompts are out of reach. On a Mac and on Linux with an X11 login screen, an optional service reaches the login window.
• A browser decodes video well, but it is not a native client. For gaming, Parsec or Moonlight will do better.

Related