Installation

VRCS is available for Windows and Linux (x64). Sign in with the Nyxall account that has access, and the download button on the project page offers the build for your system (you can also pick the other one). The SHA-256 checksum of every build is listed next to its download on your downloads page.

Windows

1. Download VRCS_<version>_Setup.exe.
2. Run it. VRCS is not code-signed, so Windows may say the publisher is unknown and SmartScreen may warn you: after verifying your download (below), choose More info → Run anyway.
3. Follow the wizard. It can install over an existing VRCS install, or over the open-source app it builds on — your settings and data are kept; they live separately in %APPDATA%\VRCX.

Windows installs update themselves: see Updating.

Portable (no installer)

Download VRCS_<version>.zip, extract it anywhere, and run VRCX.exe from the extracted folder (the program file keeps its old name so existing installs keep working). Portable copies still keep their data in %APPDATA%\VRCX.

Linux (x64)

Tested on Ubuntu 24.04 (x64, GNOME). Other distributions may work but have not been tested, and there is no ARM64 Linux build.

1. Install the FUSE 2 library (once)

AppImages need libfuse.so.2, which a clean Ubuntu install does not include:

sudo apt install libfuse2t64

(On Ubuntu 22.04 and older the package is called libfuse2.)

2. Download and start VRCS

Download VRCS_<version>_x64.AppImage, then:

chmod +x VRCS_<version>_x64.AppImage
./VRCS_<version>_x64.AppImage

On first start VRCS offers to install itself: it moves into ~/Applications and adds a VRCS entry to your app menu, so you can start it from there afterwards. Keep the AppImage inside your home folder.

3. Allow the sandbox on Ubuntu 23.10 and later (once, if asked)

VRCS always runs with Chromium’s security sandbox on. Ubuntu 23.10 and later restrict the user namespaces that sandbox needs, so the first start may show a message saying VRCS can’t start safely instead of opening. By then VRCS has already written a small AppArmor profile that grants those namespaces to the VRCS AppImage only. Install it with the command from the message:

sudo install -m 644 ~/.config/VRCX/vrcs-appimage.apparmor /etc/apparmor.d/vrcs-appimage
sudo apparmor_parser -r /etc/apparmor.d/vrcs-appimage

Then start VRCS again. Please don’t work around this by running VRCS with --no-sandbox or by turning off the namespace restriction system-wide — VRCS refuses to run unsandboxed on purpose, and the profile only affects the VRCS AppImage.

What works on Linux, and what hasn’t been tested

Tested on Ubuntu 24.04 x64: installing and replacing an older AppImage, Nyxall sign-in (it opens your default browser), VRChat login, staying signed in across restarts, settings, profiles and decorations, menus, the clipboard, the tray icon, and quitting and restarting cleanly.

Not yet tested on real hardware: Steam/Proton integration, reading VRChat’s log (the instance and player views depend on it), Open in Game, and VR headset overlays. Phone pairing is not available on any platform yet.

Your data lives in ~/.config/VRCX.

Verifying your download

Compare the file’s checksum with the SHA-256 listed next to the download. It must match exactly — if it doesn’t, delete the file and download it again. Never run a file that fails verification.

# Windows (PowerShell)
Get-FileHash .\VRCS_<version>_Setup.exe

# Linux
sha256sum VRCS_<version>_x64.AppImage

Older macOS and ARM64 builds

Releases up to 2026.09.20a also attached macOS (DMG) and Linux ARM64 builds. Those builds were never tested on real hardware, are not updated after 2026.09.20a, and are not offered for download here. VRCS 2026.09.21 and later are released for Windows and Linux x64 only.