Client downloads and architecture
Choose your operating system, then your processor architecture. Use v2rayN on desktop; v2rayNG is the recommended choice for Android, while v2flyNG is an option when you need the V2Fly core.
All three clients are free and open source. The installer prepares the client; subscriptions and server settings must be imported separately.
New to setup? Follow the subscription import and connection guide →Choose by platform
Not sure which architecture you need? Check your system’s About page or device information, then download the matching file.
7.24.1
Desktop · x64
A next-generation cross-platform UI, ideal for first-time installs and users who want a consistent experience across desktop operating systems.
Classic WPF · x64
The classic, stable edition with a familiar Windows interface. Choose this option if you’re used to the WPF version.
Both downloads are ZIP archives. Extract the entire archive before running the installer; don’t launch it from the archive preview.
| Check | What to choose and prepare |
|---|---|
| System and architecture | This page provides Windows x64 packages. Check your system type under Settings → System → About; don’t treat an x64 package as a native package for another architecture. |
| Runtime environment | Check the installer for the exact Windows version and runtime requirements. If a runtime is missing, note its name and architecture before troubleshooting. |
| Folder and permissions | Extract to a folder your account can write to, and leave enough space for installation and settings. You don’t need to enable TUN just to test the regular system proxy. |
Desktop and WPF mainly differ in their interface technology and layout; they don’t turn your subscription into two different sets of servers. For a first install, start with one edition. After importing a subscription and testing browser access, decide whether to switch. Before comparing editions, exit the running client to avoid local port conflicts and mistaking another instance’s tray status for the current settings.
If you already have settings, back up your subscription groups, routing rules, and DNS settings before upgrading or switching editions. After installation, check the launch path and the location from which the client actually loads its settings; don’t just copy one program file over the old folder. If startup fails, keep the exact error message and check for missing runtimes, folder permissions, or a port conflict based on the reported cause.
7.24.1
Apple Silicon · arm64
Choose this package if About This Mac lists an Apple chip. It’s the arm64 build for Apple silicon.
Intel · x64
Choose this package if About This Mac lists an Intel processor. Don’t guess the architecture based on the device’s appearance or purchase year.
Open the DMG and follow the installer window to place the app. Once installed, launch it from the Applications folder rather than running it from the disk image.
| Check | What to choose and prepare |
|---|---|
| Chip type | Open About This Mac from the Apple menu and choose the Apple silicon or Intel package based on the chip or processor listed. |
| macOS version | Check the current release package for its macOS version requirements. The right architecture doesn’t guarantee your macOS version is supported. |
| Network permissions | When setting up a proxy or enabling a virtual network interface for the first time, read the system’s permission prompt and grant only what the current task requires. |
Check your chip type before opening the matching disk image. After installation, eject the disk image and relaunch the client from Applications to confirm settings are saved correctly. If macOS says the app can’t be opened, read the specific reason and distinguish between an unidentified developer, an unsupported macOS version, and an architecture mismatch. Don’t disable system-wide security protections.
For your first connection, start with the system proxy. Test a browser that follows the system proxy, then try other apps. Command-line tools may not use the system proxy, so a failed terminal request doesn’t mean the client is installed incorrectly. To cover more apps, read the TUN mode guide, then enable settings one at a time after checking permissions, DNS, and routing.
2.2.6
arm64
Most mainstream phones released after 2015 use arm64. Check that your device’s system supports apps built for this architecture.
Universal
An alternative if you’re unsure which app architecture your device supports. It includes components for multiple architectures, but may not support every Android version.
For importing subscriptions, choosing servers, and configuring routing on Android. The system will ask you to authorize the VPN connection when you connect.
1.10.31
arm64
Choose this if you need V2Fly core behavior and your device supports arm64. If you already have a configuration, check protocol and transport compatibility first.
Universal
Choose this if you’re unsure of the app architecture. It uses a different core from v2rayNG, so a similar interface doesn’t guarantee the same configuration support.
Use v2flyNG as an alternative when you specifically need its core. If you’re new to this, start with the v2rayNG setup process.
| Check | What to choose and prepare |
|---|---|
| App architecture | Check which app architectures your device supports. A 64-bit processor doesn’t necessarily mean the current system provides a full 64-bit app environment. |
| System compatibility | Follow the system requirements reported by the APK installer. A Universal package covers more architectures; it doesn’t reduce the app’s system requirements. |
| Install and connection permissions | Grant install permission only to the browser or file manager you use to open the APK. Confirm the system VPN permission when connecting for the first time. |
| Background operation | If the connection drops when the screen locks, check battery optimization and background restrictions. Also check whether another VPN app is using the connection. |
Open the APK from your downloads or file manager to install it. If installation fails, read the error: an architecture mismatch, outdated Android version, insufficient storage, and a signature conflict are different issues. Don’t uninstall the old client without a backup. If you have subscriptions or custom rules, export them before deciding whether to reinstall.
v2rayNG and v2flyNG are both graphical clients, but their cores may support different configuration options. Successfully importing a subscription only means the client recognized its format; it doesn’t guarantee that every connection parameter will work. If your provider specifies a client or core, check that requirement first. Before switching clients, record your transport, security, and routing settings so configuration differences aren’t mistaken for network problems.
When you turn on the connection, the system usually routes traffic covered by your configuration through a VPN interface. This interface handles traffic locally; routing rules determine whether it goes through a proxy outbound. For initial troubleshooting, enable only one proxy client, test a regular webpage, then check apps that need special routing. Don’t change app routing, DNS, and background settings at the same time, or it will be hard to identify what changed the result.
7.24.1
deb · x64
For x64 desktop systems that use DEB packages. Let your software installer handle dependencies.
For ARM64 devices: download the DEB package →rpm · x64
For x64 desktop systems that use RPM packages. Check that your distribution and dependency versions are compatible.
For ARM64 devices: download the RPM package →Choose the package format first, then the processor architecture. DEB and RPM aren’t different interface editions; simply changing a file extension or forcing a conversion isn’t recommended.
| Check | What to choose and prepare |
|---|---|
| Desktop environment | This page provides a graphical client and requires a working desktop session. This installation guide isn’t for terminal-only environments. |
| Package system | Choose DEB or RPM based on your distribution’s package manager. Matching the file extension is only the first step; required system libraries must also be available. |
| Architecture names | amd64 and x86_64 usually mean x64; arm64 and aarch64 mean 64-bit ARM. Check your system’s actual architecture before downloading. |
| Permissions and network mode | Installing a package and enabling a virtual network interface may require different permissions. Start the interface as a regular user, then follow prompts for any additional permissions the feature needs. |
Check your distribution and processor details in system settings, choose the matching package, then open it with your system’s software installer. If the package manager reports unsatisfied dependencies, check which libraries and versions are missing; don’t force-install while bypassing dependency checks. Matching file extensions don’t guarantee compatibility across distributions, and a matching architecture doesn’t replace checking system library versions.
After launch, import a subscription and test the connection in an app that supports proxy settings. Linux desktop environments may handle the system proxy differently, and some command-line tools need separate proxy environment settings. TUN involves routing, interface permissions, and DNS, so enable it only after the basic connection works. When testing is done, confirm the system routes have been restored so leftover settings don’t affect later troubleshooting.
After downloading
Start with the minimum working configuration, then add routing, DNS, and TUN settings one at a time.
After installing, get a valid subscription URL or share link. Subscription URLs often contain access credentials, so store them securely and don’t include the full link in public screenshots, forums, or troubleshooting logs. Add a subscription group and refresh it; once the server list appears, choose a server and test the connection.
If the list is empty, check whether the subscription has expired, the group is enabled, and what the update log says. Reinstalling the client repeatedly usually won’t fix an expired subscription URL. When importing a share link manually, make sure you copied it in full without spaces, extra text, or missing parameters.
View the subscription import guide →On desktop, start by testing a browser with the system proxy; on Android, first authorize the VPN interface. Once a webpage loads, check that routing works as expected. The system proxy affects only apps that follow that setting, so one app’s results don’t tell you how every app is connected.
Routing rules, DNS, and TUN affect different parts of the connection. Record the current settings before making changes, adjust one thing at a time, and repeat the same test. If something breaks, undo the last change and check the outbound and DNS results in the logs. This makes the cause easier to pinpoint than switching several features at once.
Read the routing rules guide →Installers and updates
For your first install, consider Desktop, which uses a next-generation cross-platform interface. Choose the classic WPF edition if you prefer its familiar interface or need to keep using its established workflow. Both are v2rayN clients. Back up existing settings before installing, and run only one instance while testing.
Most mainstream phones released after 2015 are best served by arm64, but check which app architectures your device supports. If you’re unsure or the arm64 package reports an incompatibility, try Universal. Universal does not support every Android version or resolve signature conflicts.
For Android, v2rayNG with the Xray core is the usual choice. Choose v2flyNG if you need V2Fly core behavior or already have a compatible configuration. Check the provider’s protocol, transport, and security requirements before choosing a client; a subscription link’s appearance alone does not indicate compatibility.
First, make sure the operating system, processor architecture, and package format match, then check the specific error message. Fully extract Windows archives before running the installer; on Android, check install-source permissions and signature conflicts; on Linux, check package dependencies; on macOS, check the chip type and system security warning. Don’t disable system-wide security protections.
Installing the client is only the first step. You’ll also need a valid subscription URL, share link, or configuration. Import the subscription and refresh the server list, choose a server, enable the system proxy or VPN interface if needed, then check that the target app is using the expected outbound route.
Use the client’s backup or export feature to save subscription groups, routing rules, DNS settings, and custom outbounds, and note your current network mode. Backups may contain subscription URLs and access credentials, so store them securely. After upgrading, confirm the settings load before testing connections and routing one step at a time.