An independent Windows Parsec client with a native Rust core.
EvoParseq connects to existing, unmodified Parsec hosts. Native Rust handles sign-in, computer discovery, signaling, transport, GPU video, audio and input. It does not bundle or run the proprietary Parsec WebAssembly client core and requires no browser, WebView or helper executable.
This is an independent community project, not affiliated with or endorsed by Parsec, Unity or lowlat. A Parsec account and a compatible host are required.
The stable release is EvoParseq v0.9.5.
main contains the stable Windows client; dev carries ongoing Windows and
Android TV development. Android TV previews are not part of this Windows release.
- Native account and sessions: optional 2FA, encrypted remembered sign-in, background-refreshing computer picker and manual peer ID. Owner connections are supported; friend/invitation authorization is not implemented.
- WebRTC or BUD: direct or custom TURN connections over UDP/TLS/TCP, Force TURN, STUN-only and Cloudflare TURN credentials. No silent transport switch. Optional experimental Windows TCP/TLS QoS marks outgoing TURN traffic.
- GPU video: H.264 and H.265/HEVC, GPU selection, Media Foundation and experimental vendor HEVC decoders, 10-bit SDR output, original-surface zero-copy, and compatible NVIDIA/Intel HEVC 4:4:4 at 8 or 10 bits.
- Session overlay: draggable icon; resolution, bandwidth, FPS, constant FPS, orientation, fullscreen and immersive input controls. Switch the current stream between host-listed physical or virtual displays.
- Audio: stereo Opus, configurable buffering, BUD raw PCM and experimental multichannel output. Automatically reopen the Windows audio output after transient device errors or default-device changes, retiring stale audio.
- Input: two-way Unicode text clipboard; normal mouse/keyboard forwarding; experimental BUD USB HID mouse and keyboard, including relative camera input.
- Diagnostics: route, RTT, traffic, FPS, actual decoder/format, audio queues, host/local timings and system resource use. Optional bounded event logs record failures without continuous mouse/key activity.
- Presentation: Automatic, Low latency, VSync and experimental DXGI VRR, with reference-safe catch-up after bursts. VRR requires an enabled compatible display/driver; DXGI support alone does not verify panel activation. Zero copy retains Windows-managed timing. WebRTC uses bounded recent queue history.
Host permissions, encoders and graphics drivers determine the actual stream. Connection stats shows the received depth/chroma and application RGB output; a selected preference alone does not prove that the host accepted it.
The Session panel compares the client's configured display refresh with the host FPS setting and shows measured decoded FPS separately. It can suggest a Windows-listed refresh rate at the current client resolution for more even fixed-refresh cadence; it never changes the display automatically. VRR activation is not verified. A confirmed 120 FPS request does not prove 120 distinct frames: the captured host display/mode must support it, and static content can lower FPS.
Start with Normal GPU rendering for compatibility. Zero copy skips a separate picture-conversion pass on supported systems; AI upscaling can improve enlarged video but uses more GPU resources and may add latency. The animation illustrates processing order, not measured speed. Check Connection stats for the mode actually in use.
- Download
EvoParseq-v0.9.5-win64.zipfrom the stable release. Development artifacts are also available from successful dev CI runs. - Extract to a writable folder and run EvoParseq.exe. Settings and optional
encrypted sessions are stored beside it in
settings.json. - Sign in with the host owner's account, choose a computer and connect. Configure Network, Video, Audio and Input in Settings. Save and reconnect after changing transport or connection capabilities; session video requests can be applied while connected.
Windows 11 x64 and a GPU with Direct3D feature level 11.0 or newer are required, with compatible D3D11 video-support drivers. The DirectX version shown on dxdiag's System tab is the installed runtime version; check Feature Levels on its Display tab for the GPU's capabilities. DirectX 10.x hardware, such as the GeForce 210, is unsupported. Support below feature level 11.0 is not planned, as it would require developing and maintaining a separate video path in parallel.
Zero-copy requires Windows 11 and suitable drivers. Ordinary client use needs no admin rights. The stock host must already be configured for hosting.
Upgrading from ParsecWebTurn: keep settings.json under the same Windows
account and sign in again. The old web-core login is not imported. A legacy-named
transition ZIP supports existing executable shortcuts. After the repository rename,
older updaters may reject the new download URL; use the release page for this
one-time manual upgrade. See migration.
Help > Check for updates offers newer stable EvoParseq packages; prerelease
installation is manual.
| Shortcut | Action |
|---|---|
| Ctrl+Shift+M / Ctrl+Shift+O | Open session menu and restore hidden icon |
| Ctrl+Shift+W | Toggle fullscreen |
| Ctrl+Shift+R | Release / recapture remote input |
| Ctrl+Shift+Q | Disconnect |
| Ctrl+Shift+S | Open Connection stats |
| Ctrl+Alt+End | Request host Ctrl+Alt+Del |
These exact shortcuts stay local; their trigger keys are not also forwarded to the host. In Keyboard or Keyboard + Mouse immersive mode, other supported keys and combinations (including Alt+Tab, Alt+Enter, Windows-key chords and F8/F11) are forwarded while the stream has input focus. Extra Alt/Windows modifiers do not activate a Ctrl+Shift client shortcut. Local menus and released input retain normal Windows handling; Ctrl+Shift+R releases or recaptures remote input.
Ctrl+Alt+Del requires the installed Parsec host service and permissions; a portable host may not execute it.
TURN forwards encrypted session traffic when NAT or a firewall prevents a direct connection. The stock Parsec host stays unmodified. The client-to-relay leg can use UDP, TLS or TCP; the relay-to-host leg uses UDP. Direct connections remain available unless Force TURN relay is enabled.
A relay does not necessarily mean higher latency. When the route through the relay is better than the available direct or VPN route, TURN can deliver comparable or even lower round-trip time (RTT). This depends on ISP peering, relay location and congestion; it is not a guaranteed improvement. Compare the actual routes in Connection stats. Cloudflare describes its routing in TURN and anycast. No separate VPN, tunnel client, driver or relay helper needs to be installed on the client PC: TURN support is built into the application.
Cloudflare Realtime TURN is our recommended relay. A free Cloudflare account is sufficient, including an account already used for Zero Trust Free. TURN is a separate Realtime service: no paid Zero Trust plan or Cloudflare Tunnel is required.
- Sign in to the Cloudflare dashboard, select your account, and open Realtime → TURN Server → Create (or search for TURN Server in the dashboard).
- Give the TURN key a name and create it. Copy its TURN Key ID / Token ID and API Token from the resulting credentials panel.
- In the client's Settings → Network, select Cloudflare TURN, enter the key ID and API token, then save and reconnect. The client generates temporary TURN credentials automatically. Enable Force TURN relay if you want to require the relay; Connection stats shows the route actually used.
Keep the API token private; do not attach it or settings.json to issues.
See Cloudflare's setup guide
and dashboard example.
Free allowance: 1 TB (1,000 GB) per month, shared with Realtime SFU. At a constant average relayed bitrate, this is approximately:
| Average relayed traffic | Hours/month | Hours/day over 30 days |
|---|---|---|
| 10 Mbit/s | 222 | 7.4 |
| 20 Mbit/s | 111 | 3.7 |
| 30 Mbit/s | 74 | 2.5 |
| 50 Mbit/s | 44 | 1.5 |
Video uses a variable bitrate: with little or no screen movement, such as mostly static desktop work, it can use much less bandwidth than during active gameplay. Read the table using the actual average relayed bitrate, not the configured bandwidth limit. Lower average usage makes the allowance last longer; these figures are estimates, not fixed daily streaming limits.
Estimates use decimal GB and exclude audio/control/protocol overhead, which reduces the available streaming time. Actual usage varies with the stream; direct traffic does not consume TURN allowance. Cloudflare meters traffic sent from its edge to the TURN client. Usage above the shared allowance is currently $0.05/GB; check current pricing and the TURN billing FAQ.
The Video tab offers one AI upscaling (experimental) selector: NVIDIA RTX VSR has Off/Low/Medium/High/Ultra; Intel VPL AI has Off/On. Other GPUs disable the control. Each vendor's saved preference is retained.
Both paths upscale on the GPU in normal DXGI mode. They add GPU processing, resources and an output copy, may increase latency, and are not Zero copy. Unsupported configurations retain ordinary rendering. No CPU pixel readback or generated frames are introduced.
- NVIDIA: RTX Video SDK 1.1.0; RTX 3060 playback is live-confirmed.
The runtime is outside the EXE. On first launch with an NVIDIA GPU, setup asks
permission before downloading the pinned official NVIDIA payload. Archive
and DLL hashes are checked; verified caches are reused. The DLL lives under
%LOCALAPPDATA%/EvoParseq/vsr/1.1.0, without admin rights. Declining leaves normal video available; enabling VSR later can authorize setup on next launch. SDK-enabled packages include NVIDIA's license; no CUDA toolkit is required. - Intel: documented VPL 2.17 API with the installed Intel driver runtime, without a bundled/downloaded DLL or model. Hardware operation is unverified. Strict checks require the AI filter and same-device D3D11 surfaces; rejected runtime/configuration details remain in event logs. Currently limited to 8-bit SDR upscaling; 10-bit, 4:4:4 and Zero copy keep their existing paths.
Vendor HEVC, zero-copy, 10-bit HEVC, 4:4:4, display timing, USB HID and multichannel audio remain experimental. For conservative operation, use H.264, stereo Opus and Automatic timing with experimental options disabled.
- Video: live decoded frames remain on the GPU. Normal rendering uses the conversion/output pass; zero-copy presents original 8-bit NV12 or capability-checked 10-bit P010 surfaces. HEVC 10-bit 4:2:0 Zero copy is live-confirmed by the maintainer on tested AMD and NVIDIA systems. Intel HEVC, including 8/10-bit 4:4:4 normal rendering, has also been live-tested on the maintainer's UHD 770 setup; this does not establish support on every Intel GPU or driver. Driver/compositor copies and direct scanout are not independently verified.
- 10-bit: RGB10 output is SDR, not HDR. NVIDIA host encoding is confirmed; other host encoders may refuse it or send 8-bit. An initial encoder failure asks you to disable 10-bit and reconnect. AMF Main10 output is live-validated on AMD Radeon 780M and is now the AMD default.
- 4:4:4: 8/10-bit playback is live-validated on NVIDIA RTX 3060. Intel UHD 770 8/10-bit playback is also live-confirmed. Support remains capability-gated; a measured UHD 770 driver-query exception is logged. AMD selection is disabled. H.264 stays 4:2:0; 4:4:4 does not combine with original-surface zero-copy. Compatible host encoding, account permissions and service terms still apply.
- HID: requires BUD and the stock host's USB/Yubikey passthrough plus its supported USB driver. HID mouse uses the host primary display and disables display switching; forwarding pauses until that selection is reported. Use matching host/client keyboard layouts. No host patch is needed.
- Audio: raw PCM is BUD-only and requires host permission
(
network_raw_audio=1). WebRTC remains stereo Opus. Multichannel audio has synthetic coverage only; live surround playback/channel order is unconfirmed. - Displays and timing: host virtual-display limitations can delay switching. Reported timings are CPU/host durations, not GPU completion, scanout or total latency. Adaptive catch-up, QoS benefit and physical audio-device recovery still require broader live testing; no measured latency gain is claimed.
Gamepads, microphone/camera forwarding, HDR and multi-monitor HID mapping are not implemented. See the changelog for shipped changes.
Enable Event logging in Network settings for client-events.jsonl beside
settings.json. Include the build, GPU/driver, transport and reproduction steps
with a log or screenshot when reporting issues. Logs omit credentials, media,
clipboard text and continuous input. Do not publish settings.json or tokens.
Saved credentials use Windows CurrentUser DPAPI; copying them to another machine
or Windows account does not transfer access. --data-dir "C:\YourFolder" selects
another writable data directory.
Build with Rust MSVC and Windows C++ Build Tools/SDK:
cargo build --locked --release --manifest-path src-native/Cargo.tomlCI packages src-native/target/x86_64-pc-windows-msvc/release/evoparseq.exe as
EvoParseq.exe. Application logic lives in src-native/src; platform, transport
and video adapters reuse the existing bounded workers and GPU path.
Architecture · Settings comparison · Development references
Thanks to Duy (Nguyen Duy) and lowlat for inspiration, feedback and selected MIT-licensed protocol, transport and GPU components. Their licenses and local-change notices are retained. EvoParseq is independently developed and maintained; it is not an official lowlat client.
Our code uses the MIT license. Applicable Parsec service terms and third-party licenses still apply. Development did not use Parsec's proprietary source code, and EvoParseq does not patch the official host or client. Parsec and Unity names and marks belong to their owners; no affiliation is implied.

