client shelf

V2Ray client downloads,
choose a package for your platform

Use v2rayN on desktop and v2rayNG on Android. Check your operating system and CPU architecture before installing and importing a subscription.

  • Free forever
  • Open source
  • Graphical configuration
New here? Get started quickly →

download

Platform and architecture, download options

Each platform has the corresponding client and package formats. Version details appear on each card; check the installed client and system prompts for feature and compatibility information.

Windows downloads

v2rayN

Windows desktop client · x64

Recommended

Desktop

Next-generation cross-platform interface. Recommended for fresh installs.

Download Desktop · x64 ZIP archive; extract it, then run the installer

Classic WPF

A tried-and-true version with the familiar Windows desktop interface.

Download classic WPF · x64 ZIP archive; follow the installation prompts
7.24.1Core: Xray / V2FlyPackage architecture: x64

The main differences are the interface and runtime environment, not the proxy protocols. Desktop brings a next-generation interface to multiple desktop platforms, while WPF retains the classic Windows layout. If you already have a setup, stick with the version you know. Before migrating, export your subscription groups and custom routes so you don’t mistake an interface change for lost settings.

Both download options here are x64 packages. Before downloading, open Settings → System → About and confirm your system type. Once the download finishes, extract the entire archive before running the installer—don’t launch it from the archive utility’s temporary folder. If the installer reports a missing runtime component, follow its instructions instead of repeatedly switching nodes.

On first launch, check the local listening port, then import a subscription and select a node. The system proxy affects only apps that honor system proxy settings; it won’t automatically route every program. If an older version is still running in the background, both instances may try to use the same port. Exit the old process before testing the new version to help distinguish installation issues from connection issues.

Windows system requirements and installation checks

CheckWhat to look forBefore installing
System and architecture64-bit Windows; use the x64 packageCheck the system type in System Information. Refer to the installer prompts for compatibility with your specific Windows version.
Runtime environmentDesktop and WPF may have different dependenciesInstall any runtime components prompted for your chosen version, and keep the full program directory intact.
Permissions and portsStandard proxy mode and TUN have different permission requirementsTest standard proxy mode first. If you need TUN, check the prompts for elevated permissions and network drivers.

after install

Once installed, start with a subscription

Installation is just the first step. The client handles configuration and traffic routing; remote nodes must be provided separately. Follow these steps in order to make troubleshooting easier and avoid changing several settings at once.

01 / import

Import a subscription or node

Use a subscription or node share link you’re authorized to access. Create a subscription group, paste the link, and update it to see available nodes. Avoid copying extra spaces or line breaks. Subscription links may contain access credentials, so don’t share them or include them in public screenshots.

See how to import a subscription →

02 / mode

Choose how to route traffic

On desktop, check the client’s port before enabling the system proxy. On Android, confirm local VPN permission first. System proxy, routing mode, and TUN control different things: the system proxy directs apps to the client, routing determines where traffic goes next, and TUN changes which traffic enters the client.

Learn about routing rules →

03 / verify

Start and test the connection

Select a node and start it, then check the client logs, app proxy settings, and target website. A running status doesn’t mean every app is using the proxy. If a site won’t load, check the time, port, and proxy settings first, then look at DNS and rules. Change one setting at a time.

Troubleshoot connection issues →

How clients, cores, and configurations fit together

Project V is part of the open-source ecosystem behind proxy tools; V2Fly and Xray are related core families. Graphical clients organize subscriptions, nodes, ports, and routing settings into a working configuration. v2rayN is for desktop systems, while v2rayNG and v2flyNG are for Android. Choose a client based on both your device and the core features your configuration needs. The same protocol name doesn’t guarantee compatibility when transport or security layer extensions differ.

Updating the client doesn’t update your subscription or switch remote nodes. If something goes wrong after an update, compare your local settings with the previous configuration, then check the specific error in the logs. For details on protocols and DNS, see the quick reference and the DNS settings guide. If you’re new, follow the quick-start steps rather than changing every advanced setting at once.

download questions

Choosing a package, common questions

Check package format, architecture, and installation requirements before setting up subscriptions and connections.

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

For a fresh install, choose Desktop for its next-generation cross-platform interface. Classic WPF retains the familiar Windows layout and workflow. Export your configuration before migrating, and avoid running both versions on the same local port.

Should you download the arm64 or universal Android version?

Most phones released after 2015 are best served by arm64, but check which app architectures your device supports. If you’re unsure or the arm64 package is reported as incompatible, try the universal version. It includes multiple architectures, but older systems may still fall short of the client’s requirements.

What’s the difference between Linux deb and rpm packages?

Use deb on distributions such as Debian and Ubuntu, and rpm on distributions such as Fedora and RHEL. Check your distribution first, then choose x64 or arm64. Even with the right package format, dependencies and system library versions can differ.

Will updating the client keep my subscriptions and routing settings?

Whether your settings carry over depends on the client version, installation method, and configuration directory. Export your configuration before updating, note your subscription groups, ports, and custom routes, and fully exit the old process. Check each setting after the update; don’t assume everything migrates automatically.

Why can’t I connect after installing the client?

The client installer doesn’t include ready-to-use remote nodes. Import a subscription or node configuration you’re authorized to use, select a node, and start it. Then check your system proxy settings or local VPN permission. Installing the app alone doesn’t establish a proxy connection.

Why doesn’t the installer filename match the version shown on the card?

The version shown on the card and the file paths for each architecture come from different manifest fields and may update at different times. After downloading, check the actual version on the client’s About page. Use the installed client to confirm settings migration and feature support; don’t rely on the filename alone.