GUI Clients · Downloads

V2Ray Client Downloads

Choose your operating system first, then select v2rayN, v2rayNG, or v2flyNG by processor architecture and package format.

Desktop
ZIP / DMG / DEB / RPM
Mobile
APK

Choose a package by platform

Choose based on the device that will run the client, not the device you’re using to browse this page.

Windows client

v2rayN

v2rayN

Windows · 7.24.1

Top pick
Desktop
Download Desktop · x64 v2rayN-Desktop-Setup-x64-7.24.1.zip

A next-generation cross-platform interface. Recommended for first-time installs or when you want a consistent workflow across desktop operating systems.

Classic WPF
Download Classic WPF · x64 v2rayN-Setup-x64-7.24.1.zip

A stable release that retains the classic Windows interface. Choose it if you’re used to WPF or following instructions written for the older interface.

Windows system requirements

CheckRequirementsHow to check
Operating system and architectureA supported 64-bit version of Windows is recommended. The builds here are x64.Open Settings → System → About and check System type.
Package formatBoth ZIP files are archives containing the installer.Extract the entire archive to a local folder, then run the installer from the extracted folder.
Runtime requirementsRuntime requirements may differ between interface builds.If startup reports a missing runtime component, note its name and version, then follow the requirements for that build.

Choose either Desktop or Classic WPF; you don’t need both. When switching from Classic, exit the old client from the notification area before launching Desktop. If both instances listen on the same port, the new one may not be able to start the local proxy.

If a desktop shortcut still opens the old version after an update, check the running version on the client’s About page, then create a new shortcut from the updated installation folder. If startup fails, first identify whether the archive was incompletely extracted, the installer did not finish, or the app reported an error after launch. Troubleshoot each stage separately.

Installation and upgrade checks

Check each stage in order: download, installation, and first launch. Change one thing at a time to pinpoint where the problem occurs.

Before downloading: identify the target device

On the target device, note the operating system, version, and architecture. If you’re downloading for another computer or a virtual machine, choose based on that target system. The computer running the browser determines where the file is saved first, not which package you need.

Package format and architecture are independent requirements. For example, x64 DEB and RPM packages use different installation tools, while x64 and arm64 DEB packages target different system architectures. Check both, then verify distribution compatibility.

When preparing packages for multiple devices, organize downloads by operating system and architecture. Record the client name, architecture, and package format in your handoff notes. Don’t rename every package to the same filename, or it’ll be difficult to tell which one you chose if something goes wrong.

Before upgrading: organize your existing configuration

Keep installation files separate from user data. User data may include subscription groups, manually added servers, local listening ports, and custom routing. Use the old client’s export or backup feature before installing the new version.

Check whether the export includes manually created entries and local settings. If it only saves subscription URLs, also note your existing proxy mode and ports. Subscription URLs and export files may contain credentials, so store them somewhere you control.

Quit the old client before replacing it. Closing the main window may leave it running in the notification area or menu bar. Confirm that the old process has exited before launching the new version. This helps prevent port conflicts and avoids mistaking the old instance’s status for the upgraded client’s.

During installation: follow the system prompts

If you can’t open the file, first confirm the download is complete and that the file extension matches the selected download. If the installer opens, the system can handle that package format. Next, use the installation prompts to distinguish permission issues, missing dependencies, and conflicts with existing apps.

When a permission prompt appears, check the installation source and destination it identifies. On a device managed by your employer or school, follow the administrator’s instructions. For dependency issues, save the exact error message and identify the missing component instead of trying a package for another platform.

If the system says it can’t install an older version, first check the version of the existing client. Before rolling back, make sure you have a recoverable copy of your configuration. Newer configuration files may contain settings the older client doesn’t recognize, so review the configuration again after downgrading.

After launch: restore one configuration item first

On first launch, confirm that you opened the expected client and version. Then import a subscription or server configuration you’re authorized to use, select an entry, and follow the Getting Started guide to check the mode and connection.

After migration, check your subscription groups, selected entry, and local ports. If you changed a port, also verify the proxy address in apps such as your browser and terminal. If a listening port is already in use, see how to troubleshoot a local port conflict.

Successful installation and a working connection are two different things. If the interface opens, the app has started—that’s all it confirms. To test the connection, use one app and one configuration, note whether the error comes from the client or the app or is a request timeout, then decide which layer to investigate.

Download FAQs

Find answers by package type, compatibility issue, or post-installation status.

Which should you choose: the Windows Desktop or Classic WPF version?

For a first install, choose Desktop for its cross-platform interface. Choose Classic WPF if you prefer the familiar classic interface or already use a WPF-based workflow. Both packages are x64.

Which macOS build should you download: Apple Silicon or Intel?

Open About This Mac from the Apple menu. Choose arm64 for an Apple chip or x64 for an Intel processor. Don’t choose based on the Mac’s purchase year alone.

Will the Android universal build fix every installation issue?

No. The universal build supports multiple architectures, but installation can still be limited by the Android version, app signatures, or device policies. If the device reports a conflict with an installed app, back up your configuration and check where the existing app came from.

Can you use Linux DEB and RPM packages interchangeably?

No. Choose a package format supported by your distribution, then check the processor architecture and dependencies. The current RPM filename includes el10, so confirm your system is compatible with this build before installing.

Why is there no server to connect to after installation?

The package contains only the client. Before using it, import a subscription or server configuration you’re authorized to use, select an entry, and follow the Getting Started guide to test the connection.

The version on the card differs from the version in the package filename. Which one should I trust?

The card shows the app version listed in the manifest; the filename identifies the download package. To check the installed version, see the client’s About page or the app details in your system settings.