Client installers / platforms and architectures

Download V2Ray clientsv2rayN and Android clients

Choose v2rayN for desktop and v2rayNG for Android. Select your operating system first, then confirm your processor architecture. After installation, import a valid subscription or server configuration.

Free to use Open source New to setup? Read the quick-start guide →

Choose an operating system

Installer for your platform

Check the architecture in the package name before comparing file sizes.

Windows: two v2rayN editions

v2rayN

Windows desktop client · x64

Recommended 7.24.1

Desktop edition

A newer cross-platform UI, ideal for a first install.

Download Desktop · x64 ZIP archive · extract before running

Classic WPF edition

A stable classic edition with the familiar Windows interface.

Download classic WPF · x64 ZIP archive · use in a separate directory

Choose one edition; there’s no need to install both. Desktop uses a newer cross-platform interface and suits users who want a consistent experience across desktop operating systems. WPF is the classic Windows edition for users who already know its menus and configuration workflow. The editions may differ in settings, layout, and runtime requirements, so archive size alone won’t tell you which is the better fit.

Extract the entire archive to a permanent directory where you have write access, then launch the program from there. Don’t run it from an archive preview or extract only the executable. If Windows reports a missing runtime, check the component name, architecture, and required version, then install what’s missing. Downloading the same archive again usually won’t resolve a missing runtime.

Before switching from WPF to Desktop, export your settings and save custom routing rules separately. Install the new edition in a different directory, then import your settings and test the connection before doing anything with the old directory. Check local listening ports, subscription groups, and routing mode during migration; don’t assume every setting has a direct equivalent.

Windows installation requirements and first launch

Check	What to choose or do
Operating system and architecture	This page provides a Windows x64 package. Check your system type under Settings → System → About. For devices with a different architecture, confirm compatibility before installing.
Runtime	Minimum system requirements and runtimes vary by release. Follow the installer’s included notes and any startup prompts. Desktop and WPF have different runtime requirements, so check them separately.
Directory and permissions	Extract the full archive to a writable directory. You generally don’t need to run the app as an administrator for routine imports or system proxy use. Follow the permission prompts for features such as TUN.

After launch, import a subscription, select a server, enable the system proxy, and test it in a browser. Opening the main window confirms only that the app started; it doesn’t mean every app is using the proxy. Browsers and terminal programs may use different proxy settings, and command-line tools may need their own environment variables. See the quick-start guide.

macOS: choose v2rayN by processor

v2rayN

macOS desktop client · DMG

7.24.1

Apple Silicon

Choose this if About This Mac shows an Apple M-series chip.

Download Apple Silicon · arm64 Native arm64 architecture · DMG

Intel

Choose this if About This Mac shows an Intel processor.

Download Intel · x64 Intel 64-bit architecture · DMG

Check your chip before downloading. Open About This Mac: choose arm64 for an Apple M-series chip or x64 for an Intel processor. Don’t guess based on the year you bought your Mac; different chips may be available in the same year. A native build avoids extra compatibility layers, and the two DMG files aren’t interchangeable.

Open the DMG and follow its instructions to move the app to Applications, then launch it from there. Avoid running it from the mounted disk image, since the app will be unavailable when you eject it. If macOS shows a security warning, read it and confirm the app’s source and file type before following the system’s security settings. Don’t disable system protection globally just to install one app.

First test the regular system proxy, then configure TUN if needed. These modes use different permissions and network paths, so testing the browser connection before expanding traffic routing makes issues easier to diagnose. If you have other proxy or network-filtering tools installed, check whether they also modify the system proxy. Otherwise, one app may leave a stale proxy port behind when it exits.

macOS installation requirements and chip identification

Check	What to choose or do
Processor architecture	Choose arm64 for Apple M-series chips and x64 for Intel processors. Check About This Mac to confirm your chip.
System compatibility	Check the current release notes for minimum macOS requirements. If the app won’t start on an older system, verify compatibility before trying a package for a different processor architecture.
Installation and permissions	Move the app to Applications before launching it. Follow macOS permission prompts when setting up the system proxy or routing network traffic.

When moving settings from another desktop operating system, use the client’s import and export features where possible. Check any local file paths, external rules, or custom scripts in your configuration to make sure the referenced files exist on the new system. A successful subscription import doesn’t mean system-specific paths have migrated too.

Android: v2rayNG recommended, v2flyNG alternative

v2rayNG

Android client · Xray core

Recommended 2.2.6

arm64

For most mainstream phones released after 2015, arm64 is a good first choice. Check your device’s supported architecture.

Download v2rayNG · arm64 APK · arm64-v8a

Universal

Choose this if the architecture is unclear or your device doesn’t support arm64 apps.

Download v2rayNG · Universal APK · includes multiple architectures

For a first Android install, v2rayNG is a good place to start. It uses the Xray core, and support for protocols, transports, and parameters depends on the client and core versions. If your subscription uses REALITY or a specific flow field, confirm that the client recognizes those settings. Successful installation doesn’t guarantee configuration compatibility; seeing a subscription in the list isn’t enough.

After downloading the APK, open it from your browser’s download list or a file manager. If Android asks you to allow installs from this source, grant permission only to the browser or file manager you’re using, then revoke it after installation if you like. The first connection usually triggers a system VPN permission prompt; check the app name before granting access. Other VPN apps running at the same time may conflict.

v2flyNG

Alternative Android client · v2fly core

Alternative 1.10.31

arm64

Choose this if you specifically need the v2fly core and your device supports arm64.

Download v2flyNG · arm64 APK · arm64-v8a

Universal

A compatibility option for this architecture, not a guarantee of broader protocol support.

Download v2flyNG · Universal APK · includes multiple architectures

v2flyNG is for users who need a configuration supported by the v2fly core; it isn’t a drop-in replacement for v2rayNG. The interfaces have some similarities, but the cores support different features. Before switching, check the protocols, transports, and security settings used by your nodes. If your configuration depends on features specific to another core, changing clients won’t convert those settings automatically.

When testing the alternative client, disconnect the original one before importing your configuration into the new app. This helps distinguish node issues from VPN routing conflicts. Share subscription links only through trusted channels; don’t post full links, QR codes, or exported connection details in public forums.

Android installation requirements and background operation

Check	What to choose or do
Processor and system	Most mainstream devices use arm64. Some devices run a 32-bit system even with a 64-bit processor, so check that the app supports your system architecture. If you’re unsure, try the universal version.
Installation	Make sure you have enough storage and allow installs from your current source when prompted. Check the current app release notes and installer prompts for the minimum Android version.
Connection and background operation	A system VPN permission is required to connect. If the connection drops when the screen locks, check battery optimization and background restrictions before assuming the node is down.

If an update won’t install over the existing app, check the Android version, architecture, and signing source first. Packages signed by different sources can’t be installed over the same app, and uninstalling may delete your existing settings. Export any data you need from the old app before deciding how to migrate. If the installer reports incompatibility, don’t keep changing the file extension and trying again.

Linux: choose deb or rpm for your distribution

v2rayN

Linux GUI client · deb / rpm

7.24.1

deb · x64

For compatible distributions that use the deb package format.

Download deb · x64 For arm64 devices: download deb

rpm · x64

For compatible distributions that use the rpm package format.

Download rpm · x64 For arm64 devices: download rpm

On Linux, check both the package format and processor architecture. Debian- and Ubuntu-based systems typically use deb; Fedora- and RHEL-based systems typically use rpm. A matching package format doesn’t guarantee compatibility with every release. Check your distribution and architecture in system information, then open the downloaded file with your package installer and review dependency and compatibility warnings before installing.

x64 is also called amd64 or x86_64; arm64 is also called aarch64. These are different processor architectures, and renaming a file won’t convert it. If the package installer reports an unsatisfied dependency, check whether your distribution meets the package requirements. Don’t force an upgrade to core system components just to install a GUI client.

After installation, launch v2rayN from your desktop’s application menu. Whether the system proxy is applied depends on your desktop environment and the app. Browsers, terminals, and background services may use different proxy settings. Test with an app that explicitly supports proxies before troubleshooting others. If you need TUN, also check permissions, routing, and any existing network management tools.

Linux installation requirements and environment differences

Check	What to choose or do
Package format	Choose deb or rpm based on your distribution. A package manager recognizing a file doesn’t guarantee its dependencies are met, so review the installation prompts.
Device architecture	Most desktop PCs use x64. For arm64 devices, choose the matching link; don’t install a package built for a different architecture.
Desktop and permissions	A working graphical desktop and its required runtime dependencies are needed. Routine use and network routing features may require different permissions.

When migrating existing settings, check path capitalization and file permissions carefully. Paths from another operating system won’t work as-is on Linux. After changing routing or DNS, reload the client configuration and check how the connection behaves; saving a text file alone may not update the running core.

After installation

Import your configuration, then test the connection

Check the client, server, and routing mode separately. Following these steps can save you from repeated reinstalls.

Import a subscription or server
Import and update a valid configuration from your service provider. Installing the app doesn’t create a server. Once your nodes appear, check that their protocol settings were recognized correctly.
Choose how to route traffic
On desktop, start by testing the system proxy. On Android, allow the VPN connection when prompted. Temporarily stop other proxy tools to prevent multiple apps from changing system settings at once. Fine-tune per-app routing after the basic connection works.
Check results and logs
Test access to your target service in a real app and check the logs if it fails. For startup issues, check the installation environment first; for connection issues, check the server and configuration. When you’re done, exit the client normally and confirm the system proxy has returned to the expected state.

Subscription and connection guide Compare the three clients Routing, DNS, and TUN settings

Download and installation FAQ

What else should I know after choosing an installer?

Visit the help center →

Can I connect as soon as I download the client?

You’ll also need a valid server configuration or subscription link. The client imports your settings, starts the core, and configures your local proxy; it does not provide a server account. After importing your configuration, select a server and enable the system proxy or Android VPN as needed. If this is your first time, start with the quick-start guide.

Which should I choose: the Windows Desktop or classic WPF edition?

For a first install, try Desktop, which uses a newer cross-platform interface. If you’re familiar with the classic Windows interface, choose WPF. The editions have different interfaces and runtime requirements, so don’t mix their program directories. Export your settings before switching, then import and test the connection in a separate directory.

Should I choose arm64 or universal for Android?

Most mainstream phones released after 2015 will work best with arm64, but check which app architectures your device actually supports. Choose the universal version if your system is older, the architecture is unclear, or installation reports an incompatible package. The universal build includes multiple architectures and is usually larger; it does not offer more features.

How can I keep my subscriptions and routing settings when upgrading?

Export your configuration from the current client and save any custom routing rules before closing the app and upgrading. On desktop, don’t delete the existing data directory first. Android apps can usually be installed over the existing version, but a different signing source may prevent the update. Don’t uninstall and reinstall until you’ve confirmed your backup is usable.

Why hasn’t the download started, or why did it stop partway through?

Check your browser’s download list for prompts about the save location, permissions, or available storage. If a download stops, click the link for that installer again and try a more reliable network if needed. The links on this page point directly to the files, so you can still try downloading even if the version information hasn’t refreshed.

What should I check if the client won’t start or connect?

If the app won’t start, check the package’s operating system and architecture, make sure it was fully extracted, and review any runtime error messages. If it starts but won’t connect, check your subscription, device clock, port conflicts, and core logs. Troubleshoot startup and connection problems separately; repeatedly changing installers won’t fix a connection issue.

Download V2Ray clientsv2rayN and Android clients

Installer for your platform

Windows: two v2rayN editions

v2rayN

Desktop edition

Classic WPF edition

Windows installation requirements and first launch

macOS: choose v2rayN by processor

v2rayN

Apple Silicon

Intel

macOS installation requirements and chip identification

Android: v2rayNG recommended, v2flyNG alternative

v2rayNG

arm64

Universal

v2flyNG

arm64

Universal

Android installation requirements and background operation

Linux: choose deb or rpm for your distribution

v2rayN

deb · x64

rpm · x64

Linux installation requirements and environment differences

Import your configuration, then test the connection

Import a subscription or server

Choose how to route traffic

Check results and logs

What else should I know after choosing an installer?