Use VNC when you need to view a desktop through a separate client, such as a browser using noVNC. The shared Remote Framebuffer (RFB) protocol supports a choice of implementations. A browser client needs WebSockets support at the server or a proxy.
One release, many branches
VNC was released as open source in 1998 by the Cambridge research team. The projects here include descendants of that code and independent implementations. noVNC implements RFB for browsers; wayvnc targets wlroots-based Wayland compositors.
Compare project roles and releases
| Project | License | Upstream release at check date | Role and limits | Release archive |
|---|---|---|---|---|
| TigerVNC | GPL-2.0 | 1.16.2 · 26 Mar 2026 | Viewer; Unix/Linux virtual, X11 and Wayland servers. macOS has the viewer only. The Windows server is unmaintained. | all releases, including older versions ↗ |
| TightVNC | GPL-2.0 | 2.8.88 · 19 Jun 2026 | Windows server and viewer. The 2.x download is Windows-only; Unix-like systems are directed to 1.3.10. The official changelog lists releases through 2.8.88. Official changelog. | Dated release news; Older releases |
| UltraVNC | GPL-3.0 | 1.8.3.0 · Sep 2026 | Windows server; Windows 7 minimum for 1.8.3.0. License source. | all releases, including older versions ↗ |
| noVNC | MPL-2.0 | 1.7.0 · 28 Apr 2026 | Browser client and client library. Requires a server with WebSockets support or a WebSocket-to-TCP proxy. | all releases, including older versions ↗ |
| x11vnc | GPL-2.0 | 0.9.17 · 1 May 2025 | Server for an existing X11 display. The maintainer request describes Wayland support as rudimentary; the request remains open. | all releases, including older versions ↗ |
| libvncserver / libvncclient | GPL-2.0 | 0.9.15 · 22 Dec 2024 | Library for implementing a VNC server. Application integration is required; this is not an end-user server. | all releases, including older versions ↗ |
| wayvnc | ISC | 0.10.2 · 25 Sep 2026 | Server for wlroots-based Wayland compositors. GNOME, KDE and Weston are unsupported. | all releases, including older versions ↗ |
| Remmina | GPL-2.0+ | 1.4.43 · 20 Feb 2026 | Multi-protocol GTK client with VNC support; it does not provide a VNC server. | all releases, including older versions ↗ |
RustDesk is a cross-platform remote desktop with a self-hosting route; Sunshine/Moonlight targets low-latency desktop and game streaming. They are alternatives readers may consider, but they are not VNC implementations and do not belong to the VNC/RFB lineage shown here.
Report an error in these facts.
Five projects in the table have profiles at vendors.html: TigerVNC, TightVNC, UltraVNC, noVNC and Remmina. The release archives link to upstream sources for every table entry.
Get the software
The server goes on the computer whose desktop you want to share; the viewer goes on the computer you will use to view it. Match each machine to its OS release, then choose an existing desktop or a separate virtual session. The rows below are examples.
| Platform | Example project | Which piece | Route | Checks and scope |
|---|---|---|---|---|
| Windows | TightVNC | Server + Viewer bundle | Windows download | TightVNC 2.8.88 Windows downloads bundle the server and viewer. |
| macOS | TigerVNC | Viewer |
brew install --cask tigervnc, then check the viewer route
|
Homebrew must already be installed. The cask installs TigerVNC.app in /Applications. Homebrew 7.0.7 checks the cask SHA-256 by default. On a mismatch it stops with SHA-256 mismatch, showing expected and actual values. Stop if that check fails.
|
| Debian 13 (Trixie) | TigerVNC | Written for TigerVNC 1.15.0+dfsg-2.1~deb13u1 on Debian 13 (Trixie). Server, viewer and tools. Requires an installed X11 desktop or window manager. Debian 13 packages do not list a Wayland server binary. |
sudo apt install tigervnc-standalone-server tigervnc-viewer tigervnc-tools, then read the package routes
|
This installation changes system packages and requires administrator privileges. As your regular user, run tigervncserver and set the requested VNC password. Expect a new-server message naming the display and port. On the same computer, run the xtigervncviewer command printed by the wrapper. Confirm that the session opens. If startup fails, inspect the log path printed by the wrapper. A missing X11 session is a prerequisite failure. Stop here if the local session does not open. Debian 13 APT 3.0.3 checks repository Release signatures and refuses unsigned repositories by default. Stop on a signature error or Hash Sum mismatch; do not bypass the check. The TigerVNC wrapper defaults to VncAuth on localhost, so this walkthrough ends at a local session.
|
| Raspberry Pi | wayvnc for the running Raspberry Pi OS desktop | wayvnc included on the Pi; TigerVNC viewer on the other computer | check the viewer route | The default desktop on Raspberry Pi OS Trixie is Wayland with labwc. An X11 variant exists through rpd-x-core in place of rpd-wayland-core. Raspberry Pi OS includes wayvnc for sharing the running desktop.
|
No recommendations are available for this platform.
Interoperability in practice
Sharing RFB does not establish that a particular viewer and server will connect. Check the security types and encodings supported by both ends. RFC 6143 defines the protocol. noVNC 1.7.0 requires WebSockets support at the server or a WebSocket-to-TCP proxy. For wayvnc 0.10.2, WebSockets is opt-in and the default listener is localhost. The base RFB protocol does not protect the data stream against observation or tampering. Keep the local walkthrough on localhost; remote deployment needs a separately configured protected transport and authentication. See RFC 6143, Security Considerations and wayvnc 0.10.2 exposure guidance. Read the RFB explainer for protocol background.
Taking part
noVNC directs bug reports and feature requests to GitHub issues, questions to its discussion group, and new contributors to issues labeled patchwelcome. For code contributions, wayvnc 0.10.2 and LibVNCServer 0.9.15 publish contribution guides. Remmina 1.4.43 documents merge requests. x11vnc has an open maintainer request. The community’s Open Source VNC group is the cross-project room on this site.
Open source or commercial?
Open-source VNC suits personal projects and home labs. When your business depends on remote access, RealVNC Connect adds end-to-end encryption, centralised management and commercial support from the team that created VNC.
For your own Raspberry Pis or a home lab, plan who will control network exposure and configure authentication. With open source, you must arrange those responsibilities, including a support route through project documentation and community channels.
When your business relies on remote access to critical systems, look at RealVNC Connect. It includes up to 256-bit AES end-to-end session encryption and requires authentication for connecting viewers. Management features vary by plan: Plus adds user and device groups and user roles and permissions. Commercial support provides a route beyond community channels.
Sources accurate as of 30 September 2026.