Client Releases / Platform Selection

V2Ray Client Downloads

For desktop, choose v2rayN. For Android, v2rayNG is the recommended choice; v2flyNG is another option if it better fits your configuration. Select your OS first, then check the processor architecture and package type.

Choose a package by operating system

v2rayN

v2rayN

Windows x64 · 7.24.1
Recommended

The desktop edition offers a modern, cross-platform proxy interface. It's a good fit for first-time users and anyone who wants a similar experience across desktop operating systems. WPF retains the classic Windows interface, making it a natural choice if you're familiar with its menus and configuration workflow. These are two interface editions of the same client; you don't need both to support a particular subscription.

Both downloads are ZIP files containing an installer. Extract the archive to a writable folder, then run the installer inside. Don't launch it from the archive preview. Before upgrading or switching editions, note where your configuration is stored and exit the old client from the system tray.

Windows requirements and how to choose
CheckHow to verify
System typeGo to Settings → System → About and check System type. This page offers x64 packages; a “64-bit” label alone doesn't confirm that your system is x64.
Runtime environmentCheck the release notes for the minimum Windows version and runtime requirements. If startup reports a missing runtime component, verify its name, version, and architecture.
Installation permissionsOn a managed device, check your organization's software installation policy first. Being able to run the client doesn't necessarily mean you have permission to create a virtual network adapter.
Installation Order / Configuration Migration

Three things to check before installing

Check OS version and architecture separately

If installation fails, first determine whether you chose the wrong package or the device doesn't meet the runtime requirements. The OS version determines which APIs and runtime libraries are available; the architecture determines whether the included program can run in your environment. Neither tells you the other. Two 64-bit computers may use different architectures—one x64, the other ARM64. Even with the same processor, different OS versions can support different client releases. When helping someone remotely, ask them to check the target device's details instead of guessing from your own device model.

Match the package format to the installation method

The file extension determines which program handles a download. Extract ZIP files, open DMG disk images, install APK files through Android's installer, and use the relevant package manager for deb and rpm files. Seeing a download in your browser's history doesn't mean installation is complete. If the system says it can't open a file, check that the download finished and that the format is supported by your OS. Don't rename an extension to try installing a package on another platform; changing the name doesn't convert the package or its executable.

Know whether you're installing, upgrading, or switching clients

A new installation requires the right package and runtime environment. An in-place upgrade also depends on the version, release channel, and existing data. When switching clients, check configuration compatibility separately; being able to import a subscription doesn't mean every entry will work. If the old client had multiple groups, note the selected group, frequently used servers, proxy mode, and custom routing rules. Store backups containing subscription URLs or authentication details somewhere secure; don't upload or forward them with troubleshooting screenshots.

Verify after first launch and upgrades

After installation, make sure the interface opens normally, then test with one configuration you're authorized to use. Don't change subscriptions, routing rules, and traffic interception mode all at once, or it will be hard to identify the cause if something fails. If you used the system proxy before, you can keep using it after upgrading to test apps that follow system proxy settings. Test TUN separately if needed. These modes route traffic differently: a successful browser test doesn't prove other apps use the same route.

During migration, check in this order: group is visible → entries are readable → one connection works → the target app can access the network. If entries don't appear after a subscription update, check the import or update logs first. If an entry appears but won't connect, check its protocol, transport, and security layer. If the client reports a connection but nothing changes in the target app, check the proxy mode and which routing rule applies. Troubleshooting these three layers makes it easier to keep existing settings and diagnostic clues than simply reinstalling.

If the problem started after an upgrade, note the step where it occurred and any system message, then compare the settings with your backup. On desktop, check whether the old process is still running in the system tray and whether the system proxy is restored as expected when you quit. On mobile, disconnect the previous client before switching. For step-by-step instructions, see the subscription import and connection guide. If an entry may be incompatible with the core, see the protocol and core reference.

Download and installation FAQs

Which should you choose: the Windows desktop edition or the classic WPF edition?

For a first-time installation, start with the desktop edition. Choose WPF if you prefer the classic Windows interface and menu layout. Back up your configuration before switching editions, and avoid letting both clients modify the system proxy when launching the new version for the first time.

What should I do if an Android update is blocked because the signatures don't match?

Check the release channel of the installed version and, if possible, get the update from the same channel. If you need to switch channels, back up your configuration and make sure you can restore it before uninstalling the old version and installing the new one. Uninstalling may erase app data.

What should I do if macOS says the downloaded app isn't compatible with this computer?

Check your chip or processor in About This Mac, then compare your macOS version with the release requirements. Choose the ARM64 build for Apple silicon or the x64 build for Intel Macs. The right architecture doesn't guarantee that your macOS version is supported.

Can I install the same Linux package format on every distribution?

No. Choose deb or rpm based on your distribution, then check the processor architecture and target distribution. In particular, don't force-install an rpm marked el10 on another distribution just because it supports rpm.

Why aren't there any servers in the client after installation?

The client installer doesn't include subscriptions or server configurations. Open the client and import a subscription URL you’re authorized to use, or add an individual server configuration. If the list is still empty, check the import or update logs.