CLIENT / PACKAGE / ARCHITECTURE

V2Ray Client
Downloads & Installation

Choose your operating system first, then the architecture. Use v2rayN on desktop and v2rayNG on Android by default; choose v2flyNG if you need the V2Fly core.

Download links are grouped by platform below. After downloading, install the client and import your configuration before setting up the system proxy, VPN, or Tun. These traffic-routing methods work differently.

How to choose an installer

01 · Operating systemChoose a platform
02 · CPU architecturex64 / arm64
03 · Interface & package formatChoose as needed

Not sure which architecture you need? Check your system information instead of guessing from the device’s appearance.

Configuration after installation →

01 / Downloads

Choose your operating system

After switching platforms, copy the current page URL to keep a direct link to that platform’s downloads.

v2rayN

v2rayN

7.24.1 Recommended

The Desktop edition uses a modern cross-platform UI. It’s a good choice for first-time installs and for anyone who wants a consistent layout across desktop systems. The WPF edition retains the classic interface and is a stable option if you’re used to the traditional server list and settings windows.

Both downloads are ZIP archives. Extract the entire archive first, then run the installer or launch file inside. Don’t launch files directly from the archive preview.

Desktop filev2rayN-Desktop-Setup-x64-7.24.1.zip

Windows system requirements and installation

CheckRequirement
System & architectureWindows x64. Check System type under Settings → System → About.
Package formatZIP. Extract to a writable folder and keep the complete file structure intact.
Runtime componentsIf you see a missing runtime warning, install the required components listed for the current release.
Tun permissionsGrant permissions as prompted by the client. Check system proxy and Tun permissions separately.

Before installing, confirm that System type shows an x64-based processor. A successful launch doesn’t mean every dependency is ready. If the core exits as soon as you connect, check the startup error in the logs instead of assuming the server timed out. System and runtime requirements may change between releases; follow the installer prompts and current release notes.

On first launch, import a share link from the Server menu or add a subscription URL under Subscription groups. Select the profile you want to use, then set the system proxy to Automatically configure system proxy. Back up your groups and routing settings before switching editions. Don’t run two instances on the same local port at once; the second one may report that the port is already in use.

02 / First launch

Three checks after installation

Downloading the client is only the first step. Importing a configuration, routing traffic through the client, and verifying the connection each require different checks. Follow them in order to separate installation problems from network configuration issues.

View the full configuration guide →
  1. Import a configuration you’re authorized to use

    Import a share link or subscription in the client, then confirm it recognizes the server address, port, protocol, and transport settings. Subscription URLs may contain access credentials; don’t share the full URL in screenshots, public discussions, or diagnostic logs.

  2. Choose how to route traffic

    On desktop, check the system proxy; on Android, approve the VPN request. Tun changes the routing path for more traffic, so understand why you need it before enabling it. A working system proxy and an accessible remote server are separate things—test both.

  3. Check the logs before changing settings

    Select one profile to test, then check the logs for a failed connection, a DNS lookup failure, or a core that didn’t start. Change one setting at a time and test again. If the issue began after an update, keep a backup of your previous configuration and check whether the interface or configuration fields changed.

03 / Download FAQs

Installer FAQs

See the connection troubleshooting guide →
Which should you choose: v2rayN Desktop or the classic WPF edition?

For a first install, choose Desktop, which uses a modern cross-platform interface. If you prefer the classic window layout, choose the stable WPF edition. Match the architecture to your system. Back up your settings before switching editions, and avoid running two instances on the same listening port.

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

Most mainstream phones released since 2015 use arm64, but check which app architectures your Android system supports. The Universal build includes multiple architectures and is worth trying if your device architecture is unclear or the arm64 build fails to install. If installation still fails, check system compatibility, available storage, and the signature of any existing app instead of repeatedly switching packages.

Can you install v2rayNG over v2flyNG, or vice versa?

These are separate apps, not interchangeable packages. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core, so manage their configurations separately. Before switching, export any settings you want to keep and confirm the new client supports your protocols. Allow only one app at a time to manage the system VPN connection.

Why does the displayed version differ from the number in the download filename?

The displayed version comes from the release manifest’s latest field, while the download URL comes from the selected platform’s download field. They may differ while a release is being updated. The filename alone doesn’t confirm the installed version; check About or Check for updates in the client after installation.

Why can’t I connect right after installing the client?

The client manages connection settings; the installer does not include a working server. First import a share link or subscription you’re authorized to use, select an active profile, then enable the system proxy or VPN. If the connection fails, check the logs to distinguish a configuration error, an unreachable server, or traffic that isn’t being routed through the proxy.

The download finished, but installation failed. What should you check first?

Check the operating system, CPU architecture, and package format first, then review any system warnings, available storage, and installation permissions. Extract Windows ZIP files before use. On macOS, choose the right build for Apple Silicon or Intel. On Linux, match the deb or rpm package system. On Android, allow app installs from the source you’re using.