CLIENT / PLATFORM / ARCHITECTURE
v2rayN for desktop; v2rayNG for Android.
Choose your operating system, then your CPU architecture.
All three clients are free and open source. The installers set up the client; you'll need to provide your own subscription and server settings.
Choose a platform and installer ↓This section covers the client, interface edition, and installation architecture. Protocols are configured after importing your settings; you don't need a separate client for each protocol.
Windows x64 installers. Desktop uses a modern cross-platform UI; Classic WPF retains the traditional Windows interface and is a stable choice if you prefer the older workflow.
The download is a ZIP file. Extract it completely before running the installer inside; don't launch it from the ZIP preview.
| Check | Requirements or recommendations | Where to check |
|---|---|---|
| OS and architecture | Recommended for Windows 10 or 11 on x64. Check the installer prompt for the requirements of a specific build. | Settings → System → About |
| Runtime | If prompted that a runtime is missing, install the .NET Desktop Runtime required by the build and choose the x64 version. | Installer prompt or startup error |
| Folder permissions | The installation and configuration folders must be writable. Don't run the client from a read-only location or an archive that hasn't been extracted. | File Explorer → Folder properties |
| Traffic routing | Use the system proxy with standard permissions. TUN may require administrator access and a virtual network adapter component. | Client system proxy and TUN settings |
After opening the client for the first time, import a configuration you know works before setting the system proxy. Don't keep toggling TUN to troubleshoot ordinary startup issues: runtimes, folder permissions, and proxy modes are separate checks.
A graphical desktop client for macOS. Choose arm64 for Apple Silicon or x64 for Intel. Both downloads are DMG disk images.
Open the DMG and follow the on-screen instructions to move the app to Applications. Then launch it from Applications.
| Check | Requirements or recommendations | Where to check |
|---|---|---|
| Processor | Choose arm64 for Apple Silicon and x64 for Intel. | Apple menu → About This Mac |
| OS version | Make sure your macOS version meets the selected build's requirements. If you see a warning that your OS is too old, check your version first. | About This Mac → macOS version |
| Installation location | Move the app to Applications instead of running it long-term from a mounted disk image. | Finder → Applications |
| Network permissions | Changing the system proxy or enabling TUN may require system authorization. Follow the prompts you see. | System Settings and client permission prompts |
Quit the client before switching installation architectures. Overwriting files while the old app is still running can leave the menu bar status out of sync with the actual process. After switching, check which local port the system proxy points to.
Recommended for Android; powered by the Xray core. Most mainstream phones released since 2015 can start with arm64. If you're unsure of your device's architecture, or the system won't accept the arm64 package, try the universal version.
Before choosing a configuration that uses VLESS, REALITY, or similar settings, check its subscription fields and confirm support in the current core.
For Android users who need to keep using configurations from the V2Fly ecosystem. v2flyNG is a separate client from v2rayNG; a similar name doesn't guarantee identical protocol extensions, subscription parsing, or data folders.
Keep a record of your subscription source before switching clients. Data from the old app won't transfer automatically to another client.
| Check | Requirements or recommendations | Where to check |
|---|---|---|
| Architecture and OS | arm64 requires OS support for the corresponding ABI. A 64-bit-capable processor doesn't guarantee that the OS supports it. | Device system information and installer prompts |
| Installation source | Allow the browser or file manager you're using to open the APK to install apps. You can revoke this permission afterward. | Settings → Apps → Special app access |
| System compatibility | Check the package's declared minimum Android version. If installation fails during parsing, also check the OS version and architecture. | Settings → About phone |
| Connection permission | The first time you connect, confirm Android's VPN connection request. | System VPN permission dialog |
| Background operation | Power-saving settings may interrupt long-running connections. Adjust this app's battery restrictions only if it actually stops running in the background. | Settings → Apps → Battery |
The universal version includes support for more architectures; that doesn't mean it connects faster. If installation reports a conflict with an existing app, the cause may be its signature or version. Back up your settings first, then decide whether to change the installation source. Don't uninstall the app before locating your original subscription.
A graphical desktop client for Linux. Debian, Ubuntu, and similar distributions usually use DEB; distributions with RPM package management use RPM. Check distribution dependencies and CPU architecture as well.
amd64 and x86_64 usually mean x64; aarch64 usually means arm64. Matching package formats don't guarantee matching dependencies.
| Check | Requirements or recommendations | Where to check |
|---|---|---|
| Desktop environment | Requires a graphical desktop session and the graphical runtime dependencies required by the build. | System Information and graphical software installer |
| Package format | Choose DEB or RPM for your distribution. Don't use dependency-resolution steps intended for another distribution. | Distribution documentation and software manager |
| Architecture | Choose x64 for most desktop PCs. For ARM desktops, choose arm64 if supported by your OS. | Settings → About → System architecture |
| Permissions and proxy | Installing software requires the appropriate permissions. Whether apps follow the system proxy depends on the desktop environment and each app's settings. | Software installer and system network settings |
After installation, test browser access using one proxy method at a time. Changing the system proxy, an app's manual proxy, and TUN simultaneously makes troubleshooting harder. If you need to route more traffic, first review TUN permissions and routing requirements.
Installation, configuration import, and routing traffic through the proxy are three separate steps. Complete them in order to make problems easier to pinpoint.
Install desktop versions using the appropriate package format. On Android, open the APK and approve the installation permission. On first launch, check that the main window, menus, and configuration list appear. If the client won't start, troubleshoot OS compatibility, runtimes, or folder permissions first; there's no need to change server settings yet.
In v2rayN, add a subscription URL in Subscription Group Settings, then update the subscription. On Android, use the subscription settings or import option. Menu names may vary slightly between interface versions. After importing, check the protocol, address, and security parameters, then select the configuration you want to use. Seeing it in the list isn't enough.
On desktop, start by setting the system proxy. On Android, start the connection and approve the VPN permission. Test access in a browser and check the client logs for specific errors. A configuration test can help narrow down options, but it doesn't replace testing an actual webpage. If something goes wrong, change one setting at a time.
An installer handles device compatibility. Whether a subscription connects also depends on a match between the protocol, security layer, and core capabilities.
v2rayN, v2rayNG, and v2flyNG provide interfaces for managing configurations and connections. Xray and V2Fly are core ecosystems that handle the connections themselves. Project V is a starting point for understanding this technology family, but extensions aren't necessarily compatible across branches. When comparing installers, look at platform and architecture. To compare connection capabilities, check the configuration requirements and core support.
For example, VLESS is a protocol, while REALITY is a related transport security solution; they aren't interchangeable settings. The address, port, user ID, flow control, and security parameters in a subscription must work together. Changing installers won't fill in missing fields or fix a server-side configuration error.
For a first install, use the client's standard settings: import the subscription, select a configuration, and set the system proxy, one step at a time. Once the basic connection works, adjust routing, DNS, or TUN. If an app doesn't follow the system proxy, check whether it supports proxies instead of assuming the client installation failed.
On mobile, also account for battery-saving restrictions, network changes, and interference from other VPN apps. Power use during extended sessions depends on traffic, wireless signal, transport, and OS scheduling—not just the client name. For more on protocol trade-offs and core differences, see Protocol and Core Technical Reference.
Check which installation step failed, then review the connection settings. The questions below cover package formats, architecture, and moving configurations.
For a fresh install, start with Desktop, which uses a modern cross-platform interface. Classic WPF retains the familiar Windows interface and is a stable choice if you prefer the traditional workflow. These are not different protocol bundles. Back up your configuration before switching, and don't let both instances set the system proxy at the same time.
On Windows, check System type under Settings → System → About. On macOS, check the chip or processor in About This Mac. On Linux, check the architecture in System Information. Apple Silicon uses arm64; Intel desktop processors generally use x64.
Most mainstream Android phones released since 2015 can start with arm64, but check which architectures the device's OS supports. If you're unsure, choose the universal version. Knowing the processor model alone doesn't rule out the possibility that the OS uses a different ABI.
For Android, new users should start with v2rayNG, which uses the Xray core. Consider v2flyNG if you need to keep using a V2Fly configuration. For VLESS, REALITY, or specific transport settings, check support in the client and core you're using; being able to import a subscription doesn't guarantee that every parameter is compatible.
A client manages configuration and connections; installing it doesn't provide a working connection. You'll need a subscription URL or server settings from a service you're authorized to use, then import and select a configuration and choose a proxy mode. Example domains, user IDs, and public keys won't connect to a server.
First, make sure the installer matches your system architecture. Fully extract Windows ZIP files before running the installer inside. If prompted for a runtime, install the required .NET Desktop Runtime. On Android, check permission to install from the current source, available storage, and conflicts with an existing app signature. On desktop, also check folder write permissions and any security prompts.
If you need to investigate further, note the exact error message and see Frequently Asked Questions. Changing routing or DNS repeatedly won't usually fix a startup issue if the configuration hasn't started running.
Routine updates to the same client usually retain existing data, but compatibility isn't guaranteed when switching interfaces, folders, or clients. Before updating, use the client's backup or export feature and keep your subscription sources and custom rules. Once the new version is working, you can remove the old folder. Back up local settings before uninstalling an Android app.