CLIENT PACKAGES / DOWNLOADS

V2Ray Clients
Downloads & Architecture

Choose v2rayN for desktop and v2rayNG for Android. Select your operating system, then match the download to your device’s CPU architecture.

Open source Free to use Setup guide ↗

Choose your device

Client downloads

Your platform selection is saved in the address bar, so you can copy the page link.

Windows · v2rayN

Both downloads are x64 archives. Extract the entire archive before opening the installer inside.

v2rayN

Recommended 7.24.1

Desktop version

A newer cross-platform UI, ideal for first-time installs and users who want a consistent interface across desktop systems.

Download Desktop · x64 v2rayN-Desktop-Setup-x64-7.24.1.zip

Classic WPF version

The classic stable release with a traditional Windows interface. Choose it if you prefer the familiar menus or already know your way around.

Download classic WPF · x64 v2rayN-Setup-x64-7.24.1.zip

The main difference is the UI technology and layout—not that one version will necessarily connect faster to the same server. For initial setup, run one version at a time to avoid local port conflicts.

System requirements and package selection

Check	Before you download
System architecture	This page offers x64 packages. Find your system type under Settings → System → About.
Runtime	Follow the installer’s operating system and runtime requirements. Install any missing components as prompted.
Folder permissions	Keep the configuration folder writable. Don’t run an archive directly from its preview window.
Proxy permissions	System proxy and Tun have different permission requirements. Test a basic proxy connection first.

What to do after installation

Extract the archive to its own folder, then run the installer. On first launch, check that the window displays correctly and note any runtime prompts. Don’t reinstall the client just because the server list is empty; it usually means no configuration has been imported yet.

Open Subscription Group Settings, add and save your subscription URL, then select Update subscription (without proxy). If the subscription service specifically requires a proxy, adjust this setting as needed. Select a valid configuration, choose Set system proxy to auto in System Proxy, and test with a browser.

Before switching from classic WPF to Desktop, export your configuration and note the routing mode. Close the old version before opening the new one, and make sure no other program is using the local listening port. When you don’t need a proxy, clear the system proxy before closing the client so your browser doesn’t keep trying to use a stopped local port.

See the first-install and initial setup guide →

macOS · v2rayN

Open About This Mac from the Apple menu and choose a DMG based on your chip or processor.

v2rayN

7.24.1

Apple Silicon

Choose this package if About This Mac lists an Apple chip. It’s a native app built for that chip architecture.

Download for Apple silicon v2rayN-macos-arm64.dmg

Intel

Choose this package if About This Mac lists an Intel processor. Don’t rely on the computer’s appearance or purchase year.

Download for Intel v2rayN-macos-64.dmg

Open the DMG, move the app to the Applications folder, then launch it from there. Once the copy is complete, you can eject the disk image.

System requirements and chip identification

Check	Before you download
Chip type	Apple silicon uses arm64; Intel uses x64.
System compatibility	Check the compatibility notes for the current package. Confirm support before installing on an older system.
Install location	Copy the app to Applications. Don’t keep running it from the disk image.
System permissions	Changing proxy settings or enabling Tun may require system authorization or administrator privileges.

First launch and proxy setup

Copy the app before launching it. If macOS shows a security alert, check the download source and read the message. If you need to allow the app to open, look for the relevant option under System Settings → Privacy & Security. Don’t disable system security features just to fix one app’s startup issue.

Import a valid subscription first, confirm the server configuration appears in the list, then set up the system proxy. Desktop apps don’t always follow the system proxy, so test with a browser first. If only a specific app still can’t connect, check its own proxy settings or look into Tun.

Before upgrading, quit the old app and keep your subscription and routing settings, then replace the app files. If the new version opens but websites won’t load, check the system proxy and local port before changing protocols. If your network has issues after quitting the client, first check whether the system proxy still points to a local address.

See desktop setup steps →

Android · v2rayNG and v2flyNG

Most mainstream phones released since 2015 use arm64. If you’re unsure of the architecture, try the universal build and check device compatibility.

v2rayNG

Recommended Xray core 2.2.6

arm64 package

For mainstream Android devices that support 64-bit apps. Choose based on the device architecture, not just the processor’s marketing name.

Download v2rayNG · arm64 v2rayNG_2.3.11_arm64-v8a.apk

Universal package

Supports more processor architectures. Try this download if you’re unsure of your device’s architecture or the arm64 package isn’t compatible.

Download v2rayNG · Universal v2rayNG_2.3.11_universal.apk

The version shown on the card and platform download URLs may be updated separately. Check the filename below the download link; confirm the installed version on the client’s About page.

v2flyNG

Alternative v2fly core 1.10.31

arm64 package

For users who specifically need the v2fly core and have a device that supports 64-bit apps. First, make sure the protocols and settings in your subscription are supported.

Download v2flyNG · arm64 v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Universal package

An alternative for devices with an uncertain architecture. Device compatibility doesn’t mean the app can parse every subscription and protocol combination.

Download v2flyNG · Universal v2flyNG_1.10.31-fdroid_universal.apk

v2rayNG and v2flyNG use different core ecosystems. Don’t assume their configuration settings are interchangeable just because their names are similar.

System requirements and installation permissions

Check	Before you download
App architecture	arm64 requires system support for 64-bit apps. If unsure, try the universal build.
Install permissions	Follow the system prompt to temporarily allow your browser or file manager to install apps.
Android version	Follow the installer’s compatibility notices. The universal build won’t solve issues caused by an outdated Android version.
Connection permission	When connecting for the first time, confirm the system VPN request. Avoid having another VPN app take over the connection at the same time.

Import a subscription and connect with v2rayNG

After installation, open the side menu and go to Subscription Group Settings. Add a name and subscription URL, save, then return to the main screen and update the subscription. Menu locations may vary slightly between versions. Save the group before updating; adding a URL without updating won’t populate the server list.

Select a valid configuration, then tap the connect button. When the system shows a VPN permission prompt, confirm it’s from the current client. A connection icon in the status bar only means the system tunnel has started; open a browser to check that traffic actually works. If importing fails, first check that the subscription URL is complete and hasn’t expired, then confirm the client supports its protocols.

If an upgrade reports a signature conflict, don’t uninstall the old app straight away. Export or back up your settings, check whether the old and new apps came from the same source and have matching signatures, then decide how to migrate. Android battery optimization can also stop background connections. Adjust the app’s battery settings only if it’s actually being stopped in the background, and keep an eye on battery usage.

See the v2rayNG user guide →

Linux · v2rayN

Check whether your distribution uses deb or rpm, then choose x64 or arm64. Both the package format and CPU architecture must match.

v2rayN

7.24.1

deb · x64

For distributions that use deb packages, including Debian, Ubuntu, and other desktop systems with the same package format.

Download deb · x64 v2rayn_7.24.1_amd64.deb For ARM devices: Download deb · arm64 ↗

rpm · x64

For distributions that use rpm packages. Before installing, check that the package is compatible with your distribution’s dependencies.

Download rpm · x64 v2rayN-7.24.1-1.el10.x86_64.rpm For ARM devices: Download rpm · arm64 ↗

In filenames, amd64 and x86_64 usually mean x64; arm64 and aarch64 mean 64-bit ARM. Renaming a file or changing its extension won’t convert a package.

System requirements and distribution compatibility

Check	Before you download
Desktop environment	This page provides a graphical client, so you’ll need a working desktop session.
Package format	Check your distribution and package manager in system information or the software manager.
CPU architecture	Most Intel and AMD desktop computers use x64; check whether your ARM device uses arm64.
Dependencies and permissions	Check dependency notices in the system software installer. System proxy and Tun permissions are handled separately.

Graphical installation and first connection

Open the downloaded package in your system’s software installer. Review dependency and compatibility notices before confirming installation. Some distributions use the same file extension but different system libraries. If the installer reports unmet dependencies, check compatibility first; don’t routinely bypass dependency checks.

Launch v2rayN from the app menu, import a subscription, and select a valid configuration. Linux desktop environments handle system proxies differently, and some apps use their own proxy settings. If your browser connects but another app doesn’t, first check whether that app follows the desktop system proxy before trying other ways to route traffic.

Understand the additional permissions and routing changes before enabling Tun, and avoid running multiple apps that take over network traffic at the same time. Keep your configuration before upgrading, and close the old process before installing the new package. If the new version won’t start, note the installer or client error and determine whether the issue is with desktop dependencies, permissions, or configuration.

See core compatibility and protocol references →

After installation

Configure, connect, and test

View the full guide

Get one configuration working first

The client manages configurations and connections; a subscription provides server settings. First check that the subscription URL works, update it, select a configuration, then set the proxy mode. Don’t change subscriptions, routing, DNS, and the core all at once during your first test. Change one thing at a time so you can tell what made a difference.

The system proxy affects only apps that follow that setting. On desktop, start with automatic system proxy setup; on Android, confirm the system VPN permission. Once a browser test succeeds, set up other apps as needed. If the client says it’s connected but websites won’t load, check the system proxy, local port, routing, DNS, and server availability—in that order.

Keep your settings and plan updates

Before updating the client, back up subscription groups, custom routing rules, and manually added server configurations. Subscription URLs may contain private access credentials; don’t include them in public screenshots or support requests. When reporting a problem, include the error text and steps to reproduce it, but remove personal information from URLs.

The client interface and the core are separate layers. Being able to save an option in the interface doesn’t mean the current core supports it; switching clients doesn’t guarantee subscription compatibility either. For VMess, VLESS, REALITY, and other protocol choices, check core support before importing the full configuration.

See the troubleshooting checklist for connected but inaccessible traffic →

Download FAQs

Packages and first launch

Do I need a subscription after downloading the client?

You’ll need a valid subscription URL or a complete server configuration. The client reads your configuration and connects to servers; the installer does not include any usable servers. In v2rayN, open Subscription Group Settings, save the URL, and update the subscription. In v2rayNG, open Subscription Group Settings, add the URL, and update the current group.

Which should I choose: the Windows Desktop or classic WPF version?

For a first install, try the Desktop version, which uses a newer cross-platform interface. The classic WPF version has a traditional Windows interface and may suit users who prefer the familiar layout or want the classic stable release. Both require a valid configuration. Before switching, export your configuration and note your system proxy and routing settings. Don’t run both clients at the same time if they would use the same proxy port.

Should I choose arm64 or the universal Android build?

Most mainstream phones released since 2015 should use arm64, but check that the device supports 64-bit apps. If you’re unsure of the architecture or arm64 won’t install, try the universal build. It supports more architectures and is usually larger; it won’t automatically improve connection performance.

Why doesn’t the package filename match the version shown on the card?

The version shown on each card and the download URLs for each platform are maintained separately, so they may not be updated at the same time. Check the filename next to the download link before downloading, then confirm the installed version on the client’s About page. Don’t rely on the card’s version number for a specific package or edit the numbers in a download URL.

The download finished, but the app won’t start. What should I check first?

First, make sure the package matches your operating system and CPU architecture. Fully extract Windows archives before running the installer. On macOS, move the app to the Applications folder first. On Linux, check the package format, architecture, and dependency notices. On Android, check install permissions and possible signature conflicts with an existing app. Keep any error messages and follow the relevant steps in the guide.

Should I enable Tun right after installation?

Tun isn’t required for your first connection. On desktop, select a valid configuration, enable automatic system proxy setup, and test the connection in a browser. Look into Tun permissions and routing only if an app doesn’t follow the system proxy. On Android, confirm the system VPN permission prompt when you connect for the first time.

V2Ray ClientsDownloads & Architecture

Client downloads

Windows · v2rayN

v2rayN

Desktop version

Classic WPF version

System requirements and package selection

What to do after installation

macOS · v2rayN

v2rayN

Apple Silicon

Intel

System requirements and chip identification

First launch and proxy setup

Android · v2rayNG and v2flyNG

v2rayNG

arm64 package

Universal package

v2flyNG

arm64 package

Universal package

System requirements and installation permissions

Import a subscription and connect with v2rayNG

Linux · v2rayN

v2rayN

deb · x64

rpm · x64

System requirements and distribution compatibility

Graphical installation and first connection

Configure, connect, and test

Get one configuration working first

Keep your settings and plan updates

Packages and first launch

V2Ray Clients
Downloads & Architecture