v2rayN · v2rayNG · v2flyNG

V2Ray Client Downloads

Choose a client based on your operating system, CPU architecture, and package format. For desktop, use v2rayN. For Android, start with v2rayNG; consider v2flyNG if you need compatibility with V2Fly configurations.

Desktop / Android
x64 / arm64
Free and open source
GUI configuration

The package contains the client app only. Before connecting, import a working configuration and make sure its protocols are supported by the selected core. New users can start with the Getting Started guide.

Windows clients

Choose an interface before installing. Both downloads below are x64 packages.

v2rayN

RecommendedWindows x647.24.1

Desktop edition

A newer cross-platform UI for first-time installs and anyone who prefers a consistent desktop interface.

Download v2rayN Desktop

x64 · ZIP package

Classic WPF edition

The stable classic edition, with familiar Windows layouts and native technologies.

Download v2rayN WPF

x64 · ZIP package

The main differences are the interface technology and layout—not whether you need to import a subscription. If you’re happy with your current setup, keep using the interface you know. Before switching, export or note your subscription groups, routing rules, and local ports, then check each setting in the new interface.

Once the download finishes, extract the ZIP to a local folder before running the installer. Don’t launch it from your archive utility’s temporary preview folder. Start the client without elevated permissions; only grant system-level access if prompted for a feature that requires it.

Windows installation requirements

Check	What to choose and prepare
System and architecture	Use a Windows 10 or 11 version that’s still supported by Microsoft. Both downloads on this page are for x64 systems.
Runtime components	Whether additional runtime components are needed depends on the package. If prompted, follow the installer’s instructions.
Install location	Allow enough space to extract and install the app. Make sure the current user can read and write to the configuration folder, and don’t share one configuration between multiple instances.
Network permissions	The system proxy applies to apps that honor proxy settings. TUN uses a virtual network device, so check permissions and potential network conflicts separately.

These are general selection and installation checks, not a replacement for the minimum requirements of a specific package. If an older system can’t run the app, check the OS and runtime requirements instead of repeatedly trying packages for the same architecture.

macOS client

Check your chip type under About This Mac, then choose the matching DMG.

v2rayN

macOS7.24.1

Apple Silicon

Choose this option if About This Mac lists an M-series chip. It’s the native arm64 package.

Download v2rayN · Apple Silicon

arm64 · DMG

Intel

Choose this option if the processor is listed as Intel. It’s the x64 package.

Download v2rayN · Intel

x64 · DMG

Your chip determines the package architecture; screen size and purchase year don’t. Open About This Mac from the Apple menu and check Chip or Processor. Apple Silicon users should choose the arm64 package; there’s no need to pick the Intel build for consistency with other computers.

Open the DMG and follow the window prompts to move the app to Applications, then launch it from there. If macOS displays a security warning the first time you open it, verify the source and review the system guidance—don’t disable system protection. After installation, import one working configuration and test the connection before setting up complex routing.

macOS installation requirements

Check	What to choose and prepare
macOS version	Use a macOS version supported by the package you choose. If your system is older, check its compatibility range before deciding whether to upgrade macOS.
Processor	Choose Apple Silicon for M-series chips and Intel for Intel processors. Both packages use the DMG format.
Disk space and permissions	Allow enough space to mount the DMG and copy the app. Make sure you can write to the Applications folder.
Proxy environment	Check for other proxy apps and network extensions. Before enabling the system proxy, avoid having multiple tools change the same network setting.

Launching the app and connecting through a proxy configuration are separate checks. Launching depends on the system and architecture; connecting also depends on server settings, routing, and DNS.

Android clients

Start with v2rayNG. Choose v2flyNG if you need compatibility with V2Fly configurations.

v2rayNG

RecommendedXray core2.2.6

arm64

Most mainstream phones released after 2015 can use this package, provided the OS supports 64-bit apps.

Download v2rayNG · arm64

arm64-v8a · APK

Universal

For devices where the app architecture is unclear. Includes multiple architectures and is usually larger.

Download v2rayNG · Universal

universal · APK

v2rayNG uses the Xray core and suits Android configurations that need its protocol and transport support. After installation, import a subscription or a share link from your clipboard using the client menu. Importing alone doesn’t start a connection: update the list, select a server, and approve the VPN connection prompt the first time you connect.

If the arm64 package can’t be parsed or is reported as incompatible, first confirm the download finished, then check the OS version and supported app architecture. A 64-bit-capable processor doesn’t guarantee that the installed system supports 64-bit apps. A universal package can help avoid choosing the wrong architecture, but it can’t bypass the minimum OS version.

v2flyNG

AlternativeV2Fly core1.10.31

arm64

For devices that support arm64 apps, and configurations confirmed to use V2Fly settings.

Download v2flyNG · arm64

arm64-v8a · APK

Universal

An alternative when you’re unsure of the architecture. Check the requirements for the specific package.

Download v2flyNG · Universal

universal · APK

v2flyNG uses the V2Fly core. It’s a separate core-compatibility option, not a v2rayNG skin. Choose based on the protocols and transports your configuration needs, not the similar client names. If your configuration uses core-specific settings, check compatibility before switching.

If you install both clients for comparison, manage their subscriptions and rules separately. Stop one client’s VPN connection before testing the other to avoid mistaking a system connection takeover conflict for a server issue. Don’t start troubleshooting by uninstalling the app—you could lose configurations you haven’t backed up.

Android installation requirements

Check	What to choose and prepare
System and architecture	Meet the selected APK’s system requirements. On mainstream 64-bit systems, start with arm64; if you’re unsure, try the universal package.
Installation permission	Follow the system prompt and grant installation permission only to the browser or file manager you’re using to open the APK, and only as needed.
Installing over an existing app	The app signature, package name, and Android version can all affect upgrades. If an installation conflict occurs, keep your configuration and check whether the installation sources differ.
Connections and background activity	Approve the VPN prompt when connecting for the first time. If the connection drops when the screen turns off, check battery optimization and background restrictions before trying another package.

The year 2015 is only a rough guide to common device architectures, not a compatibility cutoff. Your device’s system information and the installer’s requirements are more reliable.

Linux client

Choose deb or rpm based on your distribution’s package format, then check the CPU architecture.

v2rayN

Linux desktop7.24.1

deb package

For distributions using the deb package system. The primary download is x64.

Download v2rayN · deb x64

amd64 · DEB

Download deb · arm64 →

rpm package

For distributions using the rpm package system. The primary download is x64.

Download v2rayN · rpm x64

x86_64 · RPM

Download rpm · arm64 →

Check your OS and hardware architecture on the system’s About page, then open the matching package with your distribution’s software installer. deb and rpm are different package systems; changing a file extension won’t convert one to the other. amd64 and x86_64 generally refer to the same 64-bit desktop architecture; arm64 and aarch64 refer to 64-bit ARM.

A matching package format doesn’t guarantee compatibility with every distribution. If the installer reports missing dependencies or incompatible library versions, check the exact error and the package’s target environment. Don’t force installation by ignoring dependencies. After installation, launch the GUI client from your desktop app menu. This page provides a desktop app, not server deployment instructions.

Linux installation requirements

Check	What to choose and prepare
Desktop environment	You need a desktop session that can run graphical apps. Check the selected package for display and runtime library requirements.
Package system	First confirm whether your distribution uses deb or rpm, then check that its system libraries are compatible with the package’s target environment.
CPU architecture	Choose x64 for most desktop PCs or the matching arm64 package for ARM desktops. Don’t infer architecture from the brand name.
System integration	Installing packages usually requires administrator privileges. Check separately how the app proxy and desktop system proxy apply.

If you enable TUN, also check device permissions and how your network is managed. Test a standard proxy connection first, then add system-level routing to make troubleshooting easier.

Installation and upgrade checklist

Before installing, check your operating system, architecture, and package format. These determine whether the app can run, whether the system can load it, and whether the installer can recognize it. If something goes wrong, note the full error message—not just “it won’t open.” Installation errors and connection errors occur at different stages and need different fixes.

Before upgrading an existing client, save a copy of your subscription groups, routing rules, local listening ports, and DNS settings. Backups may include server credentials, so store them somewhere you control and don’t upload them publicly. Stop the proxy before installing to prevent an old process from locking files or network ports.

Release details on the cards and package filenames come from different fields, so don’t use a version number in a filename alone to judge compatibility. After installation, check the app’s About page to confirm the installed version. Before rolling back, make sure the older version can read your current configuration.

How to choose a client and core

Project V provides the broader technical context for the V2Ray ecosystem. V2Fly and Xray are related core families, while GUI clients organize subscriptions, servers, and routing settings into runnable configurations. Core names help indicate feature compatibility, but you still need to check the specific protocol, transport, and security settings.

Use v2rayN as the desktop option. On Android, v2rayNG and v2flyNG follow different core paths. All three clients are free and open source, but configuration support can change between versions. If an import fails, check the subscription format and required features instead of routinely reinstalling the app.

What to do after downloading

For a first connection, follow the Getting Started guide’s steps to import a configuration, choose a mode, and test it. If you already have a working configuration and want to organize subscription groups or adjust rules, move on to advanced settings. Don’t change DNS, routing, and TUN all at once before testing a basic connection.

Choosing a Client: Find the right option for your desktop or Android device and core requirements.
Advanced settings: Learn about subscription groups, routing, DNS, and TUN.
Quick reference: Understand the differences between protocols, transports, cores, and client features.

Download and installation FAQs

Which v2rayN Windows edition should you choose: Desktop or classic WPF?

For a first install, try Desktop, the newer cross-platform interface. If you prefer the familiar Windows layout, choose the stable classic WPF edition. Both require a working configuration. Before switching, back up subscription groups and custom rules, and avoid running both system proxy setups or TUN at the same time.

Should you choose the arm64 or universal Android package?

Most mainstream phones released after 2015 are likely to support arm64, but the deciding factor is the app architecture supported by the operating system—not just the processor name. If you’re unsure or arm64 is reported as incompatible, try the universal build. It’s usually larger and may not support every older system.

Does installing the client give you a working server?

The client app is not a connection configuration. After installation, import a subscription or individual share link that you obtained and are authorized to use. Update the list, select a server, then enable proxy mode. Never share subscription URLs that contain access credentials publicly.

What should you save before upgrading?

Record your subscription groups, local ports, routing rules, DNS, and TUN settings. Use the client’s backup or export feature to save your configuration. Stop the proxy before upgrading and keep a copy of the old configuration. After upgrading, test one configuration before restoring custom routing rules.

The download link opens, but installation fails. What should you do?

First make sure the download is complete, then check your OS version, CPU architecture, available disk space, and installation permissions. Extract Windows ZIP files before running them. For Android upgrades, make sure the app signature matches the installed version. If you see a security warning, verify the source instead of disabling system protection.

Can you use the same configuration in v2rayNG and v2flyNG?

Don’t assume they’re interchangeable based on their names. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core; protocol and transport support varies by core and version. Before switching, check the protocol, transport, security settings, and subscription format—not just the server address.