Choose v2rayN for desktop, v2rayNG for Android, or v2flyNG if you need the v2fly core. Select the platform for your device, then choose a package based on its processor architecture and package format.
Desktop uses a modern cross-platform interface and is a good place to start. WPF retains the classic Windows interface and suits users familiar with the older menus. The main differences are the interface and where settings are found; you don't need both versions to import the same subscription.
Windows System Requirements
Check
What to look for
System and architecture
For Windows 10/11 x64 desktop systems. Check your system type under Settings → System → About.
Package format
Both downloads are ZIP files. Extract the entire archive before running the installer inside.
Runtime
If startup reports a missing .NET component, install the runtime named in the error, matching the required version.
Don't run the installer from the archive preview: this may extract only the installer temporarily, leaving its supporting files behind. Before upgrading, quit the old version from the system tray menu; closing its main window may leave it running in the background. If the new version reports that a port is already in use, check for an old process before considering a port change.
Not sure which chip your Mac has? Open About This Mac from the Apple menu. Choose Apple Silicon if it says Apple M series, or Intel if it says Intel processor. Both packages serve the same purpose but are built for different chips; migrate your settings using a method supported by the client.
macOS System Requirements
Check
What to look for
Chip
Apple Silicon uses arm64; Intel uses x64.
macOS version
For older macOS versions, check the current release's compatibility requirements. Matching the chip does not guarantee that your macOS version is supported.
Install location
Mount the DMG, copy the app to Applications, then launch it from there.
If the old version is still running, quit it before replacing the copy in Applications. After copying, eject the disk image to avoid accidentally launching another copy from it next time. If macOS blocks the app, note whether the warning concerns the system version, architecture or a security restriction. On a managed device, follow your organization's installation policies.
v2rayNG with the Xray core is the recommended choice. Most mainstream phones released after 2015 can start with arm64. If your device runs a 32-bit system or you confirm it doesn't support arm64-v8a, choose the universal version instead.
v2flyNG uses the v2fly core. Choose it if your existing configuration specifically requires this core. If you're migrating from v2rayNG, check the original node's protocol and transport settings; don't assume both clients support exactly the same options.
Android System Requirements
Check
What to look for
System architecture
Choose arm64 if your system supports arm64-v8a; if you're unsure, consider the universal package.
Package format
Open the APK with Android's package installer. Whether it can be installed on an older system depends on the package's minimum Android version.
Device permissions
Permission to install apps and permission to use a VPN connection on first connect are separate system permissions.
A 64-bit phone processor doesn't necessarily mean the installed operating system supports 64-bit apps. Switch to the universal package only if the installer explicitly reports an architecture mismatch. If it reports a conflict with an older version, check the version or signing certificate first. A universal package supports more architectures, but won't fix an outdated system or a signing mismatch.
The release version shown here may differ from the filename of a specific package. When reporting an installation problem, include the selected filename, device model, system version and installer message. If the first connection fails, also check whether another app is using the system VPN connection.
Debian- and Ubuntu-based systems generally use DEB packages. The el10 marker in the RPM filename indicates a build for Enterprise Linux 10; on other RPM-based distributions, check dependency compatibility first. The package format determines how it's installed, while the architecture determines whether it can run on your system. Both must match.
Linux System Requirements
Check
What to look for
Distribution
Check your distribution and version first, then choose a DEB or a compatible RPM package.
Processor architecture
x86_64 corresponds to x64; aarch64 corresponds to arm64.
Desktop environment
These are graphical clients. Install and use them in a session that can run desktop apps.
Use uname -m to help identify your machine's architecture. If you're installing in a virtual machine or container, also check the package manager's architecture in that environment. When a dependency error appears, rely on the package manager's message rather than switching packages based only on the file extension. If installation succeeds but the app isn't in the desktop menu, first confirm that the package manager reports a successful install, then look for the app launcher.
After downloading
First-Time Setup and Migration
For a first-time setup, confirm the app launches before importing nodes. Before replacing an older version, keep a recoverable copy of your settings. This makes it easier to tell whether a problem comes from installation, loading settings or connecting to the network.
After downloading, open the file from the right location
The browser's downloads list is a better way to find a file than the address bar. Confirm the download is complete, then use Show in Folder or Open File Location to find it. Browsers may add a number to duplicate filenames. If you aren't sure whether you're opening the new file or an older one, compare the download time with the filename listed below the button on this page; don't rely on the icon alone.
Extract ZIP files, mount DMGs, and open APKs and Linux packages with the appropriate system installer or package manager. Don't change a file's extension just to make it look openable. Managed computers and phones may restrict installation sources, locations or network settings. If you hit a restriction, first determine whether it's a device policy or the wrong package; don't change global settings just to complete one installation.
Keep your settings separate from the app before updating
Downloading the installer again can restore the app, but not manually added nodes, custom routing rules or changed local ports. Routing rules determine which outbound connection a type of traffic uses. If you've customized rules for a work network or specific apps, note the rule set in use before updating. Prefer the client's export feature, and check what's included: node lists, subscription groups and app preferences may not all be saved in the same file.
When moving to another device, save exported files somewhere only you can access. Subscription URLs often contain access credentials, so don't share them through public cloud storage or group chats. If you only need to remember a few key options, note their names and current values without including node addresses or account details. Once the new version starts normally, check the current group, selected node and proxy status. Remove the old copy only after confirming everything works.
Test a basic connection before enabling advanced features
For the first connection, test one node with one proxy method. On desktop, the system proxy passes a proxy address to the operating system for apps that follow that setting; it doesn't guarantee that every app uses the same route. On a phone, if another app is already using the system VPN, check which connection you want to keep. Test with a page or app you already need to access, note the settings that work, then adjust one thing at a time.
If the app starts but the subscription list is empty, check that the address was added to the right group, then refresh it manually. If the list is visible but pages won't load, check that you've selected the intended node and enabled the relevant proxy setting. Don't change routing, DNS (the service that resolves domain names to addresses) and other network interception options all at once. Change one setting at a time and retest the same scenario so it's easier to roll back if something fails.
Download and Installation FAQs
Do I need to install both the Windows desktop and classic WPF versions?
Install just one. For a first-time setup, start with the desktop version. If you prefer the classic interface, choose WPF. Before switching, quit the running version and back up your settings. Running both clients at once can cause local port conflicts or lead them to overwrite each other's system proxy settings.
How do I know which Mac package to download?
Open About This Mac from the Apple menu. If it lists an Apple chip, such as M1, M2 or a later model, choose Apple Silicon. If it lists an Intel processor, choose Intel. Use the information for your Mac rather than guessing from the architecture shown by a browser or another app.
Android says the app wasn't installed. Should I try the universal version?
If your device doesn't support the arm64 package, try the universal version. If Android reports a conflict with an existing app, first check where the old version came from; apps with different signing certificates usually can't be installed over each other. Back up or note any settings you can re-import before deciding whether to uninstall the old version, so you don't lose local settings.
Linux reports missing dependencies during installation. What should I do?
First check your distribution, package format and architecture, then use your distribution's package manager to install the local package. If a dependency still can't be satisfied, note its name and required version. In particular, don't force-install RPMs marked el10 on a different distribution or an older system.
Will my subscription appear automatically after I install the client?
No. The installer only provides the client; a subscription is an address used to retrieve a node list, and must be imported separately or migrated from an old device. After importing it, update the relevant subscription group, then choose a node from the list. Don't post your full subscription URL in a public support thread.
Can't connect after an update? What should I check first?
First confirm that the new version has loaded your existing settings, then check the selected node and system proxy status. If any settings have changed, restore one at a time and test using the same page that worked before. If the app won't open, troubleshoot startup or installation first; there's no need to change your subscription yet.