For desktop, choose v2rayN; for Android, v2rayNG is the recommended choice. Select your operating system, then choose an installer for your device’s architecture.
Windows installers
For x64 systems. Choose either the Desktop version or the classic WPF version.
The v2rayN Desktop version uses a newer cross-platform interface and is a good choice for first-time installs. The classic WPF version retains the familiar Windows interface for those who prefer it. Both downloads are ZIP archives. Extract the archive to its own folder, then run the installer from there.
If the installer immediately reports a missing runtime, note the name, version and architecture shown in the message and install the required component. The standard .NET runtime and .NET Desktop Runtime are not always interchangeable. If you already have an older version, exit the client from the system tray first; closing only the main window may leave it running.
Windows system requirements
Check
How to check
Operating system
Use a supported 64-bit version of Windows where possible. Check your Windows version and system type under Settings → System → About.
Architecture
Only x64 installers are available here. If Windows reports x86 or ARM, don’t assume the installer is compatible just because the system is 64-bit.
Runtime
Check the installer’s prompts for required desktop runtimes. Make sure you have permission to read and write to the installation folder during setup and first launch.
Installed but won’t open? Follow the startup crash troubleshooting steps to check for runtime, folder permission or old configuration issues.
macOS installers
Check About This Mac for your chip or processor, then choose the matching DMG.
If About This Mac shows an Apple M-series chip, choose Apple Silicon (arm64). If it shows an Intel processor, choose Intel (x64). Both installers offer the same client features. Choose based on your Mac’s processor, not its screen size, model name or purchase date.
Open the DMG and follow the instructions in the disk image window to move the app to Applications. Launch it from that folder. If macOS says the app can’t be opened, check whether the issue is an incompatible macOS version, the wrong architecture or a security restriction. Don’t disable system-wide security just to run one app.
macOS system requirements
Check
How to check
Chip
Apple Silicon uses arm64; Intel uses x64.
macOS version
Check your version in About This Mac. For older versions, compare it with the minimum macOS version required by the build you chose.
Install location
Use an Applications folder you can write to. On managed devices, follow your organization’s software installation policies.
Before upgrading, quit the old version and then open the newly installed app. If the Dock still has an old shortcut, launch the app from Applications to avoid testing the wrong version.
Android installers
We recommend v2rayNG. Consider v2flyNG if you need compatibility with V2Fly.
Uses the Xray core. Most mainstream phones released after 2015 can use the arm64 version if the system supports arm64-v8a. Some devices have 64-bit processors but only provide a 32-bit app environment. If you’re unsure which architectures your device supports, choose the universal version.
Uses the V2Fly core and is suited to configurations known to be compatible with V2Fly. The two clients can read similar subscription formats, but a node appearing in the list doesn’t guarantee support for its transport or security settings. When switching, test with one known-working configuration before moving other groups.
Android system requirements
Check
How to check
macOS version
Check your Android version under Settings → About phone. For older versions, follow the compatibility requirements for the build you selected.
App architecture
Choose arm64 if your device supports arm64-v8a; if you’re unsure, choose the universal version.
Install permission
When you open an APK from a browser or file manager, Android may ask you to allow installs from that source.
VPN permission
The first time you use VPN mode, approve the system connection request. This is separate from permission to install the app.
The version shown here comes from the release manifest. If it differs from the number in the APK filename and you plan to install over an existing app, use the version shown in Android’s installation screen or the app details after installation.
Debian and Ubuntu-based distributions generally use DEB packages. For RPM-based distributions, check that the package targets your system and its dependencies. The RPM filename here includes el10. Using RPM doesn’t guarantee that your system has the dependencies required by this build.
Open the installer with your distribution’s package installer to check whether dependencies can be met. If it reports an error, note what’s missing and confirm that the distribution and build match. Don’t force the installation by ignoring dependencies.
Linux system requirements
Check
How to check
Distribution
Check your distribution and version in System Details, then confirm which package formats your package manager supports.
Architecture
x86_64 maps to x64 and is listed as amd64 in DEB packages; aarch64 maps to arm64.
Desktop environment
These packages are for graphical clients. Run them in a regular desktop session and make sure the dependencies listed by your package manager are met.
Installing a package may require administrator privileges, but the client should be launched from a regular desktop account. Installation permissions and runtime permissions are separate.
First install or in-place upgrade
For a first install, choose a package that matches your device. If you already use the app, first check whether you can keep your data. Package selection depends on the OS version, architecture and package format; upgrades also depend on the current app version, installation source and where its settings are stored. These checks answer different questions: an installer that works on your device may not be suitable for upgrading over an existing version.
First, confirm which device you’re downloading for
If you’re downloading an installer on a computer for your phone, choose based on the phone’s Android version and app architecture, not the computer’s. Likewise, when choosing an installer for another computer, check the architecture in that device’s system details. Computers in the same product line may have different processors. Being able to run some compatible apps doesn’t mean every installer for that architecture will work; choose a native build where possible.
Back up subscriptions and local settings before upgrading
Note which client you use, where it came from and which subscription groups you have. If the client offers an export feature, save a restorable copy outside its app folder. Manually added nodes, routing rules and local port settings may not be restored from a subscription, so make a note of anything you changed. Subscription URLs may contain credentials; don’t post them in public comments, screenshots or shared logs.
When upgrading from the same source, quit the old client before installing the new package. After upgrading, open the app and check that your groups, nodes and rules are still there before testing a connection. If you need to switch clients, first import a configuration you know works. Keep the existing setup until the new client has been verified.
Check installation, import and connection separately
If the package won’t open or the installer reports an error, check the OS and architecture first and note the message. If the app opens but the list is empty, check the subscription URL and whether the group updated. If nodes appear but you can’t connect, then check node reachability, proxy mode and routing rules separately. Change one setting at a time and retest in the same app to identify what made a difference.
Installer FAQs
Do I need to install both the Windows Desktop and classic WPF versions?
Choose one. For a first install, start with the Desktop version, which uses a cross-platform interface. If you’re used to WPF, you can keep using the classic version. Before switching, fully exit the old client to prevent both instances from changing system proxy settings or competing for the same local port.
Is the Android universal version more stable than the arm64 version?
The universal version supports more CPU architectures and is usually larger, but that doesn’t make the connection more stable. Choose arm64 if your device supports arm64-v8a. If you can’t confirm the supported architecture, start with the universal version. It must still meet Android version, app signature and other installation requirements.
Why does my device say it can’t install the update?
Check your Android version, the installer’s architecture and available storage. If Android reports a conflict with the existing app, note the full message and confirm that both installers are for the same app and have compatible signatures. Use the original installation source where possible. If you need to uninstall and reinstall, back up your subscriptions and local settings first.
Do I need to download a core separately after installing the client?
For a first install, start with the components bundled with the client you chose. If the app reports a missing component at startup, check the component name in the client log, then make sure the archive was fully extracted or check whether your system package manager reports unmet dependencies.
Why is the node list empty after installation?
The installer provides the client. After opening it for the first time, import a subscription URL you already have or a node configuration. For subscriptions, save the URL and update the relevant group. Once nodes appear, select one, connect and check that it works.