Client downloads / platform and architecture

V2Ray Client Downloadsv2rayN and Android Clients

For desktop, choose v2rayN; for Android, start with v2rayNG. Confirm your operating system first, then select a package by processor architecture and installation format.

Free, open-source clients
Subscriptions not included
Import your configuration after installation

New here? Start with the subscription import guide →

Windows：v2rayN

Both downloads are x64 packages. Desktop uses a cross-platform interface; the classic WPF version keeps the familiar window layout.

v2rayN

Desktop proxy client · 7.24.1

Recommended

Download Desktop · x64 Download classic WPF · x64

The download is a ZIP archive. Extract it to a separate folder, then run the installer inside.

If this is your first time using v2rayN, start with Desktop. Its next-generation cross-platform interface offers a consistent experience across desktop operating systems. WPF is the classic, stable version for users who prefer the traditional layout. Both versions handle subscriptions and proxy settings, so you don't need to install both to import the same subscription.

Before switching versions, note your subscription groups, routing choices, and custom ports. Don't set both clients to launch at startup: they may compete for local ports or overwrite system proxy settings. The interface doesn't determine server quality or give the same configuration access to different network resources.

Windows system and installation requirements

What to check	Available on this page	Before installing
Processor architecture	x64	Check the system type under Settings → System → About
System compatibility	Windows desktop installer	Follow the installer's prompts; check runtime support on older systems
File format	ZIP archive containing the installer	Extract the files before running the installer; don't run it from the archive preview
Permissions	Configure standard proxy or TUN mode as needed	Grant administrator permissions only if the installer or TUN mode requires them

After installation, add a subscription and check that servers appear in the list before choosing a system proxy mode. TUN is not required to finish setup. For regular browser use, start with the system proxy to make configuration issues easier to troubleshoot.

macOS: choose v2rayN by chip

Open the Apple menu → About This Mac. Check the Chip or Processor field, then choose the matching package.

v2rayN

macOS desktop client · 7.24.1

Download Apple Silicon · arm64 Download Intel · x64

Choose Apple Silicon for an Apple M-series chip, or Intel for an Intel processor. Both downloads are DMG files.

Use the system information to check your chip architecture; don't guess based on the computer's appearance. Open the downloaded disk image and follow the window instructions to move the app to the Applications folder, then eject the disk image. Don't run the app from the mounted disk image long-term or keep multiple copies with the same name in different locations after updating.

If macOS blocks the app on first launch, check the file's source and type, then review the app-specific options under System Settings → Privacy & Security. Don't disable security checks globally. Once the app opens, configure your subscription and proxy settings; a successful installation doesn't mean a proxy connection is active.

macOS system and installation requirements

What to check	Choose	How to check
Apple Silicon	arm64 DMG	About This Mac shows an Apple M-series chip in the Chip field
Intel	x64 DMG	About This Mac shows Intel in the Processor field
System compatibility	Check the current app's requirements	If macOS reports an incompatible version, first check whether your system can be updated
App location	Applications folder	Launch the app from this folder after copying it, then eject the disk image

Choose the matching proxy mode in the client when you need apps that follow system proxy settings to use the proxy. If an app doesn't use the proxy, first check whether it reads system settings; repeatedly switching installers won't fix that.

Android: v2rayNG and v2flyNG

Start with v2rayNG. Consider v2flyNG if you need compatibility with the V2Fly core. Each app manages its own settings independently.

v2rayNG

Xray core · 2.2.6

Recommended

Download v2rayNG · arm64 Download v2rayNG · universal

Most mainstream phones released since 2015 should use arm64. Check the ABI supported by your operating system. If you're unsure of the architecture, consider the universal version.

v2rayNG is a good everyday choice for Android. After installing the APK, import a configuration through a subscription group or from the clipboard, then choose a server. The first time you connect, Android asks for permission to establish a VPN connection. This lets the client handle device traffic; it doesn't mean you have access to a working remote service.

The arm64 package is usually a smaller download for mainstream phones. The universal version includes code for more architectures to improve installation compatibility; it won't make the same server configuration faster. Older devices may run a 32-bit operating system even if the processor supports 64-bit, so don't rely on the processor's marketing name alone.

v2flyNG

V2Fly core alternative · 1.10.31

Alternative

Download v2flyNG · arm64 Download v2flyNG · universal

Choose the package for your device's architecture. Installation and subscription settings are independent of v2rayNG.

Choose v2flyNG if your existing configuration is built around the V2Fly core. The two apps are not simply the same program with different names; protocol and transport support depends on the core version each one includes. If some settings aren't recognized after importing, check which features the configuration requires instead of repeatedly switching between arm64 and universal packages.

Before testing another client, disconnect the one you're already using. Android typically allows one app to manage the VPN connection at a time, so running multiple proxy apps at once makes troubleshooting harder. Don't uninstall the original app before migrating; first make sure your subscriptions and custom rules are saved.

Android system and installation requirements

What to check	Recommended choice	Notes
System ABI	arm64 or universal	Hardware and operating system architectures can differ; check what the system supports
Installation format	APK	Allow the browser or file manager you're using to install apps from unknown sources
System compatibility	Depends on the APK's system requirements	If the installer reports an incompatible system version, check your system information first
Connection permission	System VPN permission	Approve the first connection; disconnect other VPN apps before testing

If the installer says “App not installed,” the existing app may have a conflicting signature or version, or there may not be enough storage. Save your settings and review the error first; uninstalling may delete local data, so don't make it your first step.

Linux: choose v2rayN by distribution

Check your package manager first, then confirm the processor architecture. deb and rpm are package formats, not different feature editions.

v2rayN

Linux GUI client · 7.24.1

Download deb · x64 Download rpm · x64

For arm64 devices: Download deb · arm64 Download rpm · arm64

Debian- and Ubuntu-based distributions typically use deb. Choose rpm for distributions that use RPM package management, and check that the package dependencies are compatible.

Check the processor in your system's About or hardware information page. Most Intel and AMD desktop computers use x64; choose the matching architecture for an arm64 desktop. In filenames, amd64 and x86_64 both refer to x64, while arm64 and aarch64 refer to the corresponding 64-bit ARM architecture.

Open the package with your distribution's software installer so the package manager can check dependencies and compatibility. The same file extension doesn't guarantee compatibility with every distribution; runtime versions matter too. Don't force installation by ignoring dependencies. Once the app starts, configure subscriptions, system proxy, and routing as needed.

Linux system and installation requirements

What to check	Package to use	Check before installing
Debian package management	deb	Use the software installer to check dependencies and distribution compatibility
RPM package management	rpm	Confirm that your distribution meets the package dependencies
Processor architecture	x64 / arm64	The package architecture must match your system
Runtime environment	Desktop session	This page covers the GUI client, not server installation

Whether apps use the system proxy depends on the desktop environment and each app's settings. Test with an app that explicitly supports proxy settings before considering TUN. TUN requires additional permissions and routing configuration; avoid changing multiple network options at once during initial setup.

Check before installing

Choose a platform, architecture, and package format in that order

First identify the operating system running on your device rather than relying on its brand. Then check the processor and architecture in system information, and choose a package format. Architecture-specific packages help the client run on compatible hardware; they don't change subscription contents or indicate different service tiers.

Version numbers on download cards come from the release list, while actual filenames may include a release identifier. If they differ, don't assume the displayed number is the installed version. After installation, check the client's About page for the current version. Don't rename the downloaded file just to make the numbers match.

After installation: import a subscription and check proxy mode

When setting things up for the first time, change one thing at a time. First make sure the app opens, then confirm the configuration imports, and finally test whether traffic is routed as expected.

Add a subscription and refresh the server list

On desktop, add a group under subscription groups, enter the subscription URL, and save it. Then update the subscription. Saving the URL only adds a source; servers appear after a successful update. If you have a share link, import it from the main window's clipboard option instead of pasting it into the subscription URL field.

On Android, set up the subscription first, then update the configuration list. Menu labels may vary between clients, but saving a subscription source and fetching its contents are separate steps. If the list is empty, check the update result before assuming there's a problem with the installer.

See how to import a subscription →

System proxy and TUN: what's the difference?

On desktop, choose “Set system proxy” to route traffic from apps that follow the system proxy settings. Routing options determine which connections use the proxy and which connect directly; they are separate from the system proxy setting. First confirm the selected configuration works, then adjust routing rules.

TUN uses a virtual network interface to handle traffic and requires permissions, DNS, and routing configuration. It's not required for installation and won't fix every connection issue. On Android, disconnect other apps using the system VPN interface first.

Read about proxy modes →

Updating or reinstalling: save your settings first

If your existing client works, note the subscription groups, manually added configurations, custom routing, and port settings you want to keep before updating. Being able to fetch a subscription again doesn't mean manual changes will be restored. If the client offers an export or backup option, use it and store the backup outside the installation folder.

Close the running app and disable its startup entry before installing. This is especially important when switching between Desktop and the classic version: don't run both instances against the same port. After installing, check the app information, confirm your subscription groups and defaults are intact, then restore your proxy mode. Changing the client, subscription, DNS, and routing all at once makes problems harder to pinpoint.

If Android won't install over an existing app, check the version and signature messages before uninstalling. On Linux, keep using the same package manager where possible to avoid multiple installation sources. If the new app won't start, record the exact system error; it usually helps identify compatibility problems more than repeatedly downloading the package.

Go to the FAQ to troubleshoot by symptom →

Download and installation FAQs

Desktop or classic WPF: which version should you choose?

For a first install, start with Desktop, which uses a next-generation cross-platform interface. Choose WPF if you prefer the familiar classic layout. Both are versions of v2rayN, and there is no need to install both. Back up your subscription groups and custom settings before switching.

Android: arm64 or universal?

Most mainstream phones released since 2015 should use arm64, but check which ABI your device's operating system supports. If you're unsure of the device architecture or know the system is not 64-bit, consider the universal version. It includes code for more architectures and is usually a larger download; it does not make connections faster.

macOS: how to choose between Apple Silicon and Intel

Open About This Mac from the Apple menu. Choose Apple Silicon if the Chip field shows an Apple M-series chip, or Intel if the Processor field shows Intel. Match the package to your hardware rather than judging by the computer's appearance or purchase year.

Do you need a subscription after installing the client?

You'll need to provide a working subscription URL or share link. The installer includes the client application, not ready-to-use server configurations. On desktop, add a URL under subscription groups and update the subscription after saving. You can also import a share link from the clipboard.

How can you keep your settings when updating the client?

Back up your subscription groups, custom routing, and other important settings before updating, then close the old client before installing the new one. Keep the same client, architecture, and installation method where possible. Don't assume settings will migrate automatically when switching interface versions or package types. After updating, check your subscription list, proxy mode, and routing choices.

Downloaded but can't install? Check these first

Check the operating system, processor architecture, and file format, then review the specific error message. On Windows, extract ZIP files before running the installer. On Android, allow the browser or file manager you're using to install apps from that source. On Linux, check dependency messages in your package manager. Don't disable system security protections globally just to install the client.