Client Downloads / Platform Index

V2Ray Client Downloads

For desktop, choose v2rayN. For Android, v2rayNG is the first choice; v2flyNG is another option if your configuration requires it. Select the target operating system, then choose the architecture and package format.

Choose a package in this orderOperating system → Processor architecture → Package

Windows packages

v2rayN

v2rayN

7.24.1
Recommended

Both downloads are x64 ZIP packages. Desktop is the newer cross-platform interface and a good place to start for a first install. WPF is the classic, stable version for users who prefer its familiar interface and workflow. Choose one.

From extraction to first launch

Extract the entire ZIP to a directory you can write to, then run the installer from the extracted folder. Don’t launch it from the archive preview or drag out just the installer and leave its companion files behind. On a managed work device, check your organization’s installation and permission requirements first.

If the app won’t open, check whether the system reports an architecture mismatch, a missing runtime, or insufficient permission to write to the directory. If a runtime is required, follow the prompt for the named component and version. Switching to the other interface won’t fix an architecture mismatch.

Before switching from the classic version to Desktop, save your subscriptions and custom rules, then quit the old client from the system tray. Once the new interface can update subscriptions and connect successfully, you can remove the old version. If you keep the old configuration, don’t point both programs at the same data in active use.

Downloads, updates, and initial setup

First identify what you’re doing: installing for the first time, updating an existing version, or switching clients. For a first install, check that the device can run the package. For an update, consider existing settings and the installation source. When switching clients, check whether your subscription’s protocols and settings will carry over. Treating these as separate tasks can save time and avoid unnecessary troubleshooting.

Before downloading: check the device you’ll install on

If you’re downloading on a computer for another device, don’t choose a package based on the system running your current browser. Check the target device’s operating system, version, and architecture in its system information, then select a package here. This is especially important when transferring an installer between computers: the same operating system can have different package options.

After starting the download, check the browser’s download list to make sure it has finished. If it’s paused or interrupted, resume it or download the file again; don’t open an incomplete file. Save it somewhere easy to find. If the folder contains multiple versions, compare the download time and full filename instead of relying on the icon.

Before updating: back up subscriptions and custom settings separately

Subscription addresses and client settings are separate types of data. Updating a subscription can retrieve configurations provided by the server, but it may not restore manually added configurations, custom routing rules, local ports, or app-specific settings. Before updating, use the client’s export feature where available. For settings that can’t be exported, make a note of the non-sensitive details you’ll need to restore.

Subscription addresses may contain parameters that grant access to account settings. Don’t post an address, QR code, or full runtime log in public comments, and don’t upload unredacted configuration backups to shared drives. For troubleshooting, the operating system version, client name, steps to reproduce the issue, and an error message with sensitive details removed are usually enough.

Before updating a desktop version, stop the connection and fully quit the background process. Before replacing an app on a mobile device, check whether it supports an in-place update or requires a reinstall. If the new version has problems, record the error and restore the last working setup from your backup. Avoid changing the package, subscription, and proxy mode all at once.

After installation: test subscriptions, connections, and apps in order

When you first open the client, check that the main window opens and that settings can be saved. Next, add a subscription group, update it, and select the configuration you want to test. A successful subscription update only confirms that the client retrieved the subscription content; test node connectivity and app traffic separately.

Start by testing an app that reads the system proxy settings. On desktop, begin with the system proxy and look into TUN mode only if needed after confirming the basic connection. On mobile, check whether the system allows a VPN connection and whether another VPN is already active. If the connection works but one app doesn’t, check whether it uses system settings, its own proxy settings, or a direct connection.

When something fails, note which step it happened at. If the installer won’t open, check the architecture and system requirements. If the client opens but has no configuration, check the subscription group and update result. If a configuration appears but won’t connect, check what’s enabled and review the runtime log. Change one thing at a time and test again so installation issues don’t get mixed up with connection issues.

Download FAQs

Do I need to install both the Desktop and classic WPF versions?

Choose one. For a first install, start with Desktop. If you already use a WPF workflow, stick with the classic WPF version. Don’t run both versions at the same time with the same configuration; their local listening ports or system proxy settings may conflict.

Should I choose x64 for every 64-bit system?

No. Both x64 and arm64 are 64-bit architectures. Check the processor architecture in your system information. For Linux package names, amd64 and x86_64 correspond to x64, while aarch64 corresponds to arm64.

Android says the APK can’t be installed. What should I check first?

First check system compatibility, available storage, and permission to install from the current source. Then check whether an older version with the same package name but a different signature is installed. A universal package may help with architecture selection, but won’t fix a signature conflict. Back up your subscriptions and settings before uninstalling the old version.

The version shown on the card doesn’t match the package name. Which should I trust?

The card version and package download links come from separate manifest entries, so they may not match. To confirm the installed version, check the app details shown by the installer or open the client’s About page after installation. Don’t rely on the card version alone.

Why are there no usable nodes after installing the client?

The installer provides the client, not a subscription service. Get a subscription address you’re authorized to use, import it, and update it. Then select a configuration on the main screen. If you already have configurations, check that the right group is selected.