Downloads / GUI clients

V2Ray Client Downloads
Choose a Platform and Package

Choose v2rayN for desktop and v2rayNG for Android. Confirm your operating system, then download the build for your CPU architecture.

Free to use Open source Choose by architecture

Have a subscription URL? After installation, follow the subscription import steps. The client and server configuration are separate; the installer does not include a working server.

01 / Choose an operating system

Download options and system requirements

Each platform lists the most common packages first, followed by alternative architectures. After switching tabs, you can copy the address bar URL to save a link to the selected platform.

v2rayN · Windows

Recommended

Manifest version 7.24.1 · x64 package

Desktop edition

Download Desktop · x64

The newer cross-platform UI. A good starting point for new users, with a consistent interface and workflow when you use v2rayN on other desktop platforms.

Classic edition (WPF)

Download WPF · x64

A stable option with the classic Windows interface. Choose it if you’re already familiar with WPF menus and workflows.

Both downloads are ZIP archives. Extract the entire archive to its own folder, then run the installer inside and follow the prompts. Don’t launch it from the archive preview or mix files from the two editions in one folder.

Before installing on Windows
CheckRequirements and guidance
Operating systemWindows 10 or 11 with ongoing support is recommended. Check the requirements for your chosen client build for specific compatibility details.
ProcessorBoth downloads on this page are x64. Go to Settings → System → About to check your system type.
RuntimeIf startup reports a missing desktop runtime, check the component name and architecture in the error message. Don’t keep reinstalling the client.
PermissionsSystem proxy and TUN have different permission requirements. If you need TUN, check administrator permissions and virtual network interface availability.

Windows installation and migration

After the first launch, make sure the interface opens normally before importing a configuration. Don’t enable system proxy and TUN at the same time initially. First test the system proxy with a browser that follows system proxy settings. Once the basic connection works, adjust traffic routing to suit your apps.

Before switching from WPF to Desktop, use the client’s export or backup feature to save your configuration. Note your local listening ports, subscription groups, and custom routes separately. Quit the old client before launching the new one to prevent both from competing for the same ports. Switching interfaces doesn’t guarantee all preferences will carry over, so check the active server and proxy mode after importing your settings.

02 / What to do after installation

First connection checklist

Test the basic connection first, then add routing rules and expand traffic coverage. This makes it easier to pinpoint where something goes wrong.

Install → Import configuration → Test connection

Import first, then enable the proxy

In v2rayN, open Subscription Group → Subscription Group Settings, add a group, save the subscription URL, and update the subscription. Menu names may differ slightly between interface versions, but follow the same order: save the source, update the list, then select a server. On Android, import a subscription or configuration link from the add configuration screen.

When servers appear in the list, select one, then enable the system proxy or Android VPN connection. Test with an app that explicitly follows the selected proxy method. A successful latency test doesn’t prove that all apps are routed through the client, and one download speed test doesn’t establish long-term connection quality.

Set up routing and TUN after confirming the connection

Once the basic connection works, configure routing rules such as bypassing mainland China traffic as needed. Routing decides which outbound handles traffic that has already reached the client; it doesn’t automatically route traffic from every app into the client. If you need broader app coverage, review the TUN permission and conflict checks before enabling the mode.

03 / Download FAQs

Installation and updates FAQs

What else do I need after downloading a client?

You’ll also need a working server configuration or subscription URL. The client imports configurations, selects an outbound, and sets up a proxy; it does not provide a server. Once you have a configuration, import the subscription, select a server, and test the connection.

Should I choose Desktop or WPF for Windows?

For a first installation, start with Desktop, which uses the newer cross-platform interface. Choose WPF if you prefer the classic interface or want to keep familiar workflows. Both are v2rayN builds. Back up your configuration before switching, and don’t run both builds on the same ports.

What’s the difference between arm64 and universal Android builds?

arm64 is for devices that support 64-bit ARM apps; most mainstream phones released after 2015 are good candidates. The universal build supports multiple architectures and is a safer choice if you’re unsure. Check which app architectures your system supports before installing.

Do I need to uninstall the old client before updating?

Usually, back up your settings and update using the same installation method; uninstalling first isn’t necessary. Quit desktop clients before updating. Android apps can usually be installed over the existing version. If you see a signature mismatch warning, check the package source and build type before proceeding to avoid losing app data.

The version next to the download button differs from the number in the filename. Which should I trust?

The displayed version and package path are separate manifest fields and may update on different schedules. Check the client’s About page for the installed version. Choose a download by platform, CPU architecture, and package format—not by the number in its filename.

The client installed but won’t connect. Should I download it again?

First check that the subscription is imported, a server is selected, and system proxy or VPN permissions are enabled. Then review the logs. Recheck the download only if you see an installation issue such as a corrupted package, architecture mismatch, or failure to launch.

If the client launches but connections still fail, follow Troubleshooting by symptom. To compare the features of the three clients, see Choosing a Client.