Client Downloads

V2Ray Client Downloads

Choose the target device’s operating system, then check its CPU architecture and package format.

Windows Downloads

v2rayN

Recommended Listed version 7.24.1

Desktop uses a next-generation cross-platform interface. Classic WPF keeps the familiar Windows layout, making it a good fit if you’re used to it or following older guides. The main differences are the interface and menu layout; you don’t need to change subscriptions when switching editions.

Both links download a ZIP containing the installer. Extract the entire archive to a local folder, then run the installer inside. Before upgrading, close the running client, including any instance still in the notification area, to prevent old and new instances from competing for the same local listening port.

System Requirements

CheckRequirement
System and architecture64-bit Windows with an x64 processor
Where to checkSettings → System → About → System type
Package formatZIP; extract it, then run the installer

Check both “64-bit operating system” and “x64-based processor.” Both downloads on this page are x64; choosing a different interface does not change the architecture requirement.

Choose, Install and Upgrade

The target device determines which package to install; the client configuration determines how it connects. Check each stage in order to avoid conflating problems.

  1. 01 Before downloading

    Check the target device’s architecture

    If you’re downloading for another device, check that device’s system information rather than choosing based on the device you’re browsing from. In particular, distinguish the instruction set supported by the processor from the app architectures supported by the operating system. 64-bit hardware doesn’t guarantee that the current system can install every 64-bit app.

    You can’t determine which architecture package is right by comparing file sizes. A universal package is usually larger because it contains components for multiple architectures, not because it supports more protocols. Check the architecture first, then compare interface options or package formats for the same platform.

  2. 02 During installation

    Start with the first installer error

    A file that won’t open, an installer that refuses to install, and a client that exits on launch are problems at different stages. First identify whether the file is an archive, disk image or package for the system installer, then note the first specific error message. It’s usually more helpful than the final “Installation failed” line.

    If the message points to an outdated system version or missing dependencies, check whether your system meets the requirements. If it says the app already exists or can’t be replaced, determine whether an old instance is still running, you’re downgrading, or the mobile package comes from a different source than the installed app. Don’t uninstall the old version before investigating.

  3. 03 Before upgrading

    Keep a restorable copy of your configuration

    If you have custom routing, manually added nodes or changed local ports, back up your configuration using a method supported by the client. A subscription URL usually lets you fetch nodes from that subscription again, but may not restore individually added nodes, local routing rules or the currently selected configuration.

    Store backup files somewhere you control. Don’t post subscription URLs or exported configurations in public forums. After upgrading, confirm the app launches on its own and your existing nodes are still there, then check routing and proxy status. Don’t assume settings will migrate automatically when switching interfaces or clients.

First checks after installation

Once the client opens normally, import an existing subscription or a single node. For the first test, select one known-working configuration and keep its protocol and transport settings unchanged; adjust one setting at a time. This makes it easier to tell whether a problem occurred during import, when the client took over traffic, or while connecting to the remote server.

A node list doesn’t mean you’re connected

A successful import means the client received the node configuration; it doesn’t mean the remote server is available or that the app is routing traffic through the client. First confirm that the selected node is the one you expect, then check the client logs for connection requests. If the subscription updates but app traffic fails, troubleshoot the subscription URL and node server separately—they’re two different connections.

Proxy entry points and routing rules are different

The system proxy directs traffic from apps that honor that setting to the local proxy endpoint, but not every app uses the same proxy settings. Routing rules determine which outbound connection is used by traffic that reaches the client. If one app works and another doesn’t, first check whether the latter sends requests to the local proxy. You don’t need to reinstall the client or switch to global routing right away.

The first time you start a connection through a client on Android, the system usually asks you to authorize a VPN connection. If another app is already using this type of connection, check which app is currently active. Selecting a node in the client doesn’t replace system-level authorization or connection status.

Use the error to troubleshoot before reinstalling

If the startup log points to a local port conflict, check whether an old instance or another app is listening on the same port. If you need to change the port, update any app proxy settings you entered manually. If the log shows the request reached the client, check the remote address, protocol, transport and routing against the error. Don’t change the package, node and routing rules all at once.

For the full import and verification process, see Getting Started. For local port conflicts, see Troubleshooting Port Conflicts. To understand how configuration options relate, consult the JSON Manual.

Download and Installation FAQs

Which should you choose: the Windows Desktop or Classic WPF edition?

For a first-time install, choose Desktop for its next-generation cross-platform interface. If you prefer the familiar layout or need to follow screenshots from classic-interface guides, choose Classic WPF. Both downloads are x64; the interface choice does not change the required CPU architecture.

Which DMG should you download for your Mac?

Open About This Mac from the Apple menu. If it shows an Apple M-series chip, choose Apple Silicon (arm64); if it shows an Intel processor, choose Intel (x64). When downloading for another Mac, use the details shown on that machine.

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

The arm64 build is for Android devices that support arm64-v8a. The universal build includes components for multiple architectures and is usually larger. If you’re unsure which architecture your device supports, try the universal build. It does not support every Android version or resolve app-signature conflicts.

Which Linux package should you use for your distribution?

For Debian-based distributions, look for the DEB package; for distributions that use RPM, look for RPM. Check CPU architecture and distribution compatibility too. The RPM filename on this page includes el10, so RPM format alone does not mean it will install on other distributions or older systems.

Why does the version shown on the card differ from the one in the filename?

The listed version comes from the client entry, while each download link maps a specific architecture to a file; the two version numbers may differ. Check the saved filename to identify the downloaded package, and the client’s version information to see which version is running.

Why do I need to import a subscription or node after installation?

The installer provides the client application. Before connecting through a proxy, import an existing subscription or node configuration, select an available node, and choose how traffic should be routed based on your device settings. Installation, configuration import and connection are three separate steps.