Client and package selection

V2Ray Client Downloads

Choose v2rayN for desktop and v2rayNG for Android. Check your operating system first, then select the processor architecture. After installation, import a subscription and set up your proxy.

Free to use Open source Installation and setup guide →

Windows packages

Two interfaces, one v2rayN client. The downloads below are for x64 systems.

v2rayN

Recommended 7.24.1

Desktop editionx64 · ZIP

A newer cross-platform UI. A good starting point for first-time installs or if you want a consistent layout across desktop systems.

Download v2rayN Desktop

Classic WPF editionx64 · ZIP

The classic, stable Windows interface. A good fit if you already know your way around the older menus, lists, and settings.

Download v2rayN WPF

Extract the entire archive before running the installer inside. Don’t launch it from the archive preview.

Windows requirements and installation

Check	Package requirements	How to check
Processor architecture	x64; not a native Windows ARM package	Go to Settings → System → About and check System type
System and runtime	64-bit Windows; check the selected client’s release requirements for the minimum version and runtime libraries	If prompted to install a runtime, note the full component name
Installation requirements	A writable folder, enough space to extract, and any required installation permissions	Extract the entire archive first; follow the system prompt to decide whether to grant installation permissions

Desktop and WPF differ mainly in their UI framework and layout, not subscription quality or server capabilities. Choose the interface that suits how you work; there’s no need to run both editions at once. If both client processes use the same local listening port, one may fail to bind. The window may open even though the proxy hasn’t started.

For a first-time install, use a dedicated working folder. Don’t move just the executable and leave the other bundled files behind, or mix the installation folder with a temporary extraction folder. After installation, open settings and check the local listening address, port, and current proxy mode before importing an existing subscription.

When migrating from an older version, use the client’s export or backup feature to save your configuration before installing the new interface edition. Don’t assume that different interfaces or releases use identical configuration folders. After launch, check that your subscription groups, custom routing, and DNS settings migrated correctly. For step-by-step instructions, see the v2rayN initial setup guide.

macOS packages

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

v2rayN

7.24.1

Apple Siliconarm64 · DMG

Choose this package if About This Mac lists an Apple M-series chip. Use the chip name to decide, not the computer’s appearance or purchase year.

Download v2rayN · Apple Silicon

Intelx64 · DMG

Choose this package if About This Mac lists an Intel processor. It serves the same purpose as the Apple Silicon package but targets a different architecture.

Download v2rayN · Intel

Open the DMG and follow the installation instructions in the disk image. Move the app to a permanent location before launching it.

macOS requirements and installation

Check	Package requirements	How to check
Chip type	Apple Silicon uses arm64; Intel uses x64	Apple menu → About This Mac → Chip or Processor
macOS version	Must meet the macOS requirements for the selected v2rayN release	Check your macOS version in About This Mac and read any system prompts before installing
Permissions and storage	A writable Applications location, with enough room for the download, installation, and configuration	Grant only the permissions needed for the proxy features you use

Apple Silicon and Intel differ at the processor architecture level; changing a file extension won’t convert one package into the other. Choosing the package built for your chip avoids uncertainty from compatibility layers. If the system says the app isn’t supported on your Mac, check the chip and macOS version again rather than repeatedly downloading the same incompatible package.

After installation, launch the app from the Applications folder instead of running it indefinitely from the disk image. Quit the client before updating and keep a backup of your existing configuration. If macOS blocks the app, read the full warning and verify the file’s source before using the security settings provided by the system. Don’t disable system security entirely just to open one app.

A desktop client window opening successfully doesn’t mean your browser is using the proxy. Import a configuration and select an entry, then enable the system proxy or another supported traffic-routing mode as needed. Some apps have their own proxy settings and may not follow the system proxy. If only certain apps are affected, check their network settings first.

Android packages

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

v2rayNG

Recommended 2.2.6

An Android GUI client powered by the Xray core. A good first choice for importing subscriptions and everyday mobile proxy use.

arm64arm64-v8a · APK

For most phones released since 2015, this is usually the right package. Check which app architecture your system supports.

Download v2rayNG · arm64

Universal editionUniversal · APK

Choose this if you’re unsure of your architecture or the arm64 package reports an incompatibility. It includes multiple architectures and is usually a larger download.

Download v2rayNG · Universal

v2flyNG

Alternative · V2Fly core 1.10.31

An Android alternative for the V2Fly core ecosystem. Consider it if your existing configuration depends on V2Fly behavior; check protocol and transport support before importing.

arm64arm64-v8a · APK

For devices that support 64-bit ARM apps. Choose it the same way as the v2rayNG arm64 package above.

Download v2flyNG · arm64

Universal editionUniversal · APK

For devices with an unknown architecture. The Universal package covers more architectures; it doesn’t add features that the core itself lacks.

Download v2flyNG · Universal

Android requirements and installation

Check	Package requirements	How to check
App architecture	The arm64 package requires arm64-v8a support; choose Universal if you’re unsure	Check your device specifications and the app ABIs supported by your system
macOS version	Must meet the Android minimum requirements for the selected client release	Check your Android version in Settings and read any compatibility warnings from the installer
Install permission	Allow the browser or file manager you’re using to install apps	Grant permission only to the install source you’re using, and revoke it afterward if you wish
Connection permission	VPN mode requires system confirmation	Read and confirm the system’s VPN request the first time you connect

A 64-bit phone processor doesn’t necessarily mean the manufacturer’s system allows 64-bit apps, so don’t rely on the chip model alone. If the arm64 package won’t install, check whether the installer specifically reports an architecture mismatch. If the issue is an outdated system, low storage, or a signature conflict with an existing app, switching to Universal usually won’t fix it.

v2rayNG and v2flyNG aren’t the same app under different names. Their cores differ in protocol support and configuration details, especially for newer security parameters and transport combinations. If some entries are missing after you import a subscription, don’t assume it’s corrupted; first check whether the client and core can parse those configurations. For details, see the protocol and core selection guide.

Most Android devices allow only one regular VPN service to route connections at a time. Before starting the client, check whether another app using a VPN connection is running. If the connection drops after the screen has been locked for a while, check battery optimization and background activity permissions. There’s no need to grant every background permission during installation; adjust them as needed to address the actual issue.

Linux packages

Match the package format to your distribution, then choose the processor architecture. The main downloads below are for x64.

v2rayN

7.24.1

deb packagex64 · amd64

For distributions that use the deb package management system. Use your system’s software installer to handle dependencies and track the installation.

Download v2rayN · x64 deb

rpm packagex64 · x86_64

For distributions that use the rpm package management system. Check that the package dependencies match your distribution version.

Download v2rayN · x64 rpm

ARM64 devices Download arm64 deb → Download arm64 rpm →

Linux requirements and installation

Check	Package requirements	How to check
Processor architecture	x64 corresponds to amd64 / x86_64; arm64 corresponds to aarch64	Check the processor or architecture field in your system information
Package management system	deb or rpm, matching your distribution	Check which package formats your distribution’s software manager supports
Runtime environment	A graphical desktop and the system dependencies required by the package	Let the software installer check dependencies and version requirements
Installation permissions	Permission to install system software; a writable user configuration directory	Grant permissions only when installing; run as a regular user day to day

A matching package format only means the system can read the installer; it doesn’t guarantee compatibility with every release of a distribution. Even within the same rpm or deb ecosystem, system library versions, desktop dependencies, and build targets can differ. If the installer reports unsatisfied dependencies, check the missing components and version requirements. Don’t force the installation by ignoring them.

The v2rayN package on this page is a graphical client for Linux systems with a desktop environment. After installation, launch it from the application menu and check that the configuration directory is writable. You shouldn’t need to run the entire client with elevated privileges for everyday use. If a specific traffic-routing mode requires extra permissions, configure them separately as described for that feature.

When updating, stick with the same package management method where possible so the system can track the installation and handle removal. Don’t mix installations from different architectures or package formats while troubleshooting. If your configuration is imported but the app’s network behavior hasn’t changed, check your desktop proxy settings and the app’s own network options before moving on to routing, DNS, or other advanced setup.

After installation, check these three settings

Installing a client and connecting through a proxy are two separate steps. Confirm the basics first, then adjust advanced settings.

01 / Configuration

Import a working subscription

The package doesn’t include a ready-to-use server configuration. Add your own configuration using the client’s subscription or import option, then check that the protocol fields are recognized. Subscription URLs often contain credentials, so don’t share the full URL or a QR code in screenshots.

02 / Traffic routing

Choose a proxy mode

On desktop, check the local listening port first, then enable the system proxy if needed. On Android, confirm the VPN connection when prompted. The system proxy doesn’t automatically cover every app, and apps with their own proxy settings may keep using a different port.

03 / Verification

Check the connection and logs

Test with an app that you know follows the proxy settings, then check the client logs for specific errors. Troubleshoot import failures, connection failures, and DNS resolution failures separately. Changing multiple settings at once makes it harder to identify the cause.

Continue to the installation and initial setup guide →

Download and update FAQs

First choose the right package, then troubleshoot startup and connection issues.

Can I connect as soon as the client is installed?

Installing the client alone is not enough to connect. The client reads your configuration and routes traffic; you also need a valid server configuration or subscription URL. After importing it, check the protocol, transport, and security settings, then enable the system proxy or VPN connection as needed.

Which should I choose for Windows: Desktop or WPF?

If this is your first time, try Desktop, which uses a newer cross-platform interface. If you prefer the familiar classic layout, choose the stable WPF edition. Both are v2rayN, and all Windows packages on this page are x64. Back up your configuration before switching, then check that it imported correctly on first launch.

What’s the difference between Android arm64 and Universal packages?

Most phones released since 2015 can usually use arm64, but check which app ABIs your system actually supports. Universal includes multiple architectures, making it a good choice if you’re unsure or the arm64 package is reported as incompatible. It doesn’t add proxy features or fix an outdated Android version.

What should I back up before updating the client?

Back up your subscription groups, custom routing, DNS settings, and any other manually changed configuration. Then exit the client before installing the update. Configurations and subscription URLs may contain credentials, so store them somewhere you trust. After upgrading, check that your listening port, proxy mode, and rules are still in place.

What if the version shown on the download button doesn’t match the filename?

The displayed version and package path are maintained separately and may briefly get out of sync after a release. A filename may not show the package’s full version; check the client’s About page after installation. If the app warns that the update is a downgrade or can’t be installed over the current version, cancel and keep your existing configuration.

What should I check if the download won’t install?

Check your operating system, processor architecture, package format, and available storage. Extract Windows ZIP files completely before installing; choose the macOS DMG for your chip; check whether Android has authorized the current install source; and match the Linux package format and dependencies to your distribution. If it still fails, note the system message and follow its guidance.