Choose your operating system, then download the package for your processor and package format. Use v2rayN on desktop; for Android, start with v2rayNG, or choose v2flyNG if you need the v2fly core.
Desktop uses a newer cross-platform interface and is a good fit for first-time installs or switching between desktop devices. WPF is the classic, stable edition for users who prefer its familiar interface. Both packages are ZIP files: extract the entire archive before opening the installer. Don’t run it from inside the archive.
Open About This Mac. If it lists an Apple M-series chip, choose the Apple Silicon package; if it lists an Intel processor, choose the Intel package. Open the DMG and follow the window’s instructions to copy the app to Applications, then launch it from there. Once the copy is complete, you can eject the mounted disk image.
Most mainstream phones released after 2015 support arm64, but check whether your system supports arm64-v8a to be sure. If you’re unsure of the architecture or your device runs a 32-bit system, choose the universal package. The manifest version may differ from the downloaded file’s name; before updating, compare it with the version shown in the client.
Choose this client only if you specifically need the v2fly core. The arm64 and universal packages differ in architecture support, not in core or protocol. If you’re migrating from v2rayNG, first make sure the new client supports the protocols, transports, and security settings in your existing configuration.
Choose deb or rpm based on your distribution, then select the right architecture. amd64 and x86_64 correspond to x64 here; arm64 and aarch64 correspond to the 64-bit ARM package. Use your distribution’s package manager to inspect dependencies and error details during installation.
The installer contains only the client. For importing a configuration and testing a connection, see the usage guide. For help choosing a client and core, see the client comparison.
Install and update: follow these checks in order
Before installing: check your OS and architecture
Choose based on the device you’re installing the client on, not the device you’re using to view this page. For example, if you download a package for your phone from a desktop browser, choose Android. If you’re preparing packages for several devices, keep the original filenames and store them separately by platform. Packages for the same client can look similar; the architecture and file extension are more reliable clues than the order you downloaded them.
Check architecture and OS version separately. Architecture determines whether your device can run the program in the package; the OS version determines whether the client can use the required system interfaces. The right architecture doesn’t guarantee compatibility with an older OS. On Linux, also check the distribution’s package format and dependencies. If the installer rejects a package, check whether it reports an architecture mismatch, an unsupported OS version, or a missing dependency.
Install from the downloaded file
First, confirm in your browser’s downloads list that the file has finished downloading, then open it with your system’s file manager. Extract ZIP archives completely; open DMG files and copy the app as instructed; let Android’s installer handle APKs; and install deb or rpm files with your distribution’s package manager. Renaming a file extension won’t convert one package format into another.
If a ZIP archive extracts into nested folders, make sure you open the folder from the latest extraction, not an older folder with the same name. If you see a message that a component is missing, don’t drag a single executable to the desktop and run it on its own. After installation, launch the app from your system’s app list or its actual install location so an old shortcut doesn’t open an earlier copy. For permission prompts, first identify whether they come from the installer, a system policy, or authorization to enable the proxy for the first time; each requires a different response.
Before updating: keep a recoverable copy of your settings
Before updating, note the client name, current version, and install source. If the client offers a backup or export option, save your configuration first. Also note the imported source group, selected connection, whether the system proxy is enabled, and any custom local listening ports. These settings may not all be stored in one file. Subscription URLs and exported configurations may contain credentials; keep them on your own devices instead of posting them publicly or including them in troubleshooting screenshots.
On desktop, stop the proxy and quit the client, including any old instance still running in the system tray, before updating. After the update, launch it once and check that your original groups and settings are still there before connecting. If Android says the app can’t be installed over the existing version, keep the current app and check whether the error is a signature conflict. Trying different architecture packages from the same source usually won’t fix a signature issue, and an installation failure doesn’t mean you need to uninstall the existing app.
After installing, verify the app first, then the connection
If the client launches and opens its settings, the basic installation is complete—but that doesn’t mean a network connection is configured. On first use, import your own subscription or configuration, confirm that entries appear in the list, select one, then enable the proxy mode you need. If the list is empty, check the imported group and update the subscription. If entries appear but won’t connect, check the client logs. This helps distinguish configuration problems from package selection issues.
On desktop, test with an app that you know follows the system proxy settings. If only certain apps fail, check whether they use their own proxy settings and whether the protocol and port match the client. On Android, if the client is running but no VPN connection is established, check for a pending system authorization or another app using the same type of connection. Follow the first-time setup guide for the recommended steps; for manual listener and routing changes, see the configuration reference.
Package FAQs
Do I need to install both Desktop and WPF on Windows?
No. Choose one. Desktop is a good starting point for a fresh install. Stick with WPF if you prefer its familiar interface or need to migrate existing settings. Before trying the other edition, quit the current client to prevent both from listening on the same local port.
Which macOS package should I choose: Apple Silicon or Intel?
Open About This Mac from the Apple menu. If the Chip section lists an Apple M-series chip, choose Apple Silicon. If the Processor section lists Intel, choose Intel. Don’t base your choice on the purchase year or the computer’s appearance.
What if Android says the app isn’t compatible with my device?
Check your Android version against the app’s supported versions, then verify which ABIs your system supports. If it doesn’t support arm64-v8a, try the universal package for the same client. Universal packages support more CPU architectures; they don’t lower the app’s minimum Android version.
What should I do if an Android update reports a signature conflict?
First, try updating the app from the same source you used to install it. Android won’t let a package with a different signature replace an existing app. If you need to switch sources, back up or export your configuration first; uninstalling the old app may delete local data.
Can I use deb and rpm packages interchangeably on Linux?
No. Check which package format your distribution uses, then choose the matching architecture. Debian- and Ubuntu-based systems generally use deb; Fedora- and RHEL-based systems generally use rpm. Even with the right format, make sure your distribution and version meet the package’s dependencies.
Why is the list still empty after I download and install the client?
The installer provides the client, not connection settings. Import your own subscription, share link, or configuration file first. If no entries appear after importing a subscription, check that you’ve updated it. Don’t share your full subscription URL with anyone.