TigerVNC

TigerVNC is a free, open-source VNC server and viewer for administrators who need fast, encrypted remote desktops on Linux and a reliable VNC client on Windows, macOS and Linux. A TigerVNC download gives you a viewer that connects to almost any VNC server, and on Linux a set of servers that either create virtual desktops or share the screen that is already running.

The project started in 2009 from the VNC 4-based TightVNC 1.5 code line and is now developed by an open community with Cendio as a major contributor. It is the VNC implementation shipped by Red Hat, Fedora and many other distributions, so it is often already one package away on your servers.

TigerVNC at a glance

What it does

• Xvnc runs a complete virtual X11 desktop per user, independent of any monitor, which is ideal for headless servers.
• x0vncserver shares an existing X11 display, so you can see and control what is on a physical screen.
• w0vncserver, new in 1.16.0, shares Wayland desktops.
• Encrypts connections with TLS (anonymous or X.509 certificates) and supports VNC password or system-account authentication.
• Uses Tight, ZRLE and other encodings with automatic quality selection, so it stays usable on slower links.
• The native viewer forwards system keys on Windows and macOS, supports full-screen across multiple monitors and remembers server history in a searchable field.
• Integrates with systemd on Linux so VNC sessions start at boot for named users.

How IT teams use it

Run a persistent desktop on a headless Linux server

1. Install the server package and a light desktop, for example on RHEL, Rocky or Fedora:

   sudo dnf install tigervnc-server
   sudo dnf groupinstall "Xfce"

   On Debian or Ubuntu the package is tigervnc-standalone-server.

2. As the user who will own the session, set a VNC password: vncpasswd.
3. Map a display number to that user in /etc/tigervnc/vncserver.users:

   :1=alice

4. Optionally choose the desktop in ~/.config/tigervnc/config, for example session=xfce.
5. Start the service and enable it at boot:

   sudo systemctl enable --now vncserver@:1

6. Display :1 listens on TCP 5901, :2 on 5902, and so on.

Reach it safely over SSH

1. Keep port 5901 closed in the firewall and add localhost to the user’s TigerVNC config so the server only listens locally.
2. From your workstation open a tunnel:

   ssh -L 5901:localhost:5901 alice@server

3. In TigerVNC Viewer connect to localhost:1.

Look at a user’s real screen on a Linux desktop

1. As the logged-in user, create a password with vncpasswd (new users get it in ~/.config/tigervnc/passwd, older setups in ~/.vnc/passwd), then on an X11 desktop run:

   x0vncserver -display :0 -PasswordFile ~/.config/tigervnc/passwd

2. On a Wayland desktop use w0vncserver instead.
3. Update to 1.16.2 first: 1.16.1 and 1.16.2 fix an x0vncserver flaw that let other local users observe and control the screen.

Install and first run

Windows. Official builds include the viewer (vncviewer64-1.16.2.exe runs without installation) and a separate WinVNC server installer. The viewer needs no admin rights; the server does.

macOS. A .dmg with the viewer only. Since 1.16.0 the viewer intercepts system keys in a different way, so macOS asks you to approve its accessibility permission on first use.

Linux. Use your distribution’s packages (tigervnc, tigervnc-server, tigervnc-standalone-server) or the generic x86_64 tarball from the project. RHEL 10 packages were added in 1.16.0; Ubuntu 20.04 and RHEL 7 packages were dropped.

Gotchas. Open TCP 5900 + display number only when you must, and prefer an SSH tunnel or TLS. GNOME on Xvnc can fail to start or run slowly; Xfce and MATE are safer choices. The old F8 menu key in the viewer was replaced in 1.16.0 by a new keyboard shortcut system, so check the viewer’s options if your habits stop working.

Limitations

• No built-in NAT traversal, address book or cloud relay: you need a VPN, SSH or open ports.
• No file transfer in the protocol as TigerVNC implements it; use SCP or SFTP alongside.
• No audio forwarding.
• The Windows server is less widely used than the Linux servers; for Windows hosts, many admins prefer other VNC servers or RDP.
• macOS gets a viewer only, no server.

TigerVNC vs alternatives

TightVNC is the better-known free VNC server for Windows hosts, while TigerVNC is the stronger choice for Linux servers and as a cross-platform viewer. RealVNC Viewer adds a cloud address book and brokered connections that require RealVNC’s paid server side. UltraVNC is Windows-only but includes file transfer and chat. If you need many users on Linux with load balancing and a web client, ThinLinc is built on TigerVNC and adds those layers.

FAQ

Where can I get TigerVNC Viewer for Windows?

Official Windows builds of the viewer and server are linked from tigervnc.org, which also has the release notes. The standalone viewer .exe runs without installation.

Is there TigerVNC for Mac?

Yes, the viewer is available as a .dmg for macOS. There is no TigerVNC server for macOS.

Is TigerVNC free?

Yes. It is free and open source under the GNU GPL v2, including for commercial use.

TigerVNC vs TightVNC: which should I use?

Use TigerVNC for Linux servers and as a general viewer; use TightVNC when you need a simple free VNC server on Windows. Both speak standard VNC, so they work together.

TigerVNC vs RealVNC?

TigerVNC is fully free and self-managed. RealVNC Viewer is free, but RealVNC’s server and cloud connectivity are paid products with extra management features.

How do I start a TigerVNC server on Linux?

Set a password with vncpasswd, add a line such as :1=username to /etc/tigervnc/vncserver.users and run sudo systemctl enable --now vncserver@:1.

TigerVNC vs RDP?

RDP is usually faster for Windows hosts and supports audio and drive redirection. TigerVNC is the natural choice for Linux desktops and mixed environments where a standard VNC protocol is needed.

Last checked against official sources: 1 October 2026 (developer website: tigervnc.org). Versions and licence terms change — confirm on the developer's site before deploying in production.