DOWNLOAD / Package index

V2Ray Client Downloads

Choose your operating system, then your architecture. Use v2rayN on desktop systems, or choose v2rayNG or v2flyNG for Android.

  • 01 Operating system
  • 02 Processor architecture
  • 03 Package format

Windows downloads

v2rayN

Recommended

Listed version 7.24.1 · x64

Desktop uses a next-generation cross-platform interface. It's a good choice for a first install or if you use v2rayN on computers running different operating systems.

Classic WPF is the stable edition with the traditional Windows interface. Stick with WPF if you're used to the older menus and system tray layout. Before switching editions, note your current settings; don't assume both editions use the same configuration files.

Windows requirements

RequirementPackage on this page
System type64-bit Windows with an x64 processor
Package formatZIP archive; extract it before running the installer

Go to Settings → System → About and check System type. Seeing “64-bit operating system” isn't enough; also confirm that the processor is x64. Don't run the installer from the archive preview.

Before upgrading, quit the old client from the system tray. If your browser still connects to the old port after the new version starts, compare the client's listening port with your system proxy settings. There's no need to re-import your subscription.

INSTALL / Installation and migration

Fresh installs and in-place updates

For a fresh install, check that the client launches. For an in-place update, also confirm that your existing settings are preserved.

First install: make sure the client launches

After downloading, check your browser's downloads list to confirm the download is complete, then open the file from its actual save location. Once the app opens, make sure the main window works; don't rush to enable the system proxy or launch at login. If you see an architecture or dependency warning during installation, fix the package selection first. Importing subscriptions or changing routes won't usually help at this stage.

Once the client launches normally, import a subscription you're authorized to use, refresh it, and select a node. For testing, start with a single browser or app and note the proxy endpoint and routing mode. If the test fails, check those two items first. Don't change the package, node, and DNS settings all at once, or you won't know what made a difference.

See the subscription import and connection guide →

In-place updates: keep your settings before replacing the client

Before upgrading, note the client name, current version, installation method, and configuration location. Back up subscription groups, custom routing rules, and local listening ports. If a subscription URL contains access credentials, keep it on your own device—don't share it in public logs or screenshots. If there's no single export option, record your settings by section so you don't have to troubleshoot everything from scratch after migrating.

After upgrading, check that your subscription groups are still there, refresh them manually, and confirm that your system proxy points to the current client's port. Seeing old nodes doesn't mean the new process is routing traffic. If something goes wrong, note what you did and the message you saw before deciding whether to restore the old settings. Don't repeatedly uninstall the app or leave multiple copies running while troubleshooting.

Find troubleshooting steps by symptom →

FAQ / Download questions

Packages, versions, and updates

Which v2rayN edition should you choose: Desktop or classic WPF?

For a first install, choose Desktop, with its next-generation cross-platform interface. If you prefer the classic Windows interface, choose the stable WPF edition. Before switching editions, back up your settings and check that your subscription groups, routing rules, and proxy ports are preserved.

Can the Android universal package update an installed arm64 version?

The universal package addresses architecture compatibility, but it may not install over an existing version. Android also checks the app package name, signing certificate, and version. If an update is rejected, read the installer message and keep the existing app's settings; don't make uninstalling your first step.

Why might the listed version differ from the version in the filename?

The version shown on a card comes from the client's release listing, while each download link points to a file for a specific platform and architecture. These versions may not match. Choose a package based on your system and architecture; check the client's About page to confirm the installed version.

Will updating the client remove my subscriptions and routing rules?

Whether your data is preserved depends on how you update and where settings are stored—not just on the client name. Back up subscription groups, custom routing rules, and local port settings first. After updating, check them before enabling the system proxy. On mobile, don't uninstall the old app without a backup.

Can I connect as soon as the client is installed?

The installer provides the client only. Import a subscription or node configuration you're authorized to use, select a node, then configure the system proxy or start the connection for your platform. Opening the client confirms only that installation succeeded; it doesn't mean nodes have been imported or app traffic is being routed.