Use v2rayN on desktop and start with v2rayNG on Android. Check your operating system and CPU architecture, then import a subscription and configure the proxy after installation.
Each button links to an installer; version labels update with the release manifest.
7.24.1
Windows x64 installer. Desktop uses a modern cross-platform UI; classic WPF keeps the traditional Windows interface and is a stable option for users who prefer the familiar layout.
This download is a ZIP archive. Extract it completely before running the installer; don’t launch it from the archive preview.
| Check | How to choose | What to do |
|---|---|---|
| System environment | A Windows desktop environment supported by the current client | Read the installer’s compatibility notices before installing; don’t assume current builds support older Windows versions. |
| Processor | x64 system | Check the system type in System Information; don’t rely on the computer’s brand or model alone. |
| Installation permissions | A writable installation folder and installable dependencies | If a runtime component is missing, install it as instructed. Repeatedly changing subscriptions won’t help. |
| Traffic routing | System proxy or TUN | Test the system proxy first. TUN requires additional checks for permissions and network adapters. |
Both interfaces require a valid node configuration. Import and update your subscription, select a node, then choose “System proxy → Set system proxy” from the tray menu. Whether a browser uses the proxy also depends on whether it follows system settings. Before closing the client, select “Clear system proxy” to prevent your system from pointing to a stopped local port.
If the main window doesn’t appear, check the notification area and hidden icons on the right side of the taskbar. If a runtime error appears, note the full message before troubleshooting. Successful installation, a running core, and successful website access are separate stages; check each one rather than relying on the tray icon to confirm a connection.
7.24.1
Choose a DMG for your Mac’s processor. Apple Silicon uses arm64; Intel processors use x64. Prefer the build that matches your Mac’s architecture.
Open About This Mac from the Apple menu. If it lists a chip and an M-series name, choose Apple Silicon; if it lists an Intel processor, choose Intel.
| Check | How to choose | What to do |
|---|---|---|
| System environment | A macOS desktop environment supported by the current build | Check the app’s startup message and build requirements; confirm compatibility carefully on older systems. |
| Apple Silicon | M-series chip, arm64 | Choose the Apple Silicon DMG; there’s no need to try the Intel package first. |
| Intel | Intel processor, x64 | Choose the Intel DMG. Apps built only for arm64 won’t run on Intel. |
| Proxy permissions | System allows network proxy settings to be changed | Follow the permission prompts. TUN also requires the appropriate network and permissions configuration. |
After installation, add a subscription and check that the system proxy is set for the network service you’re using. You may need to check it again after switching between wired and wireless networks. Some apps use their own proxy settings instead of the system proxy; check those options before changing node settings.
Quit the client before updating, then replace the app. If your network acts up after quitting, check Network settings for a leftover local proxy address. TUN isn’t a general-purpose fix: get the standard system proxy working first, then decide whether you need to route traffic from other apps.
2.2.6
The recommended Android client. Most mainstream phones released after 2015 can use arm64; if you’re unsure of your device’s architecture or arm64 won’t install, check whether you need the Universal build.
Universal supports multiple CPU architectures and is usually a larger download. The version label and file path come from separate manifest fields and may temporarily be out of sync. Check the app details shown by the system during installation.
1.10.31
An alternative when you need compatibility with the V2Fly core. First confirm that the protocols and transports in your configuration are supported; similar names don’t mean the two clients support exactly the same options.
Each client stores its configuration separately. Back up your subscription before switching, and run only one client at a time while testing to avoid conflicts over Android’s VPN connection.
| Check | How to choose | What to do |
|---|---|---|
| System compatibility | The device meets the selected APK’s minimum system requirements | Let the installer check compatibility. A matching architecture doesn’t guarantee the Android version meets the requirements. |
| CPU architecture | arm64 or Universal | For most mainstream phones, start with arm64; for other devices, check the system information. |
| Installation permissions | Allow installs from this source | Grant permission only to the browser or file manager you’re using for this installation. |
| Connection permissions | Android VPN permission | Review and approve the permission request when connecting for the first time. Check whether another VPN app is running. |
Before installing an APK, note whether the system reports an incompatible version, a signature conflict, or an unauthorized installation source. Each has a different fix, and repeatedly downloading the same package usually won’t help. Updating an existing app also requires a matching package name and signing key. Don’t uninstall the old version until you’ve backed up your subscription and custom rules.
After opening the app for the first time, add a valid subscription URL in the subscription settings and update it. Select a node, tap Connect, and approve Android’s VPN request. The VPN icon in the status bar only shows that traffic routing is active; it doesn’t guarantee a successful remote connection. Test an actual webpage and check the logs if anything goes wrong.
Some systems restrict background activity. Check battery optimization and background permissions only if the connection keeps dropping or stops working when the screen is locked. Work profiles, cloned apps, and per-app proxy settings can also affect which traffic is routed. Start with the default scope while troubleshooting, and avoid changing several variables at once.
7.24.1
A graphical desktop client for Linux. Debian- and Ubuntu-based distributions generally use deb; Fedora- and RHEL-based distributions generally use rpm. Check package dependencies and distribution compatibility too.
| Check | How to choose | What to do |
|---|---|---|
| Package format | deb or rpm | Choose based on your distribution. Don’t ignore dependency conflicts reported by the installer. |
| Processor | x64 or arm64 | amd64 and x86_64 correspond to x64; aarch64 usually corresponds to arm64. |
| Desktop session | A supported graphical desktop and required runtime dependencies | If the tray icon isn’t visible, first check whether your desktop environment supports it. |
| Network permissions | Requirements vary between standard proxy and TUN | Test the system proxy first. Configure the permissions required for TUN using the documentation. |
Open the package with your distribution’s software installer and check its dependencies and target architecture first. Also consider the build tag in an rpm filename when checking compatibility; not every rpm-based distribution can install the same build. If dependencies can’t be met, keep the error message and check it against your distribution and the client’s runtime requirements.
System proxy behavior varies across desktop environments such as GNOME and KDE. Some apps only read their own proxy settings or environment variables. After enabling “Set system proxy,” test your browser and the target app separately. If the browser works but another app doesn’t, check whether that app reads system proxy settings before reinstalling the client.
Before enabling TUN, confirm permissions for the virtual network interface, routing, and DNS settings. Avoid running multiple traffic-routing tools at once. Keep a backup of your subscriptions and rules before updates. Clear system proxy settings you no longer need before quitting the client to prevent your network from pointing to a local port at your next login.
Choosing the right installer is only the first step; a working connection also depends on your configuration, node, and traffic-routing mode.
Get a valid subscription URL, add it to a subscription group, and update it. The URL may contain personal access credentials, so don’t post the full link publicly while troubleshooting. If the update fails, check that the URL is complete and your current network can reach the subscription service before trying another update method.
On desktop, start with the system proxy. On Android, grant VPN permission when prompted. TUN can route more traffic, but still depends on correct routing and DNS settings. Neither the system proxy nor TUN is a node; switching modes won’t fix an invalid remote configuration.
Select a node, start the connection, test the target website, and then check the logs for specific errors. Change one setting at a time and note the results. Successfully importing a subscription only confirms that the configuration was read; it doesn’t replace a connection test.
First distinguish installation problems from connection problems, then follow the relevant steps.
You’ll also need a valid subscription URL or node configuration. The client reads the configuration, starts the core, and routes traffic; the installer does not include working nodes. After importing and updating your subscription, select a node and configure the system proxy or enable the appropriate traffic-routing mode.
For a first install, try Desktop, which uses a modern cross-platform interface. If you prefer the traditional Windows layout, choose the stable classic WPF edition. Both are v2rayN, but their menus and interfaces differ. The interface alone won’t make the same node connect twice as fast.
Most mainstream phones released after 2015 can start with arm64, but check which app architectures your device supports. If the architecture is incompatible or you’re unsure which device variant you have, choose Universal. It includes multiple architectures and is usually a larger download; it doesn’t add proxy features.
The version label and download path are separate fields in the release manifest and may be updated at different times. The download button uses the package path listed there; it doesn’t generate a filename from the version label. If they differ, check the app details shown by the installer before installing, and the client’s About page afterward.
Back up your subscription groups, routing rules, and custom settings before updating using the instructions for your platform. Android generally requires the package name and signing key to match for an in-place update. Don’t assume you can install over an existing app when switching clients or distribution packages. If there’s a conflict, keep your old configuration and don’t clear app data just to proceed.
First, make sure the subscription updated successfully, a working node is selected, and your system clock is correct. Then check the client logs. On desktop, verify that the system proxy was configured; on Android, check VPN permission and conflicts with other VPN apps. Let only one client route traffic. Test a basic connection before adding complex routing rules or TUN settings.