Client downloads · Platform and architecture

V2Ray Client Downloads
v2rayN and v2rayNG

Choose your operating system first, then the processor architecture. Use v2rayN on desktop; for Android, v2rayNG is the recommended choice, with v2flyNG as an alternative depending on your configuration needs.

New here? See the installation and setup steps

Choose a package by platform

After choosing a platform, check the matching client, package format and system requirements. Version details appear on each client card.

Windows · v2rayN

v2rayN

Top pick

Windows x64Desktop GUI client7.24.1

Desktop edition

New-generation cross-platform UI; recommended for first-time installs.

Download Desktop · x64 ZIP archive · Extract to install

Classic WPF edition

A familiar, reliable Windows interface for users who prefer the classic layout.

Download WPF · x64 ZIP archive · Extract to install

Desktop and WPF differ in their interface technology and layout, not in their connection protocols. Both require a valid configuration; the interface edition doesn’t determine whether your subscription works. Start with Desktop if you’re new. If you already use WPF, you can stick with the classic interface—switching editions repeatedly won’t fix connection problems.

After downloading, extract the entire archive to a writable folder, then run the installer inside it. Don’t launch the app from the archive preview. If Windows reports a missing runtime, check which component and architecture it requires. Don’t mix program files from different versions in the same folder.

Windows requirements and installation checks

Check	What to look for	Where to check
Processor architecture	Both downloads on this page are x64 packages.	Settings → System → About: check System type.
OS and runtime	Use a supported 64-bit version of Windows. Check the installer for the current minimum requirements.	Run the installer and note any compatibility or runtime warnings.
Installation and permissions	The install folder must be writable. System proxy and TUN have different permission requirements.	Start without elevated permissions; grant them only when enabling a feature that requires admin access.

After installation, first test browser access using the system proxy. TUN routes traffic through a virtual network interface and usually needs additional permissions. You don’t need to enable every traffic-capture feature on first launch.

macOS · v2rayN

v2rayN

Recommended

macOSChoose a DMG for your chip7.24.1

Apple Silicon

For a Mac with an M-series chip, choose the native arm64 build.

Download for Apple Silicon DMG disk image · arm64

Intel

If About This Mac shows an Intel processor, choose the x64 build.

Download for Intel DMG disk image · x64

Open About This Mac from the Apple menu and check Chip or Processor. M-series chips use Apple Silicon; if an Intel model is listed, choose the Intel build. Don’t rely on the computer’s appearance or purchase year—the same product name can span multiple chip generations.

Open the DMG and follow the on-screen instructions to move the app to Applications. Launch it from there. If macOS shows a security warning, read it and confirm the app’s source before using the system’s authorization options. Don’t disable system-wide security settings to fix one app’s startup issue.

On your first connection, check that the client is running, a profile is selected and a proxy mode is enabled. Seeing the app window doesn’t mean the system proxy is on. Quit the old app before updating so it doesn’t keep a listening port in use.

macOS requirements and installation checks

Check	What to look for	Where to check
Chip	Choose arm64 for Apple Silicon and x64 for Intel.	Apple menu → About This Mac.
OS compatibility	Use a supported version of macOS. Check the app’s current requirements.	The macOS version and startup prompts in About This Mac.
Install location	Move the app to Applications and keep enough writable space for its configuration data.	Finder → Applications.

If you downloaded the wrong architecture, quit the app and install the matching build. Don’t assume translation is the best option; use a build made for your chip when available.

Android · Choose a client, then an architecture

v2rayNG

Top pick

AndroidXray core2.2.6

arm64

Recommended for most phones released since 2015; check that your OS is supported.

Download v2rayNG · arm64 APK · arm64-v8a

Universal

Choose this build if you’re unsure of your architecture or arm64 isn’t compatible.

Download v2rayNG · Universal APK · Multiple architectures

v2rayNG uses the Xray core and lets you import subscriptions, configure routing and manage per-app proxy settings on Android. The core handles connections; the client provides the configuration interface. You’ll still need valid connection details. Match protocol and transport settings to the server—don’t guess additional fields based on the protocol name alone.

When you open the APK, Android may ask you to allow the browser or file manager to install unknown apps. Grant permission only to the app you’re using to install it. The first time you start VPN mode, review and approve Android’s connection request. This grants access to the local traffic-routing interface; it doesn’t provide a valid subscription.

v2flyNG

Alternative

Androidv2fly core1.10.31

arm64

Choose this build if you need the v2fly core and your device supports arm64.

Download v2flyNG · arm64 APK · arm64-v8a

Universal

For devices with an unknown architecture or a need for broader architecture support.

Download v2flyNG · Universal APK · Multiple architectures

v2flyNG is an alternative client that uses the v2fly core, not another architecture build of v2rayNG. Choose it only if its configuration support meets your needs; the two apps’ core features aren’t identical. After switching, check that your subscription imported correctly, then review routing rules and proxy mode.

Before migrating, save your subscription URL and custom settings, then import them into the new app. Don’t overwrite one app’s data directory with files from another. When testing both apps, enable VPN mode in only one at a time to avoid confusion if Android switches the active VPN.

Android requirements and installation checks

Check	What to look for	Where to check
App architecture	Choose arm64 for most devices; use Universal if you’re unsure.	Device specifications and compatibility warnings during installation.
Android version	Check the APK’s minimum Android version and any system installation warnings.	Settings → About phone → Android version.
Install permissions	Allow the app you’re installing from to install apps.	Android’s Install unknown apps setting.
Connection permission	VPN mode requires approval of Android’s connection request.	The system permission prompt shown on first launch.

A background disconnect and an installation failure are different issues. Check battery optimization and background restrictions only if the system stops the client after the screen locks. Don’t start by repeatedly uninstalling the app.

Linux · v2rayN

v2rayN

Recommended

Linux desktopdeb / rpm7.24.1

deb · x64

For distributions that use deb packages.

Download deb · x64 For arm64 devices: download the deb package

rpm · x64

For distributions that use rpm packages.

Download rpm · x64 For arm64 devices: download the rpm package

Check your distribution’s package format first, then your processor architecture. deb and rpm refer to packaging systems, not connection capabilities. amd64 and x86_64 usually correspond to x64 here; aarch64 corresponds to arm64. Different architecture aliases in a filename don’t mean it’s a different client.

Open the downloaded package with your distribution’s software installer and review its dependency and compatibility warnings. Using the same package format doesn’t guarantee compatibility with every release of a distribution. If the installer reports a missing library version, check whether your distribution is supported. Don’t force past dependency checks or use a package for another system.

This page provides a desktop GUI client. After installation, launch it from the app menu, import your configuration and test the system proxy before considering TUN. Proxy behavior depends on how your desktop environment applies proxy settings and whether each app respects them. Seeing the client running doesn’t mean every app is using the proxy.

Linux requirements and installation checks

Check	What to look for	Where to check
Package format	Choose deb or rpm for your distribution; the installer will check the required dependencies.	Your distribution’s software center and system documentation.
Processor architecture	Use the matching package for x64 or arm64.	Device or processor details in system settings.
Runtime environment	Requires a graphical desktop environment and a writable user configuration directory.	Your desktop session and any dependency warnings from the software installer.

After upgrading with the package manager, quit and relaunch the client. Check the About page to confirm the version actually running, so you don’t continue using an old process still in the background.

Three checks to make after downloading

Installation is just the first step. Follow these checks in order to separate installation issues from configuration problems.

Step 01

Confirm the app starts

Open the client and find Settings and About. Note the client name, running version and OS version. If the app closes immediately, check the architecture, runtime, install location and permission warnings first. Don’t start by repeatedly changing your subscription settings.

Step 02

Import an existing subscription

A subscription link retrieves connection configurations in bulk. Paste it into a subscription group, save it, then update the list and check that profiles appear. Subscription links may contain access credentials—don’t include the full URL in public screenshots, support posts or shared logs.

Step 03

Choose a mode and test the connection

Select a profile, confirm the proxy mode and routing preset, then connect. First, test a real website in your browser, then check other apps. A latency test reflects only its target and test method; it can’t replace a real-world connection test.

Read the complete getting started guide →

Back up your configuration before updating

Back up before you update. Keep your subscription URLs, custom routing rules, per-app proxy lists and manually added profiles. Use the client’s export feature when available. Exported files may contain access credentials, so store them somewhere private and trusted. Updating the client and refreshing a subscription are separate actions; an app update won’t renew or repair an invalid service configuration.

Before updating, stop the connection and quit the old app, then run the installer. If changing the install location, don’t mix the old and new program files in one folder. After relaunching, check that your configuration is intact, whether the listening port has changed and whether the system proxy is enabled. Test the basic connection before restoring custom features one by one.

If something goes wrong after an update, note which step failed and record the full error message. If the app starts but can’t connect, check the configuration and mode first. If it won’t start at all, troubleshoot the runtime environment. Checking each setting in turn makes it easier to find the cause than changing several at once.

Download and installation FAQs

First identify whether the issue occurs during download, installation, startup or connection, then follow the relevant steps.

Can I connect right after downloading the client?

You’ll also need a valid connection configuration. The installer contains the client app, not a ready-to-use service configuration. Import an existing subscription link or configuration file, update the list, select a profile, then start the proxy. For your first setup, follow the getting started guide to choose a mode and verify the connection.

Should I choose arm64 or Universal for Android?

Most phones released since 2015 support arm64, but check which app architectures your device supports. If Android reports an architecture incompatibility or you’re unsure, choose the Universal build. It supports more architectures and is usually larger. You only need one build of the same client.

Do I need to install both the Windows Desktop and WPF editions?

No. Desktop uses the newer cross-platform interface; WPF uses the classic Windows interface. Both are editions of v2rayN. For a first install, start with Desktop. Choose WPF if you prefer its familiar layout. Back up your configuration and quit the current app before switching to avoid two instances competing for the local proxy port.

How do I keep my subscriptions and settings when updating the client?

First, use the client’s backup or export feature to save your subscription URLs and custom routing rules separately. Then stop the connection and quit the app. Update using the same client and architecture. When switching to another client, don’t overwrite its data directory; migrate your settings using an import method supported by both apps.

Why might the version shown on a card differ from the installer filename?

The version label shows the app-level version, while the download button points to a package for a specific architecture; these may be updated at different times. Check the client’s About page to confirm the installed version. When troubleshooting compatibility, note the installed version, OS version and package type.

What should I check first if the app won’t open or connect after installation?

First, determine whether the app fails to start or fails to connect. If it won’t open, check the architecture, extraction location, system prompts and runtime requirements. If it opens but won’t connect, check the subscription update, selected profile, system time and proxy mode, then review the logs. Repeatedly switching installers won’t fix a configuration issue.

More FAQs · Browse configuration fields

V2Ray Client Downloadsv2rayN and v2rayNG

Choose a package by platform

Windows · v2rayN

v2rayN

Desktop edition

Classic WPF edition

Windows requirements and installation checks

macOS · v2rayN

v2rayN

Apple Silicon

Intel

macOS requirements and installation checks

Android · Choose a client, then an architecture

v2rayNG

arm64

Universal

v2flyNG

arm64

Universal

Android requirements and installation checks

Linux · v2rayN

v2rayN

deb · x64

rpm · x64

Linux requirements and installation checks

Three checks to make after downloading

Confirm the app starts

Import an existing subscription

Choose a mode and test the connection

Back up your configuration before updating

Download and installation FAQs

V2Ray Client Downloads
v2rayN and v2rayNG