v2rayN
RecommendedDesktop is the modern edition with a cross-platform interface and is recommended for new installs. WPF is the classic, stable edition for users already familiar with the Windows layout and system tray menu. Choose one, not both.
Use v2rayN on desktop. For Android, v2rayNG is the recommended choice; choose v2flyNG if you need its core. Select your device’s OS first, then confirm its chip architecture or package format.
Desktop is the modern edition with a cross-platform interface and is recommended for new installs. WPF is the classic, stable edition for users already familiar with the Windows layout and system tray menu. Choose one, not both.
| Check | Requirement |
|---|---|
| System type | Go to Settings → System → About and confirm that your system is 64-bit and the processor is x64. |
| Installation media | Extract the ZIP to a writable folder before opening the installer. |
| Runtime environment | If your OS version or runtime libraries don’t meet the requirements, follow the installer’s instructions. |
In System Information, check for both “64-bit operating system” and “x64-based processor.” Seeing “64-bit” alone isn’t enough: 64-bit systems can run on different processor architectures. Once confirmed, use File Explorer’s Extract All option to unpack the ZIP. Don’t run the installer from the archive preview; it may need other bundled files that aren’t available until the whole archive is extracted.
When switching from classic WPF to Desktop, back up your nodes and subscription groups, then exit the old version from the system tray—not just by closing its main window. On the new version’s first launch, check your node list, routing choices, and local listening port. If the client is open but webpages won’t load, check whether the old version left a system proxy setting behind and whether a program is still listening on its configured port. Don’t start by reinstalling or repeatedly switching nodes.
Open About This Mac from the Apple menu. Choose Apple Silicon for an Apple M-series chip or Intel for an Intel processor.
| Check | Requirement |
|---|---|
| Chip or processor | Apple Silicon uses arm64; Intel uses x64. |
| Installation location | You must be able to mount DMG files and copy apps to Applications. |
| OS version | Check your current version in About This Mac. If the app reports that your OS is incompatible, first check the requirements for the package you downloaded. |
Double-click the DMG, copy the app to Applications, then launch it from that folder for the first time. Once the copy is complete, you can eject the disk image in Finder. The icon in the mounted image and the installed app aren’t separate versions that you need to run. If a compatibility warning appears, check the chip architecture and OS version first. If installation is blocked by a device management policy, contact your administrator rather than changing global security settings.
Before upgrading, quit the old version from the menu bar or app menu, then replace the app. After launching the new version, verify a node in the client, then check the proxy settings for your active network service under System Settings → Network. If you switch between Wi-Fi and Ethernet, check the service currently in use. Looking at an inactive service won’t tell you how your browser is connecting.
For most phones released since 2015, arm64 is the best choice. If you’re unsure whether your system supports arm64-v8a, choose the universal version. Architecture support depends on the device’s OS, not just its processor model.
Choose v2flyNG if your existing configuration is specifically designed for V2Fly. Before switching, check the node’s transport and security settings; the two apps don’t support exactly the same core features or configuration options.
| Check | Requirement |
|---|---|
| App architecture | Choose arm64 if your system supports arm64-v8a; if you’re unsure, choose the universal version. |
| System and storage | Your OS must meet the selected package’s minimum requirements, and you’ll need enough storage space to install it. |
| Installation permission | Allow the browser or file manager you use to open the APK to install apps. |
| Connection permission | The first time you start a proxy connection, approve the VPN request in the system prompt. |
In the same user session, disconnect any other active VPN before testing the new client.
If you see “App not installed,” first work out whether the issue is APK parsing, installation permissions, or an attempt to replace an existing app. A phone’s processor may support 64-bit while its OS provides only a 32-bit app environment; in that case, try the universal version. If the system reports a conflict with an existing app, check whether you changed the installation source. Android generally allows an app to be replaced only by a version with a matching signature. Uninstalling may erase local data, so back it up before deciding whether to reinstall.
Approve the system VPN request the first time you start the proxy. If the connection drops immediately, check whether another app is using the VPN and whether “Always-on VPN” is enabled for an older app. If it drops only after the screen has been off for a while, check whether battery settings restrict background activity, then compare how the same node performs with the screen on and off. This helps distinguish an app being suspended from an unstable node.
The number on each card is the app version listed in the release manifest; it may differ from a package’s filename. When replacing an existing app, check the actual installer and the version shown under system App info. Universal and arm64 packages are architecture choices, not separate upgrade and downgrade versions.
For Debian- and Ubuntu-based distributions, start with deb. For RPM-based distributions, start with rpm. A matching package format doesn’t guarantee compatibility with your distribution version or its dependencies.
| Check | Requirement |
|---|---|
| Desktop environment | The package is intended for systems with a graphical desktop session. |
| System architecture | x86_64 corresponds to x64; aarch64 corresponds to arm64. |
| Packages and dependencies | Choose a package format for your distribution, then check the graphical installer’s dependency and compatibility information. |
Check your distribution, version, and system architecture on the system’s About page. amd64 and x86_64 are the x64 architecture names here; they don’t mean the package works only with processors from a particular brand. Open the downloaded file with your distribution’s graphical package installer. If dependencies are missing, note their names and versions from the error, then check whether your distribution provides them. Don’t switch to rpm just because deb won’t install, or vice versa.
After launch, verify a node, then check whether your desktop environment accepts the client’s system proxy settings. Some apps use their own network settings even after the desktop proxy changes. If your browser works but another app doesn’t, check whether that app uses the system proxy. If only certain traffic needs to go through TUN, follow the installation guide to check permissions and current routing rather than running every app as an administrator.
Test installation, configuration import, and traffic routing separately. When something goes wrong, first identify which step didn’t complete.
Your browser may still be writing the downloaded file. Check the browser’s download history to make sure the download is complete, then open the destination folder. If file extensions are hidden, use Properties or Get Info to tell ZIP, DMG, APK, deb, and rpm files apart. If you see a file corruption or cannot-open error, note the exact message and download status. Changing a file extension won’t convert it to another package format.
If you already use the client, back up your nodes, subscription groups, and custom routing rules, and note the local port and traffic-handling mode in use. Manually added nodes may not be included in subscriptions, and custom routes won’t automatically return when a subscription updates. Backups may contain subscription URLs and node credentials. Store them somewhere you control, not in a public cloud drive, chat screenshot, or support request. After installing the new version, make sure it can still read your settings before deleting old files.
An empty list after a fresh install is normal. In v2rayN, for example, add an address under Subscription Group, then choose Update All Subscriptions and confirm that nodes appear in the list. Select a node, check the client logs for connection or handshake errors, then choose system proxy or TUN. Don’t run multiple clients or change several settings at once while troubleshooting. Change one thing, then retry the same webpage to narrow down the cause.
For step-by-step instructions, see Quick Start. For differences in system permissions, package dependencies, or proxy routing, see Installation Guide.
Choosing a package, upgrading, and connecting for the first time.
No. For a fresh install, choose the desktop edition with its modern cross-platform interface. If you prefer the classic Windows layout or need to follow instructions for that edition, choose the classic WPF version. Run only one client while troubleshooting to prevent two instances from changing your system proxy at the same time.
Open About This Mac from the Apple menu. Choose Apple Silicon if Chip lists an Apple M-series chip, or Intel if Processor lists an Intel processor. Choose based on the Mac’s actual chip, not its purchase date or storage capacity.
No. The universal version is useful when you’re unsure which app architecture your device supports. It won’t fix failures caused by an outdated OS, installation-source permissions, or a signature conflict with an existing app. Check the system message first, then decide whether to try a different package.
First choose deb or rpm based on your distribution’s package system, then select x64 or arm64 to match your system architecture. Even when both match, check the installer’s compatibility and dependency requirements for your distribution.
Back up your existing nodes, subscription groups, and custom routing rules. Separately note your local listening port and current traffic-handling mode. Exit the old client before upgrading. After launching the new version, verify your nodes and routes before enabling the system proxy or TUN. Keep your backups and subscription URLs somewhere secure.
The installer provides only the client. You need to configure server nodes separately: import your own node configuration, or add and update a subscription you’re authorized to use. Once nodes appear, select one, configure how traffic is routed through the proxy, and test the connection.