Client installers / platforms and architectures

V2Ray Client Downloads

Choose v2rayN for desktop and v2rayNG for Android. Confirm your operating system first, then download the right CPU architecture. v2flyNG is an alternative powered by the V2Fly core.

Free to use Open source Graphical interface Import your own subscription

Windows Desktop Installers

One client, two interfaces. Both downloads below are for x64.

v2rayN

Recommended 7.24.1

Desktop edition · x64

Download Desktop installer

A modern, cross-platform UI. A good starting point for a first install or if you want a consistent experience across desktop systems. Manage server lists, subscription groups, and routing settings in the graphical interface.

Classic WPF edition · x64

Download classic WPF installer

The familiar, stable Windows interface. Choose this edition if you prefer traditional menus and lists. Menus may differ between editions, so follow the labels in your current interface. Switching editions doesn’t require buying another subscription.

Once the ZIP file downloads, extract all its contents to a writable folder, then run the installer inside. Don’t launch it from the archive preview. After installation, import a subscription or share link, select an active server, and configure the system proxy. Simply opening the client won’t automatically route all your apps through the proxy.

Before switching between Desktop and WPF, export any manually added servers and custom rules. On first launch, check local listening ports, DNS, and routing settings to avoid carrying over parameters that don’t suit your setup. Running both editions at once may cause port conflicts, so exit the first one before starting the other.

Windows installation requirements

What to check	Selection and setup
System and architecture	Open Settings → System → About to check your system type. Both installers on this page are for x64 and aren’t native installers for other architectures.
Runtime dependencies	Supported Windows versions and runtime requirements vary by release. If the installer reports a missing runtime, follow the instructions for that release. A file extension alone doesn’t tell you whether it’s compatible.
Permissions and folders	The configuration folder must be readable and writable. Standard system proxy and TUN have different permission requirements; grant the permissions requested by the client only when enabling the relevant feature.

macOS Choose by chip

Open the Apple menu → About This Mac and check Chip or Processor.

v2rayN

Desktop client 7.24.1

Apple Silicon · arm64

Download for Apple Silicon

For Macs that show an Apple M-series chip in About This Mac. Prefer the native build for your chip; don’t choose the Intel build just because its filename contains “64.”

Intel · x64

Download for Intel

For Macs that list an Intel processor. The same macOS version doesn’t mean the processors are the same. If the app reports an architecture mismatch at launch, check About This Mac instead of reinstalling repeatedly.

After opening the DMG, follow the installer prompts to move the app into Applications, then launch it from there. If macOS displays a security warning on first launch, check the file’s source and the warning, then use the system’s one-time approval option. Avoid disabling system-wide security just to launch one app.

After importing a configuration, check the server type and transport settings, then enable the system proxy or configure TUN if needed. Some apps use their own network settings and may not follow the system proxy. If your browser works but other apps don’t, check those apps’ proxy settings before changing your subscription.

macOS installation requirements

What to check	Selection and setup
Chip type	Choose arm64 for Apple M-series chips and x64 for Intel processors. Check About This Mac to confirm.
System compatibility	Check the release notes for the minimum macOS version. Older systems may not support dependencies required by the new interface, so confirm compatibility before downloading.
Network permissions	System proxy and TUN work differently. When prompted to approve a network extension or grant elevated permissions, confirm which feature you’re enabling and why it needs access.

Android Choose a client

We recommend v2rayNG. Consider v2flyNG if you need compatibility with the V2Fly configuration ecosystem.

v2rayNG

Recommended · Xray core 2.2.6

arm64 · Recommended for most phones

Download v2rayNG arm64

Most mainstream phones released since 2015 can use arm64. Actual support depends on the app ABI provided by the system. A small number of phones have 64-bit processors but run a system with a different architecture, so check what your device supports.

Universal · For unknown architectures

Download v2rayNG universal

One installer supports multiple compatible CPU architectures, making it a good choice if you haven’t confirmed your device’s ABI. Universal doesn’t mean it works with every Android version; the system version and client requirements still apply.

v2rayNG uses the Xray core and suits Android configurations that need its protocol and transport features. After installation, import a configuration from the clipboard, a QR code, or a subscription group. The first time you enable VPN mode, Android will ask for permission to connect. Approve it so the client can use VpnService to route traffic from selected apps.

If the connection drops after the screen locks, check battery optimization and background activity permissions. When per-app proxying is enabled, review the app list and what bypass mode means. You’ll usually need to reconnect for changes to the list to take effect. Don’t run another app that occupies the system VPN connection at the same time.

v2flyNG

Alternative · V2Fly core 1.10.31

arm64 · Confirmed architecture

Download v2flyNG arm64

For devices running an arm64 system with configurations that match V2Fly features. Choose this alternative for configuration compatibility, not simply by comparing app names or version numbers.

Universal · Supports multiple architectures

Download v2flyNG universal

Choose the universal build if you’re unsure of your architecture. Save your original subscription URL and manual configurations before installing. Data from v2rayNG won’t automatically transfer when you install another app.

V2Fly and Xray are related but independently developed core families, with differences in extensions and configuration fields. Don’t assume another client can read every custom JSON configuration. To migrate, import one known-working configuration first and check the protocol, transport, TLS, and routing before restoring the rest of your subscriptions. See the protocol reference for details.

Android installation requirements

What to check	Selection and setup
System and ABI	Your Android version must meet the APK’s minimum requirements. Choose arm64 once you’ve confirmed your architecture, or the universal build if you’re unsure. Device age is only a rough guide.
Installation permission	Allow the browser or file manager you use to open the APK to install unknown apps. You can revoke this permission after installation if you prefer.
Connection and background activity	VPN mode requires system permission to connect. Background restrictions may interrupt the connection; adjust battery management settings for the client as needed.

Linux Distribution and architecture

First check whether your distribution uses deb or rpm, then choose x64 or arm64.

v2rayN

Desktop GUI 7.24.1

deb · x64 / amd64

Download x64 deb package

For compatible desktop distributions that use the deb package system, such as Debian and Ubuntu-based systems. Here, amd64 means x64 architecture and isn’t tied to a specific processor manufacturer.

For arm64 devices: Download deb package →

rpm · x64 / x86_64

Download x64 rpm package

For compatible desktop distributions that use the rpm package system. The same package format doesn’t guarantee the same dependencies, so check both the target system and your local dependencies.

For arm64 devices: Download rpm package →

Open the package with your distribution’s software installer, review the dependency prompts, and complete installation. If dependencies are missing, check your distribution, the package’s target environment, and your architecture. Don’t force installation by ignoring dependencies. The GUI client requires a working desktop session; these installers aren’t server-side service packages.

On first launch, import a configuration and check the local proxy listening address and port. Whether the desktop system proxy takes effect depends on whether each app follows that setting. For broader traffic routing, review TUN permissions and routing implications. Keep the original network settings so you can troubleshoot and restore them if needed.

Linux installation requirements

What to check	Selection and setup
Package format	Choose deb or rpm based on your distribution’s package manager. Renaming a file extension won’t convert a package to another format.
CPU architecture	x86_64 and amd64 correspond to the x64 package on this page; aarch64 usually corresponds to arm64. Check your device information in system settings to confirm.
Desktop and dependencies	You need a compatible graphical desktop and the runtime dependencies required by the release. If the installer reports an error, note the missing components before deciding whether the package suits your system.

Setup after installation

Get one connection working first, then adjust routing and advanced options. This makes problems easier to pinpoint.

Import a configuration

The client and subscription are separate. Have a subscription URL, QR code, or share link that you obtained legitimately, then import it through the client’s import option. After adding a subscription URL, update the subscription to generate a server list. URLs may contain credentials, so don’t post them publicly.
Choose a server and mode

Select an active server, check its protocol and transport settings, then enable system proxy or VPN mode. A desktop system proxy may not cover every app, and Android per-app lists change which traffic is routed. Start with clear, basic settings; avoid changing routing, DNS, and multiple transport parameters at once.
Test and save your settings

Visit a service you use regularly and check the client logs to confirm the connection is established. A connectivity test doesn’t tell you the actual download speed. If something goes wrong, check the server, network path, and local settings in turn. Once connected, back up your configuration and add routing rules as needed.

See the subscription import and connection guide →

Updates and configuration migration

Keeping your data recoverable matters more than simply installing over the old version.

Before updating, note the client, installation channel, and architecture you’re using. Save subscription URLs, manually added servers, and custom routing rules. Desktop users should also record system proxy, listening ports, DNS, and TUN settings. Don’t rely on screenshots of server names alone: display names aren’t enough to restore protocol settings. Use the client’s export feature when needed.

Routine updates to the same client usually preserve user data, but that doesn’t replace a backup. Different interfaces, clients, or signing channels may use different data folders and import methods. Exit the old client first, then install the new one and import a small number of configurations to test them before restoring the rest. If Android reports a signature conflict, make sure your backup is restorable before removing the old app.

The client version shown on this page and the installer filename come from different catalog fields, so filenames may retain channel labels. After installation, check the client’s About page for the actual build details. Don’t compare version numbers across different projects to judge feature sets; protocol support depends on the client’s core and your configuration.

Installer FAQs

Six checks covering architecture, installation permissions, migration, and your first connection.

Should I choose the Windows Desktop or classic WPF edition?

For your first install, try Desktop, which uses a modern cross-platform interface. If you prefer the familiar Windows layout, choose the stable classic WPF edition. Both require an imported working configuration. Back up subscriptions, routing rules, and custom settings before switching, and avoid running both editions on the same local ports.

How do I know whether to download arm64 or another architecture?

Check your system’s processor information first. On a Mac, open About This Mac: choose Apple Silicon if it lists an Apple M-series chip, or Intel if it lists an Intel processor. Most Android devices can use arm64, but check app ABI support on older devices or systems; choose the universal build if unsure. On Linux, also confirm the package format for your distribution.

Why won’t my Android installer install?

Check that your browser or file manager is allowed to install unknown apps, then verify available storage, CPU architecture, and Android version. A signature conflict may mean the existing app came from a different signing channel. Export your configuration and make sure you can restore it before removing the old app; don’t delete data you haven’t backed up.

Can v2rayNG and v2flyNG use the same configuration?

Some common share links and subscription content can be imported into either client, but they use different cores, so their configurations aren’t fully interchangeable. For REALITY or specific transport extensions, check support in both the client and its core. Keep your original subscription URL, import it into the new client, and verify the protocol, transport, and security settings.

What should I save before updating a client?

Save subscription URLs, manually added servers, custom routing rules, and DNS settings. Desktop users should also note local ports, system proxy, and TUN settings. Use the client’s export or backup feature, and make sure the backup can be opened before updating. Subscription URLs may contain credentials, so store them only somewhere you trust.

Can I connect as soon as the client is installed?

The installer provides only the client, not a server or subscription service. Import a valid server configuration you obtained legitimately, select an active server, then enable proxy or VPN mode for your system. If the client starts but apps aren’t using the proxy, check system proxy settings, per-app settings, routing rules, and logs.

See more configuration and troubleshooting FAQs →

V2Ray Client Downloads

Windows Desktop Installers

v2rayN

Desktop edition · x64

Classic WPF edition · x64

Windows installation requirements

macOS Choose by chip

v2rayN

Apple Silicon · arm64

Intel · x64

macOS installation requirements

Android Choose a client

v2rayNG

arm64 · Recommended for most phones

Universal · For unknown architectures

v2flyNG

arm64 · Confirmed architecture

Universal · Supports multiple architectures

Android installation requirements

Linux Distribution and architecture

v2rayN

deb · x64 / amd64

rpm · x64 / x86_64

Linux installation requirements

Setup after installation

Import a configuration

Choose a server and mode

Test and save your settings

Updates and configuration migration

Installer FAQs