Downloads / OS and architecture
Choose v2rayN for desktop and v2rayNG for Android. Check your operating system first, then select the processor architecture and installer format.
The client manages settings and connections; a usable server configuration must be imported separately. For your first install, follow the setup guide.
Two interfaces for the same client. Both downloads below are x64; check your system type before downloading.
Start here for your first install.
Download Desktop · x64ZIP archive. Extract it after downloading, then run the installer.
Keeps the familiar Windows interface and workflow.
Download classic WPF · x64You don't need both editions. Choose the interface you prefer.
| Check | What to look for |
|---|---|
| Operating system | Windows desktop. Check the current installer for the minimum supported Windows version. |
| Processor architecture | Both downloads are x64. Check System type under Settings → System → About. |
| Installer files | Extract the ZIP first. Keep the full extracted folder, then run the installer inside it. |
| Runtime requirements | If the installer reports a missing runtime, check which component and architecture it requires. Don't replace program files at random. |
Don't launch the app from the ZIP preview. Extract the files to a regular writable folder first, and make sure the installer can access the files alongside it. If the old client is still running, turn off its system proxy and exit before installing to prevent the old and new instances from competing for local ports.
Desktop and WPF differ in interface technology and layout; settings aren't necessarily interchangeable between them. When switching, use the client's built-in export and import features where possible. Check custom routes, subscription groups, and local ports individually. Don't copy the entire old client folder over the new one.
After installation, import your settings and select a server, then confirm the core starts. The system proxy affects apps that use the system proxy settings; it doesn't mean all app traffic is routed through the client. For connection checks and routing options, see the first-time setup guide.
Check the chip or processor listed in About This Mac, then choose the matching DMG.
For Macs with M-series chips.
Download Apple silicon · arm64Choose the native architecture that matches your chip.
For Macs with Intel processors.
Download Intel · x64Don't rely on the device's appearance or purchase year alone.
| Check | What to look for |
|---|---|
| Operating system | macOS. Check the app package and system prompts for the minimum supported version. |
| Apple Silicon | If About This Mac shows an Apple M-series chip, choose the arm64 DMG. |
| Intel processor | If About This Mac shows Intel, choose the x64 DMG. |
| How to install | Open the DMG, move the app to Applications, then launch it from there. |
The chip name in About This Mac is a better guide than the model year. Similar-looking devices may use different architectures, and older models may have been bought more recently. A DMG can open even if it contains the wrong architecture, but the app may not run properly. Check your chip before installing.
After opening the disk image, don't use its temporary location as the app's permanent home. Copy the app to Applications and launch it from there. Before updating, quit the old instance and make sure the menu bar app has closed too. If macOS blocks the app, read the specific message under Privacy & Security. Don't disable system protection entirely just to launch one app.
After the first launch, check that your settings imported correctly before enabling the system proxy. If your browser connects but other apps don't, check whether those apps use the system proxy; browser access alone doesn't confirm that all traffic is routed. For details on protocols, security layers, and core support, see the protocol and core manual, then review your imported settings.
For most users, v2rayNG is the best choice. Most phones released after 2015 use arm64; if you aren't sure of your device's architecture, try the universal version.
An alternative if you don't know your device's architecture.
Download v2rayNG · universalChoose the app architecture supported by your device.
Download v2flyNG · universal| Check | What to look for |
|---|---|
| Operating system | Android. The current APK declares its minimum supported version; the installer checks compatibility. |
| Processor architecture | arm64 requires a system that supports 64-bit apps. The universal version supports multiple app architectures. |
| Install permission | Allow installation only for the browser or file manager you use to open the APK. |
| Connection permission | The first connection prompts for Android VPN permission. Confirm the app name before allowing it. |
A 64-bit processor doesn't necessarily mean the system can install 64-bit apps. Some older devices use different system builds, so release year is only a rough guide. If the arm64 package won't install, check the installer message. The universal version may address some architecture differences, but it can't bypass Android version requirements.
To update an installed app, Android requires the package name and signing key to match. Packages from different release channels may not install over each other. If you encounter a signature conflict, keep the existing app and export your settings first. Uninstalling usually deletes private app data, including subscription groups and custom rules.
v2rayNG and v2flyNG are different clients; similar names don't mean they support exactly the same protocols. Check core support before using a configuration with a specific security layer or transport combination. If connections drop frequently when the screen is locked, check battery optimization and background permissions. Per-app proxy selections also determine which apps use the proxy.
Check whether your distribution uses deb or rpm, then choose x64 or arm64. These downloads are for the graphical desktop client.
For Debian, Ubuntu, and other distributions that use the deb package format.
Download deb · x64 ARM devices: deb · arm64For distributions that use RPM package management.
Download rpm · x64 ARM devices: rpm · arm64| Check | What to look for |
|---|---|
| Desktop environment | Requires a Linux desktop session that can run graphical apps. This guide doesn't cover terminal-only environments. |
| Package format | Choose deb or rpm for your distribution. The same package format doesn't guarantee compatibility with every version of a distribution. |
| Architecture names | amd64 and x86_64 refer to x64; arm64 and aarch64 refer to 64-bit ARM. |
| System dependencies | The system package manager checks library dependencies. If any are missing, first check your distribution version and software repositories. |
Package format and processor architecture are separate choices. A desktop system that uses deb packages, for example, may still run on ARM; don't choose x64 just because the file extension looks familiar. Check your processor and system architecture under About or Hardware Information, then return here to choose the right download.
Open the package with your distribution's software installer and review its dependency checks. If a required system library version isn't available, first confirm that the package supports your distribution. Don't force the installation by ignoring dependencies. Don't rename an rpm file to deb or force-install a package built for a different architecture.
After installation, launch the app from the applications menu and import your settings in a regular user session. Desktop environments handle system proxy settings differently, and browsers may have their own proxy options. If the client is running but your browser isn't connecting as expected, check the desktop proxy settings, browser configuration, and local listening ports to narrow down the issue.
After installation
Downloading is just the first step. Save your settings, confirm the import, then let the client route traffic for the apps that need a proxy.
An empty server list after launching the client means no configuration has been imported yet. Get a subscription URL, share link, or configuration file that you're authorized to use, then import it using the appropriate option in the client. A subscription URL retrieves configuration; it's not a local listening address and shouldn't go in the system proxy server field.
After importing a subscription, update it and check the server list. Entries in the list aren't necessarily reachable: select a server, connect, and check the logs and app access to confirm the settings work. The protocol, transport, and security layer in your configuration must be compatible with one another.
See the setup and connection guide →Before updating, export your settings and store the backup outside the app folder. In addition to subscription groups, note custom routes, local listening ports, per-app proxy selections, and system proxy mode. Keeping only the subscription URL usually won't restore all your custom settings.
Exit the old instance before installing the new package. After updating, check that the app starts normally before restoring your settings. If you're switching interface editions or core families, test your existing configuration on its own first. Don't change the protocol, routes, and proxy mode all at once, or it will be harder to identify the cause of a problem.
See protocol and core compatibility notes →If a download fails, check your browser's download history for network interruptions, low disk space, or system download restrictions. Don't rename or install a file while it's still downloading. Before trying again, remove any incomplete file with the same name so you don't mistake the old file for a new download.
If installation fails, save the installer's exact error and identify whether the cause is an architecture mismatch, unsupported system version, missing dependency, or conflict with an existing installation. If installation succeeds but connection fails, check your configuration, core startup, and system proxy instead of reinstalling repeatedly. Consider browser results, client logs, and the selected route together.
Version labels on this page come from the update manifest; installer links are maintained separately in the download manifest. Clients follow different release schedules, so choose based on your system, architecture, and compatibility needs—not the version number alone. For more common issues, browse the Troubleshooting page by symptom.
Download questions
For your first install, try Desktop, which uses a modern cross-platform interface. If you prefer the familiar Windows layout, choose the classic, stable WPF edition. Both are v2rayN. Back up your settings before switching, and don't let both instances manage the system proxy at the same time.
For most phones released after 2015, arm64 is usually the right choice, but make sure the system supports 64-bit apps. If you don't know your device's architecture or the arm64 installer reports incompatibility, try the universal version. It won't fix an outdated Android version or a signature mismatch.
The client app and server configuration are separate. After installing the app, import a share link, subscription URL, or configuration file that you are authorized to use. Then select a server and connect. Subscription URLs may contain access credentials, so don't include them in public screenshots or logs.
Use the client's export or backup feature to save your settings, and note your subscription groups, routing rules, and local listening ports. Exit the old client before updating. Mobile updates usually require the same package name and signing key. If the installer reports a conflict, don't uninstall yet; first make sure your backup can be restored.
Make sure the download is complete, then check your operating system, processor architecture, and package format. Extract ZIP files on Windows; use APK on Android and DMG on macOS; choose deb or rpm on Linux based on your distribution. Keep the installer's exact error message and follow the steps on the Troubleshooting page.