Client downloads / platforms and architectures
Choose v2rayN for desktop and v2rayNG for Android. Check your operating system and processor before choosing a package.
Desktop clientv2rayN · Desktop / WPF
Android clientv2rayNG / v2flyNG
Before you startSubscription URL or server configuration
Choose your operating system
Windows · x64
Desktop is the modern cross-platform UI; WPF is the classic, stable version with a familiar Windows desktop layout. Desktop is a good place to start.
Current listing 7.24.1 · ZIP archive
Extract the archive to a dedicated folder, then run the installer or launcher inside. Don't launch it from the archive preview.
The main difference is the interface technology and layout—not the subscription service. Desktop suits users who want a similar experience across desktop platforms; WPF suits those familiar with classic menus and settings. Menu locations may change between interfaces and versions. If a label differs, look for the setting with the same purpose.
These are x64 packages. Check Settings → System → About to confirm that both your processor and system support this architecture. If startup reports a missing runtime, check the error for the required .NET Desktop Runtime version. Don't install an arbitrary runtime based on the client name alone.
Exit the old app and back up your settings before switching versions. Keep a copy of the original folder so you can restore it. Once the new version has the right subscription groups, routes, and local ports, you can clean up the old files. Don't let two processes control the system proxy at the same time.
| Check | Requirements and steps |
|---|---|
| System and architecture | Use a Windows version that is still supported by its vendor. This page provides x64 packages. Check the installer prompt and release notes for the exact minimum Windows version. |
| Install location | Use a dedicated folder that your account can write to. Don't overwrite a directory used by a running app. |
| Runtime | Install any required runtime based on the package type and startup prompts. Bundled and system-dependent packages may have different requirements. |
| Proxy control | The standard system proxy and TUN have different permission requirements. Start with the system proxy, then consider TUN if needed. |
macOS · Desktop
Choose based on the chip shown in About This Mac. Apple Silicon uses arm64; Intel processors use x64. Don't judge by the device's appearance or purchase year.
Current listing 7.24.1 · DMG disk image
Open the disk image, drag the app to Applications, and launch it from there. Eject the disk image when you're done.
Open About This Mac from the Apple menu. If it lists an Apple M-series chip, choose Apple Silicon; if it lists an Intel processor, choose Intel. Matching the package to your Mac's architecture avoids extra variables from translation. If the installer says your macOS version isn't supported, check the app's requirements rather than repeatedly trying packages for the same architecture.
On first launch, you may need to confirm the app's source in System Settings → Privacy & Security. Only respond to security prompts after verifying the download source and what the file does. Don't disable system-wide security protections. If your Mac is managed by an organization, administrator policies may also restrict app installation and network settings.
After importing a subscription, check the active configuration before setting the system proxy. Network extensions, other VPNs, and manual proxy settings can affect traffic. When troubleshooting, use only one traffic-control method at a time. Before quitting the client, clear the proxy settings it enabled so apps don't keep sending requests to a stopped local port.
| Check | Requirements and steps |
|---|---|
| Processor | Apple Silicon uses arm64; Intel uses x64. Check About This Mac. |
| macOS version | Use a macOS version supported by the current app build. The minimum version depends on more than the chip; check the installer and startup prompts. |
| App location | Run the app from Applications and make sure your account can write its settings normally. |
| Network permissions | Grant only the permissions requested by the system. Configure TUN and the system proxy separately, and avoid having multiple network tools control traffic at once. |
Android · Xray
An Android client powered by the Xray core. Most phones released after 2015 should start with arm64; choose universal if you're unsure of the device architecture.
Current listing 2.2.6 · APK package
The listing version may not match the package filename. When installing, use the version shown in the package information.
Android · V2Fly
An alternative client powered by the V2Fly core. Choose it when your configuration specifically requires that core. Before importing, check compatibility for protocols, transports, and extension fields.
Current listing 1.10.31 · APK package
Back up your subscriptions and custom rules before switching clients. Stop the other client's VPN connection before starting this one.
When the download finishes, open the APK with your file manager. If Android asks you to enable installs from this source, allow it only for the browser or file manager you're using; you can restore the previous setting afterward. An “App not installed” message may be caused by an incompatible Android version, low storage, or a signing-key mismatch—not just the package architecture. Export your settings before removing an existing app; don't uninstall it and hope to find a backup later.
arm64 refers to the architecture supported by the device's app runtime; the processor's release year is only a rough guide. Some devices have 64-bit processors but use a different app runtime. If you're unsure, try the universal package, but it still can't bypass the app's minimum Android version.
On the first connection, Android asks for VPN permission. Approve it so the client can route network traffic locally. If the connection drops in the background, check battery optimization, background activity, and power-saving settings. For app-based routing, check whether the list means “proxy these apps” or “bypass these apps”—don't rely on the checkmarks alone.
| Check | Requirements and steps |
|---|---|
| Architecture | Choose arm64 for most devices. If unsure, choose universal, then check the system ABI and app compatibility. |
| macOS version | Check each APK's installation requirements; the two clients may require different minimum Android versions. |
| Install permission | Allow app installs from the current file source. For updates, check that the signing key and installation source match the existing app. |
| Connection permission | Approve the system VPN prompt. Run only one client that needs the system VPN connection at a time. |
Linux · Desktop
Choose deb or rpm for your distribution, then select the processor architecture. The primary packages below are x64; choose the arm64 packages for ARM desktop devices.
Current listing 7.24.1 · Open with your distribution's package manager
Debian and Ubuntu commonly use deb; Fedora and some enterprise distributions commonly use rpm. Matching the package format only means the installation method is compatible—it doesn't guarantee your system libraries meet the requirements. Pay close attention to dependency prompts, especially when an rpm filename identifies a specific distribution build. Don't force the installation if dependencies can't be resolved.
The x64 architecture is often labeled amd64 in deb packages and x86_64 in rpm packages; arm64 may appear as aarch64 in rpm packages. These naming differences don't indicate different feature tiers. Check your system and processor in Settings → About, then open the matching package with your software installer.
Desktop environments handle the system proxy differently, and some apps need a local proxy address configured separately. TUN also involves permissions, routing, and DNS, so test a standard proxy first. Don't run a graphical client as an administrator indefinitely just to change one network setting.
| Check | Requirements and steps |
|---|---|
| Package format | Choose deb or rpm for your distribution, then check dependencies and compatibility in your software installer. |
| Processor architecture | x64 is labeled amd64 / x86_64; arm64 is labeled arm64 / aarch64. |
| Desktop environment | Requires a desktop environment capable of running graphical apps and the corresponding system libraries. This graphical package isn't a server-only component. |
| Traffic routing | Check how your desktop environment handles the system proxy. TUN has separate permission and routing requirements; don't configure it alongside another tool doing the same job. |
First launch / configuration location
The client is a graphical tool for configuring and running proxy connections. Installing it doesn't provide connection details. First, prepare a subscription or server information you're authorized to use.
View the step-by-step guidehttps://example.com/sub?token=xxxx illustrates the format only; it won't connect to a real service.Choosing and updating packages
For a first installation, try Desktop, which uses a modern cross-platform interface. WPF is the classic, stable version for users who prefer the traditional Windows layout. Both require a working configuration. Export your settings before switching, and don't run both clients at once while they control the system proxy.
Most phones released after 2015 will use arm64, but check your device's processor and system ABI. If you're unsure, choose universal. If Android says the app isn't installed, check system compatibility, available storage, and whether the existing app has a different signing key. Back up your settings before replacing the old app.
The package contains the client app, not a working service configuration. You'll need a subscription URL or server details that you're authorized to use. Import them, select a configuration, and start the connection. On desktop, configure the system proxy or TUN as needed. On Android, approve the system VPN prompt the first time you connect.
Whether your settings are retained depends on how the client was installed, its configuration directory, and how the new version migrates data—not just the package name. Before updating, export your settings and note custom routes, ports, and subscription groups. Exit the old app before installing the update. On first launch, check that your settings migrated before enabling the system proxy or TUN.
They are different Android clients: v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. Support for protocols, transports, and configuration fields may differ. A successful import doesn't guarantee every setting will work. Choose the client that matches your service configuration, and don't run both VPN connections at once.
The system proxy only affects apps that honor that setting. Terminals, some games, and apps with their own proxy settings may ignore it. First confirm the client is running and the local port matches, then check the app's proxy settings. If you need to cover more apps, consider TUN—but first check for conflicts with existing VPNs, virtual adapters, and routes.