Use v2rayN on desktop; on Android, choose v2rayNG or v2flyNG to suit your configuration. Match the system first, then check the architecture and package format.
01 Choose your operating system
02 Check your system architecture
03 Confirm the package format or interface version
Choose an installer by operating system
Switch tabs to choose a target platform. If you’re downloading for another device, use that device’s system information.
Desktop uses a newer cross-platform interface, making it a good choice for first-time installs or anyone who wants a consistent experience across desktop systems. Classic WPF keeps the familiar Windows layout and workflow. These are standalone packages; choose one.
Both downloads are ZIP files. Extract the entire archive to a writable folder, then run the installer included in the package. Don’t launch it from the archive preview. When upgrading, quit the old client from the system tray first, then install and test the new one to avoid two instances competing for the same local port.
System requirements
Check
Requirements
OS and architecture
Use a supported 64-bit version of Windows 10 or 11. Both packages on this page are x64.
How to check
Go to Settings → System → About and check System type to confirm your processor architecture and system type.
Runtime requirements
If prompted to install a runtime, check the required component, version, and architecture.
Opening the installer doesn’t mean the client has started. On first launch, check the system tray and main window; make sure you can open Settings before importing your configuration.
Open About This Mac from the Apple menu. Choose Apple Silicon for an Apple M series chip, or Intel for an Intel processor. The 64 in the filename identifies the Intel package here; don’t assume compatibility just because both systems are 64-bit.
Open the disk image and copy the app to Applications, then launch it from there. If you migrated the app from an old computer, make sure you aren’t still opening the old copy. If macOS shows a security alert, note the specific reason and follow your device’s or organization’s installation policy.
System requirements
Check
Requirements
Chip
Use arm64 for Apple Silicon and x64 for Intel.
macOS version
For older versions of macOS, check the minimum version supported by the package.
Installer format
DMG disk image. Eject the image after copying the app.
If macOS says the app can’t run on this system, check the chip type and macOS version first. Reopening the same incompatible package won’t make it compatible.
Uses the Xray core. Most phones released since 2015 can use arm64, as long as the system supports arm64-v8a. If you know the processor is 64-bit but aren’t sure which app architectures the system supports, check the device specifications or choose the universal package.
The card badge shows the app version from the manifest; each download link points to a separate file record. Before installing over an existing version, check the filename for the selected download—don’t rely on the badge as the package version.
Uses the V2Fly core and is suited to configurations that specifically require it. This is not an upgrade package for v2rayNG. Before switching clients, make sure your existing protocol and transport settings are supported. After migrating, test the connection with a known-working configuration before importing the rest.
System requirements
Check
Requirements
App architecture
The arm64 package requires system support for arm64-v8a; the universal package includes multiple architectures.
macOS version
For older devices, check the minimum system requirements for the selected app package.
Installing over an existing app
The installer also checks the app ID, signature, and version. The universal package does not change these requirements.
On a managed device, check that your device policy allows the installation. If the installer reports a conflict with an existing package, check the original installation source instead of repeatedly switching architectures.
For Debian- and Ubuntu-based distributions, start with deb. For RPM-based distributions, start with rpm, but note that el10 in the filename identifies the package’s target—it doesn’t mean every RPM-compatible system can install it. Check the dependencies and conflicts reported by your package manager.
When installing in a virtual machine, check the architecture reported by the guest OS; don’t use the host’s architecture by default. If the package installs but won’t open, make sure your current session has a graphical desktop environment. A successful install doesn’t guarantee the app window will launch.
System requirements
Check
Requirements
Package format
Your distribution must support the corresponding deb or rpm format and the dependencies declared by the package.
Architecture
x86_64 corresponds to x64; aarch64 corresponds to arm64; amd64 in a deb filename also means x64.
Desktop environment
You need a desktop session that can run graphical clients.
If dependencies are missing, note their names and version requirements, then check your distribution and software sources. Forcing the installation won’t fix compatibility.
Installation, upgrade, and rollback checks
First identify where the problem occurs: downloading, installing, launching, or connecting. If one step succeeds, troubleshoot the next one. Don’t blame every issue on the installer.
01 · Before installing
Note your system details and where the old version came from
When setting up a device for yourself or a colleague, note its OS version and architecture, along with the filename you chose. It’s easy to pick a package for the wrong architecture when preparing downloads for several devices on one computer. Match each filename to its target device, and take care to distinguish Desktop from classic, processor architectures, and the two mobile packages for the same client.
For a fresh install, you only need the installer and a source for your configuration. Before upgrading, open the old client and note its version, interface, installation source, and any custom data locations. Keep separate records of subscriptions, manually added nodes, routing, and local ports. A subscription URL alone usually isn’t enough to restore everything. Configurations and exported files may contain sensitive information; store them somewhere you control and don’t include them in public troubleshooting screenshots.
If your computer is managed by an organization, check whether your account can install apps, where the app should be installed, and whether proxy settings are managed centrally. Repeatedly extracting the files or trying another package for the same architecture usually won’t get around permission restrictions. Sharing the full error with your device administrator is more useful than trying different folders.
02 · During installation
Use the error message to distinguish architecture, dependency, and install conflicts
If the installer says the app is incompatible with your device, check the architecture in your system information first. If it’s correct, check the OS version or required runtime components. When the package manager lists dependencies and version requirements, use those details to investigate rather than assuming the OS is simply too old.
If your archive utility can’t open the download, first make sure the browser has finished downloading it. Confirm you’re opening the new file, not an older copy with the same name or an incomplete temporary file. Extract archives fully; open disk images before copying apps; and use the system installer for packages. Renaming a file extension doesn’t convert its format.
If an app won’t install over an existing version, compare the installation sources and versions. A universal package won’t fix a signature conflict; if the error mentions a version downgrade, check that you haven’t selected an older package by mistake. Before uninstalling, make sure your data has been exported and can be restored. Uninstalling may also delete local data, so don’t make it your first troubleshooting step.
03 · First launch
Make sure the interface opens before testing your configuration
After installation, open the client from its new location and make sure you can reach the main screen and view the version. Closing a desktop window may leave the program running in the system tray or menu bar; check for an existing instance before opening it again. If the app exits immediately, note the error and what you did just before it closed. Don’t import your entire old configuration before troubleshooting.
Once the interface is working, add a configuration using the subscription import steps. Start with a known-working configuration and check that the client can connect. Seeing a configuration in the list only confirms that it was imported—it doesn’t prove network traffic is going through the proxy as expected. If the connection won’t start, check the client logs. If it starts but websites won’t load, follow the can’t access the internet troubleshooting guide.
If only some apps behave differently, note which ones are affected and whether the system proxy is enabled. Some apps have their own proxy settings and may not use the system settings. Keep other conditions unchanged and compare the same app before and after connecting, then check routing rules. Changing settings at both the connection and routing layers makes the results harder to interpret.
04 · Upgrading
Keep recoverable data before replacing the old version
If the client has a backup feature, use its backup or export option first. Save the resulting file outside the program directory, and note which version created it, what it contains, and which settings you’ll need to recreate manually. When switching clients, don’t copy all the app data directly over the new client’s directory; backup formats and fields may differ.
Quit the old program and disable any system proxy it set before launching the new version. After restoring your data, check that the configuration is complete, your custom ports are still in place, and any startup shortcuts no longer point to the old location. Don’t delete the old directory until testing is complete. If you need to keep both versions temporarily, don’t run them at the same time or let them write to the same configuration.
When rolling back, use a backup made with the older version if possible. Data saved by the newer version may not be readable by the older one. After rolling back, test one configuration first, then restore groups and custom routing. If the same issue occurs with both versions on the same network, repeatedly changing packages is unlikely to help; check the sections on connections, subscriptions, or system proxy settings instead.
Download and installation FAQs
Installing on Windows? Choose Desktop or WPF?
For a first install, start with Desktop. If you already use classic WPF and want to keep its familiar interface and workflow, choose WPF again. Both downloads are x64, so check your system type first.
How do I tell Apple Silicon from Intel on a Mac?
Open About This Mac from the Apple menu. If Chip shows an Apple M series, choose Apple Silicon; if Processor shows Intel, choose Intel. Check again when switching computers—don’t rely on downloads chosen for an old machine.
Can the universal Android package fix a signature conflict?
No. The universal package supports multiple processor architectures; a signature conflict means the app can’t be installed over the existing one. Stick with the original installation source if possible. If you need to switch, make sure your configuration can be restored before uninstalling and reinstalling the app.
On Linux, should I choose by package format or processor architecture?
Both must match. Choose deb or rpm for your distribution, then select the download for your system’s x86_64 or arm64 architecture. A system that can read the package format may still be missing dependencies, so check your distribution version too.
My configuration is already imported. Should I back it up before installing an update?
Yes. Subscriptions can be fetched again, but manually added nodes, groups, and routing settings may not be recoverable. Before upgrading, use the client’s backup or export feature and save the backup outside the old program directory.
Why doesn’t the client’s release version match the installer filename?
The version shown on the card comes from the app version field in the manifest; each download link gets its filename from a separate file record. They may not match temporarily. If you need a specific version, check the filename for that download. Don’t install over an existing version if the filename doesn’t identify the version or the two records disagree.