Skip to content

Parsec

Parsec is a low-latency remote desktop and game-streaming client. It covers two related use cases with the same underlying tech:

  • Remote access — connect to your own gaming PC or workstation from another device, anywhere.
  • Session sharing — invite friends into a running session for couch co-op style play, with per-guest control over keyboard/mouse/controller input.

How it works

flowchart LR
    H[Host PC\nGPU + Parsec host app] -->|encode: NVENC/QuickSync/AMF| S[Video/audio stream]
    S -->|peer-to-peer, encrypted| C[Client device\nParsec client app]
    C -->|input: keyboard/mouse/controller| H
  • The host runs the Parsec app in host mode and grants access to specific guests (or itself, for remote access to a personal machine).
  • The client connects with the desktop app or a browser and streams the host's screen while sending input back.
  • Connections are peer-to-peer by default: Parsec's infrastructure only brokers the initial handshake (NAT traversal, session listing) — it does not sit in the video/input path and cannot see session content. Parsec for Enterprise adds an optional relay server for cases where direct P2P is not reliable enough.
  • Video is captured via hardware encoders (NVIDIA NVENC, Intel QuickSync, AMD AMF) on the host GPU rather than software encoding, which keeps CPU overhead and encode latency low.

Key characteristics

Property Detail
Latency model Proprietary streaming protocol, tuned for near-zero added latency vs. generic RDP/VNC
Max quality Up to 4K at 60 FPS, up to 240 FPS at lower resolutions, 4:4:4 color (Warp tier)
Connection Peer-to-peer, encrypted; optional relay on Enterprise
Platforms Windows, macOS, Linux, Raspberry Pi client, web client
Security SOC 2 Type 2 certified; MFA available; host controls which apps a guest can see/interact with

Access control model

The host decides per session:

  • Which connected guest gets input control (keyboard, mouse, controller) vs. view-only.
  • Which applications a guest is allowed to see and interact with, rather than the full desktop.
  • Whether the session is a 1:1 remote session (only you, from another device) or a shared session (multiple guests, e.g. split-screen co-op with controllers).

This is the same mechanism whether the "guest" is a friend or a second device you own — remote access to your own PC is just a session where you are both host and only guest.

Tiers

Tier Target use Notable extras
Parsec Free, consumer Personal remote access, friend sessions
Parsec Warp Creative pros Pressure-sensitive tablet support, 4:4:4 color, multi-monitor
Parsec for Teams Distributed teams On-prem data, admin access controls
Parsec for Enterprise Large orgs Relay server, SSO/SCIM, API access

Moonlight + Sunshine — the open-source alternative

Moonlight and Sunshine are the open-source counterpart to Parsec, and the one most likely to come up if a friend is already self-hosting a streaming setup.

  • Moonlight is the client. It reimplements NVIDIA's GameStream protocol and is available on Windows, macOS, Linux, Android, iOS, and embedded platforms (Raspberry Pi, Steam Link hardware, smart TVs).
  • Sunshine is the self-hosted server/host component, maintained by LizardByte. It replaced the discontinued NVIDIA GameStream server and added hardware encoding support for AMD, Intel, and NVIDIA GPUs (software encoding as a fallback).
flowchart LR
    H[Host PC\nSunshine server] -->|encode: NVENC/QuickSync/AMF/VCE| S[Video/audio stream]
    S -->|direct connection, LAN or port-forwarded WAN| C[Client device\nMoonlight app]
    C -->|input: keyboard/mouse/controller| H
Property Parsec Moonlight + Sunshine
License Closed-source, commercial Open-source (GPL/AGPL components)
Hosting Managed handshake, P2P data path Fully self-hosted; you manage NAT traversal/port forwarding
Setup effort Install + sign in, works out of the box Manual server config (Sunshine), pairing PIN, router setup for WAN
Hardware encoding NVENC, QuickSync, AMF NVENC, QuickSync, AMD AMF/VCE
Cost Free tier covers personal/friend use; paid tiers for teams Free, no tiers
Support model Vendor-supported, SOC 2 Type 2 Community-supported (GitHub issues, Discord)

In practice, both rely on the same class of hardware encoders and achieve comparable latency on a good connection — the real trade-off is convenience versus control. Parsec's relay-assisted handshake removes the need to touch router settings; Sunshine gives full control over encoding settings, resolution overrides, and virtual display creation, at the cost of doing that configuration yourself.

Comparison with alternatives

Tool Model Notes
Parsec Commercial, managed Proprietary protocol, hardware encoding, P2P
Moonlight + Sunshine Open-source Client/server pair, NVENC-based, similar performance profile
Microsoft RDP Built into Windows AVC444 in modern versions, not GPU-encoder-first by default
VNC (TightVNC, NoMachine, RustDesk…) Various Generally higher latency, not game-streaming oriented

Sources