Use v2rayN on desktop and v2rayNG on Android. Check your operating system and processor architecture before choosing a download; configure protocols and subscriptions after installation.
Downloads are organized by platform. The clients don’t provide servers or subscriptions. If you already have a subscription, follow the subscription setup guide after installation.
Choose either Desktop or classic WPF; you don’t need to install both.
Desktop uses a newer cross-platform UI and suits first-time users or anyone who wants a consistent desktop experience. The WPF edition retains the classic Windows interface and is a stable choice if you’re used to the original layout.
Both downloads are ZIP archives. Extract the files before installing, and don’t launch the program from the archive preview window.
The two editions mainly differ in layout and desktop technology; that doesn’t indicate how well either will connect to a given server. On first launch, import a subscription, select a server, and then configure the system proxy. Consider TUN only if you need to route apps that ignore system proxy settings. An open settings window doesn’t mean the proxy is working.
Before migrating from an older edition, export your settings and note any custom routes and local ports, then exit the old client. Running both clients can cause port conflicts or let them overwrite each other’s system proxy settings. Menus may be in different places in the new interface. After importing, verify subscription groups, core selection, and routing presets instead of copying the entire old program directory.
See the v2rayN subscription import steps →Check Chip or Processor under About This Mac; don’t guess based on the computer’s appearance.
Choose arm64 for Apple Silicon and x64 for Intel. Prefer the build native to your chip; there’s no need to choose a different architecture just to match a filename.
The download is a DMG. Open the disk image, follow the installation prompts to place the app, then launch it from Applications.
The v2rayN desktop client stores subscriptions, lets you select servers, and manages routes. The system proxy only affects apps that honor system proxy settings; it doesn’t route every app through the client. First test the selected configuration in a browser, then consider TUN if your apps need it. Don’t add a virtual network interface and DNS variables before confirming the basic connection works.
When migrating settings from another computer, you can reimport subscription addresses within their permitted scope, but check custom file paths, local listening ports, and system-specific settings again. If the interface looks normal but connections fail, start with the specific error in the logs. A processor architecture mismatch usually prevents installation or startup; it shouldn’t be blamed for every network problem.
See the desktop setup guide →For everyday use, choose an Xray-core client. Consider the alternative only if you need compatibility with V2Fly configurations.
Powered by the Xray core, v2rayNG suits everyday subscription management on Android and configurations that need its supported protocol features. Most phones released since 2015 should use arm64. If you’re unsure of your device’s architecture, consider universal and check which app architectures the system supports.
The installer is an APK. When you connect for the first time, Android will ask for VPN permission. Review the prompt before approving it.
Powered by the V2Fly core, v2flyNG suits users with existing configurations who want to keep their current compatibility path. It isn’t simply v2rayNG with a different name. For features such as REALITY, check that the core supports them; being able to import a subscription doesn’t guarantee it will connect.
Universal packages support multiple app architectures but are usually larger. Package architecture and server protocol are separate considerations.
| Check | How to choose | Notes |
|---|---|---|
| App architecture | Prefer arm64; consider universal if unsure | A 64-bit processor doesn’t necessarily mean the system can install 64-bit apps. |
| Windows version | Follow the minimum version shown by the APK installer. | Older systems may not run the current build. |
| Installation permission | Allow app installs from the download source when needed. | Revoke installation permission when it’s no longer needed. |
| Connection permission | Allow the client to establish a VPN connection. | May conflict with other apps using a VPN connection. |
After installation, add a subscription group, update it, and select a server. Android’s VPN permission lets the client route local traffic; it doesn’t make a subscription valid or replace server configuration. If the connection drops soon after you start it, check the app logs and VPN status, then review background restrictions, battery optimization, and whether another VPN app is using the connection.
Adjust background permissions only if you’ve confirmed symptoms such as disconnections when the screen turns off or the system closing the app. Don’t grant every permission at once or run two clients simultaneously to compare connections. Before switching between v2rayNG and v2flyNG, disconnect and check that the target core supports the subscription’s transport and security settings.
See the v2rayNG subscription import steps →deb and rpm belong to different package ecosystems; they are not different proxy protocols.
Choose x64 for most Intel and AMD desktop computers. Use deb on Debian, Ubuntu, and other distributions with the deb package system; use rpm on distributions with the RPM package system, and check that your distribution meets the package dependencies. For ARM desktops, use the arm64 downloads below.
The right package format doesn’t guarantee compatibility with every distribution. If dependencies are missing, review the package manager’s message instead of forcing the installation.
Desktop environments may handle system proxy settings differently. After installation, make sure the client has a valid configuration selected and is listening, then check whether the target app honors desktop proxy settings. Some apps need their own proxy configuration; a working browser doesn’t mean other apps are proxied too. TUN involves a virtual network interface, permissions, and routing, so enable it only after confirming the basic connection works.
When upgrading, use the same package manager as for the original installation. Avoid switching between manually copying files and package-manager installs. Keep backups of custom routes and subscriptions, then check local ports and the runtime user after upgrading. If dependencies conflict, record the full error and check your distribution version. Don’t bypass checks by changing package extensions or mixing dependencies from another distribution.
See the core and configuration compatibility guide →CONFIGURATION / What to configure after installation
Downloading the right installer only determines whether the app can run on your device. Establishing a connection also depends on subscription fields, core features, server settings, and local proxy mode. Troubleshoot these separately to avoid reinstalling the client unnecessarily.
In the Project V ecosystem, graphical clients mainly manage configurations, subscriptions, and system integration; the core handles protocol processing. V2Fly and Xray share technical roots, but their feature development has diverged. When choosing v2rayNG or v2flyNG, consider the features your configuration needs, not just how similar the interfaces look.
REALITY is a security layer, not a standalone outbound protocol. A VLESS subscription alone doesn’t guarantee everything needed to connect; the transport, security layer, and authentication parameters must all match. For the differences between VMess and VLESS, see the protocol reference.
For your first test, use one client, one known-good configuration, and one proxy mode. Check that the system clock is correct, the subscription updated successfully, and the configuration is selected before testing access. Don’t change the protocol, DNS, routes, and TUN all at once, or you won’t know which change fixed the connection.
publicKey and shortId against the server configuration. Changing the installer won’t fill in these parameters.
The client is free to use, but connection resources must be configured separately. Follow these steps for a first-time setup or when setting up on a new device.
Identify whether the issue is package selection, app startup, or connection setup before deciding what to check next.
If you’re new to v2rayN, start with Desktop, which uses a newer cross-platform interface. If you prefer the familiar layout, choose the established WPF edition. Both are v2rayN clients, but subscription compatibility also depends on the core and configuration fields. Back up your settings before switching editions, and don’t let both clients modify the system proxy at the same time.
Most phones released since 2015 should use arm64, but check which app architectures your device actually supports. Choose universal for older devices, systems limited to older app architectures, or when you’re unsure. Universal packages include components for multiple architectures and are usually larger; they don’t improve connectivity.
No. The client stores configurations, starts connections, and manages routing; the installer does not include a usable subscription or server account. Import a subscription link you’re authorized to use, or add server details manually, then update the subscription and select a configuration. Subscription links may contain access credentials, so don’t share them publicly.
Save your subscription groups, custom routes, DNS settings, and any manually configured servers, then exit the old client. Use the client’s export or backup feature where available, and verify the migrated settings. Backups may contain access credentials, so store them somewhere secure. Don’t overwrite the new program’s entire directory with the old one.
Check that your system and installer architectures match, then review the missing dependencies named in the system message. Windows packages distinguish x64 from other architectures; macOS packages distinguish Apple Silicon from Intel; Linux packages also come as deb or rpm. Runtime requirements vary by build, so follow the current installer’s guidance. Avoid repeatedly installing repair tools from unknown sources.
Don’t switch packages as your first step. If the client starts normally, check that your subscription is valid, the intended server configuration is selected, the system clock is correct, and system proxy or VPN permissions are working. For REALITY, verify publicKey and shortId against the server configuration. Use the logs to isolate the issue instead of changing the client, protocol, and DNS all at once.