Desktop uses a newer cross-platform UI. It’s a good fit for first-time installations and for users who want a consistent interface across desktop systems. Its menus differ from the classic WPF build, so refer to the current interface when looking for settings.
WPF is the classic, stable build with a Windows-specific interface for users who prefer the familiar windows and menus. You can keep your existing workflow; before switching to Desktop, export your configuration and install the other build separately for testing.
Packagev2rayN-Setup-x64-7.24.1.zip
Windows requirements and installation checks
Check
How to choose
Operating system
Use a supported version of Windows 10 or 11. Check the release notes for the selected package’s minimum requirements.
CPU architecture
This page provides x64 packages. Open Settings → System → About and check System type.
Runtime
If startup reports a missing .NET component, check the required runtime and architecture. WPF typically needs the corresponding .NET Desktop Runtime.
Permissions
Start with standard user permissions for the system proxy. Features such as TUN that take over network traffic may require elevated permissions.
v2rayN downloads are compressed archives. Extract the archive to a writable folder, then run the installer from there; don’t launch it from an archive preview window. After installation, import a subscription, choose a server, and enable the system proxy. Read the TUN setup guide only if you need to route traffic from more apps—there’s no need to change every network setting on first launch.
v2rayN Desktop and WPF are interface choices, not protocol choices. Supported protocols also depend on the core and server configuration. Before updating, close the old process to avoid two clients changing system proxy settings at once or competing for the same local port.
v2rayN · macOS
7.24.1
v2rayN has separate packages for the two Mac processor families. Open About This Mac from the Apple menu and choose a package based on the Chip or Processor field.
Choose the native ARM64 package for an Apple M-series chip. Don’t infer the architecture from the purchase year alone; devices sold around the same time may have different processors. The native package matches the processor architecture.
Choose the x64 package if About This Mac lists an Intel processor. The macOS version and CPU architecture are separate requirements; a system upgrade won’t turn an Intel Mac into an ARM64 device.
v2rayN-macos-64.dmg
macOS requirements and installation checks
Check
How to choose
Operating system
Use a macOS version supported by the release. On older systems, check the app’s minimum macOS requirement before installing.
Processor
Choose ARM64 for Apple M-series chips and x64 for Intel processors.
Install location
Open the DMG, move v2rayN to Applications, then launch it from that folder.
Network permissions
Grant permissions for the system proxy and traffic-routing features when prompted. Requirements vary by feature.
On first launch, v2rayN may trigger a macOS security alert. Check the download source and file type, then follow the available security settings; don’t disable system security entirely just to launch one app. If the app says your macOS version is unsupported, check the release requirements instead of repeatedly trying packages for other CPU architectures.
After installing v2rayN, first test the standard system proxy. Whether a browser uses the proxy also depends on its own settings; command-line tools may need proxy environment variables configured separately. Before quitting the client, you can clear the system proxy so it doesn’t point to a local port that is no longer listening.
v2rayNG · Android
RecommendedXray core2.2.6
v2rayNG is a good choice for a first Android installation, with share-link import, subscription management, and VPN mode. For configurations using REALITY, make sure the client core supports the configuration fields.
For mainstream phones released after 2015, arm64 is usually the best choice. Some entry-level devices may run a 32-bit OS, even if their processors support 64-bit instructions, so check system compatibility before installing.
Choose the universal build if you can’t confirm your device’s architecture. It includes components for multiple architectures and is usually larger. It addresses architecture compatibility, but doesn’t guarantee support for older Android versions.
v2rayNG_2.3.11_universal.apk
v2flyNG · Android
Alternative · V2Fly core1.10.31
v2flyNG is for users with configurations designed for the V2Fly core. Choose it when you have a specific need; its core capabilities aren’t identical to v2rayNG’s. Being able to import a link doesn’t guarantee that the connection will work.
For devices running a 64-bit ARM system. Before choosing this build, confirm that your subscription is compatible with V2Fly; changing clients won’t convert core-specific configuration automatically.
Choose this build if you’re unsure of your device’s architecture. Before switching clients, export any subscriptions or share links you can migrate, then check routing and DNS settings individually. Avoid copying the entire app data directory.
v2flyNG_1.10.31-fdroid_universal.apk
Android requirements and installation checks
Check
How to choose
Android version
Check the APK’s minimum Android version and the installation prompt. The two apps may have different requirements.
Device architecture
Choose arm64 for a 64-bit ARM system; choose universal if you’re unsure of the architecture.
Install permissions
If needed, allow your current browser or file manager to install apps. You can revoke this permission afterward.
Connection permissions
The first time you use VPN mode, approve the system connection request. Usually, only one VPN service can run at a time.
Both v2rayNG and v2flyNG need a working configuration after installation. For your first connection, keep the default settings and confirm basic connectivity before changing LAN bypass, DNS, or per-app routing. If Android reports that another VPN is active, stop the conflicting service; don’t run VPN mode in two clients at once.
Android battery policies can affect v2rayNG background activity. If the connection drops when the screen locks, check background restrictions and battery settings before relaxing them. If installation fails with “App not installed,” check the architecture, Android version, available storage, and signature compatibility with any existing app. Save your configuration before uninstalling.
v2rayN · Linux
7.24.1
v2rayN is a graphical desktop client. Choose deb or rpm based on your distribution, then select x64 or ARM64 for your device; package format and CPU architecture are separate choices.
For distributions that use the deb package format, such as Debian, Ubuntu, and their derivatives. The amd64 package name indicates x64 architecture and works with compatible Intel and AMD processors.
For systems that use the RPM package format. The same package format doesn’t guarantee compatibility with every distribution, so check dependencies and release requirements. x86_64 in the filename refers to the same architecture commonly called x64.
Requires a desktop session that can run graphical apps; this download is a GUI client.
Package format
Choose deb or rpm for your distribution and check dependency compatibility.
CPU architecture
Choose x64 for most PCs, or arm64 / aarch64 for devices running a 64-bit ARM system.
Installation and network permissions
Use your system’s software installer to handle dependencies. Configure the permissions required for traffic-routing features separately.
Install v2rayN with your distribution’s software installer. If dependencies are missing, check your software sources and distribution version, then make sure the package matches. Don’t force installation by ignoring dependencies. ARM64 packages are for devices running a compatible system; hardware appearance or device name alone isn’t enough to determine compatibility.
How v2rayN’s system proxy works depends on your desktop environment and the apps you use. Some apps follow the desktop proxy settings; others need a proxy address entered manually. First test with an app that explicitly supports proxies, then configure terminals, background services, or TUN if needed.
Post-install setup
Import a subscription, then choose a server
v2rayN, v2rayNG, and v2flyNG manage connection settings; their installers don’t include a working service. Import a subscription or share link you’re authorized to use, check the protocol, address, and transport settings, then choose a server. Subscription URLs may contain access credentials, so don’t include them in public screenshots or share them with others.
v2rayN’s system proxy lets apps connect through a local proxy; routing presets determine where traffic goes. v2rayNG’s VPN mode likewise doesn’t mean all traffic uses a remote exit. Keep settings simple for your first connection, then add rules after confirming it works. If a protocol doesn’t match, check the configuration instead of reinstalling repeatedly.
Which v2rayN build should you choose: Desktop or classic WPF?
v2rayN Desktop uses a newer cross-platform interface and is a good starting point for new installations. The classic WPF build has a Windows-specific interface for users who prefer the familiar layout. Before switching, export your configuration. Install each build separately and check your subscriptions, routing, and system proxy settings.
What’s the difference between the arm64 and universal Android builds?
The arm64 package is for 64-bit ARM systems and is usually the best choice for mainstream phones released after 2015. The universal build includes multiple architectures and is useful if you’re unsure which one your system uses. A 64-bit processor doesn’t guarantee a 64-bit OS, so check the device’s actual system architecture.
Should I download the Apple Silicon or Intel build for macOS?
Open About This Mac from the Apple menu. Choose Apple Silicon if it lists an Apple M-series chip; choose Intel if it lists an Intel processor. After installation, move v2rayN to the Applications folder and launch it from there.
Why can’t I connect right after installing the client?
v2rayN, v2rayNG, and v2flyNG manage configurations and route traffic; their installers don’t include a working service connection. Import a subscription or share link you’re authorized to use, choose a server, then configure the system proxy or VPN mode.
What should I save before updating the client?
Before updating, export your client configuration and note your subscription groups, custom routes, DNS settings, and local listening ports. Keep the backup somewhere you control. Close the running client before updating, then check your server selection and proxy mode afterward.
The version shown on the page differs from the installer filename. Which should I trust?
The displayed version and architecture-specific files are maintained separately in the download manifest, so they may temporarily differ. Download links aren’t generated from the version shown on the page. To verify a package’s version, check the package details and the client’s About page after installation.
For connection, subscription, and routing issues, see the Help Center; for definitions, see the Glossary.