GUI clients Free · Open source

V2Ray Downloads
v2rayN / v2rayNG

Choose a platform and installer ↓ View installation guide

For desktop, choose v2rayN; for Android, start with v2rayNG. Check your operating system and processor architecture before downloading. Import subscriptions, configure routing, and test the connection after installation.

Desktop / classic WPF arm64 / x64 Subscription import

Choose an installer by platform

Switch platforms using the tabs. Before downloading, check the architecture and format in the package name. Don’t try to install a package built for another operating system.

v2rayN

v2rayN

Recommended 7.24.1

Windows x64 installers. The desktop edition has a newer cross-platform UI; the WPF edition retains the classic interface and layout.

Download Desktop edition

A good starting point for new installs, with an interface consistent with other desktop platforms.

Download classic WPF edition

A stable classic edition for users who prefer traditional menus and server lists.

Both download links provide ZIP archives. After downloading, extract the entire archive before running the installer; don’t launch it from the archive preview. If the setup wizard reports a missing runtime, install the components specified for that release. Requirements from an older version don’t necessarily apply to every release.

The desktop and WPF editions aren’t different proxy protocols, and a newer-looking interface doesn’t mean a better connection. Before switching, back up subscription groups, routing rules, and personal settings. On first launch, test one configuration before restoring complex rules so you can spot migration differences.

Import a subscription after installation →

Installer, configuration, and connection steps

Check your device and architecture

First check the operating system, processor, and app bitness in System Information, then choose the package for your platform. The x64 or arm64 label and installer format indicate compatibility, not a feature tier. A processor’s advertised specs alone can’t confirm that an older device will run a newer app.

If the system reports that a package is incompatible, note the exact message and recheck the architecture. Before switching clients, rule out package format and OS version issues.

Import a subscription after installation

The client stores configurations and manages connections; it doesn’t include a remote service. Prepare a subscription URL or share link you’re authorized to use, and make sure its format is supported by the client. Subscription URLs and individual share links serve different purposes, so use the appropriate import option.

Subscriptions may contain access credentials. Don’t share them in public screenshots, discussion forums, or with untrusted conversion services. If an import fails, first check that the copied content is complete.

View the subscription import steps →

Test first, then configure routing

After importing, refresh the group, select a configuration, and enable a connection mode. The desktop system proxy controls how apps connect through the client; routing determines which outbound path traffic uses once it reaches the client. These settings are related, but they aren’t the same switch.

First confirm that basic web access works and logs look normal. Then configure custom routes, app-level routing, or TUN. Change one type of setting at a time to make troubleshooting clearer.

Continue to the full guide →

Before updating or migrating

Save your working configuration before updating. A subscription URL can only retrieve the content provided by the subscription; it doesn’t back up personal settings. Record custom routes, DNS choices, local listening ports, keyboard shortcuts, and app-level routing separately. Exported files may contain sensitive settings, so store them somewhere you control.

Where possible, stay with the same client, installation channel, and upgrade path. When migrating between clients, re-import the original subscription or share link and configure routes individually instead of copying a private data directory. If the installer reports a signature or package conflict, find out why before proceeding; uninstalling may also delete data saved by the app.

After updating, open About to confirm the installed version, then check subscription groups, the selected configuration, and proxy mode. Opening the main window doesn’t confirm that the connection works; test at least one app you use regularly and check the runtime logs. Quit older clients you no longer need to prevent leftover system proxy settings or background connections from affecting the result.

Project V is the starting point for an ecosystem of related open-source proxy technologies. V2Fly and Xray are separate core development branches, while GUI clients provide visual configuration tools. Choose a client based on platform, configuration compatibility, and maintenance needs—not its core name alone. For differences in protocols and transport settings, see the client comparison.

Common download and installation questions

Windows: desktop edition or classic WPF edition?

For a first install, consider the Desktop edition with its newer cross-platform interface. Choose WPF if you prefer the classic layout and familiar workflows. Both are v2rayN; the interface alone does not indicate protocol support, so check the actual version and configuration. Back up subscriptions, routing rules, and personal settings before switching, then test before migrating.

Android: arm64 or universal APK?

Most mainstream phones released after 2015 can start with arm64, but the deciding factor is the app architecture supported by the operating system. Some devices have 64-bit processors but run a 32-bit OS, so an arm64 APK may not install. If you’re unsure, choose the universal build. If installation fails, check the OS version, signature conflicts, and available storage.

Why does the v2rayNG version shown differ from the installer filename?

The displayed version and installer URL come from different fields in the release manifest, so they may not be in sync. The current static manifest lists v2rayNG version 2.2.6, while the installer filename says 2.3.11. The page preserves the manifest values; don’t infer the version field from the filename. Check the client’s About page for the installed version.

Why can’t I connect right after installing the client?

The client manages configurations and routes traffic; it does not include a ready-to-use remote service. After installing, import a subscription or share link you’re authorized to use, refresh the group, select a configuration, and enable the appropriate system proxy or connection mode. If the connection fails, check the runtime logs first. A successful installation does not mean the service is available.

Will updating the installer keep my subscriptions and routing rules?

A normal in-place update of the same client usually retains its configuration, but installation method, signing, data directories, and cross-version migrations can affect the result. Back up or export settings before updating, and note custom routes and local ports. Don’t uninstall to resolve an installation conflict until you’ve confirmed the configuration is saved.

What if the download won’t start or the installer won’t open?

Check the browser’s downloads list for a blocked, paused, or incomplete task, then check available disk space and whether the installer format is supported by your system. If the download fails, reload this page and try again. If the file downloaded but won’t install, verify the OS, processor architecture, and installation permissions. Keep the full error message for troubleshooting.