# Install tiger-vnc with Homebrew, scoop, winget High-performance, platform-neutral implementation of VNC. Version 1.16.2 via Homebrew; verified 2026-05-11. ## Install ```sh sudo av install brew:tiger-vnc ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install tiger-vnc ``` Evidence: local Homebrew formula metadata ### Windows - Scoop (92%): ```sh scoop install extras/vncviewer ``` Evidence: Scoop official bucket manifest trees: bucket/vncviewer.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 - winget (92%): ```sh winget install --id RealVNC.VNCViewer -e ``` Evidence: Windows Package Manager source index: RealVNC.VNCViewer from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:tiger-vnc - **Package manager:** Homebrew - **Package manager page:** - **Version:** 1.16.2 - **Source summary:** High-performance, platform-neutral implementation of VNC - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** GPL-2.0-or-later - **Source archive:** - **Last updated:** 2026-05-11T18:07:38Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - vncconfig (cli) - vncpasswd (cli) - vncsession (cli) - vncviewer (cli) - x0vncserver (cli) - vncconfig (alias) - vncpasswd (alias) - vncsession (alias) - vncviewer (alias) - x0vncserver (alias) ## Dependencies - fltk@1.3 - gettext - gmp - gnutls - jpeg-turbo - nettle - pixman ## Build dependencies - cmake - gettext ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 1.16.2 - Package-manager updated: 2026-05-11 - Local data: ok - Upstream repository: https://github.com/TigerVNC/tigervnc - Upstream latest detected: v1.16.2 (current) ## Project history and usage TigerVNC is a high-performance, multi-platform implementation of Virtual Network Computing. Its README explains VNC as a remote display system that lets a user view and interact with a desktop environment running on another computer over a network. ### Project history The official README gives TigerVNC's origin story directly: it is based on the RealVNC 4 and X.org code bases, started as a next-generation development effort for TightVNC on Unix and Linux, and split from TightVNC in early 2009 so TightVNC could focus on Windows platforms. TigerVNC's technical identity is also defined by performance. The README says it supports a variant of Tight encoding accelerated by the libjpeg-turbo JPEG codec, which explains why the project became a frequent package choice for users who wanted an open VNC client/server stack with better speed than older VNC implementations. The project includes both common cross-platform pieces and platform-specific tools. The README lists vncviewer on all platforms, winvnc on Windows, and Unix/Linux programs such as Xvnc, vncpasswd, vncconfig, x0vncserver, w0vncserver, and a systemd vncserver service. ### Adoption history TigerVNC's adoption follows the continuing need for remote graphical access to Unix and Linux desktops, lab machines, servers, and cross-platform GUI sessions. The official repository is maintained under the TigerVNC organization and shows a long-running C++ project with substantial stars, forks, releases, and active development. In package-manager culture, TigerVNC is the kind of tool installed when SSH is not enough: developers, administrators, and researchers can add a VNC viewer or server from a package manager and connect to remote graphical environments without adopting a proprietary remote-desktop stack. The Homebrew formula exposes the viewer and related command-line utilities on macOS, while Linux distributions commonly package both client and server pieces. This split packaging pattern is natural for VNC because some users only need a viewer and others need to host sessions. ### How it is used The vncviewer manual documents the classic client workflow: run vncviewer with a host and display number or port, use a .tigervnc configuration file, authenticate with a password, and open a window showing the remote desktop. On Unix/Linux, TigerVNC is also used to create virtual X desktop sessions with Xvnc, manage VNC passwords with vncpasswd, configure a running server with vncconfig, and expose an existing X display through x0vncserver. For package users, the practical pattern is simple: install the package, set or store a VNC password, start or connect to a server, and keep the rest of the workflow in shell scripts, service units, or desktop launchers. ### Why package nerds care TigerVNC is significant because it packages a historically important remote-desktop protocol into reproducible open-source builds. It sits at the intersection of X11, remote access, compression, authentication, systemd services, and desktop packaging. Its package details matter more than average: client-only versus server components, password-file locations, XDG configuration paths, FLTK viewer behavior, and platform support all affect whether a user can connect to a remote GUI from a freshly provisioned machine. ### Timeline - 1999-2008: README copyright acknowledgements trace inherited VNC, X Window System, TightVNC, and RealVNC lineage. - Early 2009: README says TigerVNC split from TightVNC so TightVNC could focus on Windows platforms. - 2014: GitHub repository for TigerVNC/tigervnc created. - 2020s: Official tags and repository metadata show continued 1.x releases and active maintenance. ### Related projects - The README names RealVNC 4, X.org, TightVNC, and libjpeg-turbo as central lineage or supporting technology. - TigerVNC belongs to the broader VNC ecosystem of viewers, servers, X11 virtual framebuffers, and remote-desktop tooling. ### Sources - - - ## Security Notes No matching local secret-handling manifest was found for tiger-vnc. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: $XDG_CONFIG_HOME/tigervnc/default.tigervnc, ~/.config/tigervnc/default.tigervnc ## Credential files - Unix: $XDG_CONFIG_HOME/tigervnc/passwd, ~/.config/tigervnc/passwd ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** tiger-vnc - **Version Scheme:** 0 - **Revision:** 1 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Scoop - extras/vncviewer: installed executable or alias match | Scoop official bucket manifest trees: bucket/vncviewer.json from https://api.github.com/repos/ScoopInstaller/Extras/git/trees/master?recursive=1 - winget - RealVNC.VNCViewer: installed executable or alias match | Windows Package Manager source index: RealVNC.VNCViewer from https://cdn.winget.microsoft.com/cache/source.msix ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [Homebrew utility packages](https://www.automicvault.com/pkg/brew-utility-packages/) - Matched Homebrew package provider. - [gettext](https://www.automicvault.com/pkg/brew/gettext/) - Runtime dependency declared by Homebrew. - [gnutls](https://www.automicvault.com/pkg/brew/gnutls/) - Runtime dependency declared by Homebrew. - [jpeg-turbo](https://www.automicvault.com/pkg/brew/jpeg-turbo/) - Runtime dependency declared by Homebrew. - [nettle](https://www.automicvault.com/pkg/brew/nettle/) - Runtime dependency declared by Homebrew. - [cmake](https://www.automicvault.com/pkg/brew/cmake/) - Build dependency declared by Homebrew. - [gtk-vnc](https://www.automicvault.com/pkg/brew/gtk-vnc/) - Shares av.db curated category or tags: cli, networking, remote-access, remote-desktop, vnc. - [vncsnapshot](https://www.automicvault.com/pkg/brew/vncsnapshot/) - Shares av.db curated category or tags: cli, networking, remote-access, remote-desktop, vnc. - [x11vnc](https://www.automicvault.com/pkg/brew/x11vnc/) - Shares av.db curated category or tags: cli, networking, remote-access, remote-desktop, vnc. - [putty](https://www.automicvault.com/pkg/brew/putty/) - Shares av.db curated category or tags: cli, networking, remote-access. - [soapyremote](https://www.automicvault.com/pkg/brew/soapyremote/) - Shares av.db curated category or tags: cli, networking, remote-access. - [telnet](https://www.automicvault.com/pkg/brew/telnet/) - Shares av.db curated category or tags: cli, networking, remote-access. - [gateway-go](https://www.automicvault.com/pkg/brew/gateway-go/) - Shares av.db curated category or tags: cli, networking, remote-access. - [mosh](https://www.automicvault.com/pkg/brew/mosh/) - Shares av.db curated category or tags: cli, networking, remote-access. - [freerdp](https://www.automicvault.com/pkg/brew/freerdp/) - Local metadata places this package in an adjacent workflow. Shared terms: cli, client, desktop, implementation, jpeg. ## Combined YAML source View the package source record on GitHub. [combined/tiger-vnc.yml](https://github.com/automic-vault/db/blob/main/combined/tiger-vnc.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph