Installers · OS and architecture

V2Ray client downloads

Select your operating system, then choose v2rayN, v2rayNG, or v2flyNG based on your CPU architecture and preferred installation method.

Windows installers

v2rayN

Recommended

Release manifest · 7.24.1

The Desktop edition uses a modern cross-platform interface, making it a good fit for new installations and users who want a consistent experience across desktop operating systems. The WPF edition retains the classic Windows interface and familiar menu layout. Both are full clients; choose one rather than installing both.

System requirements and pre-install checks

CheckDetails
System typeGo to Settings → System → About and confirm that Windows is 64-bit and the processor architecture is x64. Both packages on this page are for x64.
Installer formatExtract the ZIP file completely before opening the installer inside. Don’t launch it from the archive preview.
Runtime dependenciesIf a runtime error appears at launch, note the version and architecture mentioned in the message, install the required runtime, and try again.

When migrating from an older version, save your configuration first and exit the old process from the system tray. Closing the window doesn’t always quit the app. If the new interface reports that a local port is in use, check whether an older instance or another proxy client is still running in the background. Start one version and verify your configuration before deciding whether to remove the old one.

Install, update, and connect for the first time

Understand architecture, package format, and interface edition

Choosing an installer involves three separate decisions. Architecture determines whether the program can run on your system; package format determines which installer to use; interface edition determines the client’s layout. Confusing these can lead to questions like, “My system is 64-bit, so why can’t I install this?” Check the architecture in your system’s About page, then verify the architecture and file extension in the package name. Consider the interface edition last. When moving to another device, choose a package for that device instead of copying the executable from your old one.

Keep a restorable copy of your configuration before updating

Note which client and interface edition you use, along with the location of its configuration. If the client supports exporting, save the items you need somewhere secure and confirm that the exported file can be opened. Subscription URLs may contain access credentials, so handle backups and troubleshooting screenshots separately; don’t post a full URL in a public forum. After reinstalling, check that your subscription groups and selected connection are back before changing routing or proxy settings. This makes it easier to tell whether an issue is due to a configuration that wasn’t migrated or a setting that needs adjustment in the new version.

Verify in order: launch, import, connect

A successful installer exit only means the installation process is complete. First open the client and confirm it stays running. Then import your existing configuration and check that the expected entries appear. Finally, start a connection and test it in the app you actually use. When troubleshooting for the first time, don’t change the subscription URL, routing rules, and traffic interception mode all at once. Otherwise, even if the connection works again, it’s hard to tell which change fixed it. For detailed steps, see the configuration import guide.

Choosing an installer and troubleshooting

Download FAQs

Why might the version shown here differ from the version in the filename?

The version shown on the card comes from the app release manifest, while the filename identifies the specific installer. They may be updated at different times. To confirm the installed version, check the version shown in the client’s About page.

Do I need to uninstall the old version before updating?

For the same client and interface branch, back up your configuration first, then update as prompted by your system. Before switching interface versions, installation sources, or configuration folders, check how to migrate your data to avoid deleting local files during uninstall.

Why can’t I connect after installing the client?

Installation only prepares the client. You still need to import a valid configuration, select a connection, and grant any required permissions or enable the appropriate proxy mode. Check the client logs first to determine whether the issue is with the configuration, permissions, or connection.

Why is the installer incompatible even though my device is 64-bit?

x64 and arm64 are both 64-bit architectures, but they use different instruction sets. Check the architecture reported by your operating system, then verify that the OS version and installer format are compatible.

Where should I look if a download is interrupted or the system blocks installation?

First confirm that the browser finished downloading the file, then check the exact system error. Architecture mismatches, missing dependencies, and device management policies require different fixes. Don’t disable system protections just to install the client.

Troubleshoot connection issues →