CLIENT PACKAGES / CHOOSE AN INSTALLER
Choose your operating system, then check your CPU architecture. Use v2rayN on desktop and v2rayNG on Android. The installer and connection configuration are separate.
Two x64 options—choose the interface you prefer.
Desktop is the newer cross-platform UI; WPF is the classic, stable version. New users can start with Desktop, while users familiar with the older interface may prefer WPF.
The download is a ZIP archive. Extract all files before running the installer; don't launch it from the archive preview.
| Check | What to look for |
|---|---|
| Operating system | Use a supported, maintained version of Windows 10 or 11. Check the selected release package for its exact minimum version and runtime requirements. |
| Processor | This page offers x64 packages. Check System type under Settings → System → About. An x64 package is not a native ARM64 package. |
| Permissions | Running the standard interface and setting the system proxy are different from using a mode that needs virtual network adapter or routing permissions. Grant administrator access only when a feature explicitly requires it. |
| Install location | Choose an extraction folder you can read and write to. Quit the old process before updating so the installer can replace files that aren't in use. |
Check About This Mac to identify your chip, then choose a DMG.
Choose Apple Silicon for M-series chips and Intel for devices that show an Intel processor. Use the installer built for your chip whenever possible.
Open the DMG and copy the app to Applications. Eject the disk image when copying is complete, then launch the app from Applications.
| Check | What to look for |
|---|---|
| Operating system | Use a supported, maintained version of macOS. Minimum requirements vary by client release, so check the compatibility prompt before installing. |
| Chip | Apple Silicon uses ARM64; Intel uses x64. Choose the native architecture when available to avoid compatibility-layer issues. |
| Install location | Copy the app to Applications before running it; don't launch it from the read-only disk image. |
| Proxy settings | The system proxy affects apps that follow system settings. Check connection settings separately for terminal tools and standalone proxy apps. |
v2rayNG is the recommended choice. Choose v2flyNG if you need compatibility with a V2Fly configuration.
A popular graphical client for Android. Most mainstream phones released since 2015 should start with arm64. If you can't confirm which app architectures your device supports, choose the universal version.
The version shown on the card may not match the package filename if they were updated at different times. Check the app version shown by Android's installer, and back up your configuration before updating.
For users whose existing configurations require V2Fly. Similar names don't guarantee that configuration fields are interchangeable. Before choosing, check that the protocol, transport and security layer are supported.
v2flyNG and v2rayNG are separate apps, not two architecture builds of the same app. Keep your original subscription details before importing them.
| Check | What to look for |
|---|---|
| Android version | Check the selected APK's installation requirements for the minimum Android version. Even if an older system can install it, network interfaces and certificate support may be limited. |
| App architecture | arm64 corresponds to arm64-v8a. A 64-bit processor doesn't guarantee that the system supports 64-bit apps; check the ABIs supported by your device. |
| Installation permissions | When installing an APK for the first time, grant Install unknown apps permission only to the browser or file manager you're using. You can turn it off after installation. |
| Connection permissions | The first time you connect in VPN mode, Android displays a system permission prompt. Check the app name before approving. Other VPN apps running at the same time may already be using Android's VPN connection. |
Import your subscription before setting up per-app proxy rules and routing. If the connection drops in the background, check battery optimization and background activity restrictions. There's no need to change every advanced setting at the outset.
Choose a package format for your distribution, then select x64 or ARM64.
For Debian- and Ubuntu-based distributions, look for deb; for Fedora and other RPM-based distributions, look for rpm. The primary links below are for x64; use the matching architecture link for ARM64 devices.
| Check | What to look for |
|---|---|
| Desktop environment | Requires a working graphical session and the relevant desktop runtime libraries. A command-line-only server is not a desktop client environment. |
| Processor | amd64 / x86_64 corresponds to x64; aarch64 corresponds to ARM64. A package won't install just because its format is right if its architecture doesn't match. |
| Distribution | Choose deb or rpm for your distribution and check the required system library versions. The distribution identifier in an RPM filename also matters for compatibility. |
| Installation permissions | Installing through the system package manager usually requires authorization. You shouldn't need to run the app as root for normal desktop use. |
The platform determines the app's runtime environment; the architecture identifies the processor type the executable is built for. Check the device's platform and OS version in system settings, then identify its chip or system type. Don't assume the architecture from a phone's age or a computer's performance, and don't choose based only on installer size. A universal package typically includes multiple architectures; a larger file doesn't mean it supports more protocols.
The client download installs the app; the subscription link provides connection details. Before updating, save your subscription URLs, group notes, custom routes, DNS settings and per-app selections. Subscription URLs may contain account access tokens, so keep them private and don't post them in public comments or screenshots. After migrating, refresh the subscription and verify the imported protocols and transport settings.
Desktop apps may keep running in the system tray after you close the main window. Use the exit command to quit the process before updating. Android updates require a compatible app identity and signature; if there's a conflict, check the original installation source before taking action and don't clear app data right away. Config directories aren't guaranteed to transfer cleanly between different clients, so use the built-in import or backup feature when available.
v2rayN, v2rayNG and v2flyNG are graphical clients in the Project V ecosystem. The interface imports, selects and manages configurations; the underlying core handles the connection. v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. Even when the protocol name is the same, specific extension fields, transport combinations and security parameters may not work identically across both cores.
If a share link imports but the connection fails, first check the protocol, server address, port and security settings, then review the specific error in the logs. Reinstalling a different package won't fix an underlying configuration issue. To understand how VMess, VLESS, Trojan and REALITY fit together, read the protocol and core technical handbook before deciding whether to switch clients.
Keep your first test simple: start with a known-good configuration and the default routing mode. Confirm that your browser connects as expected, then enable per-app proxy rules, custom DNS or other advanced features one at a time so you can easily undo changes. If only terminal tools can't connect, check their proxy environment separately rather than assuming the client installation failed.
PACKAGE NOTES / DOWNLOAD FAQ
Use v2rayN on Windows, macOS and Linux. On Android, v2rayNG with the Xray core is the recommended choice; consider v2flyNG only if your existing configuration depends on V2Fly features. All three are graphical clients, and you'll still need to import a usable connection configuration after installation.
Most mainstream phones released since 2015 support arm64, but check which app ABIs your device supports. If you can't confirm the architecture, or arm64 is reported as incompatible, choose the universal version. It supports multiple architectures and is usually larger; it does not make connections faster.
Desktop is the newer cross-platform interface; WPF is the classic, stable interface. If you're new to the client, start with Desktop. Choose WPF if you're familiar with its interface or need to keep the same workflow. Check that your system supports the selected version and x64 architecture. Back up your subscriptions and routing settings before switching.
The installer doesn't include ready-to-use connection details. Get a subscription URL or share link that you're authorized to use, add it in the subscription group settings and refresh, or import a single configuration from the clipboard. Then select a configuration and start the connection.
Usually, close the running client first, then update with an installer for the same app, installation channel and compatible architecture. Back up your subscription URLs, custom routes and per-app settings before updating. If Android reports a signature conflict, don't uninstall right away; first check where the app was installed from and whether your data is backed up.
The card's version label and the installer filename come from separate manifest fields, so they may reflect different update times. Check the filename you selected and the app version shown by the installer. Don't rely on the card's version number alone to decide whether an update can replace your current installation. If unsure, keep your existing configuration and postpone the update.
If apps can't connect or you run into DNS issues, see FAQs and troubleshooting.