v2rayN
The Desktop edition features a modern cross-platform interface and is a good choice for first-time installs. WPF is the classic Windows edition for users who prefer its familiar interface and workflow. Install either edition, not both.
Choose an installer
Choose your operating system, then check the processor architecture. Use v2rayN on desktop. For Android, v2rayNG is the recommended choice; choose v2flyNG if you need the V2Fly core.
The Desktop edition features a modern cross-platform interface and is a good choice for first-time installs. WPF is the classic Windows edition for users who prefer its familiar interface and workflow. Install either edition, not both.
| Check | Requirements and how to check |
|---|---|
| Operating system | Use a supported version of Windows 11. For older systems, first check that the build and its runtime requirements are supported. |
| Architecture | These are x64 packages. Go to Settings → System → About to check your system type and processor. |
| Installation | Extract the ZIP file, then run the installer inside. If a runtime is reported missing, check that its version and architecture match the requirements. |
System bitness and processor architecture are different things. A system marked “64-bit” does not necessarily have an x64 processor. If your device uses ARM, first confirm that your version of Windows can emulate this x64 build. Neither download here is a native ARM package.
Exit the old edition before installing. Close its window, then check the notification area by the taskbar. If its icon is still there, exit from the tray menu. Running both apps at once can cause port conflicts or have each app change the same system proxy settings. On first launch, check that the interface works before importing settings; don't enable both the system proxy and TUN while troubleshooting.
If the installer fails as soon as you launch it, keep the exact error message and identify which stage failed: the installer won't run, the client window won't open, or the client opens but can't connect. For the first two, check your system, runtime requirements, and installation-folder permissions. If the interface works but the connection fails, troubleshoot the profile and network instead of switching interface editions.
Open About This Mac from the Apple menu. Choose Apple Silicon if it shows an Apple M-series chip, or Intel if it shows an Intel processor. Don't guess based on the device's appearance or purchase date.
| Check | Requirements and how to check |
|---|---|
| Operating system | Use a supported version of macOS. For older versions, check the minimum macOS version required by the selected build. |
| Chip | Apple Silicon uses arm64; Intel uses x64. |
| Installation | Open the DMG, then follow its instructions to move the app to Applications before launching it. |
Eject the disk image only after copying the app. Don't use the mounted image as the app's regular launch location. If the old version still opens after installing the new one, launch the new copy directly from Applications in Finder and check whether the old Dock icon points to a different copy.
If macOS reports that your version isn't compatible, check your macOS version first. If it says the app can't run, check that the chip architecture matches the downloaded file. Read security alerts carefully and distinguish an unidentified developer, a damaged app, and an incompatible system version. Don't assume every alert is a network issue or disable system protections globally.
Powered by the Xray core. Most mainstream phones released since 2015 can use arm64. Confirm your device supports arm64-v8a before choosing it. If you're unsure of the architecture, start with the universal package.
Powered by the V2Fly core. Switch to this client only if its build supports the protocols and transport methods required by your existing profile. The universal package supports more architectures; it doesn't add features.
| Check | Requirements and how to check |
|---|---|
| Operating system | Check your Android version under About phone. Your device must meet the selected build's minimum OS requirements and allow its installation. |
| Architecture | Check the app ABI supported by your device. A 64-bit processor alone doesn't guarantee that an arm64 package will install. |
| Installation | Your browser or file manager must be allowed to install apps. On a managed device, your administrator's policies apply. |
Permission to install and permission to connect are separate. Android may first ask you to allow app installs from the current download source; you can revoke that permission afterward. When the proxy service starts for the first time, Android may also ask you to approve a VPN connection. Successful installation means the app can run; it doesn't mean a connection is authorized or a profile has been imported.
When upgrading from another build, if Android says “App not installed,” note the exact message and don't immediately delete the existing app. Android may block installation because of an architecture mismatch, a different app signature, a lower version than the one already installed, or device policies. Find the cause before choosing another package or migrating after a backup. Uninstalling usually deletes the app's local data.
v2rayn_7.24.1_arm64.deb
v2rayN-7.24.1-1.el10.aarch64.rpm
Debian- and Ubuntu-based systems generally use DEB packages. For RPM-based systems, check your distribution and dependencies first. The RPM filename here includes el10; supporting RPM packages alone doesn't guarantee compatibility.
| Check | Requirements and how to check |
|---|---|
| Environment | A graphical desktop session is required, along with the dependencies for the selected build. |
| Architecture | uname -m returns x86_64 for x64 and aarch64 for arm64. In a multi-architecture environment, use the package manager's target architecture. |
| Package format | Choose DEB or RPM for your distribution and let the system's package manager handle dependencies. |
Match the architecture and package format separately. DEB uses amd64 for x64; it isn't limited to AMD processors. RPM typically uses x86_64. Likewise, DEB arm64 and RPM aarch64 both refer to 64-bit ARM, but the package formats aren't interchangeable.
If your package manager reports unsatisfied dependencies, note the first missing dependency or version conflict, then check your distribution version and repository status. Don't force past dependency checks or install packages from another distribution. If installation succeeds but the app won't open from the application menu, check that you're in a graphical session and distinguish an app launch problem from a proxy configuration issue.
After choosing a platform, check the filename below the button to confirm the format and architecture. If your browser still shows the download in progress, wait until it finishes before opening the file. If the saved file is a web page rather than an installer, try the download again and note whether the browser reports a network error, restricted access, or a broken link. Changing the file extension won't turn a web page into an installer.
If the manifest version on the card doesn't match the filename, distinguish the app-level version from the specific download entry. Use that entry's filename to identify the package, then compare it with your installed version before upgrading. A more recent download time doesn't mean the file is a newer version, and a package filename alone doesn't prove the running app was successfully replaced.
Before switching versions, note your current client, subscription groups, selected default node, and custom routes. Saving a subscription URL alone isn't a full backup: manually added nodes, local listening ports, and routing rules may need to be exported separately. Subscription URLs may contain access credentials, so keep backups on a trusted device and don't post them in public support tickets or group chats.
After installing, first check that the app launches, then confirm whether it has loaded your existing settings. If you need to restore them manually, import only what's needed and check the list before replacing the entire new directory. Keep the old version or backup until the new one launches, loads your settings, and passes a connection test; then decide whether to remove it.
An empty list is normal for a fresh client install. Import an existing subscription into the appropriate group and update it, or add a known server profile. Once nodes appear, select one and check the client logs for startup errors. A failed subscription update happens while fetching profiles; it's different from an imported node failing to connect, so troubleshoot them separately.
On desktop, distinguish a running client from an app actually using the proxy. Test with a site you know is reachable, then check whether the target app follows the system proxy settings. Before enabling TUN or changing routes, keep a verified working baseline and change one setting at a time. See the subscription import and connection guide. If the logs point to a port conflict, see how to troubleshoot local listening port conflicts.
The version on the card comes from the app manifest, while the filename identifies a specific download. They may not be in sync. Check the filename for your chosen download before installing. To confirm the installed version, check the client's About page or your system's app info.
No. For a fresh install, start with the Desktop edition, which uses a cross-platform interface. Choose WPF if you prefer the classic interface or want to keep your existing workflow. Before switching, back up your settings and fully exit the old edition to prevent both apps from controlling the system proxy or competing for the same local listening port.
A universal package may help only if the issue is an architecture mismatch. Also check your Android version, available storage, and whether an app with a different signature or newer version is already installed. If Android reports a signature conflict, back up your settings before deciding whether to uninstall the existing app.
Exit the client before upgrading. Export your settings using the client's built-in feature, or back up its data directory as directed for your current version. Note your subscription groups, custom routes, local ports, and proxy mode. Once the new version has loaded your settings, you can remove the old directory or app.
The installer provides only the client. First import an existing subscription or server profile. If you're using a subscription, update it and check that nodes appear in the list. Once the profile has loaded, select a node, enable the required proxy mode, and test the connection.