Client downloads

Download V2Ray clients

Choose your operating system, then select your processor architecture.

Use v2rayN on desktop. For Android, v2rayNG is the recommended choice, with v2flyNG as an alternative. Find downloads, compatibility notes and setup steps for each platform in one place.

Free to use Open source Graphical interface Subscription management

Desktop clients

Windows downloads

Two interface editions, both available as x64 packages. Choose the interface you prefer, then check system and runtime requirements.

v2rayN

Recommended 7.24.1

The Desktop edition uses a newer cross-platform UI; WPF is the classic, stable edition with a familiar Windows interface and workflow. Start with Desktop if this is your first install, or choose WPF if you prefer the interface you already know.

Download Desktop · x64 Download classic WPF · x64

Package format: Both downloads are ZIP archives. Extract the entire archive before opening the installer; do not run it from the archive preview. After installation, launch the client from your system's app list for easier updates and removal.

Switching editions: The two editions have different layouts, and menu names and settings locations may change between releases. Back up subscription URLs, routing rules and custom settings before switching; do not assume the other edition will read the same configuration directory. Run only one client instance at a time to avoid conflicts with local listening ports or system proxy settings.

Windows system and installation requirements

Check	What to look for
Processor and system	This page provides x64 packages. Check System type under Settings → System → About.
Windows version	Use a supported 64-bit Windows version where possible. The minimum version depends on the current client and its runtime requirements.
Runtime requirements	Follow the installer's prompts for required runtimes. Desktop and WPF may have different dependencies.
Permissions and proxy	Start with standard user permissions. Grant elevated access only when prompted for a setting that requires it.

If the app will not open, check that the archive was fully extracted, the system architecture matches, and the system message identifies no missing components. Do not keep reinstalling based only on a generic startup failure. If the interface opens but your browser cannot connect, check your subscription, selected server and system proxy settings; those are separate from installation.

Windows setup after installation →

Desktop clients

macOS downloads

Choose a build based on the chip shown in About This Mac, not the computer's appearance or purchase date.

v2rayN

macOS desktop 7.24.1

Choose Apple Silicon (arm64) for an Apple M-series chip, or Intel (x64) for an Intel processor. Download the build that matches your Mac's chip rather than relying on compatibility translation by default.

Download Apple Silicon · arm64 Download Intel · x64

Check your chip: Open About This Mac from the system menu and check the Chip or Processor field. Apple Silicon and Intel use different architectures, even when the app has the same name. If macOS says the app is not supported on this Mac, check the architecture and system version.

Install the app: Open the DMG and follow the window instructions to move the app to the Applications folder, then launch it from there. Before updating, quit the old instance so it is not still running from the mounted disk image. If macOS blocks the app, read the security prompt and confirm the download source; do not disable system security features wholesale.

macOS system and installation requirements

Check	What to look for
Apple Silicon	Apple M-series chip: use the arm64 DMG.
Intel	Intel processor: use the x64 DMG.
System compatibility	Minimum system requirements vary by client build. Follow the app's compatibility notice.
Proxy settings	The system proxy affects apps that follow this setting; it does not route all network traffic.

After launching the app for the first time, import an existing configuration, then choose a server and routing mode. If enabling the system proxy requires permission, follow the system prompt. Before quitting, check whether the proxy has been cleared, especially when changing networks or stopping the client. Apps with their own proxy settings may also need to be configured individually.

macOS setup after installation →

Mobile clients

Android downloads

Choose v2rayNG first. Consider v2flyNG if you need to use an existing V2Fly configuration.

v2rayNG

Recommended Xray core 2.2.6

An Android graphical client powered by the Xray core, with subscription groups, server selection and routing settings. Most mainstream phones released since 2015 can start with arm64; choose the universal build if you are unsure of your device's architecture.

Download v2rayNG · arm64 Download v2rayNG · universal

Choose an architecture: The arm64 package is for compatible 64-bit Android systems. A 64-bit processor does not necessarily mean the device's operating system can install this package; some devices need the universal build. The universal build supports more architectures and is usually larger, but does not change subscription content or make the server faster.

First launch: Add a subscription group and refresh it. Make sure a valid configuration appears in the list, then select a server and connect. On first connection, approve the system VPN request. This is the system interface the client needs to handle app traffic on your device; it does not mean the package includes a remote server.

v2flyNG

Alternative V2Fly core 1.10.31

An alternative Android client powered by the V2Fly core. It may suit setups that rely on the corresponding configuration system. Similar-looking interfaces do not mean that protocols and transport options are fully interchangeable.

Download v2flyNG · arm64 Download v2flyNG · universal

Before switching: Check which protocols, transports and security options your existing configuration uses. Different cores support different features, and some advanced configurations require a compatible client. Keep the original subscription URL and any required settings. Do not rely on screenshots alone to migrate, and never share a complete configuration that contains credentials.

Using both clients: You can keep multiple clients installed for compatibility testing, but run only one VPN connection at a time. Stop the current connection before starting another client. If the network stops working after switching, confirm the old connection has ended, then check the new client's per-app rules and routing settings.

Android system and installation requirements

Check	What to look for
arm64 package	For systems that support arm64 apps; usually the first choice for newer mainstream devices.
Universal build	Use when the device architecture is unclear or a specific package is incompatible. The app's minimum system requirements still apply.
Install permission	Allow the browser or file manager you're using to install apps, then revoke that permission when you're done.
Connection permission	Approve the system VPN request when connecting for the first time. Check whether another VPN is already active.
Background operation	If the connection often drops when the screen is locked, check battery restrictions, background activity permissions and network status.

If you see “App not installed,” check storage space, architecture, system version and signature compatibility with any existing app, in that order. Do not uninstall the older version right away; this may erase local subscriptions and routing settings, so back them up first. If installation succeeds but subscription updates fail, check the subscription URL and network access rather than repeatedly changing the package.

Compare v2rayNG and v2flyNG →

Desktop clients

Linux downloads

Choose deb or rpm for your distribution, then select x64 or arm64 for your processor.

v2rayN

Linux desktop 7.24.1

Choose deb for Debian, Ubuntu and compatible distributions; choose rpm for Fedora, RHEL-based and compatible distributions. The main downloads below are for common Intel and AMD x64 desktops. ARM desktops should use the matching arm64 package.

Download deb · x64 Download rpm · x64

ARM devices: deb · arm64 ARM devices: rpm · arm64

Reading package names: amd64 and x86_64 usually refer to the x64 architecture shown here; arm64 and aarch64 refer to 64-bit ARM. These names describe processor architectures, not Linux distributions. After choosing the right package format, make sure the required libraries are available for your system.

Install with a graphical tool: Open the package with your distribution's software installer or graphical package manager. Review dependency and permission prompts before proceeding. Launch the client from the applications menu when installation is complete. This is a desktop graphical client; these steps are not intended for server environments without a graphical session.

Linux system and installation requirements

Check	What to look for
deb format	For Debian, Ubuntu and compatible package management systems; declared dependencies must be met.
rpm format	For Fedora, RHEL-based and compatible package management systems; check distribution and runtime compatibility.
Processor architecture	Choose x64 for common Intel and AMD desktops, or arm64 for 64-bit ARM desktops.
Desktop environment	Requires a desktop session that can run graphical apps. Tray support depends on the desktop environment.
System proxy	Desktop environments and apps handle proxy settings differently; check each one separately.

If dependencies conflict, review the missing components reported by the package manager rather than forcing the installation. After enabling the system proxy, browsers and other apps may behave differently; check each app's network settings. Confirm that manual launch, import and connection all work before configuring startup at desktop login, to avoid running multiple instances.

Linux installation and desktop autostart guide →

After installation

Check subscriptions, routing and connections

Import an existing configuration

The package contains the client; server configuration must be provided separately. If you have a subscription, create a subscription group, enter the full URL and refresh it. If you have a single connection configuration, use the client's import option. After importing, check that the protocol, address and required settings are complete, then select the server you want to use.

Subscription URLs may contain access credentials. Do not include them in public screenshots, discussion forums or shared documents. If an update fails, check that the URL is complete and still valid, and that your current network can reach the subscription endpoint. Reinstalling the same client repeatedly will not fix an expired URL.

See the subscription import guide →

Understand proxy settings and routing

The system proxy directs apps that follow its settings to send traffic through the client. Routing determines whether traffic is proxied, connected directly or handled by another rule after it reaches the client. These are separate layers. On desktop, selecting a server without enabling the relevant proxy setting may leave your browser on its original network route.

On Android, check per-app settings and the system VPN status after connecting. Start by testing one specific app scenario, then add rules as needed. If you cannot connect, name resolution fails or the connection drops when the screen locks, note the exact error and what triggered it; this makes troubleshooting easier than changing several settings at once.

Troubleshoot by symptom →

Download FAQs

Choosing and updating packages

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

For a first install, try Desktop, which uses a newer cross-platform interface. WPF is the classic, stable edition for users who prefer the familiar Windows interface and workflow. Both downloads are x64 packages. Back up subscriptions, routing rules and other custom settings before switching, and avoid running both instances as system proxies at the same time.

How do I choose between Apple Silicon and Intel builds for macOS?

Open About This Mac from the system menu and check the Chip or Processor field. For an Apple M-series chip, choose Apple Silicon (arm64); for an Intel processor, choose Intel (x64). Use the build that matches your Mac's chip, and quit any older client before installing.

Should I download the arm64 or universal Android build?

Most mainstream phones released since 2015 can start with arm64, but make sure the operating system supports 64-bit apps. If you are unsure of the device architecture or the arm64 package is incompatible, try the universal build. It supports more architectures and is usually larger, but does not improve connection speed.

Which Linux package should I choose: deb or rpm?

Choose deb for Debian, Ubuntu and compatible distributions; choose rpm for Fedora, RHEL-based and compatible distributions. Then select x64 or arm64 for your processor. A matching package format does not guarantee that every distribution version meets the dependencies. If the graphical installer reports missing dependencies, check your distribution version and runtime requirements.

Can I connect as soon as the client is installed?

The package contains the client, not a usable server configuration or subscription service. Import a valid subscription or connection configuration, choose a server and routing mode, then enable the system proxy or Android VPN connection. Subscription URLs may contain access credentials, so keep them private.

Do I need to import my subscription again when updating the client?

Routine updates with the same client and configuration directory usually preserve existing settings, but you should still make a backup. Save subscription URLs, routing rules and custom settings, then quit the app before installing the update. Switching clients or configuration directories may require importing again. Updating the client and refreshing a subscription are separate tasks.

More installation and setup questions →