Client downloads

V2Ray Download

Choose your platform first, then select the architecture and package format. Use v2rayN on desktop; for Android, v2rayNG is the recommended choice, while v2flyNG is an option when you need the v2fly core.

Windows downloads

Windows package requirements
System type64-bit operating system with an x64-based processor
File formatZIP; extract the archive before running the installer inside
RuntimeIf installation or launch reports a missing runtime, check the required component and architecture as prompted.

Check your system type and plan the migration

Go to Settings → System → About and check “System type.” Verify both the operating system’s bitness and the processor type; “64-bit” alone isn’t enough. ARM processors can run 64-bit systems without being x64. If your system reports an ARM-based processor, don’t treat this page’s x64 installer as a native ARM build.

Before switching from classic WPF to Desktop, exit the old client, including any instance still running in the notification area. Keep a recoverable copy of your configuration or subscription sources, then install the new edition. On first launch, check the selected server and routing before enabling the system proxy or TUN. If you’re only checking out the new interface, keeping your existing proxy settings makes it easier to tell installation issues from connection issues.

First setup after installation

Keep your subscription sources and manual settings

The installer includes only the client and components provided in that release. After installation, whether the server list is populated depends on the configuration you import. If you can still access the old device, identify which entries came from subscriptions and which were added manually. You can fetch subscriptions again from the same URL, but keep manual entries and local routes separately. When moving between operating systems, don’t assume the entire desktop configuration folder can be read directly by the mobile app.

Subscription URLs may contain access credentials, so hide the full URL in screenshots and troubleshooting notes. In the desktop client, save the URL in v2rayN’s “Subscription Group Settings,” then update it from “Subscription Groups.” On mobile, open “Subscription Group Settings” from the client menu, save the URL, then return to the list and update the subscription. After importing, make sure you’re viewing the right group and check the update result; an empty list alone doesn’t mean you need a different installer.

Check launch, connection, and app traffic separately

An open client window only confirms that the app has launched. After importing a configuration, select the intended server, then enable a proxy method for your platform. On Windows, check the “System Proxy” option from the v2rayN tray menu. The system proxy affects only apps that honor it. If you need to route more traffic, learn about the permissions and routing requirements of TUN mode. When troubleshooting for the first time, don’t change the server, system proxy, and routes all at once; otherwise, it’s hard to tell which change affected the result.

On Android, tapping Connect usually triggers a system VPN request the first time. If another app is already using the VPN, check the current system connection before deciding whether to switch. After granting permission, test with just one target app and note whether the issue occurs during import, launch, or access. A client showing as running doesn’t mean every app will be routed as expected.

Distinguish release information from the installed version when updating

The version shown on a card comes from the release manifest, and its download link points to the file mapped there. Neither tells you which version is actually installed on your device. After installation, check the client’s About screen or the system’s app information for the installed version. If your browser kept an older file with the same name, make sure you’re opening the installer you just downloaded before updating.

After updating, test with the configuration that worked before; don’t change subscriptions and routes at the same time. If your configuration isn’t listed, first check that you launched the new client instance, selected the right group, and migrated the old configuration. Keeping a recoverable copy of the old settings can save you from having to rebuild everything after an update.

See how to import subscriptions and connect · View installation guides for all platforms · Compare the three clients

Download FAQs

Find answers about versions, architectures, and update options.

Windows Desktop or classic WPF: which should you choose?

For a fresh install, start with the Desktop edition, which uses the Avalonia interface. If you already use the classic WPF edition and prefer its familiar layout, you can stay with WPF. Both downloads are for Windows x64.

How do I check which chip my Mac has?

Open About This Mac from the Apple menu. Choose the Apple Silicon installer if it shows an Apple chip, or the Intel installer if it shows an Intel processor.

What’s the difference between the Android arm64 and universal builds?

The arm64 build is for devices that support arm64-v8a. The universal build includes components for multiple processor architectures, so its file is usually larger. Consider it if you’re unsure of your device’s architecture, but make sure your Android version meets the requirements.

Can I use Linux DEB and RPM packages interchangeably?

No. Debian and Ubuntu users should generally choose DEB; Fedora and other RPM-based distributions should choose RPM. After matching the package format, check that the architecture and dependencies suit your system.

What should I back up before updating the client?

Back up your subscription URLs, manually added servers, and custom routes first. Before switching clients, check that the new client supports the protocols, transport, and security layer used by your existing configuration, then import it.