Windows / x64
Choose between two interfaces based on your preference. For a fresh install, start with the Desktop version.
Desktop has a newer cross-platform UI; WPF is the classic, stable version. If you’re used to WPF, you can keep using it—there’s no need to reorganize all your subscriptions just to switch interfaces.
Both downloads are ZIP archives. Extract each to its own folder, then run the installer inside. Don’t launch it from the archive preview.
macOS: Apple Silicon or Intel
Check the chip name in About This Mac, then choose the matching DMG installer.
Choose Apple Silicon if About This Mac lists an Apple M-series chip; choose Intel if it lists an Intel processor. Select the package for your hardware, not based on the macOS version.
Open the DMG and follow the prompts to install the app in Applications. After installation, launch it from Applications instead of running it from the disk image.
Android / APK
Start with v2rayNG. Consider v2flyNG if you need an environment for V2Fly-based configurations.
For most Android phones, start with arm64. v2rayNG offers graphical settings for importing subscriptions, choosing nodes, and per-app proxying, making it a solid starting point for everyday use.
Most mainstream phones released since 2015 use arm64, but your system still needs to support 64-bit apps. If you’re unsure of the architecture, choose the universal version. Its larger file size does not mean a faster connection.
For users who need to work with existing V2Fly configurations. It uses a different core from v2rayNG, so check the protocol and transport settings before switching. A similar interface doesn’t mean the clients work exactly the same way.
Choose an architecture the same way you would for v2rayNG. The two apps store their data separately, so after switching, you’ll need to import your configuration again and check your routing and per-app settings.
After downloading the APK, open it from your browser’s downloads or a file manager. If Android says you can’t install apps from this source, open the permissions page for that source and allow the installation if needed. Permission is granted to the app opening the APK: if you downloaded it in a browser but open it in a file manager, check the file manager’s permission.
After installation, import a subscription or node you’re authorized to use, then select a configuration and connect. The first time you connect, Android asks you to approve a VPN connection request. The status bar icon only confirms that the VPN tunnel is active; open a website to verify that DNS, routing, and server settings are working too.
| Check | Requirements and recommendations |
|---|---|
| arm64 installer | For Android systems that support arm64-v8a apps |
| Universal installer | Use if you’re unsure of the architecture; the app must still meet its system requirements |
| System compatibility | Follow the system installer’s compatibility check for the APK |
| Required permissions | Allow installs from the source; approve the VPN request on first connection |
| Background activity | If connections drop frequently, check battery optimization and background activity restrictions |
Linux: deb and rpm
Choose a package format for your distribution, then select x64 or arm64.
Debian- and Ubuntu-based distributions generally use deb packages; distributions that use RPM package management need rpm. The main downloads below are for x64. For arm64 devices, use the matching links below.
From download to connection
Handle software installation, configuration import, and network testing as separate steps. If something goes wrong, troubleshoot that step first.
v2rayN, v2rayNG, and v2flyNG are graphical clients; their installers don’t include usable server settings. Before installing, prepare a subscription URL or complete node details that you’re authorized to use. Subscription links may contain credentials, so don’t post them in public comments or include them in screenshots.
After importing, confirm that your configuration appears in the list, then select one and connect. For your first test, use the default routing rules or rules you understand. Don’t change DNS, per-app proxy settings, and advanced transport options all at once. Adjust them one at a time after connecting so you can revert to the last working setup if anything goes wrong.
See how to import a subscription and connect →Before updating, export your subscription groups, routing rules, and custom settings, and note the mode you’re using. Backups may contain server details and credentials, so store them somewhere you control. A screenshot of your node list usually isn’t enough to restore the full configuration.
On desktop, quit the client from the system tray and make sure its process has stopped before running the installer. For an Android in-place update, check the existing app’s identity and source if Android reports a signature conflict. Don’t uninstall just to force the update; doing so may erase subscriptions, routing rules, and local preferences.
After updating, check that the active configuration is still selected and test the connection. Being able to import an old configuration doesn’t guarantee that every core setting still applies. If you use custom JSON, check the fields and structure against the documentation.
View the JSON configuration guide →Note the client name, operating system, device architecture, installer used, and full error message. If the app won’t start, check the installer’s information first; if it starts, check the client logs. Before sharing logs, remove subscription URLs, user identifiers, and server credentials. Keep the error fields and surrounding context.
“Download complete,” “installed,” “tunnel connected,” and “websites load” are different states. They correspond to file download, system compatibility, configuration startup, and actual network connectivity. Pinpointing the stage is usually more effective than repeatedly uninstalling and reinstalling.
Download FAQs
Check the architecture, interface version, and update method first.
For most Android phones released since 2015, arm64 is a good first choice, but your system must support 64-bit apps. If you’re unsure of your device’s architecture or see an architecture compatibility error during installation, try the universal version. It includes components for multiple architectures and is usually larger; that does not make the connection faster.
Desktop uses a newer cross-platform interface and is a good starting point for a fresh install. WPF is the classic, stable version for users who prefer its familiar layout. Both are v2rayN. Back up your subscriptions, routing rules, and custom settings before switching, and don’t let both versions manage the system proxy at the same time.
Export your subscriptions, routing rules, and custom settings, then quit the running client. Android apps can usually be updated in place when the package name and signing key are compatible. If you see a signature conflict, verify the app’s identity and source before taking any action—don’t rush to uninstall it. On desktop, follow the installer’s update prompts, then check your settings and system proxy status.
The client reads your configuration and establishes a connection; the installer does not include usable server settings. You’ll need a subscription URL or node details that you’re authorized to use. Import them, select a configuration, and start the connection. On Android, you’ll also need to approve the system VPN connection request the first time you connect.
Note the full error message, then check the package format, processor architecture, system compatibility, and available storage. On Android, check whether the browser or file manager you’re using has permission to install apps. On Linux, review the dependencies reported by the package installer. If the download didn’t finish, download the file again before opening it; the file icon alone can’t tell you whether it’s compatible.