Client Releases / RELEASES

V2Ray Client Downloads

Check your operating system and processor architecture before choosing a package. Use v2rayN on desktop; on Android, choose between v2rayNG and v2flyNG.

Desktop
ZIP / DMG / deb / rpm
Mobile
arm64 / Universal APK
After installation
Import a subscription →

Choose a package by platform

Windows client

v2rayN

v2rayN

Recommended
Manifest version
7.24.1
Package format
Installer included in ZIP

Desktop is the newer cross-platform interface, suited to first-time installs and anyone who wants a consistent layout across desktop operating systems. WPF is the classic, stable version, suited to users familiar with the older interface or following a guide for the classic edition. The different interfaces don't require a different subscription. When following a guide, check the menu names first, then look for the matching option.

Windows system requirements and installation
CheckRequirement
OS and architectureWindows 11 x64, which is still supported, is recommended. Go to Settings → System → About and confirm that System type says “64-bit operating system, x64-based processor.”
RuntimeIf the installer reports that the .NET Desktop Runtime is missing, check the required version and architecture. Don't substitute a different runtime version.
Extraction and permissionsKeep the entire extracted folder intact. If installation is restricted on a work device, ask your administrator to confirm the installation policy first.

Before updating, fully exit the old instance from the system tray; closing only the main window isn't enough. A desktop shortcut that still points to the old folder may launch the outdated version after the update. Check the shortcut target, then confirm the running version in the app's About information.

Installation notes / NOTES

First install and in-place updates

Whether a package installs, the app launches and the configuration connects are three separate questions.

Before downloading: check these three things separately

Identify your operating system first, then check the architecture it reports, and finally confirm the OS version and dependencies required by the package. “64-bit” describes the word size; it doesn't distinguish x64 from arm64. The same architecture may also use different package formats on different operating systems. Built-in system information is more reliable than a device's age, appearance or product listing.

On a shared computer, work computer or managed phone, also check the local installation policy. Even if the package matches the architecture, account permissions, administrator policies or work-profile restrictions may block installation. Confirm what's allowed first; don't disable protections or keep trying different packages.

Before updating: separate the app from its settings

The installer updates the app, while personal settings may be stored in a separate data directory. Before updating, use the client's backup or export feature to save subscription groups, manually added nodes and custom routing rules. If you need to back up the data directory, quit the client first to avoid copying files while they're being written.

A subscription URL can only restore the entries provided by the subscription; it won't restore all your local changes. Make a note of the current version, installation channel and data location too. Backups may contain connection credentials, so keep them somewhere access-controlled and don't share them publicly in screenshots or logs.

First launch: test with a minimal configuration

First, make sure the main window opens normally. Then follow the subscription import guide to add a configuration and select an entry. For the first connection, leave custom routing and DNS settings out. Check the client's connection status and test access in a regular app. Once the basics work, add extra settings one at a time.

If the app won't open, start with the system requirements and installation messages. If it opens but can't read the configuration, check that the subscription imported successfully. If the configuration appears but won't connect, check the selected node, connection logs and client mode. This order helps distinguish installation issues from configuration problems and makes it easier to roll back one step at a time.

Download FAQ / FAQ

Package and update FAQs

Not sure which architecture your device uses? Can you choose the universal version?

The universal version is an Android option that includes multiple application binary interfaces. It does not bypass Android version or installation permission requirements. Desktop clients have no equivalent universal option, so check your processor type in system information before choosing a package.

Why is the Windows download a ZIP file that won't run directly?

The ZIP is a compressed container for the installer. Extract the entire archive to a regular folder, then run the installer from there. Don't launch it from the archive preview; the preview tool may extract only the executable to a temporary location, leaving it unable to access files stored alongside it.

Android says there's an app conflict during installation. Should I uninstall the existing app first?

First check whether the installed app and new package come from the same distribution channel, and whether the new package is a downgrade. Android may block an update if the signatures differ or the new version is older. If you need to uninstall and reinstall, back up your subscriptions, manually added nodes and local rules first; uninstalling usually deletes app data.

The version shown on the page differs from the one in the filename. Which should I trust?

The card shows the version field from the release manifest, which may differ from the version of an individual package. If they don't match, don't rely on the card alone to decide whether an update can be installed over the existing app. Check the target package and the version currently installed on your device. If you're unsure which app the installer will affect, pause the update.

Why is the list still empty after installing the client?

The package installs a client, not connection settings. On first launch, get a subscription URL or individual configuration from a trusted source, then import it and select an entry. Subscription URLs may contain access credentials, so don't post them publicly, include them in screenshots or share them in troubleshooting logs.