Clients, packages, and architectures

V2Ray client downloads

Choose v2rayN for desktop or v2rayNG for Android.

Select your operating system, then check the processor architecture and package format. Separate downloads are available for desktop interface versions, chip types, and universal packages. Install the download using the steps for your operating system.

Windows downloads

v2rayN · x64 · Desktop / WPF

v2rayN

Recommended
7.24.1 Windows x64 GUI configuration and subscription management

Desktop version

A newer cross-platform UI. A good place to start for a first install.

Download v2rayN Desktop

x64 · ZIP archive

Classic WPF version

A classic, stable interface for users who prefer the traditional desktop workflow.

Download v2rayN WPF

x64 · ZIP archive

The main difference between these downloads is the interface technology and layout. Desktop and WPF are not different proxy protocols. Whether a subscription works depends on the node parameters, selected core, and transport settings. For your first session, import a configuration and test the connection before adjusting routing, DNS, or shortcuts.

After downloading, extract the entire ZIP archive to a writable folder using your system’s extraction tool. Then open the installer from the extracted folder and follow the prompts. Don’t run it from the archive preview. If a required runtime is missing, follow the installer’s instructions for the named component. Check the installer for supported Windows versions, required runtimes, and installation path details.

To migrate from an existing version, back up your configuration and close the old client first. The new interface may place familiar settings elsewhere. After importing, check the selected server, listening port, and system proxy status. Run only one client that manages the system proxy while testing, to prevent an old process from holding a port or overwriting proxy settings.

Windows system and installation requirements

CheckRequirementWhere to check or notes
Operating systemWindows desktop environmentOpen Settings → System → About and check your Windows version.
Processor architecturex64Check System type. Both Windows packages on this page are x64.
Package formatInstaller included in ZIPExtract the entire archive before running the installer; don’t pull out a single dependency file.
Runtime requirementsWritable folder and required runtimesFollow the installer’s prompts for dependencies. Standard system proxy use and TUN mode have different permission requirements.

If your device runs an ARM-based operating system, don’t choose this x64 package based on the system name alone. First check system compatibility and client support.

After installation

Import a configuration and make your first connection

The package installs the app; subscriptions and node details determine where it connects. Check each step in order instead of changing multiple settings at once.

01 / Configuration source

Get subscription or node details

The client doesn’t provide a server account. First get a subscription link, share link, or complete connection details that you’re authorized to use. Add them through the client’s subscription manager, clipboard import, or another available option. Subscription links may include account identifiers or access credentials. When copying one, leave out any accompanying instructions, and never post the full link in a public forum.

After importing, check that the group appears and the number of entries looks right, then select a server. A failed subscription update and a failed server connection are different problems: for the former, check the link, network, and format; for the latter, check the protocol, time, and transport settings. Reinstalling the app repeatedly won’t fix a subscription format issue.

02 / Traffic entry point

Set up the system proxy or VPN

On desktop, the system proxy determines whether apps send requests to the local listening port. The routing mode determines which outbound route handles requests that reach the client. These are separate settings. Make sure the client is running, then enable automatic system proxy configuration. Importing a configuration alone doesn’t ensure your browser will use the proxy.

On Android, you must authorize the system VPN when you first connect. If another VPN app is active, decide which connection to keep first. Don’t start by layering on complex DNS settings, app-based routing, and custom rules. Establish a connection with basic settings that you can verify, then add features as needed.

03 / Verify the connection

Test first, then adjust routing

Open a familiar website and check that the page loads and domain names resolve. Then review the client log for specific errors. If one app can’t connect, first check whether it uses the system proxy instead of immediately changing the package. If nothing can connect, check the selected server, local port conflicts, device time, and subscription details in that order.

Before stopping, clear the system proxy on desktop and then exit the client, so apps don’t keep sending requests to a closed local port. Check the proxy status again after an update or migration. For step-by-step instructions, see the getting started guide. For details on how inbounds, routing, and dns fields work together, read the JSON configuration manual.

Download and installation FAQ

Common installation questions

Which Windows desktop version should you choose: Desktop or classic WPF?

For a first-time install, start with the Desktop version, which uses a newer cross-platform interface. Choose the classic, stable WPF version if you prefer the traditional desktop workflow. Both downloads are x64 packages. Back up your configuration before switching versions, and don’t let both instances manage the system proxy at the same time.

Which macOS download should you choose: Apple Silicon or Intel?

Open About This Mac from the Apple menu. If Chip shows an Apple M-series name, choose Apple Silicon (arm64). If Processor shows Intel, choose Intel (x64). Choose based on the actual processor, not the computer’s purchase year.

What’s the difference between the Android arm64 and universal versions?

The arm64 package is for 64-bit ARM devices and is usually the first choice for mainstream phones released after 2015. The universal version supports multiple architectures and suits devices with an unknown architecture or where the dedicated package isn’t compatible. Newer processors may also run systems with different bitness, so check which app architectures your device actually supports.

Can I connect as soon as the client is installed?

The client manages configurations and connections, but the installer doesn’t include a usable server configuration. You’ll need a subscription link or node details that you’re authorized to use. Import them, select a server, then configure the system proxy or grant Android VPN permission. Subscription links may contain access credentials, so don’t share them publicly.

What should I back up before updating the client?

First note the client name and where its configuration is stored. Use the client’s backup or export feature to save your settings, subscription groups, and custom routing rules. Close the running client before updating. Afterward, check your subscriptions, listening ports, and proxy mode. Don’t delete your existing configuration just to troubleshoot a routine update.

What should I do if Linux reports missing dependencies during installation?

Check the distribution’s package format and processor architecture, then review the specific dependencies listed by the system installer. You can’t convert deb to rpm, or vice versa, by simply changing the file extension. Even rpm-based distributions may require different dependency versions. The rpm file offered here includes an el10 tag; make sure your distribution meets its requirements before installing.

Download v2rayN