Clients, Installers & Architecture

V2Ray Client Downloads

Choose v2rayN for desktop or start with v2rayNG on Android. Find the installer for your OS and CPU architecture, then import a subscription and configure the proxy.

Free, open-source clients
Choose by architecture
Back up settings before updating

Windows installer

Two interfaces, one desktop client. Pick the version that suits your preferences.

v2rayN

Desktop version / classic WPF version

Recommended

Download Desktop · x64 Download classic WPF · x64

7.24.1Windows · x64 · ZIP

The Desktop version uses a modern cross-platform UI, making it a good choice for first-time users and anyone who wants a consistent experience across desktop operating systems. The WPF version is the stable classic edition with a familiar Windows layout. Choose it if you're already comfortable with its configuration and workflow.

The download is a ZIP archive. Extract all files in your file manager, then run the installer and follow the setup wizard. Don't launch it from the archive preview. The two versions have separate installers; you don't need to run both to use the same subscription.

Import a subscription after installation →

Before you install

System and runtime requirements

Check	What to look for
Processor	Both downloads on this page are x64
Operating system	Windows 10 or 11 with ongoing security updates is recommended; check the installer for compatibility details
Runtime	Install the desktop runtime required by the version you choose
Permissions	Standard proxy and TUN require different permissions; grant access when prompted to enable TUN

Check Settings > System > About for your system type. Don't infer the architecture from your computer's brand alone.

After installation: what to check

On first launch, open Subscription Groups, add your existing subscription, and update it. Once servers appear in the list, select one and run a real connection test, then configure the system proxy. A successful installation only means the app starts; it doesn't mean browser traffic is being routed through the proxy.

If the installer reports a missing runtime, check which runtime and architecture it requires. Don't assume the two interface versions use the same dependencies. If the app starts but its logs report a port conflict, quit any other running proxy client and check the local port settings. Reinstalling usually won't resolve a port conflict.

macOS installer

Check your chip under About This Mac, then choose the matching DMG.

v2rayN

Apple Silicon / Intel

Download Apple silicon · arm64 Download Intel · x64

7.24.1macOS · DMG

Open About This Mac from the Apple menu. If it lists an Apple chip, choose the Apple silicon arm64 package. If it lists an Intel processor, choose the x64 package. Matching the architecture matters more than the file size; don't choose Intel just because the filename includes “64.”

After downloading, open the DMG and drag the app into the Applications folder. Launch it from there. Don't run it long-term from the mounted disk image: once you eject it, the app may be unavailable, or updates may be written to the wrong location.

View desktop setup steps →

Before you install

Chip and permissions

Check	What to look for
Apple silicon	Use the arm64 DMG
Intel processor	Use the x64 DMG
macOS version	Check About This Mac for your version; refer to the app's installation or startup messages for the minimum supported version
Network permissions	Follow system prompts when changing the system proxy or enabling TUN

If the app still won't start with the correct architecture, record the full error and check whether it's a compatibility issue or a macOS security warning.

Startup warnings and proxy permissions

If macOS shows a security warning, first confirm the download source and package architecture, then review the relevant details under System Settings > Privacy & Security. Once you've verified the source, Control-click the app and choose Open. Don't disable system security entirely to launch one app, and don't use bypass steps on files from unknown sources.

After importing your configuration, test the connection with the system proxy before trying TUN. The two modes route traffic differently and require different permissions. If you use other network tools, quit one of them before testing to avoid conflicting changes to system proxy and routing settings. If your browser can't connect after you quit the client, check for a leftover manual proxy in system network settings.

Android installers

Start with v2rayNG. Consider v2flyNG if you need compatibility with the V2Fly core.

v2rayNG

Android · Xray core

Recommended

Download v2rayNG · arm64 Download v2rayNG · universal

2.2.6Android · APK

Most mainstream phones released since 2015 use arm64. Keep in mind that a 64-bit processor doesn't necessarily mean the operating system can install 64-bit apps. If you're unsure of your device's architecture, or the arm64 package is reported as incompatible, try the universal version.

v2rayNG uses the Xray core and supports subscription import, server selection, and per-app proxying on Android. The first time you connect, Android will show a VPN permission prompt. Verify the app name before granting access; this permission doesn't provide a subscription or server.

See how to import a v2rayNG subscription →

v2flyNG

Android · V2Fly core

Alternative

Download v2flyNG · arm64 Download v2flyNG · universal

1.10.31Android · APK

Choose v2flyNG if you need the V2Fly core and your existing configuration is compatible with it. It's a separate app from v2rayNG. Similar names don't mean they support the same protocols, transport options, or configuration behavior.

When switching from another app, import the original subscription or configuration again, then check your routing, DNS, and per-app proxy settings. Don't copy the app's private data directory. You can keep settings in both apps, but only let one app establish a VPN connection at a time while testing.

Before you install

Architecture and installation permissions

Check	What to look for
arm64	For devices that support arm64-v8a apps
Universal version	Includes multiple architectures; choose it if you're unsure of your device's architecture
macOS version	Check the selected APK's compatibility notice; the universal version doesn't support every older Android release
Installation permission	Temporarily allow the browser or file manager you're using to install apps
Connection permission	Approve Android's VPN permission prompt the first time you connect

After installation, you can turn off Allow from this source for the browser or file manager.

Installation failures and background connections

If Android says the app wasn't installed, check available storage and system compatibility first, then see whether an app with the same name is already installed. Apps from different distribution channels may have different signatures and can't always update over each other. Don't uninstall and reinstall straight away; first make sure you can export your configuration and save your subscription source and custom settings.

If the connection drops after the screen has been off for a while, check Android's battery optimization and background activity limits. Decide whether to allow persistent background activity based on your connection needs and battery use. To proxy only certain apps, use per-app proxying to narrow the scope, then check that each target app is included.

Linux installers

Check your distribution's package format, then choose x64 or arm64.

v2rayN

Linux graphical desktop client

Download deb package · x64 Download rpm package · x64

arm64 devices

deb · arm64 rpm · arm64

7.24.1Linux · deb / rpm

Debian, Ubuntu, and their derivatives usually use deb packages; Fedora, RHEL, and their derivatives usually use rpm. Matching the package format is only the first step—your distribution version, desktop environment, and system dependencies also affect installation.

Double-click the package to review dependency and compatibility notices in your system's graphical installer. If dependencies can't be satisfied, check your distribution version instead of forcing the installation. This is a graphical desktop client and requires an available desktop session.

Learn how to configure TUN mode →

Before you install

Package format and desktop environment

Check	What to look for
x64	For amd64 / x86_64 systems
arm64	For arm64 / aarch64 systems
Package format	Choose deb or rpm for your distribution
Graphical environment	Requires a desktop session and the graphical runtime dependencies used by the app
Compatibility	Check dependencies with your package manager; the same file extension doesn't mean a package supports every distribution

Your system's About or System Information page usually shows the distribution version and CPU architecture.

Desktop proxy vs. per-app proxy

Whether the system proxy affects a particular app depends on your desktop environment and whether that app reads system proxy settings. A working browser connection doesn't mean every app is routed through the proxy. Test with an app that explicitly supports proxy settings, then choose an in-app proxy or TUN based on your needs.

Before enabling TUN, review the permissions and routing guidance and check that no other tool is already routing network traffic. Don't run your entire graphical desktop session with elevated privileges. If the system proxy isn't restored after an update, check the client status and desktop network settings, then review the app's own proxy configuration.

From installation to a working connection

What to check before and after downloading

The installer gets the app onto your device; subscriptions, routing, and proxy mode determine how connections work. Check them separately to pinpoint problems faster.

Before downloading: check your device and configuration source

First check your operating system, CPU architecture, and package format. A computer or phone's product name doesn't tell you its architecture; devices in the same product line may use different processors. The requirements listed here help you choose a package, but don't guarantee compatibility with every older system. Always check the installer's prompts.

For first-time use, you'll also need a subscription or server configuration you're authorized to use. The client and subscription service are separate: downloading the app doesn't provide network service, and updating the client doesn't extend a subscription. Contact the configuration provider to confirm service availability.

Before updating: save your settings

Record your subscription groups, routing presets, DNS, local listening ports, and per-app proxy rules. Use the client's export or backup feature if available. If backing up files manually, quit the client first to avoid copying data while it's being written.

Backups may contain server credentials and subscription access details, so store them somewhere only you can access. Quit the old app before updating. Afterward, check your server list and routing, then restore the system proxy or TUN. Don't run both versions at once while testing the same listening port.

Basic checks after installation

After adding a subscription, update it once and make sure group filters aren't hiding servers. Select a server and run a real connection test, then enable the proxy mode you need. A test only reflects the connection at that moment; it doesn't verify access from your target app. If something fails, start with the specific error in the logs.

For more setup help, follow the import and connection steps in Getting Started, then see Advanced Setup for routing, DNS, and TUN. If you encounter unfamiliar terms, check the glossary. Change one type of setting at a time and note the original value so you can revert it.

Installer FAQs

Choosing, installing, and updating

These questions cover downloads and installation. For more help troubleshooting connection issues, see the FAQ.

Which should you choose: the Windows Desktop or WPF version?

For a first installation, start with the Desktop version, which uses a modern cross-platform interface. If you prefer the classic Windows layout, choose the stable WPF version. Both manage proxy configurations, so you don't need to install both. Before switching, back up your subscription groups, routing, and custom settings, then import them using a method supported by the new version.

What's the difference between the Android arm64 and universal versions?

Most mainstream phones released since 2015 use arm64, but check which app architectures your device actually supports. The universal version includes multiple architectures and is worth trying if you're unsure of your device's architecture or the arm64 package won't install; it is usually larger. If installation fails, also check your Android version, available storage, and whether an existing app has a compatible signature.

Why is there no server after installing the client?

The client reads your configuration and routes traffic; the installer does not include a usable server. You'll need a subscription URL or server configuration that you're authorized to use. Add and update it in a subscription group, or import it from your clipboard. Subscription links may contain access credentials, so don't share the full link or screenshots that reveal them.

What should I do if macOS says the app can't be opened?

First, make sure the installer matches your Mac's chip and that you've moved the app to the Applications folder. After verifying the download source, Control-click the app in Finder and choose Open, or check the notice under System Settings > Privacy & Security. Don't disable system security entirely just to run one app. If the error persists, note the full message before troubleshooting further.

What should I back up before updating the client?

Record your subscription groups, current server, routing presets, DNS, custom rules, and local listening ports. Use the client's built-in export or backup feature whenever possible. Backup files may contain sensitive settings, so store them somewhere only you can access. Quit the old client before updating, then check system proxy, TUN, and routing settings afterward.

The version shown on the page doesn't match the installer filename. Which should I trust?

The version displayed on the page and the download filename may temporarily differ while a release is being updated. The filename identifies the installer; after installation, check the client's About or Check for Updates page for the installed version. Don't rely on the page label alone to confirm an upgrade. If you need to keep your existing settings, back them up first and review the new version's migration notes.