Browser-Based Remote Desktop: Tools Without a Client

This guide is for help-desk technicians, sysadmins and home users who want to reach a computer from a web browser without installing a remote desktop client on the device they are sitting at. The short answer: for your own PCs with nothing to run, use Chrome Remote Desktop or DWService; for a fleet you manage from your own server, MeshCentral; for a browser front door to servers that already speak RDP, VNC or SSH, Apache Guacamole. All four are free.

“Browser-based” always means the controlling side is a browser. The remote computer still needs something: an agent, a gateway in front of it, or an existing RDP, VNC or SSH service. Facts below come from the developers’ own documentation, checked on 16 October 2026. We have not measured session quality on our own hardware, so performance notes are marked “Not tested yet”.

The short list

Two architectures: agent or gateway

• Agent tools (Chrome Remote Desktop, DWService, MeshCentral) install a small service on each remote computer. The agent connects outwards to a relay or to your server, so nothing is opened on the remote router. The price is trusting the relay operator, or running the server yourself.
• Gateway tools (Guacamole, Thinfinity) install nothing on the targets. A server in your network accepts the browser session and translates it into RDP, VNC or SSH towards machines that already run those services. The gateway faces the browser, so it needs TLS, a reverse proxy and multi-factor login before it faces the internet.

ThinLinc and TSplus are session hosts: the desktop runs on the server itself, and the browser is one way to view it.

Hosted services with nothing to run

Chrome Remote Desktop

Remote Access gives permanent, PIN-protected access to computers registered to your Google account: open remotedesktop.google.com/access in Chrome, install the host package and set a PIN. Remote Support helps someone once: they open remotedesktop.google.com/support and generate a code that works a single time; while sharing they confirm every 30 minutes that they still want to share. Hosts run on Windows, macOS and 64-bit Debian or Ubuntu, where the host starts its own virtual desktop session. The network needs outbound UDP, TCP 443 and TCP/UDP 3478. There is no shell, no groups and no session recording: it is for your own machines and one-off help.

DWService

DWService is closer to an admin console. Install DWAgent on Windows, macOS or Linux, link it with a one-time installation code, and the browser offers Screen, Shell, Files and Folders, Text Editor, Log Watch and Resources. Shell, Files and Resources work on headless Linux servers, so a VPS is reachable without SSH ports open. The free account is capped at 6 Mbps per session; paid tiers only raise that cap, to 50 Mbps at most, and add no features. All traffic passes through DWService relay nodes, and there is no self-hosted relay.

Self-hosted browser console: MeshCentral

MeshCentral is the free answer when sessions must stay on infrastructure you control. The server needs Node.js 20 or newer: create a folder, run npm install meshcentral without sudo, start it with node node_modules/meshcentral, and create the first account at once, because the first account becomes the administrator. It starts in LAN-only mode; for laptops outside the office you set a DNS name and Let’s Encrypt in meshcentral-data/config.json and open TCP 443 (web UI and agents) and 80 (redirect and certificate renewal). Then create a device group, download the agent installer, and every enrolled machine gets Desktop, Terminal and Files tabs, with two-factor login, user groups and Intel AMT. TLS, backups and updates are yours. Our self-hosted remote access hub compares it with RustDesk Server, which serves a desktop client rather than a browser.

Self-hosted gateway to existing RDP, VNC and SSH: Guacamole

Apache Guacamole does not touch the targets. The guacd proxy daemon and a Java web application turn RDP, VNC, SSH, Telnet and Kubernetes sessions into an HTML5 page. The official route is Docker: images guacamole/guacd and guacamole/guacamole plus a MySQL or PostgreSQL container. The database schema is not created automatically; the manual’s command extracts it from the image:

docker run --rm guacamole/guacamole /opt/guacamole/bin/initdb.sh --postgresql > initdb.sql

The web application reads GUACD_HOSTNAME and the POSTGRESQL_DATABASE, POSTGRESQL_USERNAME and POSTGRESQL_PASSWORD variables, listens on port 8080 and serves the login page at /guacamole/. The scripts create a default administrator, guacadmin with password guacadmin; change it immediately. guacd listens on TCP 4822 with no authentication of its own, so never expose that port. Put a TLS proxy in front, set REMOTE_IP_VALVE_ENABLED=true so Tomcat logs the real client address, and enable TOTP or Duo before the login page is reachable from outside. Users see only assigned connections, which suits contractors and students; session recording and LDAP or Active Directory login are built in. The target must still be reachable from the Guacamole host on 3389, 5900 or 22.

Linux desktops and Windows apps in the browser

ThinLinc runs Linux desktops centrally and includes ThinLinc Web Access, an HTML5 client based on noVNC that works in Edge, Firefox, Chrome and Safari, served on TCP 300 over TLS. The server bundle includes 3 concurrent users, extended to 10 with the free community licence file. TSplus Remote Access publishes Windows desktops or single applications through a web portal with an HTML5 client; version 19.50.9.22 added FIPS support for it. Thinfinity, the successor to ThinRDP, is the commercial HTML5 RDP gateway with vendor support. RustDesk also has a web client, but it needs your own server with WebSocket ports 21118 and 21119 open.

Limitations of browser-based remote desktop

• Rendering happens in the browser, so full-motion video and graphics-heavy work are weaker than in a native RDP or VNC client. Not tested yet: frame rate and latency of each tool on our own LAN and over the internet.
• Shortcuts the browser owns (Ctrl+W, Ctrl+T) may never reach the remote session; MeshCentral and Guacamole provide on-screen menus for Ctrl-Alt-Del and similar keys.
• Hosted services tie identity and traffic to a third party: Google or DWSNET. Self-hosting removes that but adds TLS, backups and patching; the remote access security checklist covers both sides.
• Not tested yet: day-to-day use of the four free tools from a tablet browser. Windows App explicitly does not support mobile browsers.

How to choose

1. Your own few computers, no server: Chrome Remote Desktop if a Google account is acceptable; DWService if you also want a shell and file manager or manage headless Linux boxes.
2. A company fleet with groups, rights and two-factor login, hosted by you: MeshCentral.
3. Servers that already run RDP, VNC or SSH, and users who should see only assigned connections: Guacamole behind a TLS proxy with TOTP.
4. Many users on Linux desktops: ThinLinc, free up to 10 concurrent users. Windows applications for many users: TSplus or Thinfinity.
5. Laptops behind home routers favour an agent tool; servers in one network favour a gateway. The best free remote desktop software hub covers client-based alternatives.

FAQ

Is there a free browser-based remote desktop?

Yes. Chrome Remote Desktop and DWService are free hosted services with an agent on the remote PC; MeshCentral and Apache Guacamole are free, open-source servers you host yourself. ThinLinc Web Access is free up to 10 concurrent users.

Can I use remote desktop online with no install at all?

Only on the controlling side. The remote computer needs an agent or must already run RDP, VNC or SSH behind a gateway such as Guacamole. For one-off help, Chrome Remote Desktop’s support code and DWService’s Run mode leave nothing behind once the window closes.

Is there a web-based remote desktop for Linux?

DWService gives Shell, Files and Resources on any Linux server. MeshCentral agents support Linux and FreeBSD. Chrome Remote Desktop supports 64-bit Debian and Ubuntu hosts. Guacamole reaches Linux over SSH or VNC, and ThinLinc serves full Linux desktops in the browser.

Can I open Windows Remote Desktop in a browser?

Not directly to a plain PC. Microsoft’s Windows App web client covers Azure Virtual Desktop, Windows 365 and Dev Box, and lists Remote Desktop Services and remote PCs as unsupported in a browser. For your own Windows servers, Apache Guacamole or Thinfinity translates RDP into an HTML5 session.

Which browser-based remote desktop is open source?

Apache Guacamole and MeshCentral are open source under Apache-2.0. The DWService agent is open source (MPL-2.0 core), but the relay is operated by the vendor. Chrome Remote Desktop is proprietary freeware.

Guacamole vs MeshCentral: which one?

Guacamole when the targets already run RDP, VNC or SSH and users should see only assigned connections; MeshCentral when you want an agent on each machine for groups, power actions, terminal, files and Intel AMT. Both are free, self-hosted and run in Docker.

Last updated: 16 October 2026 · CtrlRemote editorial team. Licence, version and platform details are checked against each developer's official documentation.