v2rayN Usage Guide · Clients

V2Ray Client Downloads

Choose the operating system for your client, then match the package format to your device's architecture.

Choose a package by platform

Installation and upgrade notes ↓

Windows clients

v2rayN Recommended

Windows x64 · ZIP 7.24.1

Which interface should I choose? Desktop uses the newer cross-platform interface and is the recommended choice for a first install. WPF is the classic, stable edition for users who prefer the original menus and tray layout. Choose one package, not both. If you're following an older guide, check which interface its screenshots show.

How to open the ZIP: In your Downloads folder, right-click the archive and choose Extract All. Open the extracted folder and run the installer inside. Don't run it from the archive preview, or drag just one file to your desktop and launch it.

Note the error if startup fails: If a dialog names a missing desktop runtime, note its name, version and architecture, then install what's specified. If the window closes but the notification area still shows an icon, the client may still be running. Before switching editions, fully quit the old one from its tray menu.

Installation and upgrade notes

For a first install, make sure the client opens. Before upgrading, check that your configuration is preserved. Keep startup issues separate from connection problems.

First install: launch before configuring

  1. Open the complete file from your downloads. If the download is still in progress or the file has a temporary extension, wait for it to finish. If the download was interrupted, return to the platform section and download the same architecture and package format. Don't rename the extension to try to open it.
  2. Make sure you can reach the main screen first. On desktop, leave the system proxy unchanged for now; quit any older client that's still running. On Android, opening the app and establishing a VPN connection are separate steps. Handle the system connection prompt when you test the connection for the first time.
  3. Import your configuration before testing the connection. Check that a node appears in the list, then test a node you know works. Change one setting at a time and note the result before proceeding. Subscription URLs and single-node links use different import options; see the Client Setup Guide.

Upgrade in place: back up before replacing

  1. Record your current settings. Take screenshots of settings without exposing subscription URLs, and note your current proxy mode and port. Prefer the old client's export or backup feature, make sure you can locate the backup, then quit the old version. Backups may contain connection credentials, so store them somewhere only you can access.
  2. Check the target client. Don't assume data will migrate when switching Windows editions or changing to a different Android client. If Android reports a signature conflict, keep the old version and your backup. Uninstalling usually deletes that app's local data.
  3. Check the upgrade one item at a time. First check the version and groups, then the local port and system proxy status. If startup fails, keep the error message and the old-version backup; don't repeatedly install over the same directory. To roll back, restore the pre-upgrade backup instead of letting the old version read data rewritten by the new one.

Common download questions

Do I need to install both Windows editions?

No. For a first install, choose Desktop. If you prefer the classic interface, choose WPF. Neither edition depends on the other. If you have an older version, quit the client and back up your data before installing the edition you want.

How do I choose the right DMG for macOS?

Open About This Mac. If Chip shows an Apple M-series chip, choose Apple Silicon (arm64). If Processor shows Intel, choose Intel (x64). Use the hardware information shown by macOS, not the year you bought the Mac.

When should I use the universal Android version?

Choose arm64 if your system supports arm64-v8a. If you don't know which ABIs your system supports, or the installer reports an architecture mismatch, try the universal version. It won't fix an outdated Android version or an app-signature conflict.

Do amd64 and x86_64 both mean x64 on Linux?

Yes. The DEB packages on this page use amd64, while the RPM packages use x86_64; both are x64. For 64-bit ARM, DEB packages commonly use arm64 and RPM packages use aarch64. Choose the package format first, then check the architecture.

Why are there no server nodes after I install the client?

The package contains only the client. If you have a subscription URL, add it to a subscription group in the client and update the group. To add a single-node share link, use the client's import feature. Confirm the configuration appears in the list, then select a node to connect.