Client downloads / Choose a platform

V2Ray downloads and client selection

For Android, we recommend v2rayNG; for desktop, choose v2rayN. Check your operating system and processor architecture before downloading.

4 platforms 3 clients Xray / v2fly cores Free clients · Open-source code

These packages install the client; you’ll need to provide your own subscription URL or connection configuration. If you already have the client installed, export your current configuration before updating.

Downloads by platform

Select a platform tab to view its downloads. The platform selection is saved in the link, so reopening it returns to the same system.

v2rayN

Recommended Windows · 7.24.1

Windows x64 offers two v2rayN downloads: Desktop and classic WPF. For a first install, try Desktop; if you prefer the classic interface, choose WPF.

Desktop edition

Download Desktop · x64

A newer cross-platform UI. A good fit for first-time setup and for users who want a similar interface across desktop systems.

Classic WPF edition

Download classic WPF · x64

The classic, stable edition for Windows. Choose it if you prefer the familiar workflow; some menu names and locations differ from Desktop.

This download is a ZIP archive. Extract it to its own folder, then open the installer inside. Don’t run it from the archive preview.

Windows requirements and installation

Requirement	Package requirements	Where to check
Processor architecture	x64; not for 32-bit systems	Settings → System → About → System type
Operating system	Use Windows 10 or 11 that still receives system updates where possible; check the installer for the exact minimum version.	Settings → System → About
Installation environment	Must be able to extract ZIP archives and write to the installation folder. Follow the installer’s instructions if dependencies are missing.	Downloads folder and installer

Exit v2rayN before installing over an existing copy. If the old client has the system proxy enabled, turn it off from the tray menu first to avoid leaving your browser pointed at a local port that is no longer running. After installation, open the client and check that your subscription groups are still there before re-enabling the proxy.

Desktop and WPF are different interfaces, not different subscription services. Choose one; you don’t need to run both to connect. Running two copies that use the same local listening port can cause conflicts. To try the other edition, fully exit the current one and back up its configuration folder separately.

After installation, add your address under subscription groups and update it. Enable the system proxy only if you want your browser to use the proxy. To route apps that don’t honor system proxy settings, see the TUN section in the user guide. System proxy and TUN are separate settings.

v2rayN

macOS · 7.24.1

Open About This Mac from the Apple menu. If it shows an Apple M-series chip, choose Apple Silicon; if it shows an Intel processor, choose Intel.

Apple Silicon

Download Apple Silicon · DMG

For arm64. Choose this based on the chip shown in About This Mac, not the computer’s purchase year.

Intel

Download Intel · DMG

For x64. Choose this for a Mac identified as having an Intel processor in About This Mac.

macOS requirements and installation

Requirement	Package requirements	Where to check
Chip architecture	Apple Silicon uses arm64; Intel uses x64	Apple menu → About This Mac
Operating system	Use a macOS version that still receives system updates; check the app installer for the minimum version.	System Settings → General → About
Installation permissions	You must be able to copy the app to Applications. Follow system prompts to authorize network configuration changes.	Finder and System Settings

After downloading the DMG, double-click it to mount the disk image, then copy the app to Applications and launch it from there. Once the copy is complete, you can eject the disk image. Avoid running the client from the mounted image; it can be easy to lose track of the active copy when updating or clearing downloads.

If a security prompt appears on first launch, read it carefully and check the app name and file source before following the steps in System Settings → Privacy & Security. Don’t disable system-wide security protections just to launch the app. If macOS explicitly reports that the file is damaged or unsafe, stop and verify the download before proceeding.

After importing a subscription, select a profile and connect before deciding whether to enable the system proxy. If your browser stops working after a network change, waking from sleep, or quitting the client, check whether the system proxy still points to a local listening port. It can forward requests only while the client is running and using that same port.

v2rayNG

Recommended Android · Xray core · 2.2.6

For Android, we recommend v2rayNG. Most phones released since 2015 can use arm64; choose the universal build if you’re unsure of your system architecture.

arm64

Download v2rayNG · arm64

For Android systems that support arm64-v8a apps. This is a good first choice for most newer phones.

Universal

Download v2rayNG · Universal

Choose this if you’re unsure of your device’s architecture. It includes components for multiple architectures and is usually larger than a single-architecture package.

The version shown in the manifest may temporarily differ from the version in the package name. Check the version shown by the system installer before installing, then confirm it in the client’s About screen.

v2flyNG

Alternative Android · v2fly core · 1.10.31

Consider v2flyNG if your existing configuration is specifically designed for the v2fly core. Before choosing it, check that the client’s built-in core supports your protocol, transport, and configuration fields.

arm64

Download v2flyNG · arm64

For phones that support arm64-v8a. Installs as a separate client and does not replace v2rayNG.

Universal

Download v2flyNG · Universal

For devices with an unknown architecture. The universal build does not add protocol support that the core itself lacks.

Android requirements and installation

Requirement	Package requirements	Where to check
Device architecture	The arm64 package requires arm64-v8a support; choose Universal if you’re unsure.	Device specifications or system app compatibility information
Android version	Check compatibility in the installer; older systems may not support the current package.	Settings → About phone → Android version
Installation permissions	Allow installs for the browser or file manager you’re using to open the APK.	Settings → Apps → Special app access → Install unknown apps
Connection permission	The first time you connect in VPN mode, approve the system connection request.	System dialog shown when the client starts a connection

Once the download is complete, open the APK from your browser’s downloads or a file manager. If Android asks for permission, allow installs only for the app opening the file. You can turn this permission off again in Settings after installation. Menu names vary by phone; follow what your system displays.

A 64-bit processor doesn’t guarantee that the system can run 64-bit apps. Some older devices use different system builds, so the phone’s release year alone isn’t enough to determine compatibility. If the arm64 package won’t install, read the system message and try the universal build only if it reports an incompatibility. Don’t keep downloading the same file.

After installation, open Subscription Group Settings, enter a name and subscription URL, save, then return to the main screen and update the subscription. Once profiles appear, select one and tap Connect. Approve the system prompt the first time you use VPN mode. If another VPN connection is already active, decide which one to keep; typically, only one VPN service can be active for a user at a time.

v2rayNG and v2flyNG use different core families, so similar interfaces don’t guarantee that configurations are interchangeable. Check core support especially for VLESS, REALITY, and newer transport fields. You don’t need to run both clients at once. To compare their differences, see a side-by-side comparison of three clients.

v2rayN

Linux · 7.24.1

Choose deb or rpm based on your distribution, then check the processor architecture. The two primary downloads below are x64; arm64 devices should use the smaller links.

deb package · x64

Download deb · x64

For distributions that use the deb package format. Compatibility still depends on the distribution version and its dependencies.

arm64 devices: Download deb

rpm package · x64

Download rpm · x64

For distributions that use the rpm package format. A matching package format doesn’t guarantee that every distribution has the required runtime dependencies.

arm64 devices: Download rpm

Linux requirements and installation

Requirement	Package requirements	Where to check
Desktop environment	A desktop session that can run graphical applications	System Settings → About
Processor architecture	x64 corresponds to amd64 / x86_64; arm64 corresponds to arm64 / aarch64	Hardware and architecture in system information
Package format	Choose deb or rpm for your distribution and install the dependencies listed by its package manager.	System software installer
Permissions	Installation requires the appropriate system permissions. TUN requires different authorization from the standard system proxy.	Installation and network-mode permission prompts

Open the package in your file manager and use your distribution’s software installer to review its details and dependencies. If dependencies are missing or their versions don’t meet requirements, resolve the system warnings first; don’t force the installation past dependency checks. After installation, launch v2rayN from the application menu, then import your subscription.

On Linux desktops, system proxy behavior depends on both the desktop environment and the app. Some apps use the system proxy; others require you to enter the local proxy address in their network settings. First check that the client is running and the app’s port matches the local listening port. Then decide whether you need TUN to route traffic.

On an arm64 device, don’t download the x64 package just because its main button stands out. In filenames, amd64 and x86_64 both refer to the x64 download; aarch64 refers to arm64. If the installer reports an architecture mismatch, return to this page and choose the right package instead of changing the file extension.

Configure the client after installation

Get one configuration working first, then add routing rules, per-app proxying, or TUN. Changing one thing at a time makes problems easier to track down.

Import your subscription, then update it

Open the client’s subscription group menu, add a group, and paste the full URL. Saving the address creates a group but doesn’t fetch profiles; return to the subscription menu and update it, then check the list. Preserve the full URL, including any access parameters. Don’t mistake a shortened URL displayed by your browser for the complete address.

A subscription provides connection configurations; the client runs them. Downloading a client doesn’t create a usable subscription or change the validity period of an existing one. If an update fails, first check that the URL is still valid, then review the logs. Reinstalling the app repeatedly won’t troubleshoot the issue.

See how to import a subscription

Test the connection before configuring routes

Select a profile and connect, then check that the client reports no core startup errors. On Android, check VPN permission; on desktop, check whether the system proxy or app proxy is enabled. Web access also depends on DNS, routing, and the destination service, so one test can’t tell you whether every part of the connection is working.

Once the basic connection works, configure LAN bypass, domain rules, or per-app proxying as needed. Change one type of setting at a time and keep a backup you can restore. For a step-by-step learning path, start with the manual’s core concepts; you don’t need to enable every advanced option during initial setup.

Read the guide, from beginner to advanced

Download and installation FAQ

Start by checking the package type and system requirements mentioned in the prompt. For connection issues, see the FAQ.

Should I download arm64 or universal for my Android phone?

Most phones released since 2015 can use arm64, but check that the system supports 64-bit apps. Choose the universal build if you’re unsure of the architecture or the arm64 package is reported as incompatible. The universal build is usually larger; it does not mean faster connections.

What’s the difference between v2rayN Desktop and the classic WPF edition?

Desktop uses a newer cross-platform UI, while WPF is the classic, stable edition for Windows. For a fresh install, start with Desktop; if you’re used to WPF, you can stick with it. Menus may differ between editions, so back up subscriptions and settings before switching.

Can I connect right after installing the client?

The client reads configurations and establishes connections; it does not include a ready-to-use subscription. After installation, import a subscription URL or configuration you’re authorized to use, update it, then select a profile and connect. On Android, you’ll typically need to approve the system VPN prompt the first time.

Android says “App not installed.” What should I check first?

Check that the package finished downloading, there’s enough free storage, and its architecture matches your device. An update may also fail if the installed app has a different signing key or the new version is older. Back up your configuration, then check the installed version and the new package’s source before taking any further action.

Will updating the client erase my subscriptions or routing settings?

An in-place update of the same app with a compatible signature will usually keep your data, but it’s no substitute for a backup. Before updating, export your configuration and note your subscription groups, routing rules, and local ports. For migration between clients, downgrades, or uninstalling and reinstalling, check configuration compatibility separately.

What if the version shown on the page differs from the one in the installer’s filename?

The displayed version and file path come from separate manifest fields, so they may briefly be out of sync after an update. Check the app version shown by the system installer before installing, then confirm the installed version in the client’s About screen. Don’t edit the download URL or filename based on the page text.