CLIENT PACKAGES

V2Ray client downloads

Use v2rayN on desktop; for Android, start with v2rayNG or choose v2flyNG if you need its core. Check your OS and CPU architecture before choosing a package.

How to choose a package
  1. Choose your operating system
  2. Check your CPU architecture
  3. Choose a UI version or package format
Start with your OS

Platforms and packages

Switch to the platform you're installing on. Download options and system requirements will update together.

Windows downloads

v2rayN

Recommended
7.24.1 ZIP · x64

The desktop version uses a newer cross-platform interface. WPF is the classic, stable option for users who prefer the familiar interface. Both versions support subscription and routing management; there's no need to install both.

After downloading, select “Extract All” for the ZIP, then run the installer from the extracted folder. Before upgrading, exit the old version from the system tray; closing its main window may not stop the process. If the installer reports a missing runtime, check the runtime name, version, and architecture it specifies. Don't switch back and forth between Desktop and WPF in the hope of fixing it.

System requirements and where to check

CheckRequirement or where to check
System typeGo to Settings → System → About and check “System type.” This section provides x64 packages.
RuntimeOn older systems, first confirm compatibility with this release. If you're asked to install a .NET runtime, note the version shown in the dialog.
Installation permissionsThe installation location must be writable. On a managed device, check whether desktop app installation is allowed.

“64-bit operating system” alone doesn't identify the right package. Check whether the system also says “x64-based processor.” If it reports an ARM processor, neither of these downloads is a native ARM package.

Back up first

Installation and upgrade checklist

For a first install, start with the package type. Before upgrading in place, save your existing configuration and verify each step.

Choose a package for the OS you're running

The host OS, a virtual machine, and a dual-boot system on the same computer may all need different packages. Check system information in the OS where you plan to install the client. The processor model can indicate hardware capabilities, but it can't replace the app architecture reported by the running OS. A processor that supports 64-bit apps, for example, doesn't mean the current OS does too.

Check the OS, architecture, and package format on the download button, then review your browser's download history. If the download contains only an error message, or won't open and has the wrong extension, return to the platform and download it again. Changing a file extension won't turn a webpage into an installer or convert one architecture's package to another.

Back up your configuration, not just the subscription link

Refreshing a subscription can usually restore the nodes in that subscription group, but manually added servers, custom routing, and local listening ports may not be included. Before updating, use the client's configuration backup feature if available. Also note the group in use, selected routing mode, system proxy status, and whether LAN access is enabled so you can compare behavior after the upgrade.

Keep the old backup until you've confirmed the new version can read the configuration. Don't edit the same configuration directory in both versions at once. Subscription URLs, sharing QR codes, and exported files may contain connection credentials. Store backups somewhere secure. When asking for help, share only error excerpts with addresses and credentials removed.

Start the client before restoring proxy settings

On desktop, first confirm that the app opens and can read the server list, then select a configuration you normally use. Avoid changing ports, routing, and DNS at the same time. Restore the previous system proxy settings and test the same app, then toggle the proxy once for comparison. If the toggle makes no difference, check whether the app uses the system proxy before assuming the node is unavailable.

On Android, first check that the configuration imported successfully, then tap Connect and approve the system VPN request. If the configuration list is empty after an upgrade, check whether you opened a different client or the original configuration wasn't restored. A visible app screen doesn't mean it's ready to connect until a server is selected.

Record the error before changing settings

For an installer error, note the OS version, package type, and first missing requirement in the message. For a client error, find the first relevant log entry after the current launch. If a local port is already in use, check whether an old client is still running in the background. For certificate or timeout errors, check the system clock, server configuration, and current network.

Change one variable at a time during testing, and restore its original value if the test fails. For setup from a subscription, see the subscription import steps. To check listening addresses and ports, see the inbound fields reference. Troubleshoot these separately to avoid mistaking a configuration issue for the wrong installer package.

Download and installation FAQs

Do I need to install both the Windows desktop and WPF versions?

Install just one. For a first-time installation, choose the desktop version. If you're upgrading from the classic WPF version and want to keep its familiar interface, choose WPF again. Don't run both versions at once: they may compete for the same local listening port or overwrite system proxy settings in turn.

Should I choose arm64 or universal for my Android device?

Most mainstream Android phones released after 2015 can use arm64, but installation depends on the app architectures supported by the OS, not just the processor. Choose arm64 if the system supports arm64-v8a; if you're unsure, start with the universal build. If Android reports an incompatible version, the universal build won't lower the app's minimum Android version.

Why does an APK update conflict with the app already installed?

First, make sure both APKs come from the same release channel. Android won't install over an app with the same application ID but a different signing key, and it may also block downgrades. Don't uninstall just to troubleshoot. Back up any recoverable settings in the existing client, then try an update from the same channel.

Why did my v2rayN download come as a ZIP file?

The Windows download on this page is a ZIP archive. In File Explorer, select “Extract All,” then open the extracted folder and run the installer inside. Don't launch it from the archive preview or rename the file extension to EXE.

The client opens, so why can't it connect?

An open window only confirms that the client has started. Make sure the server list contains a usable configuration and that it's selected, then check the desktop system proxy or Android VPN permission. If it still fails, start with the first relevant log error and determine whether the problem is a local startup failure or a remote connection timeout.

View the Getting Started guide →