Can I connect as soon as the client is installed?

The installer includes the client, not a ready-to-use connection configuration. You'll need a subscription URL or share link that you're authorized to use. Import and update it, select a configuration, then enable the system proxy or grant Android VPN permission. See Getting Started for the steps.

Client installers · Choose your platform

V2Ray Download
Clients and installation guides

Choose v2rayN for desktop and v2rayNG for Android. Check your operating system first, then confirm your processor architecture.

Free to use Open source Graphical configuration

JavaScript is disabled in your browser, so the Windows download is shown by default. Enable JavaScript to switch platforms and view the download list.

Desktop / x64

Windows client

For a first installation, start with Desktop. If you prefer the familiar Windows interface, choose classic WPF. Both editions are v2rayN.

v2rayN

Recommended Windows · x64 7.24.1

Desktop edition

A newer cross-platform UI. A good starting point for your first setup.

Download v2rayN · Desktop x64 · ZIP archive

Classic WPF edition

The classic, stable Windows-only edition. A good fit if you prefer the familiar menus and layout.

Download v2rayN · WPF x64 · ZIP archive

The main differences are the interface technology and layout, not protocol support. Whether a connection works still depends on the configuration and core in use. If you already have settings, back them up before switching, and test the new edition instead of overwriting its entire configuration folder.

System requirements and installation

Check	How to choose	Installation notes
Processor architecture	Choose the x64 package on 64-bit Intel / AMD systems	Check System type under Settings → System → About; don't rely on the processor brand alone
Windows version	Windows 10 or 11 that is still supported is recommended	Check the selected release's installer for its exact minimum requirements; older Windows versions may not run it
Runtime	If startup reports a missing .NET component, install the desktop runtime specified by the client	The runtime architecture must match the client; installing only the generic runtime may not be enough
Folders and permissions	Your user account must have read and write access to the application and configuration folders	Extract the files to a local folder first; don't run the client from the ZIP preview

Extract the archive. The download is a ZIP file. Extract all its contents to a local folder before running the installer inside. Keep the required files together; don't pull out and run just one executable.
Install and launch as prompted. If you see a runtime warning, check which component and architecture are missing. Subscription management and system proxy settings generally don't require running as an administrator. Handle permissions for TUN separately.
Import your configuration. Once the client starts, add a subscription group, paste its URL, and update the subscription. Select a configuration you're authorized to use before enabling the system proxy, so system settings aren't changed before the client is ready.

If the old version is still running in the system tray, quit it before starting the new one. Two clients listening on the same local ports can cause startup failures or route apps through the old process. If the client crashes, check the runtime, folder write permissions, and configuration compatibility first. See Troubleshooting for the recommended order.

Desktop / Choose by chip

macOS client

Open About This Mac from the Apple menu and check Chip or Processor. Choose arm64 for Apple M-series chips and x64 for Intel.

v2rayN

macOS · DMG 7.24.1

Apple Silicon

For Apple M-series chips. Use the native arm64 package for best compatibility.

Download v2rayN · arm64 Apple Silicon · DMG disk image

Intel

For Intel-based Macs. Choose the x64 architecture.

Download v2rayN · Intel Intel x64 · DMG disk image

Don't infer the architecture from the Mac's purchase year; different chips may have been available around the same time. Even if macOS can translate apps built for another architecture, choose a package that matches your Mac's chip to avoid extra dependencies.

System requirements and first launch

Check	How to choose	Installation notes
Chip type	Apple M-series chips use arm64; Intel chips use x64	Use the details shown in About This Mac
System compatibility	Your macOS version must meet the current build's minimum requirements	If macOS reports that the version isn't supported, check compatibility instead of repeatedly trying other architectures
Install location	Move the app to the Applications folder	Don't keep launching the app from the mounted DMG image
Network permissions	System proxy and TUN have different permission requirements	Grant permissions only for features you use; importing a subscription doesn't require unrelated permissions

Mount the installer image. Open the downloaded DMG and drag the app into the Applications folder. Once it has copied, eject the disk image and launch the app from Applications.
Review system warnings. You may see a security warning the first time you open the app. Only after confirming the file's source and understanding the warning should you check the relevant steps under Privacy & Security in System Settings. If macOS says the app is damaged or incompatible, download it again and check the system requirements first.
Check the app's proxy settings. Import a subscription and select a configuration before enabling the system proxy options you need. The system proxy mainly affects apps that honor system settings; check proxy settings separately for terminal apps and browser extensions with their own proxy configuration.

Quit the running client before updating to avoid replacing files that are still in use. When switching architectures or moving to another device, export and reimport the settings you need rather than assuming paths, permissions, and local ports will carry over. For more setup details, see the v2rayN configuration guide.

Mobile / Check architecture first

Android client

We recommend v2rayNG. Most mainstream phones released since 2015 use arm64; consider the universal version for older devices, emulators, or when you're unsure of the architecture.

v2rayNG

Recommended Xray core · Android 2.2.6

arm64

A good fit for most mainstream phones that support 64-bit ARM apps.

Download v2rayNG · arm64 arm64-v8a · APK

Universal

Includes files for multiple architectures; choose this if you're unsure which one your device supports.

Download v2rayNG · Universal Universal · APK

v2rayNG uses the Xray core. After importing a configuration, check that the current version supports its required protocol, transport, and security settings. Importing from a QR code or clipboard only confirms that the configuration was read; it doesn't guarantee that the remote service is available.

v2flyNG

Alternative V2Fly core · Android 1.10.31

arm64

Choose this if your configuration is specifically designed for V2Fly, and match the package to your device's architecture.

Download v2flyNG · arm64 arm64-v8a · APK

Universal

For devices that need multi-architecture compatibility; this does not change the core in use.

Download v2flyNG · Universal Universal · APK

V2Fly and Xray are maintained as separate core projects. Check configuration compatibility before switching clients, especially for features supported by only one core. You can manage configurations in both clients, but they shouldn't compete for the system VPN connection at the same time.

System requirements and permissions

Check	How to choose	Installation notes
App architecture	Choose arm64 on systems that support arm64-v8a	A 64-bit processor doesn't necessarily mean the operating system supports 64-bit apps
Windows version	Your Android version must meet the selected APK's minimum requirements	If installation fails, read the specific error message from Android first
Install-from-source permission	Grant permission only to the browser or file manager you're using to open the APK	You can revoke that source's install permission after installation
VPN permission	Confirm the system prompt the first time you connect	Check whether another VPN app is already using the connection
Background activity	Allow the client to run in the background if your device requires it	Adjust battery settings for this client only; there's no need to disable battery management globally

Open the APK. Once the download is complete, open it from your downloads or file manager. If Android asks for permission to install from this source, check which app is requesting the installation and grant permission as needed.
Keep your update path open. A signature mismatch may mean the existing app and the new package were signed differently. Don't uninstall immediately. Back up your subscriptions, routes, and essential settings first, then decide whether you need to migrate. Uninstalling usually erases app data.
Import your configuration and authorize the connection. Import it from a subscription group, clipboard, or QR code. Update the subscription, select a configuration, tap Connect, and review Android's VPN permission prompt.

QR code and clipboard options read existing content; they don't create subscription URLs. Grant camera access only when needed for features such as scanning. If some apps don't use the proxy after connecting, check app routing and exclusion lists first. The system VPN icon alone doesn't confirm that every app's connection has been tested.

Desktop / Distribution and architecture

Linux client

Check your distribution's package format before choosing a CPU architecture. deb and rpm are package formats, not separate client editions.

v2rayN

Linux · Desktop 7.24.1

deb · x64

For distributions that use deb packages, such as Debian and Ubuntu.

Download v2rayN · deb 64-bit Intel / AMD · amd64

rpm · x64

For distributions that use rpm packages. Check dependencies before installing.

Download v2rayN · rpm 64-bit Intel / AMD · x86_64

For 64-bit ARM devices: Download arm64 · deb Download arm64 · rpm

Choosing the right package format is only the first step; the build must also match your system libraries and desktop environment. In particular, an rpm extension doesn't guarantee compatibility with every rpm-based distribution. Check the dependencies and error messages in your graphical package installer.

System requirements and graphical installation

Check	How to choose	Installation notes
Package format	Debian-based distributions commonly use deb; choose a compatible rpm for rpm-based distributions	Changing a file extension doesn't convert a package to another format
Processor architecture	Choose x64 for 64-bit Intel / AMD, or arm64 for 64-bit ARM	amd64 and x86_64 usually refer to the same architecture
Desktop environment	A desktop session that can run graphical applications is required	This page provides a graphical client, not a package for deploying a background service
Dependencies and permissions	System libraries must meet the requirements listed by the package installer	Handle installation authorization separately from everyday runtime permissions

Check your system information. Open your distribution's About or system information panel to check its name, version, and architecture, then choose the matching package. Don't mistake the desktop environment for the distribution.
Open the package in your software installer. Open the deb or rpm file in your file manager, review its dependencies, and follow the installation prompts. If dependencies are missing, check system compatibility instead of forcing the installation.
Launch from the app menu. Import a subscription first, then select a configuration. Whether Linux system proxy settings are honored depends on your desktop environment and the app. Terminal programs usually need proxy environment variables set separately.

Don't run the entire client with elevated privileges just to proxy browser traffic. If you need to route more traffic, first learn how TUN affects permissions, routing, and DNS. If an app ignores an enabled system proxy, check its proxy settings, local listening ports, and environment variables separately. See the routing and traffic rules guide for background.

After downloading

Installation and first-time setup

Handle installation, importing, and proxy settings as separate steps. Verify each one before moving on to make problems easier to pinpoint.

First-time setup

Import first, then enable the proxy

The client reads and manages configurations; it doesn't replace a remote service. Once you have a subscription URL you're authorized to use, add it to a subscription group and update it. For a single share link, use the appropriate import option. Pasting a webpage URL, account page, or block of explanatory text usually won't produce a valid configuration.

After selecting a configuration, set the system proxy on desktop or start the VPN connection on Android. Test with the apps you actually need and check the client's error logs. An enabled toggle alone doesn't mean the connection is working.

View subscription import steps →

Already have the client

Back up before updating

Before updating, note your current configuration sources, local listening ports, DNS, and custom routes. Use the client's export or backup feature, and store any credentials securely. Don't upload backups publicly or post them as screenshots in discussion forums.

Quit the old client before updating. When moving between interfaces, cores, or major versions, use the import method supported by the new release instead of overwriting all files. Test your frequently used apps after updating, then decide whether to enable advanced features such as TUN.

Learn about clients and cores →

Download FAQs

Choosing and updating installers

Check your device and existing configuration before choosing an installation method. For more connection help, visit Troubleshooting.

Should I choose the Desktop or classic WPF edition for Windows?

For a first-time installation, start with Desktop, which uses a newer cross-platform interface. The classic WPF edition has a Windows-specific interface and is a solid choice if you prefer the familiar layout. Both are v2rayN. Back up your settings before switching, and avoid running both clients on the same local listening ports.

Which macOS installer should I choose: Apple Silicon or Intel?

Open About This Mac from the Apple menu. If it lists an Apple M-series chip, choose the Apple Silicon arm64 package. If it lists an Intel processor, choose the Intel x64 package. If installation fails, check your macOS version and architecture; don't bypass warnings by disabling system security protections.

Should I download the arm64 or universal Android version?

Most mainstream phones released since 2015 can start with arm64, but check which architectures your device's operating system supports. Choose the universal version for older devices, emulators, or when you're unsure. It includes files for multiple architectures; that doesn't mean it will provide a better connection.

What's the difference between v2rayNG and v2flyNG?

v2rayNG uses the Xray core and is the recommended Android client on this page. v2flyNG uses the V2Fly core and is an alternative. Compatibility depends on whether the core supports the configuration's protocols, transport, and security settings; being able to import a subscription alone doesn't confirm compatibility.

Can I connect right after installing the client?

The installer includes the client, not a ready-to-use connection configuration. You'll need a subscription URL or share link you're authorized to use. Import and update it, select a configuration, then enable the system proxy or grant Android VPN permission. See Getting Started for the steps.

What settings should I keep before updating the client?

Back up your subscription groups, custom routes, DNS settings, and local ports, and note your current proxy mode. Quit the old client before installing the update. Don't assume configuration files can be carried over unchanged between versions, interfaces, or cores. After updating, check your subscriptions, listening ports, and app connections again.

V2Ray DownloadClients and installation guides

Windows client

v2rayN

Desktop edition

Classic WPF edition

System requirements and installation

macOS client

v2rayN

Apple Silicon

Intel

System requirements and first launch

Android client

v2rayNG

arm64

Universal

v2flyNG

arm64

Universal

System requirements and permissions

Linux client

v2rayN

deb · x64

rpm · x64

System requirements and graphical installation

Installation and first-time setup

Import first, then enable the proxy

Back up before updating

Choosing and updating installers

V2Ray Download
Clients and installation guides