CLIENT SHELF / DOWNLOAD

V2Ray Download
Client Downloads

For desktop, choose v2rayN. On Android, v2rayNG is the recommended choice; choose v2flyNG if you need the v2fly core.

Choose your operating system first, then select the CPU architecture and package format. All three clients are free and open source. For importing subscriptions and configuring a proxy after installation, see the Quick Start guide.

Choose an OS and download ↓ View the setup guide →

Settings shown for illustration; actual labels vary by client and version.

01 / SELECT YOUR SYSTEM

Choose a platform download

Switch platforms with the tabs. The selected platform is also preserved when you share this page’s URL.

Windows client

v2rayN

Windows · x64 · 7.24.1

Recommended

Desktop edition

Download v2rayN Desktop

A next-generation cross-platform UI, ideal for first-time installs and users who want a consistent experience across desktop systems. This link downloads the x64 package archive.

Classic WPF edition

Download v2rayN WPF

A stable choice that retains the classic Windows desktop interface, ideal for users who prefer its familiar workflow. Its layout differs from the Desktop edition, so settings may be in different places.

Fully extract the ZIP after downloading, then run the installer inside. Before updating or switching editions, quit v2rayN and back up your subscriptions and custom settings.

Windows requirements and installation tips

Check	What to look for	Before installing
OS and architecture	64-bit Windows; this download is x64	Check the system type on the About page in Settings. An x64 package is not a native ARM64 package.
Runtime	Follow the requirements for the selected edition	If prompted to install a .NET runtime, check the required Desktop Runtime and architecture.
Files and permissions	Fully extracted files and a writable settings folder	Don’t run the app directly from the ZIP preview. TUN features may require administrator privileges.

Choosing between Desktop and WPF mainly affects the interface and workflow; the edition name alone doesn’t determine whether a node will work. Support for protocols, transport layers, and security settings also depends on the bundled core and server parameters. If you already have settings, save a backup before updating, then check your subscriptions, routing rules, and local listening ports. Avoid running both editions with the same ports configured.

On first launch, import a configuration you know works, then choose how to use the system proxy. The system proxy only affects apps that honor system proxy settings; it won’t automatically route traffic from every program. If an app still connects directly, check whether it uses the system proxy before setting a proxy address separately or trying TUN. Reinstalling should not be the first step when troubleshooting a connection.

macOS client

v2rayN

macOS · DMG · 7.24.1

Apple Silicon · arm64

Download for Apple silicon

For Macs with Apple silicon. If About This Mac lists an Apple chip, choose this download to match your device’s architecture.

Intel · x64

Download for Intel

For Macs that list an Intel processor in About This Mac. Don’t identify the chip by appearance or purchase year—check your system information first.

Open the DMG and follow the installer window to move the app to Applications, then launch it from there. Quit the old app before updating to avoid running a temporary copy from the disk image.

macOS requirements and installation tips

Check	What to look for	Before installing
Chip architecture	Apple silicon: arm64; Intel: x64	Open About This Mac and check the Chip or Processor field.
OS version	Must meet the requirements for the current build	For older systems, check the app’s startup message first; don’t assume every legacy OS is supported.
System permissions	Grant permissions as needed for your use	Read the system prompts when changing the system proxy or enabling features that require additional permissions.

Apple silicon and Intel downloads use different processor instruction sets. Even if your system can run an app built for another architecture through translation, choose the package that matches your device to avoid an unnecessary compatibility layer. If the app won’t start or reports an architecture mismatch, recheck your chip and download choice rather than repeatedly changing subscription settings. App startup and node connectivity are separate troubleshooting steps.

If macOS displays a security prompt, verify the app’s source and read the message before using the system’s standard approval flow. Don’t disable system security entirely just to launch one app. After installation, check that the system proxy is actually enabled. Before quitting the client, consider restoring the system proxy; otherwise, the system may still point to a local port that is no longer listening, preventing browser access.

Android clients

v2rayNG

Android · Xray core · 2.2.6

Recommended

arm64 · Common architecture

Download v2rayNG arm64

Most mainstream phones released after 2015 are likely to use arm64, but check that the OS supports 64-bit apps. Choose this build if Xray feature support is a factor in your decision.

Universal · Multiple architectures

Download v2rayNG universal

Choose this if you can’t confirm your device’s architecture or the arm64 APK is incompatible. It includes components for multiple architectures and is usually larger than a single-architecture package.

The version label and file path come from separate manifest fields and may not match during a release. The current download is named 2.3.11. After installation, check the actual version on the client’s About page.

v2flyNG

Android · v2fly core · 1.10.31

Alternative

arm64 · Common architecture

Download v2flyNG arm64

For configurations that require the v2fly core. Choose an architecture as you would for v2rayNG: check arm64 support first on most mainstream phones released after 2015.

Universal · Multiple architectures

Download v2flyNG universal

For devices whose architecture you haven’t confirmed. The universal version supports more installation architectures; it doesn’t add protocols or transport features that the core doesn’t support.

v2rayNG and v2flyNG have different core capabilities. If a node uses features such as REALITY, check Xray support first. Being able to import a share link doesn’t mean the clients are fully compatible.

Android requirements and installation tips

Check	What to look for	Before installing
App architecture	Choose arm64 for 64-bit app support; choose universal if unsure	A 64-bit-capable processor doesn’t guarantee that the OS supports 64-bit apps. Check your system information.
OS compatibility	Check the system requirements for the current APK	If the installer reports a parsing error, first check that the download is complete and your OS isn’t too old.
Installation and connection permissions	Allow app installs from this source; approve the VPN request if needed	Install permission and VPN permission are separate. Read the system prompt when enabling a connection.

When downloading an APK for the first time, your browser may ask you to allow app installs from the current source. After installation, you can revoke that source’s permission in your device’s security settings. If an update fails with an “App not installed” message, possible causes include a different signing key, a downgrade, low storage, or an incompatible architecture. Don’t immediately uninstall the old client. Export your settings and note the error first to avoid losing subscriptions and routing rules.

A VPN permission prompt during connection setup is part of routing traffic; it doesn’t mean your subscription has been verified. Android typically allows only one active VPN service, so other apps using a VPN connection may conflict. If background connections keep dropping, check battery optimization and your device maker’s background restrictions, then consider per-app proxy settings to exclude traffic that doesn’t need routing. Don’t disable background restrictions for every app just to keep the connection alive.

Linux client

v2rayN

Linux · Desktop environment · 7.24.1

deb · x64

Download v2rayN DEB

For distributions that use DEB packages. The amd64 filename suffix refers to the common x64 desktop architecture, not a specific processor brand.

For ARM64 devices: download the ARM64 DEB →

rpm · x64

Download v2rayN RPM

For distributions that use RPM packages. The same package format doesn’t guarantee identical dependencies; check your distribution version and dependency resolution before installing.

For ARM64 devices: download the ARM64 RPM →

Choose the package format first, then the CPU architecture. arm64 and aarch64 usually refer to the same 64-bit ARM architecture. This is a GUI client; launch it from your desktop application menu after installation.

Linux requirements and installation tips

Check	What to look for	Before installing
Package format	DEB or RPM, depending on your distribution	Open the package with your system’s software installer and check dependency and compatibility notices first.
Processor architecture	x64 or ARM64	Check the architecture in system information; amd64 and x86_64 are x64 naming conventions.
Desktop and permissions	A desktop environment that can run graphical apps	Installing packages requires the appropriate permissions. Check desktop and permission support separately when configuring the system proxy or TUN.

DEB and RPM refer to package management systems, not proxy protocols or connection speed tiers. Before downloading, check which package manager your distribution uses, then confirm the processor architecture. Pay attention to distribution-specific package names and dependencies too. If the installer reports missing dependencies or an incompatible version, resolve the system compatibility issue rather than forcing the installation.

Desktop environments may handle system proxy settings differently, and some apps use their own proxy settings. After launching the client, check the local listening address and port, then verify which settings the target app actually uses. A GUI client starting successfully doesn’t mean it’s proxying traffic for every desktop process. For TUN or other features that require additional permissions, follow the client’s instructions; avoid running the entire desktop app with elevated privileges long-term.

02 / AFTER INSTALLATION

Configuration steps after installation

The installer installs the app. Connecting also requires configuration, a traffic routing method, and a connection check.

IMPORT
Import a share link or subscription

Import an authorized share link from the clipboard, or add a subscription URL. Check the protocol, server address, port, and TLS settings. Keep subscription URLs private: they may contain credentials. Redact them from screenshots.
CONNECT
Choose a node and routing method

Select a node and enable system proxy, VPN, or TUN as appropriate. On desktop, check that your app uses the proxy. On Android, review VPN permission and per-app rules. Change one setting group at a time to isolate problems.
VERIFY
Check access and connection logs

Test access in your intended app; a running status alone does not confirm connectivity. Check logs for DNS, TLS, and outbound routing errors. Record the full error message and time, then investigate DNS, certificates, or port conflicts as indicated.

Read the v2rayN setup guide → Compare protocols and cores → Browse protocol and routing terms →

03 / PACKAGE QUESTIONS

Download and installation FAQs

Quick answers on package formats, architecture, updates, and first-time connections.

Which should you choose for Windows: Desktop or classic WPF?

For a first install, consider Desktop, which uses a next-generation cross-platform interface. Choose the classic, stable WPF edition if you prefer the traditional interface or want to keep your usual workflow. Check the system and runtime requirements for either edition. Back up your settings before switching, and don’t run both editions on the same ports.

Which Android version should you choose: arm64 or universal?

Most mainstream phones released after 2015 are likely to use arm64, but check that your OS supports 64-bit apps. Choose the universal version if you can’t confirm your architecture or the arm64 APK is incompatible. Universal APKs are usually larger because they include multiple architectures; that doesn’t mean they offer better connectivity.

Why might the displayed version differ from the download filename?

The version label and package path are separate manifest fields and may temporarily get out of sync during a release. This page shows each field as listed rather than inferring the displayed version from the filename. To check your installed version, open the client’s About page; don’t rely on the filename saved by your browser to tell whether an update succeeded.

Do I need to uninstall the old version before updating?

Back up your subscriptions, routing rules, and custom settings first. Then quit the old app and update as directed by the installer; follow its instructions on whether uninstalling is required. Android updates also require the same package name and signing key. If the signature is incompatible, don’t uninstall right away—you could lose your settings.

Can I connect as soon as the client is installed?

The installer provides the client app, not a ready-to-use server configuration. Import a share link or subscription you’re authorized to use, select a node, and configure system proxy or VPN mode as needed. A successful import only means the format was recognized; check the server settings, certificate configuration, and actual connection afterward.

What should I do if a download is interrupted or the installer won’t open?

Make sure the browser finished downloading, delete any incomplete temporary file, and try again. Then check the file extension, OS, and CPU architecture. Fully extract Windows ZIP files before running the installer, and allow installs from the current source on Android. If it still fails, note your OS version and the full error, then search the Help Center for the issue.

Continue troubleshooting in the Help Center →

V2Ray DownloadClient Downloads

Choose a platform download

Windows client

Desktop edition

Classic WPF edition

Windows requirements and installation tips

macOS client

Apple Silicon · arm64

Intel · x64

macOS requirements and installation tips

Android clients

arm64 · Common architecture

Universal · Multiple architectures

arm64 · Common architecture

Universal · Multiple architectures

Android requirements and installation tips

Linux client

deb · x64

rpm · x64

Linux requirements and installation tips

Configuration steps after installation

Import a share link or subscription

Choose a node and routing method

Check access and connection logs

Download and installation FAQs

V2Ray Download
Client Downloads