v2rayN Recommended
7.24.1Desktop uses the newer cross-platform Avalonia interface; the classic WPF edition retains the established Windows layout. Choose either installer.
Client downloads
Choose your platform first, then select the architecture and package format. Use v2rayN on desktop; for Android, v2rayNG is the recommended choice, while v2flyNG is an option when you need the v2fly core.
Desktop uses the newer cross-platform Avalonia interface; the classic WPF edition retains the established Windows layout. Choose either installer.
| System type | 64-bit operating system with an x64-based processor |
|---|---|
| File format | ZIP; extract the archive before running the installer inside |
| Runtime | If installation or launch reports a missing runtime, check the required component and architecture as prompted. |
Go to Settings → System → About and check “System type.” Verify both the operating system’s bitness and the processor type; “64-bit” alone isn’t enough. ARM processors can run 64-bit systems without being x64. If your system reports an ARM-based processor, don’t treat this page’s x64 installer as a native ARM build.
Before switching from classic WPF to Desktop, exit the old client, including any instance still running in the notification area. Keep a recoverable copy of your configuration or subscription sources, then install the new edition. On first launch, check the selected server and routing before enabling the system proxy or TUN. If you’re only checking out the new interface, keeping your existing proxy settings makes it easier to tell installation issues from connection issues.
Check About This Mac for the chip or processor. Choose arm64 for an Apple chip and x64 for an Intel processor.
| Apple chip | Choose the arm64 DMG |
|---|---|
| Intel processor | Choose the x64 DMG |
| Install location | Copy the app from the disk image to Applications |
Open the downloaded DMG and follow the window prompts to copy the app. When copying is complete, launch it from Applications rather than running it from the mounted disk image. Before replacing the app with a newer version, quit the running client. Removing the downloaded disk image and removing the installed app are separate actions.
If macOS says the app can’t be opened, read the message and check the file’s source and chip architecture. Managed devices may restrict software installation or network settings; follow your device’s management requirements rather than disabling system-wide protections just to install an app. Opening the window doesn’t mean the app is routing traffic. Check the system proxy or TUN separately after installation.
Uses the Xray core. Most mainstream phones released after 2015 are good candidates for arm64, but check that the system supports arm64-v8a.
Uses the v2fly core. Choose it if your existing configuration specifically requires this core, and check protocol and security-layer compatibility before switching.
| arm64 | System supports arm64-v8a |
|---|---|
| Universal build | For devices with an unknown architecture; the Android version must still meet the package requirements |
| Install permission | Android must allow the browser or file manager to install APKs |
The same processor can run systems with different bitness. To decide whether the arm64 package will work, check the application architectures supported by your system, not the processor’s advertised specs. The universal build supports more architectures, but it doesn’t lower the Android version requirement or fix update conflicts caused by different signing keys.
If Android blocks your browser from opening the APK, first confirm the download source, then check the system’s install permission for that source. If the installer reports a conflict with an existing app, check whether a same-named app from a different distribution channel is already installed and back up its configuration. Uninstalling and reinstalling may erase app data, so don’t make that your first troubleshooting step. The VPN permission request shown when you first connect is separate from install permission.
| Package format | Debian and Ubuntu usually use DEB; RPM-based distributions use RPM |
|---|---|
| x64 | The DEB filename uses amd64; the RPM filename uses x86_64 |
| arm64 | The DEB filename uses arm64; the RPM filename uses aarch64 |
Check your distribution name and architecture in system information. The same package format doesn’t mean a package will work on every distribution. If the installer reports unmet dependencies, check your distribution version and the dependency names rather than forcing the installation to ignore them. This page’s RPM filename includes the el10 marker; for other RPM-based distributions, rely on the installer’s dependency checks.
After installation, launch v2rayN from your desktop’s application menu. First make sure the GUI opens, then set up subscriptions and proxying. Whether apps use the desktop environment’s system proxy depends on whether they honor that setting; an app that doesn’t use the proxy doesn’t necessarily mean you chose the wrong installer.
The installer includes only the client and components provided in that release. After installation, whether the server list is populated depends on the configuration you import. If you can still access the old device, identify which entries came from subscriptions and which were added manually. You can fetch subscriptions again from the same URL, but keep manual entries and local routes separately. When moving between operating systems, don’t assume the entire desktop configuration folder can be read directly by the mobile app.
Subscription URLs may contain access credentials, so hide the full URL in screenshots and troubleshooting notes. In the desktop client, save the URL in v2rayN’s “Subscription Group Settings,” then update it from “Subscription Groups.” On mobile, open “Subscription Group Settings” from the client menu, save the URL, then return to the list and update the subscription. After importing, make sure you’re viewing the right group and check the update result; an empty list alone doesn’t mean you need a different installer.
An open client window only confirms that the app has launched. After importing a configuration, select the intended server, then enable a proxy method for your platform. On Windows, check the “System Proxy” option from the v2rayN tray menu. The system proxy affects only apps that honor it. If you need to route more traffic, learn about the permissions and routing requirements of TUN mode. When troubleshooting for the first time, don’t change the server, system proxy, and routes all at once; otherwise, it’s hard to tell which change affected the result.
On Android, tapping Connect usually triggers a system VPN request the first time. If another app is already using the VPN, check the current system connection before deciding whether to switch. After granting permission, test with just one target app and note whether the issue occurs during import, launch, or access. A client showing as running doesn’t mean every app will be routed as expected.
The version shown on a card comes from the release manifest, and its download link points to the file mapped there. Neither tells you which version is actually installed on your device. After installation, check the client’s About screen or the system’s app information for the installed version. If your browser kept an older file with the same name, make sure you’re opening the installer you just downloaded before updating.
After updating, test with the configuration that worked before; don’t change subscriptions and routes at the same time. If your configuration isn’t listed, first check that you launched the new client instance, selected the right group, and migrated the old configuration. Keeping a recoverable copy of the old settings can save you from having to rebuild everything after an update.
See how to import subscriptions and connect · View installation guides for all platforms · Compare the three clients
Find answers about versions, architectures, and update options.
For a fresh install, start with the Desktop edition, which uses the Avalonia interface. If you already use the classic WPF edition and prefer its familiar layout, you can stay with WPF. Both downloads are for Windows x64.
Open About This Mac from the Apple menu. Choose the Apple Silicon installer if it shows an Apple chip, or the Intel installer if it shows an Intel processor.
The arm64 build is for devices that support arm64-v8a. The universal build includes components for multiple processor architectures, so its file is usually larger. Consider it if you’re unsure of your device’s architecture, but make sure your Android version meets the requirements.
No. Debian and Ubuntu users should generally choose DEB; Fedora and other RPM-based distributions should choose RPM. After matching the package format, check that the architecture and dependencies suit your system.
Back up your subscription URLs, manually added servers, and custom routes first. Before switching clients, check that the new client supports the protocols, transport, and security layer used by your existing configuration, then import it.