Client downloads · Four platforms
Choose v2rayN for desktop systems and v2rayNG for Android.
Check your operating system and processor architecture before downloading.
Platforms and downloads
Each button starts the corresponding file download.
If you already have a configuration, back it up before upgrading.
Windows x64 packages. Desktop uses a newer cross-platform UI; WPF keeps the classic desktop interface for users who prefer the familiar workflow.
A good choice for a first installation
Download Desktop · x64 ZIP package · Newer cross-platform interfaceChoose this if you prefer the classic layout
Download WPF · x64 ZIP package · Classic, stable edition| What to check | How to choose and what to prepare |
|---|---|
| Processor architecture | Both downloads on this page are x64. Check your system type under Settings → System → About. Don’t use these packages for other architectures. |
| Windows version and runtime | Use a supported version of Windows. Check the release notes for compatibility details. If you’re told a runtime is missing, note the component name and architecture before installing it. |
| Installation permissions | You generally don’t need to run the client as an administrator just to use the system proxy. Enabling TUN creates a virtual network interface and may require additional permissions. |
| Install location | Extract the entire ZIP before running the installer. Keep the data location writable, and don’t launch the program from the ZIP preview window. |
Check your system type, then download either Desktop or WPF. Extract the ZIP to its own folder, close any running client, and follow the installer prompts. Don’t run the old and new instances at the same time: if both listen on the same ports, the core may fail to start or your browser may not connect.
After the first launch, check the local mixed-proxy listening port, then import an existing subscription or server configuration. Select a server and test the connection before enabling automatic system proxy configuration. Start by testing with a browser; you don’t need to enable TUN right away. When switching interface editions, keep your subscription, routing rules and ports unchanged. Change one thing at a time to make it easier to identify the cause of any issue.
If Windows blocks the installation, check the app name, file source and reason shown before taking action. Don’t disable system protection altogether. If a runtime component is missing, install the required component for the correct architecture. Switching interface editions usually won’t fix a missing runtime. See the Windows installation and setup guide for detailed steps.
Open About This Mac. Choose Apple Silicon if it shows an Apple chip, or the Intel package if it shows an Intel processor.
For Macs with Apple chips
Download Apple Silicon · arm64 DMG package · Native architecture| What to check | How to choose and what to prepare |
|---|---|
| Chip type | Check the chip or processor in About This Mac under the Apple menu. Don’t guess based on the device’s appearance or purchase year. |
| macOS version | Use a supported version of macOS. Check the selected release notes and installer prompts for the minimum requirements. |
| Installing the app | Open the DMG and follow its prompts to move the app to Applications. Launch it from there. |
| Network permissions | When setting up the system proxy or enabling TUN, follow any permission prompts required for the feature. Check which app and action the prompt refers to before granting access. |
The two DMG packages differ mainly in processor architecture, not features. Choose the one that matches your chip to avoid introducing an extra compatibility layer. After installation, eject the disk image and open the client from Applications. This makes it easier to find the app you’re actually using and confirm which copy to replace during an upgrade.
Read the details of any macOS security warning first. If macOS lets you approve the app in Privacy & Security settings, verify the source and follow the on-screen steps. Don’t disable system-wide security as a routine installation step. If macOS says the app is incompatible, check the chip type and system version instead of repeatedly granting permission.
After importing a configuration, test your browser connection using the system proxy. Some apps don’t use the system proxy, so a working browser connection doesn’t mean all apps are covered. Set up TUN using the system guide only if you need to route more traffic. Before upgrading, quit the old process and back up your configuration; afterward, check that the proxy is working as expected.
An Android client based on the Xray core. Most mainstream phones released after 2015 can start with arm64; choose the universal build if you’re unsure of the architecture.
For devices with an unknown architecture
Download v2rayNG · Universal APK · Includes multiple architecturesAn alternative client based on the V2Fly core. Consider it when an existing configuration depends on V2Fly compatibility; switching clients shouldn’t be your first step when troubleshooting a connection.
Choose this if you’re unsure of the app architecture
Download v2flyNG · Universal APK · Includes multiple architectures| What to check | How to choose and what to prepare |
|---|---|
| App architecture | Most mainstream phones use arm64, but a 64-bit processor doesn’t guarantee that the system supports 64-bit apps. Check your device’s actual configuration. |
| Android compatibility | Check the client’s release notes for minimum Android requirements. If the package won’t install, check both system compatibility and whether the download completed. |
| Installation permission | Follow Android’s prompts to allow the browser or file manager you’re using to install this package. You can revoke the permission afterward. |
| Connections and background activity | VPN mode requires system permission. Background activity settings can affect persistent connections; adjust battery management for your device if needed. |
When the download finishes, open the APK from your browser’s downloads list or a file manager. If Android reports a conflict with an existing app, check which client is installed and whether it came from a distribution channel with a different signing key. Don’t immediately uninstall it and clear its data. Back up your configuration before deciding whether to migrate. The universal build addresses architecture compatibility; it won’t fix a signing conflict or an outdated Android version.
The first time you connect, Android will ask for VPN permission so the client can handle your device’s traffic. Before approving, import a valid configuration and check the server settings. A device can usually have only one active VPN connection. If another network tool is already handling traffic, disconnect it before testing to avoid two apps replacing each other’s network service and making a working server look faulty.
After connecting, keep the app in the foreground to test it, then lock your screen and check whether it stays connected. If it disconnects only when the screen is locked, check battery optimization and background activity restrictions before downloading a different package. Subscription URLs may contain access credentials; don’t post links, QR codes or configuration screenshots in public forums.
Choose deb or rpm based on your distribution, then check your processor architecture. The main downloads below are x64; use the matching additional package for arm64 devices.
For distributions that use deb packages
Download deb · x64 arm64 devices: Download deb →For distributions that use rpm packages
Download rpm · x64 arm64 devices: Download rpm →| What to check | How to choose and what to prepare |
|---|---|
| Package format | Distributions such as Debian and Ubuntu generally use deb packages. Choose rpm for rpm-based distributions, and check that the package’s specific dependencies are met. |
| Processor architecture | x86_64 usually means x64, and aarch64 usually means arm64. Check your system information rather than relying on the distribution name. |
| Desktop and dependencies | v2rayN is a graphical client and requires a compatible desktop environment. If dependencies are missing, review the message in your distribution’s package manager and resolve the listed issues. |
| Permissions and networking | Installing a package usually requires administrator privileges. Whether apps use the system proxy depends on your desktop environment and the apps themselves; TUN requires additional network permissions. |
Open the package in your distribution’s graphical software installer and review its dependencies and compatibility warnings before installing. Don’t force the installation by ignoring dependency errors. If the graphical app won’t start, possible causes include missing desktop components, system library versions or an architecture mismatch. If the system says the package isn’t supported, recheck the package format and distribution version.
After installation, launch the client from the app menu, import a configuration and test the server connection. Desktop environments handle system proxies differently, and some apps use their own proxy settings. Test with an app that explicitly supports proxies before trying other apps. This helps distinguish an app that ignores the proxy from a client connection failure.
Before enabling TUN, note your existing DNS settings, other VPN services and network manager configuration. If name resolution fails after changing how traffic is routed, restore the last working setup before making further changes. For routine upgrades, use the same package manager as before to avoid duplicate installation directories and launch entries. Keep a configuration backup and confirm that you’re starting the updated program.
After downloading
Installing the client is only the first step. Get a valid subscription or server configuration from a trusted source, import it, select a server and test the connection. Then choose how to route traffic: desktop users can start with the system proxy, while Android users should grant VPN permission when prompted. Begin with the default routing rules or rules you understand, and avoid running multiple network tools at once.
After the test succeeds, use a browser to visit a service you need, then check whether the target app uses the proxy. A successful latency test confirms only that a specific check passed; it doesn’t prove that every domain, app and transport is working. If one app has an issue, check its own proxy settings first. See the user guide for the full walkthrough.
Back up your subscription groups, custom servers, routing rules and port settings before upgrading, and make sure you can read the backup. You can re-import subscriptions, but manually added entries and custom rules may not be restored automatically. Quit the old client before updating. Afterward, check that your settings are intact, then test subscription updates, core startup and traffic routing separately.
If the new version has a problem, don’t delete the entire data directory right away. Record the error, system environment and steps that triggered it, then determine whether the issue is with installation or configuration compatibility. Before rolling back, check that the older version can read the configuration format. For step-by-step troubleshooting, start with Troubleshooting.
Download questions
First identify whether the issue is with downloading, installing or connecting, then follow the steps for what you’re seeing.
For a first installation, consider Desktop, which uses a newer cross-platform interface. If you prefer the classic layout or want to keep your existing workflow, choose the stable WPF edition. Both require an imported configuration to connect. Back up subscription groups and custom settings before switching, and avoid running both editions at once if they use the same local ports.
Most mainstream phones released after 2015 can start with arm64, but check which app architectures your device actually supports. If you’re unsure whether the system is 64-bit, or the arm64 APK reports an incompatibility, try the universal build. If that also fails to install, check the Android version, available storage and signing of any existing app rather than repeatedly downloading the same package.
The version shown on the card and the download file path come from separate manifest fields, so they may not update at the same time. Don’t change the version number in the link yourself. After downloading, check the package details and the client’s About screen. If an upgrade warns that it would downgrade the version, cancel and verify the target and installed versions first.
You’ll also need a valid server configuration or subscription. The client imports configurations, runs a local proxy and applies routing rules; the installer does not include a server. After importing a configuration, select a server and test the connection. Then enable the system proxy or grant VPN permission, and check that your browser or target app handles traffic as expected.
Back up settings such as subscription groups, custom servers, routing rules and local listening ports. Quit the running client before upgrading, using the method appropriate for your installation. Don’t delete app data before making a backup. After the upgrade, check your subscriptions, system proxy and TUN settings one by one; remove the old directory only after everything works.
Check your browser’s downloads list and any blocked-download warning to see whether the download has started, then check available storage and your network connection. Refresh the page and click the package link again, avoiding repeated clicks that create duplicate downloads. If it still fails, note the platform, package type and browser error. Determine whether the issue is downloading or installing, then follow the relevant steps in Troubleshooting.