Client / Downloads

V2Ray client downloads

Choose your operating system, then check the architecture. Use v2rayN on desktop; on Android, choose v2rayNG or v2flyNG to match your existing configuration.

Choose a package by platform

v2rayN

Recommended

Windows x64 · ZIP · 7.24.1

The desktop edition features a newer cross-platform interface and is a good place to start if you're installing for the first time. The classic WPF edition keeps the established Windows interface for those who prefer its familiar workflow. These are two interface options for the same client, not a main app and an add-on.

The download is a compressed archive. Extract it fully to a local folder where you have write access, then run the installer inside. Don't launch it from the archive preview, and don't mix files from the two editions in the same folder.

Windows system requirements

CheckRequirement
Architecture64-bit operating system with an x64-based processor
EnvironmentDesktop environment; dependencies vary by release and are listed in its release notes and installer prompts

Open Settings → System → About and check both the system type and processor. Seeing “64-bit operating system” isn't enough: if the processor is listed as ARM, don't treat these x64 packages as native ARM installers.

What to check before and after installation

Check OS, architecture, and version separately

The operating system determines which file type can open, the architecture determines whether the program can run on your device, and the version affects upgrade order and configuration compatibility. When switching devices, check the new device instead of reusing the old download. Even if two computers use the same client, different operating systems or chips may require different packages.

When comparing versions, rely on the information shown in the app and the installer prompts. The version listed on the download page comes from a manifest, and the filename may also contain a version number. If they don't match, don't decide whether to install over the existing version based on just one number. If the installer warns that it's downgrading the app or replacing a version from another source, cancel and check the app details and backup status in the old client first.

Back up local settings before upgrading

A subscription URL isn't a full backup. Locally added configurations, custom routing rules, auto-update intervals, and proxy ports may not be restored from a subscription. If the client offers an export feature, use it; otherwise, make a note of the key settings. After backing up, quit the old version and keep a recoverable copy. Delete it only after you've confirmed the new version imports your settings and connects successfully.

Use a connection test to separate installation from configuration issues

First, make sure the main window opens. Then follow the subscription import guide to save the URL and update the group. Once configurations appear, select one to test. “The client opens,” “the subscription updates,” and “app traffic is routed as expected” are three different outcomes. Note where the process fails; that makes troubleshooting easier than reinstalling.

For an initial desktop test, check system proxy settings and use an app that follows the system settings. On mobile, first confirm that the system allows the client to establish a VPN connection. Change one setting at a time, and avoid running two clients simultaneously. If something goes wrong, revert your last change before deciding whether to adjust routing or DNS.

Keep relevant context when sharing error details

Note your operating system, client name, package architecture, and the step where the error occurred. During installation, keep the exact error reported by the system; during connection tests, share only the relevant log entries. Remove full subscription URLs, credentials, and private server addresses from screenshots or logs before sharing them. For core differences, see the core section in the full handbook.

Download and installation FAQs

Do I need to install both the desktop and classic WPF editions?

Install either edition. The desktop edition uses a newer cross-platform interface, while the classic WPF edition retains the familiar Windows layout. Before trying the other edition, quit the running client and back up your existing configuration.

Why can't I install over an older Android version?

Android may reject an update if the app ID, signing key, or version sequence differs. Back up your settings in the old app first, then check whether the download matches the original installation source. Don't uninstall the old version just to get past the prompt; uninstalling may erase local settings.

Why is the list empty even though the app opens?

The client reads configuration; it doesn't include a subscription or server with the installer. Once you have a working subscription URL, add a subscription group and update it. The configuration list may remain empty if you only save the URL without updating.

Why won't a Linux package install even though the architecture matches?

Matching the package format and CPU architecture is only the first step; your distribution must also meet the package's declared dependencies. Check the missing packages or version conflicts reported by your package manager. Don't force the installation if your system repositories can't provide the required dependencies.

Will importing the same subscription restore all my settings on a new device?

A shared subscription mainly lets you retrieve the configuration it provides. Proxy mode, local ports, custom routing, and app permissions usually need to be checked again on the new device. If both clients support a compatible backup format, import a backup first, then review these settings.