v2rayN Recommended
The desktop version features a modern cross-platform interface. WPF is the classic, stable version with the familiar Windows layout and controls. Choose either one.
Installers and system requirements
Choose your operating system first, then check the processor architecture. Use v2rayN on desktop and v2rayNG on Android. Consider v2flyNG if your configuration requires the v2fly core.
The desktop version features a modern cross-platform interface. WPF is the classic, stable version with the familiar Windows layout and controls. Choose either one.
| What to check | How to choose |
|---|---|
| System type | Check your system type under Settings → System → About. This page provides x64 installers. |
| Runtime | If startup reports a missing .NET desktop runtime, check the required version and architecture in the message. |
| Installation permissions | Extract the files before running the installer. On managed devices, follow your organization's software installation policies. |
Don't run the app from the archive preview window. Extract it to a directory where you have write access, then run the installer. This also makes it easier to distinguish extraction issues from missing runtimes or insufficient installation permissions.
Compare the desktop and WPF versions →
Open About This Mac to check your chip or processor. Choose arm64 for Apple silicon or x64 for an Intel processor. Both downloads are disk images.
| What to check | How to choose |
|---|---|
| Chip architecture | Apple silicon uses arm64; Intel uses x64. |
| OS compatibility | Matching the chip architecture doesn't guarantee OS compatibility. If you see a compatibility warning, check the build's minimum OS requirement. |
| Installation location | Mount the DMG, drag the app to Applications, then open it from there. |
Quit any running instance before updating, then replace the app. If macOS blocks it from opening, read the warning carefully and determine whether it's due to an incompatible OS version, an incomplete download, or an organization's security policy. Don't disable system protections just to install the app.
Powered by the Xray core. Most mainstream phones released after 2015 can use arm64. Choose the universal build if your device runs a 32-bit OS or you're unsure of its architecture.
Powered by the v2fly core. Choose this client when your configuration specifically requires that core. Before switching, check the protocol and transport settings; importing a subscription alone doesn't guarantee compatibility.
| What to check | How to choose |
|---|---|
| App architecture | Choose arm64 if your system supports arm64-v8a. A phone with a 64-bit chip doesn't necessarily support 64-bit apps. |
| Installation source | If prompted, grant install permission temporarily only to a file manager or browser you trust. |
| Connection permission | Android asks for VPN permission when you first connect; it's not part of installation. Disconnect your current connection before switching clients. |
DEB is usually the right choice for Debian- and Ubuntu-based distributions. For RPM-based distributions, check the target build and dependencies; the RPM here is marked el10.
| What to check | How to choose |
|---|---|
| Processor architecture | If uname -m returns x86_64, choose x64. If it returns aarch64, choose the 64-bit ARM package. |
| Package format and dependencies | Check dependencies with your distribution's package manager. Matching file extensions don't guarantee compatibility across distributions. |
| Runtime | v2rayN is a GUI client. Launch it in a local graphical session and check its status. |
When you encounter a dependency error, note the library name, version, and distribution shown in the message. Don't force-install a package built for another distribution; skipping checks won't provide the libraries the app needs to run.
The platform, architecture, and package format determine whether an installer will work. Check separately whether your existing configuration is still compatible.
Don't rely only on the device model or purchase date. Check system information on a desktop or laptop; for Android, check which app architectures the current OS supports. The packages supported by a device can change if you install a different OS. When downloading for someone else, use the target device's details, not those of the device you're downloading on.
amd64 and x86_64 both refer to the common 64-bit x86 architecture; neither is limited to a particular processor brand. arm64 and aarch64 refer to 64-bit ARM. Once you know these names, check the platform selected on this page to avoid mixing packages that share an architecture but target different operating systems.
Back up subscriptions, manual configurations, and client-specific settings separately. Reimporting a subscription usually restores its entries, but not locally added entries, routing rules, or listening ports. If the old client supports export, export anything you want to keep and note the current proxy mode and active configuration.
Subscription URLs may contain access credentials. Keep them somewhere secure and don't share them publicly, even in screenshots. If you're only switching interfaces or builds, stop the old instance before starting the new one to avoid port conflicts or repeated changes to system proxy settings. Once basic connectivity and required rules are working, you can remove the old app and manage your backups.
An installer that won't open, an app that exits after installation, and an app that opens but won't connect are problems at three different stages. For the first, check that the download completed, the package format matches, and review any permission warnings from the OS. For the second, note any runtime errors, directory permissions, or startup logs. There's no need to reimport your subscription yet.
On older systems, the processor architecture may be correct while system APIs or dependency versions are incompatible. Troubleshoot by checking the OS version, selected build, and exact error message together instead of repeatedly trying different packages. On Android, if you see “App not installed,” check for a signature mismatch, unmet system requirements, or insufficient storage.
Troubleshoot startup crashes →If your current configuration works, note the client, proxy mode, and local port before upgrading. Test the original configuration first after the upgrade. If you also change the core, subscription, and routing, it will be difficult to identify what caused any issue.
If you need to revert to the old client, first check whether the new version changed the configuration format, then consider restoring your pre-upgrade backup. Don't extract old and new versions into the same directory. For package-managed apps, distinguish uninstalling the app from deleting user configuration, so you don't remove rules you still need when cleaning up an old package.
First confirm that the app launches, then import your configuration and test the connection. Downloading, installing, and routing traffic through the app are separate steps.
After opening the client, add a group for your existing subscription, then run a manual update. Seeing entries doesn't mean you're connected: select an active configuration and check the client logs to confirm the core process started successfully. Keep manual configurations separate from subscription entries to avoid confusion when updating later.
If a subscription update fails, determine whether the URL is unreachable or its contents can't be parsed. You don't need to open multiple clients to test it; running them at the same time can change system proxy or VPN settings and make the error harder to reproduce. If you need help, share the failure stage and a redacted error message, not the full subscription URL.
See how to import a subscription →On desktop, start by testing with a browser that follows system proxy settings. Terminal tools and some desktop apps may ignore the system proxy, so check which proxy address they use individually. If an update changes the local port, also update the proxy address in any apps where you entered it manually. Don't rely solely on the connection status shown in the client.
On Android, watch for the system VPN permission prompt when connecting for the first time. If another VPN session is active, decide which one to keep before switching clients. Read the TUN and routing sections of the manual only if the app isn't handling the traffic you need. For an initial test, there's no need to change both traffic capture and routing rules at once.
See routing and traffic-splitting guide →Choosing an installer, in-place updates, and identifying versions.
No. Choose the desktop version for a first installation. Choose WPF if you prefer the classic interface. Exit the old client and back up your configuration before switching.
No. The universal build can help avoid choosing the wrong architecture, but it does not change the minimum system requirements or resolve signing conflicts or device management restrictions.
First check whether an in-place update is supported, and back up your configuration. If Android reports a signature mismatch, don't uninstall right away; uninstalling may erase app data.
The installer contains the client app. After installing, import your existing subscription or configuration separately. A successful installation does not mean a proxy connection is active.
The card shows the app version, while each download is a specific build. If they differ, note the actual filename and check the running version in the client's About screen after installation.