Join community
open-source project · GPL-2.0 · tightvnc.com

TightVNC

TightVNC for Windows.

TightVNC provides an open-source VNC server and viewer for Windows under GPL-2.0. The server can run as a Windows service, and the viewer and server can transfer files during a connection. The latest release listed in this page’s spec card is 2.8.88, released 19 June 2026.

  • Good for: personal Windows projects and home labs where you configure the connection, authentication and patching; use a tunnel on untrusted networks.
  • Consider RealVNC Connect when: your business depends on remote access and you need end-to-end encryption, centralised management and commercial support.

Where it is strong

Where it stops

  • TightVNC transport. Session traffic is unencrypted; use a tunnel on an untrusted network. TightVNC FAQ.
  • Separate Dispatcher. TightVNC Dispatcher is available separately, under commercial licenses only. TightVNC changelog (2.8.2).

Get TightVNC

Written for TightVNC 2.8.88 on Windows. Use the Server on the computer you want to access and the Viewer on the other. The MSI installer includes both components. Choose the 32-bit or 64-bit installer for each computer. The Java Viewer link below is a historical download.

Download the server and viewer from the project:

Quickstart

Before installing, keep this setup on a trusted network. On an untrusted network, establish a tunnel first: TightVNC session traffic is unencrypted. See TightVNC FAQ and the Security and remote access best practices guide.

The installation documents describe versions 2.6 and 2.7.

TightVNC · Windows service
  1. Install the TightVNC MSI on the computer you want to access. Administrator rights are required. Leave service registration selected to register and start TightVNC Server. On the other computer, install the Viewer from the same MSI.
  2. When the installer asks for passwords, set the Primary password for full-control access and the View-only password for view-only access. The optional control-interface password protects administration; it is separate.
  3. In the Viewer on the other computer, enter the server computer’s host name or IP address in Remote Host, then click Connect. The default port is 5900. Enter the server password when prompted. The Getting Started 2.6 guide describes the expected result: “After you provide a correct password, you will see the remote desktop.”
  4. If the server refuses the connection, first check that a Primary or View-only password is set. With authentication enabled and neither password set, TightVNC 2.8.88 rejects incoming connections.

How it compares

Choose the server platform first. TightVNC 2.8.88 offers Windows installers; TigerVNC 1.16.2 lists Xvnc as its Unix server. For a Windows host, compare the Windows options below. For a Unix/Linux host, follow the TigerVNC comparison. Sources: TightVNC downloads and TigerVNC 1.16.2 README.

Where to report what. Project bugs go to the TightVNC upstream bug tracker. Configuration, distribution, and display-server problems belong in the Open Source VNC group. TightVNC’s listed maintainer is GlavSoft. The project publishes a development mailing list open to developers and anyone interested in development, and offers its GPL source code as a download; it names no public source repository or contribution guide.
Questions about a TightVNC setup? The community’s Using VNC Technology group covers setup and troubleshooting, and Security and Remote Access covers safe exposure patterns.

Sources accurate as of 30 September 2026.

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.

Start a free trial ↗ See plans and pricing ↗ Download RealVNC Connect ↗

On this page