v2rayN
Windows x64 · ZIP package
Desktop uses a newer cross-platform interface; WPF is the stable edition with the classic interface. For a first install, start with Desktop. When upgrading, choose WPF if you want to keep the familiar interface.
Choose your operating system, then select a package by CPU architecture and format. Use v2rayN on desktop and v2rayNG on Android.
Downloading for another device? Use that device’s system information.
Windows x64 · ZIP package
Desktop uses a newer cross-platform interface; WPF is the stable edition with the classic interface. For a first install, start with Desktop. When upgrading, choose WPF if you want to keep the familiar interface.
| Check | Requirements and options |
|---|---|
| System and architecture | For Windows 10/11 x64. Go to Settings → System → About and check that System type lists an x64-based processor. |
| Format | Extract the entire ZIP archive before running the installer from the extracted folder. |
| Runtime requirements | If the installer reports a missing runtime component, check the required version and architecture in the prompt. |
If your computer is managed by your organization, check with your administrator before installing. A standard installation and enabling TUN later are separate tasks; you don’t need elevated privileges just to download the client or import a subscription.
macOS desktop · DMG
Open About This Mac from the Apple menu. If the Chip field shows an Apple M-series chip, choose the Apple silicon edition. If the Processor field shows Intel, choose the Intel edition. Each package is for a different processor, so you only need one.
| Check | Requirements and options |
|---|---|
| Architecture | Apple silicon uses arm64; Intel processors use x64. |
| macOS version | Check your version in About This Mac. If macOS says the app requires a newer version, changing the architecture won’t help. |
| Install location | Open the DMG, drag the app to Applications, then launch it from there. |
Once the copy is complete, you can eject the disk image. If the app won’t launch, first check whether the issue is an incompatible chip, an outdated macOS version, or a permissions prompt. Don’t assume every alert has the same cause.
Xray core · APK
Most phones released since 2015 are likely to support arm64. Check whether your system supports arm64-v8a to be sure. Some devices have a 64-bit processor but run a 32-bit system; choose the universal package in that case.
v2fly core · APK
Choose this client if you already have a config designed for the v2fly core. The two Android apps aren’t upgrade packages for each other. Before switching, make sure the target client supports your subscription’s protocols and transport settings.
| Check | Requirements and options |
|---|---|
| Architecture | Choose arm64 if your system supports arm64-v8a. If you’re not sure, choose the universal package. |
| macOS version | Check your Android version under Settings → About phone. If the installer says your Android version is too old, switching to a different architecture package won’t help. |
| Installation permissions | Android may require you to grant permission to the browser or file manager that opened the APK. Confirm the source before allowing installation, and revoke the permission afterward if you like. |
Linux desktop · deb / rpm
Choose the package format for your distribution first, then select the package for your system’s architecture. In the rpm filename, el10 identifies the build target; it doesn’t mean every rpm-based distribution has the required dependencies.
| Check | Requirements and options |
|---|---|
| Package format | Debian- and Ubuntu-based systems typically use deb packages. For rpm-based systems, check that the distribution and package build target match. |
| Architecture | Run uname -m in a terminal. x86_64 means x64; aarch64 means arm64. |
| Desktop environment | The packages on this page are GUI clients. You’ll need a desktop environment that can run graphical apps, and your system’s package manager must be able to meet their dependencies. |
If your package manager reports an unmet dependency, note the dependency name and your distribution version. Don’t force past the dependency or try to change package formats by renaming the file extension.
A single client may have several packages, but that doesn’t mean they’re interchangeable. Your operating system determines which installer format to use; the architecture determines whether the app can run on your device; and your distribution and its dependencies determine whether the package manager can install it. For example, system settings may describe both x64 and arm64 as “64-bit,” but that alone isn’t enough to choose a package. On Linux, amd64 and x86_64 in a filename refer to the same architecture class, not a specific processor brand.
When installing in a virtual machine, check the system and architecture shown inside the VM, not the host machine. The same applies when moving to a new computer: a package that worked on the old machine may not work on the new one, but you can usually import your subscription URL into the new client. If the installer reports an OS version or dependency mismatch, downloading the same package again won’t change your system. Save the exact error message, then decide whether to upgrade the OS or choose a compatible package.
Note your subscription group names, active server, and routing mode in the current client. Record any custom DNS settings or local listening ports too. If the client can export its config, save the file outside the app’s directory so it won’t be deleted along with app data if you uninstall. Subscription URLs may contain access credentials, so store backups securely and never post a full URL in a public forum or screenshot when asking for help.
Adding your subscription again usually restores the list provided by the service, but it may not restore manually added servers, your previously selected routing mode, or local overrides. Back these up separately: keep the subscription source, and save an export or notes for manual settings. When switching clients, import a compatible subscription first, then set up client-specific options again. Don’t copy the entire app data directory into another app.
After launching the client for the first time, make sure the main window opens and check that the server list and subscription groups look right. An empty list after a fresh install is normal. If an existing setup appears empty, clear any list filters and check the selected group and client. Installation doesn’t update your subscription or enable the system proxy. Handle each step separately to pinpoint where something went wrong.
When switching desktop clients, close the old window and make sure its background process has exited from the system tray. Two clients running at once may compete for the same port or change system proxy settings in turn. On a phone, Android may show a VPN connection request the first time you connect; check the app name in the prompt. Disconnect from the old client before testing the new one. Adjust routing, DNS, or TUN only after the basic connection works.
First identify whether the issue is with package selection, installation, or configuration, then follow the relevant steps.
No. Choose Desktop for a first-time installation, or stick with the classic edition if you prefer WPF. Save your config before switching, and close the old client before testing to prevent both apps from competing for local ports or changing system proxy settings.
The arm64 package is for systems that support arm64-v8a. The universal package includes multiple architectures supported by the app build and is usually larger. If you’re unsure of your device’s architecture, start with the universal package. It won’t fix an outdated Android version or a signature conflict.
The version shown on the card comes from the release manifest and may not be updated at the same time as the package name. Check the app, platform, and architecture first. If the downloaded package isn’t the version you expected, don’t overwrite your existing installation; wait for the manifest to be updated and check again.
A standard in-place update of the same app will usually keep its data, but don’t count on that after uninstalling and reinstalling, switching clients, or changing the config directory. Back up any exportable config before updating, note your subscription groups and routing settings separately, and check the list before connecting.
In v2rayN, add and update subscriptions under Subscription Groups. In v2rayNG, open Subscription Group Settings from the sidebar, then return to the list to update. Downloading a client doesn’t provide a subscription; get the subscription URL from your service provider or administrator.