Skip to content

Glossary

What is VNC?

VNC is a way to see and control another computer's screen over a network, using the Remote Framebuffer (RFB) protocol.

Updated · Facts checked · By Runtime Cloud

3 min read

Read as Markdown

On Runtime (withruntime.com), every desktop runs a VNC server and noVNC, so its screen opens in a browser tab through a private, token-protected address. The same desktop takes screenshots and mouse and keyboard steps over the API, which is what a computer-use agent needs. Each desktop is a Firecracker microVM of its own, so one user's session never shares a kernel or a display with another's.

How VNC works

A VNC server watches a display and sends its pixels to a client. The client draws them and sends back key presses and pointer moves. The protocol under it, RFB, is defined in RFC 6143. It works at the level of the framebuffer, the grid of pixels on the screen, so it does not care which operating system, desktop or program is running.

  • Server. It runs on the machine whose screen is shared: x11vnc and TigerVNC on Linux, and built-in servers on macOS and on Raspberry Pi OS.
  • Client. It shows the screen: RealVNC Viewer, TigerVNC's viewer, the macOS Screen Sharing app, or noVNC in a web page.
  • Port. By convention the server for display N listens on TCP port 5900 plus N, so the first display is on 5900.

noVNC: VNC in a browser tab

A web page cannot open a raw TCP connection, so a browser cannot speak RFB to port 5900 directly. noVNC is a VNC client written in JavaScript that speaks RFB over a WebSocket instead. websockify, from the same project, sits beside the VNC server and carries the WebSocket's bytes to it as plain TCP. The result is a desktop that opens from a link, with no viewer to install, which suits support sessions, training labs and watching an AI agent use a computer. How to run a Linux desktop in the browser builds one step by step.

VNC and security

VNC's own password check is weak. RFC 6143 describes VNC authentication as cryptographically weak and not meant for untrusted networks, and the classic scheme uses at most eight characters of the password. Common ways to protect a VNC server:

Protection What it does
Listen on localhost only The server takes no connections from the network at all
SSH tunnel The client reaches the port through an encrypted, logged-in tunnel
HTTPS with a login in front noVNC's page and its WebSocket sit behind a proxy that checks users
A VPN or private network Only machines on that network can reach port 5900

Never leave a VNC server reachable from the internet without one of these. Scanners look for open 5900 ports, and a server that has no password gives its screen, and its keyboard, to whoever connects.

VNC and RDP

Point VNC (RFB) RDP
What it sends Pixels of the screen Drawing commands, with pixels as a fallback
Session Usually shares the screen that is running Usually starts its own session for the user
Operating system Any, through the framebuffer Built for Windows, with servers for Linux
In a browser noVNC Gateways such as Apache Guacamole

VNC is the common choice on Linux servers and for headless displays such as Xvfb, because it needs nothing from the desktop it shares.

Sources

Facts on this page were checked on 17 November 2026.

Cut your cloud billby 66%.

7 days of Pro for $0, and no card to sign up. Billed by the second after.

Start your free trial