Choose the operating system of the device you’re installing on, then check its processor architecture and package format. For Android, choose v2rayNG or v2flyNG; for desktop, use v2rayN.
The desktop edition uses a newer cross-platform interface and is a good place to start. WPF is the classic, stable version for users who prefer the original menu layout. These are two interface options; you don’t need both for the same subscription.
Before Installing on Windows
Windows System Requirements
Check
What to look for
System and architecture
Use a supported Windows 11 x64 system. Go to Settings → System → About and check System type.
Package format
Both are ZIP archives containing installers. Extract the entire archive before running the installer inside.
Runtime
If startup reports a missing runtime, install the component and architecture named in the message. There’s no need to install multiple versions in advance.
Extract the ZIP to a separate folder first; don’t run the installer from the archive preview. If extraction fails, make sure the download completed. If extraction succeeds but installation is blocked, check folder permissions or device management policies. These are different problems, and switching to WPF won’t fix a write-permission issue.
If the old client is still running, restore the previous system proxy settings first, then exit the app from the notification area. Keep a configuration backup when switching, and note which subscription groups you’ll need to restore. On the first launch of the new version, make sure it can read the configuration before enabling the system proxy. Don’t change the routing mode at the same time, or it’ll be harder to pinpoint the cause of any issue.
Open Apple menu → About This Mac. Choose arm64 if it shows an Apple M-series chip, or x64 if it shows an Intel processor. Match the package to the chip listed there—don’t rely on the model name or purchase year.
Before Installing on macOS
macOS System Requirements
Check
What to look for
Chip
Choose arm64 for Apple silicon and x64 for Intel.
Operating system version
Check your macOS version in About This Mac. If an older system reports an incompatibility, first check which macOS versions the release supports.
Install location
After opening the DMG, follow its instructions to copy the app to Applications.
After copying, launch the client from Applications. Don’t use the mounted disk image as a permanent place to run it from. Before updating, quit the old app and follow any replacement prompts. Check the app’s location in Finder so you don’t accidentally open another copy from an old download folder.
If macOS says the app can’t be opened, note the exact message and determine whether the issue is architecture incompatibility, an app-source restriction, or a device management policy. First make sure the download matches your chip, then follow the instructions from macOS or your device administrator. There’s no need to disable system-wide security settings to resolve an issue with a single install.
Powered by the Xray core. Most mainstream phones released since 2015 use arm64. If your phone has a 64-bit processor but the system only supports 32-bit apps, choose a package based on the architecture your system supports. If you’re unsure, choose universal.
Powered by the V2Fly core and suited to users with existing compatible configurations. Before switching clients, check which protocols and transport options your configuration requires. Being able to import a configuration doesn’t mean both cores support every field in it.
Before Installing on Android
Android System Requirements
Check
What to look for
App architecture
Choose arm64 if your system supports arm64-v8a; choose universal if you’re unsure.
Operating system version
Check your Android version in Settings → About phone. The universal build doesn’t reduce the minimum Android version requirement.
Install permissions
Installation is initiated by the browser or file manager used to open the APK. On managed devices, the administrator’s settings apply.
Open the APK after it finishes downloading. If Android says apps from this source can’t be installed, check whether the app named in the prompt is the browser or file manager you used to open the file. Once you’ve confirmed the source, follow the system prompt to allow installation; you can revoke that permission after installation. If the message reports a signature conflict, changing source permissions won’t help—use the same distribution channel as the installed app.
Install permissions and VPN connection requests are separate. The first appears when you open the APK; the second usually appears the first time you tap Connect. If another VPN app is already connected, decide whether to keep that session before switching. When trying two clients, disconnect one before testing the other on the same network, so a system connection switch isn’t mistaken for a broken configuration.
Debian- and Ubuntu-based distributions generally use deb packages. The rpm here is built for EL10, so an rpm-based distribution isn’t necessarily compatible. Check your distribution version and dependencies before choosing an architecture.
Before Installing on Linux
Linux System Requirements
Check
What to look for
Desktop environment
Use in a desktop session that can run graphical applications.
Architecture names
x86_64 and amd64 refer to x64; aarch64 refers to arm64.
Package dependencies
Follow the results from your distribution’s package manager; don’t force installation past dependency errors.
Check your distribution and processor architecture in system information, then open the download with your system’s package installer. If the package manager reports an architecture mismatch, return to this section and choose the matching package. If a dependency can’t be met, check your distribution version and enabled repositories. Don’t try to fix an installation failure by switching package formats.
After the package manager finishes installing, launch the client from the desktop menu. A successful package installation only confirms that the program was installed; it doesn’t mean your desktop environment will apply the client’s system proxy settings. Import a known working configuration and test the connection first, then check whether the apps you want to proxy use the desktop environment’s proxy settings.
Installation and Migration
First-time Install and Updates
First install: Make sure the app opens
Check installation and connection separately. During installation, confirm only that the system can open the client, the app window displays correctly, and you can open Settings. An empty list is normal at this point; there’s no need to use an unfamiliar subscription to fill it. If you’re downloading on one device but installing on another, choose the package for the target device’s operating system and processor—not the device you’re downloading from.
Once the app opens, follow the quick start guide to import your own subscription or individual configuration. Check that the expected entries appear in the list, then select one and test the connection. Start with the default routing mode and minimal settings. Once the connection works, adjust per-app proxying, domain rules, or DNS as needed.
Updating: Keep a backup you can restore
Before updating, check whether the old client offers an export or backup feature. Note which configurations came from subscriptions and which you added manually. A subscription URL can retrieve remote entries again, but may not restore local rules, renamed entries, or groups. After backing up, make sure the file is saved somewhere that won’t be cleared when the app is uninstalled. Keep backups containing credentials in storage you control.
After updating, check your subscription groups, selected entry, and basic settings before reconnecting. On desktop, verify that the system proxy wasn’t left enabled by the old instance. On Android, make sure the VPN connection request comes from the app you just opened. If you run into compatibility issues, note the client, OS version, package architecture, and exact error message, then check troubleshooting. You don’t need to include your full subscription URL when describing the issue.
Download FAQ
Installer FAQs
Should I choose arm64 or universal for my Android phone?
Choose arm64 if your system supports arm64-v8a; if you’re unsure, choose universal. The universal build includes components for multiple architectures but still depends on your Android version and installation policies.
Should I install both the Windows desktop and WPF editions?
Choose one. The desktop edition uses a newer cross-platform interface; WPF is the classic, stable version for users who prefer its familiar layout. Back up your configuration and exit the old client before switching.
What should I do if an Android update reports an app conflict?
Check where the installed app came from and where the new installer came from. Android usually won’t install an update over an app with the same ID if the signatures differ. Use the original distribution channel when possible. If you need to uninstall first, back up your configuration, as uninstalling may erase app data.
Why is there no configuration after installation?
The installer only provides the client. Get your own subscription URL or individual configuration, then import it using the guide. Never post a subscription URL containing access credentials in a public forum.
Can I open a file if the download was interrupted?
Check your browser’s downloads list to make sure the download is complete. If it failed or the file is still temporary, download the installer again, then open it with your system or an archive utility.