v2rayN
Windows · 7.24.1
Choose your operating system first, then select v2rayN, v2rayNG, or v2flyNG by processor architecture and package format.
ZIP / DMG / DEB / RPMAPKChoose based on the device that will run the client, not the device you’re using to browse this page.
Windows · 7.24.1
| Check | Requirements | How to check |
|---|---|---|
| Operating system and architecture | A supported 64-bit version of Windows is recommended. The builds here are x64. | Open Settings → System → About and check System type. |
| Package format | Both ZIP files are archives containing the installer. | Extract the entire archive to a local folder, then run the installer from the extracted folder. |
| Runtime requirements | Runtime requirements may differ between interface builds. | If startup reports a missing runtime component, note its name and version, then follow the requirements for that build. |
Choose either Desktop or Classic WPF; you don’t need both. When switching from Classic, exit the old client from the notification area before launching Desktop. If both instances listen on the same port, the new one may not be able to start the local proxy.
If a desktop shortcut still opens the old version after an update, check the running version on the client’s About page, then create a new shortcut from the updated installation folder. If startup fails, first identify whether the archive was incompletely extracted, the installer did not finish, or the app reported an error after launch. Troubleshoot each stage separately.
macOS · 7.24.1
| Check | Requirements | How to check |
|---|---|---|
| Chip or processor | Choose arm64 for Apple silicon or x64 for an Intel processor. | Open About This Mac from the Apple menu and check Chip or Processor. |
| Operating system version | Your macOS version must meet the minimum requirement for the selected build. | Note your macOS version in About This Mac and compare it with the selected build’s release notes or system prompt. |
| Installation location | Open the DMG disk image, then install the app in a writable Applications folder. | After copying the app, launch it from its destination folder, not from the disk image. |
After moving to a new Mac, download the build for its chip. You can migrate the app and its configuration separately: first check that the newly installed client launches, then import the old configuration using a method supported by the client. This helps distinguish architecture issues from configuration migration issues.
After opening the DMG, follow the window instructions to copy the app to Applications. If macOS reports that an app with the same name is already there, quit the old process and back up your configuration before deciding whether to replace it. Read any security prompts carefully; on a managed device, follow your organization’s installation process.
Android · Xray core · 2.2.6
Android · V2Fly core · 1.10.31
| Check | Requirements | How to check |
|---|---|---|
| App architecture | The arm64 package requires system support for arm64-v8a. A 64-bit processor alone does not guarantee compatibility. | Check the device manufacturer’s information about system architecture. If you can’t confirm it, choose Universal. |
| Operating system version | The Android version must meet the requirements for the selected APK. | Check your Android version under Settings → About phone, then compare it with the build requirements. |
| Installation permissions | Your device must allow the browser or file manager you’re using to install apps. | Check which app the system prompt identifies as the source. For work profiles and managed devices, follow the device policies. |
Before switching Android clients, check the configuration instructions from your service provider. The clients use different cores, and support for the same link format doesn’t mean every option will work the same way. After switching, test a known-good configuration before organizing your subscriptions in bulk.
If the system reports an app signature conflict, installing the Universal build usually won’t help. Keep the existing app, back up any configuration you need, and check where the original app came from. Open the downloaded APK in your phone’s file manager rather than starting installation from a notification while the download is still in progress.
Linux · 7.24.1
| Check | Requirements | How to check |
|---|---|---|
| Package format | Choose a DEB package supported by your distribution or a compatible RPM build. | Check your distribution and release in system information, then use your system’s package manager to inspect the package details. |
| Processor architecture | x86_64 corresponds to x64; aarch64 corresponds to arm64. | Check the architecture of the target system. For a virtual machine, use the guest system’s details. |
| Desktop environment | This page provides a GUI client, which requires a working desktop session and the relevant dependencies. | If your package manager reports missing dependencies, note the package names and version requirements, then check that the distribution and build are compatible. |
After downloading, open the package with your distribution’s software installer. If it reports an architecture mismatch, choose a package for the correct architecture. If dependencies are missing, first check that the distribution matches the build target. Changing the file extension won’t change the package format or add missing components.
If the client opens but desktop apps aren’t using the proxy, check the desktop environment’s proxy settings and each app’s network options. Terminal programs may use a separate proxy configuration. Follow the steps to troubleshoot browsers and terminals separately to narrow down the issue; there’s no need to reinstall the client first.
Check each stage in order: download, installation, and first launch. Change one thing at a time to pinpoint where the problem occurs.
On the target device, note the operating system, version, and architecture. If you’re downloading for another computer or a virtual machine, choose based on that target system. The computer running the browser determines where the file is saved first, not which package you need.
Package format and architecture are independent requirements. For example, x64 DEB and RPM packages use different installation tools, while x64 and arm64 DEB packages target different system architectures. Check both, then verify distribution compatibility.
When preparing packages for multiple devices, organize downloads by operating system and architecture. Record the client name, architecture, and package format in your handoff notes. Don’t rename every package to the same filename, or it’ll be difficult to tell which one you chose if something goes wrong.
Keep installation files separate from user data. User data may include subscription groups, manually added servers, local listening ports, and custom routing. Use the old client’s export or backup feature before installing the new version.
Check whether the export includes manually created entries and local settings. If it only saves subscription URLs, also note your existing proxy mode and ports. Subscription URLs and export files may contain credentials, so store them somewhere you control.
Quit the old client before replacing it. Closing the main window may leave it running in the notification area or menu bar. Confirm that the old process has exited before launching the new version. This helps prevent port conflicts and avoids mistaking the old instance’s status for the upgraded client’s.
If you can’t open the file, first confirm the download is complete and that the file extension matches the selected download. If the installer opens, the system can handle that package format. Next, use the installation prompts to distinguish permission issues, missing dependencies, and conflicts with existing apps.
When a permission prompt appears, check the installation source and destination it identifies. On a device managed by your employer or school, follow the administrator’s instructions. For dependency issues, save the exact error message and identify the missing component instead of trying a package for another platform.
If the system says it can’t install an older version, first check the version of the existing client. Before rolling back, make sure you have a recoverable copy of your configuration. Newer configuration files may contain settings the older client doesn’t recognize, so review the configuration again after downgrading.
On first launch, confirm that you opened the expected client and version. Then import a subscription or server configuration you’re authorized to use, select an entry, and follow the Getting Started guide to check the mode and connection.
After migration, check your subscription groups, selected entry, and local ports. If you changed a port, also verify the proxy address in apps such as your browser and terminal. If a listening port is already in use, see how to troubleshoot a local port conflict.
Successful installation and a working connection are two different things. If the interface opens, the app has started—that’s all it confirms. To test the connection, use one app and one configuration, note whether the error comes from the client or the app or is a request timeout, then decide which layer to investigate.
Find answers by package type, compatibility issue, or post-installation status.
For a first install, choose Desktop for its cross-platform interface. Choose Classic WPF if you prefer the familiar classic interface or already use a WPF-based workflow. Both packages are x64.
Open About This Mac from the Apple menu. Choose arm64 for an Apple chip or x64 for an Intel processor. Don’t choose based on the Mac’s purchase year alone.
No. The universal build supports multiple architectures, but installation can still be limited by the Android version, app signatures, or device policies. If the device reports a conflict with an installed app, back up your configuration and check where the existing app came from.
No. Choose a package format supported by your distribution, then check the processor architecture and dependencies. The current RPM filename includes el10, so confirm your system is compatible with this build before installing.
The package contains only the client. Before using it, import a subscription or server configuration you’re authorized to use, select an entry, and follow the Getting Started guide to test the connection.
The card shows the app version listed in the manifest; the filename identifies the download package. To check the installed version, see the client’s About page or the app details in your system settings.