v2rayN
The desktop edition has a modern cross-platform interface; the classic WPF edition keeps the familiar Windows layout. Choose either one for your first install.
Choose v2rayN for desktop, or v2rayNG or v2flyNG for Android. Select your operating system first, then choose a package for your device's architecture and package format.
The desktop edition has a modern cross-platform interface; the classic WPF edition keeps the familiar Windows layout. Choose either one for your first install.
| Check | Requirements |
|---|---|
| System | A currently supported 64-bit version of Windows is recommended. |
| Architecture | Both packages are x64. Check System type under Settings → System → About. |
| File | Extract the ZIP file completely, then run the installer from the extracted folder. |
Don't run a program by dragging it out of the ZIP preview window; nearby files may also be required. If you see a missing runtime message at startup, note the component name and version, then follow the system's instructions.
When switching from WPF to the desktop edition, note your subscription groups, routing options, and local ports first. After installing, open the client and check these settings before deciding whether to remove the old version. If both editions try to use the same local port, the one launched second may fail to listen.
Check About This Mac for your chip or processor. Choose arm64 for Apple M-series chips and x64 for Intel processors. Both downloads are DMG files.
| Check | Requirements |
|---|---|
| System | A currently supported version of macOS is recommended. For older versions, check the compatibility notes for the current release. |
| Architecture | Apple Silicon uses arm64; Intel uses x64. |
| File | Open the DMG and follow the instructions in the disk image to place the app. |
After copying the app, launch it from its destination, then eject the disk image. Running the app directly from the mounted window may make future launches or updates depend on that image.
When moving to another Mac, a package downloaded for your old computer may not suit the new one. Check the new device's chip before transferring settings. If macOS says the app can't be opened, determine whether the cause is an incompatible system version, the wrong architecture, or a device management policy. Don't disable system protection globally just to install the app.
Powered by the Xray core. Most mainstream phones released since 2015 can start with arm64. Choose Universal if your device only supports 32-bit apps or you can't confirm its architecture.
Powered by the V2Fly core, this client is a good fit if you need to check existing settings against V2Fly features. Both packages offer the same client features; choose based on your device's architecture.
| Check | Requirements |
|---|---|
| System | Your device must meet the minimum Android version listed for the current APK. |
| Architecture | Choose arm64 if your system supports arm64-v8a; if you're unsure, consider the Universal package. |
| Install source | Open the APK with the system installer. If device management policies restrict installation, check with your administrator. |
A 64-bit phone chip doesn't guarantee that the system supports 64-bit apps. On older devices, the app architectures supported by the system are a better guide than the chip model. Universal packages are usually larger and don't lower the client's Android version requirements.
If the manifest version on the card differs from the version in the download filename, confirm the actual version in the system installer and the installed app's details. If the installer identifies an upgrade as a downgrade, cancel and check the installed version against the package you selected.
If you already have one client installed, switching to another requires checking subscription format and protocol support again. Successfully importing data only means the client recognized the entries; it doesn't guarantee support for every transport option they use.
Choose a package format for your distribution, then select the right architecture. In filenames, amd64 and x86_64 both mean x64; aarch64 means arm64.
| Check | Requirements |
|---|---|
| Distribution | Debian- and Ubuntu-based distributions generally use deb; Fedora and RHEL-based distributions generally use rpm. |
| Environment | Requires a graphical desktop session and the system libraries listed for the current package. |
| Architecture | Check your system information to confirm whether your system is x64 or arm64. |
Use your distribution's package installer to open the local package. If it reports unavailable dependencies, check the distribution version and the package's build target. Distributions can use different dependency names or versions, even when they use the same file extension.
Some desktop environments manage the system proxy centrally, while some apps have their own network settings. After the first launch, confirm that both the client and the app you want to use open independently, then test whether the proxy settings work. A desktop proxy that doesn't cover a particular app doesn't mean the package is unusable.
Make sure the client starts normally before importing settings. Following this order makes it easier to tell installation problems from connection problems.
When downloading for another device, choose based on the device that will run the client, not the one you're browsing from. Check three things: whether the target operating system can run the client, whether the package architecture matches the system, and whether the device's package installer can open the file. If any of these don't match, downloading the same file again won't help.
The file extension tells you how to open the file: ZIP archives must be extracted; DMG is a disk image; Android's system installer handles APK files; and deb and rpm belong to different package systems. Renaming an extension doesn't convert a file. If a browser download was interrupted, confirm it finished before blaming the system or processor for an installer error.
Architecture names also depend on the platform. A Windows x64 package and a Linux x64 package are for different operating systems. An Android arm64 APK won't run on macOS, even if both devices use ARM processors. The operating system determines the platform; architecture and package format determine which file to choose within that platform.
Before updating, decide what you need to keep: subscription groups, manually added entries, routing rules, local listening ports, and system proxy or startup settings. Use the client's export feature if available; make a local note of anything it doesn't include. Subscription URLs and share links may contain access credentials, so don't include them in public screenshots or shared documents.
Before replacing a desktop client, quit it completely, including instances still running in the system tray or menu bar. This reduces file lock issues and makes it easier to tell which version launches after installation. When switching interfaces or package formats, keep the old settings until you've confirmed the new app can read or import what you need, then remove the old files.
If the installer reports a signature conflict during a mobile update, don't keep retrying. Check where the existing app came from and, if possible, update through the same distribution channel. If you need to switch channels, back up any local data you can export first. Uninstalling may erase app-private storage, and re-importing a subscription may not restore custom groups or edits to individual entries.
On first launch, make sure the app opens to its main screen, can be launched again after quitting, and saves changes to settings. If an error appears before the window opens, note the system message, package name, and steps that triggered it. Changing subscriptions or servers won't usually fix a startup failure—the client hasn't reached the point where it reads its settings yet.
Once the main screen opens normally, follow the Quick Start Guide to import a subscription or individual share link. Check that the expected groups and entries appear, then change one thing at a time—for example, select an entry and check whether the target app uses the system proxy. Don't switch clients, subscriptions, and network modes all at once, or it will be hard to tell what caused the change.
If an entry appears but a protocol or transport setting doesn't work, see the Protocol Handbook to check core and configuration compatibility. When reporting a problem, include the system and app versions, package format, and exact message. Hide subscription URLs, personal server details, and local account information. A specific error message is more useful than simply saying, "It won't connect."
Install either one. The desktop edition has a modern cross-platform interface, while the classic WPF edition retains the familiar Windows layout. Back up your settings and quit the running client before switching. Don't enable the system proxy in both editions at the same time.
Open About This Mac from the Apple menu. Choose the Apple Silicon package if it shows an Apple M-series chip, or the Intel package if it shows an Intel processor. Choose based on your Mac's processor, not the macOS version name.
The universal package supports a wider range of processor architectures, but installation can still fail if your Android version is too old, device management policies block installation, or the old and new packages have different signatures. Check the system message first. If you need to uninstall the old version to switch packages, save your local settings beforehand.
Debian- and Ubuntu-based distributions generally use deb; Fedora and RHEL-based distributions generally use rpm. After choosing the right package format, check the architecture, distribution, and dependency versions. The el10 in an rpm filename indicates its build target; it doesn't mean the package installs on every rpm-based system.
The installer provides the client application, not server details. Import server information after installation from an existing subscription or individual share link. First make sure the client opens, then follow the quick-start guide to import your details. If the list is still empty, check that the subscription has refreshed and that its format is supported.