Installers for four platforms

V2Ray Client Download and version selection

Choose an installer by operating system, processor architecture and interface version. Use v2rayN on desktop platforms, v2rayNG by default on Android, or v2flyNG when using an existing v2fly configuration setup.

Graphical clients Official releases Architecture guidance Post-install configuration
Select your platform

Installers and system requirements

Changing platforms also updates the address bar. When a platform-tagged link is shared, the page opens the matching installer list directly.

WINDOWS · X64

v2rayN Desktop and classic WPF versions

Both installers target 64-bit Windows. Desktop uses a next-generation cross-platform interface with navigation closer to other desktop platforms; WPF preserves the classic Windows workflow, with menus, tray controls and system proxy steps suited to existing users.

v2rayN
Recommended Actively maintained

v2rayN

Current version 7.24.1

New interface

Desktop edition

Next-generation cross-platform UI. Ideal for first-time installation, users who want a more consistent interface, or those moving their workflow between desktop systems.

Download Desktop
Classic interface

WPF edition

Classic, stable Windows edition. Suited to users familiar with the original menu layout, tray controls, system proxy switching and traditional configuration windows.

Download WPF

Windows system requirements and installation

Item Recommended conditions Selection guidance
Operating system 64-bit Windows 10 or later Keep system patches and the runtime environment up to date and usable.
Processor x64 The Windows installers on this page target common 64-bit computers.
Installation permissions Allow the installer to write to the application directory Windows may display a permission confirmation the first time you install or update.
Connection method System proxy or TUN mode Import the subscription first, then choose a connection method based on the apps that need it.
After installation

From installation to the first connection

The installer only deploys the client. A valid subscription, server configuration and routing settings suited to the current network are still required for an actual connection. Follow the steps below in order to make problems easier to isolate.

  1. 01

    Install and launch the client

    After installation on desktop platforms, launch v2rayN from the app menu; on Android, open v2rayNG or v2flyNG. On first run, the system may request permission for networking, VPN service, notifications or background operation. Grant only what you need and adjust permissions later in system settings.

  2. 02

    Import a subscription or individual configuration

    Get the complete subscription URL from your service provider, add a group in the client’s subscription manager and update it. For a single share link, use clipboard import; Android also supports QR-code import. After importing, verify that the server list appears before changing routing or DNS, so a subscription update problem is not mistaken for a connection-parameter problem.

  3. 03

    Choose a server and routing mode

    Select an available server from the subscription group. For an initial setup, start with the client’s standard routing preset, then adjust LAN bypass, domain rules, IP rules and per-app scope as needed. Restart the connection after editing rules so the new configuration loads completely. Do not let multiple clients control the same system proxy or VPN service.

  4. 04

    Connect and check system control status

    On desktop, confirm that system proxy mode is enabled; on Android, confirm that the VPN connection indicator appears in the status bar. If the client reports success but apps cannot access the network, check system proxy, local port, routing mode, DNS settings and conflicts with other network tools in that order. Avoid randomly switching settings back and forth.

View the complete Getting Started guide View advanced configuration
Selection criteria

Client, architecture and package format

Before downloading, make three decisions: which client to use, which processor architecture the device has, and which package format the system accepts. Once all three match, installation and future updates are smoother.

CLIENT

Choose the client by operating system first

Use v2rayN on Windows, macOS and Linux. Android users generally start with v2rayNG, which provides a complete graphical interface for mobile VPN services, per-app proxying, subscription management and routing. v2flyNG targets the v2fly core configuration ecosystem and suits users with a specific compatibility requirement.

View the client selection guide ›
ARCH

Then confirm the processor architecture

x64 is common on Windows and Linux desktop computers; arm64 is common on newer Android devices, M-series Macs and some ARM Linux devices. Different systems may show architecture names such as x86_64, amd64, aarch64 or arm64-v8a; use the comparison guidance on this page to identify the match.

View architecture and core concepts ›
PACKAGE

Finally match the package format

Windows uses the corresponding installer archive, macOS uses DMG, and Android uses APK. Linux also distinguishes deb from rpm: the distribution determines the package format, while the hardware determines the processor architecture. These are separate dimensions and must be checked independently.

View installation and import steps ›
Updates and migration

Keep settings, update by platform

Before updating the client, confirm the subscription group, routing mode, DNS settings and custom rules in use. Normal updates usually retain the existing package type: Windows Desktop stays on Desktop, WPF stays on WPF; Mac keeps the same chip architecture; Android keeps the same client model; Linux keeps the same package format and processor architecture.

When moving between clients, do not rely on interface screenshots alone. Subscription URLs, individual configurations, routing rules, DNS plans and per-app lists are different data types and should be recorded separately. Re-import subscription URLs; move individual configurations with a link or QR code; review complex routing and custom DNS fields one by one instead of mechanically copying one client’s interface settings to another.

Same-model update Keep the package series and architecture consistent
Cross-device migration Prefer centralized updates through a subscription URL
Custom rules Record routing and DNS settings before updating
Connection issues Troubleshoot ports, routing and DNS in that order
Common download questions

Installer selection and initial setup

Find answers about versions, architectures, package formats and post-install configuration below. Expand a question to see the relevant guidance.

Should Windows users choose v2rayN Desktop or the WPF version?

Desktop uses a next-generation cross-platform interface and is suitable for first-time installations or users who want a similar workflow across desktop systems. WPF is the classic Windows interface for users familiar with the original menus, tray controls and system proxy flow. Both support subscription management, server selection and routing; the main differences are interface technology and navigation.

Should Android users download arm64 or the universal version?

Most mainstream Android phones released after 2015 can start with arm64. Use the universal version when the architecture is unclear, arm64 installation fails, or older devices need support. Both packages belong to the same client version and provide the same core functions; the main difference is processor coverage.

How should I choose between Apple Silicon and Intel installers?

Open About This Mac and check the chip or processor name. Choose Apple Silicon for Macs with M-series chips and Intel for Macs whose processor is identified as Intel. Continue using the same architecture when updating to avoid switching between builds.

Should Linux users download deb or rpm?

Debian, Ubuntu and derivatives generally use deb; Fedora, RHEL and related distributions generally use rpm. After choosing the format, select x64 or arm64 based on the processor. A system showing x86_64 generally uses x64, while aarch64 generally uses arm64.

How do I start using the client after installation?

Get a valid subscription URL from your service provider, create a subscription group in the client and update it. Once the server list appears, choose a configuration, set the routing mode and connect. On desktop, check that the system proxy is enabled; on Android, check that the VPN service is connected. If the connection cannot access the network, check the local port, routing rules and DNS settings in that order.

What is the difference between v2rayNG and v2flyNG?

Both are graphical Android clients. v2rayNG uses the Xray core and is the default choice for most users; v2flyNG uses the v2fly core and suits users with an existing compatible configuration setup. Base the choice on subscription parameters, existing configuration and compatibility needs rather than running both clients at once.