Downloads · Choose your platform

Download V2Ray clients

Desktop: v2rayN
Android: v2rayNG / v2flyNG

Choose your operating system, then check the processor architecture and package format. Use the client to import subscriptions, manage servers, and configure routing; follow the Getting Started guide to finish setup.

Choose a package View installation guide

Free, open-source clients · Downloads do not include subscriptions or server configurations

Platforms and packages

Choose the operating system on your device

A client may offer packages for different architectures. Check the desktop interface, processor architecture, and package format separately.

Windows · Download v2rayN

x64 downloads are available. Choose Desktop or classic WPF based on your interface preference; you don’t need to install both.

v2rayN

Recommended 7.24.1

Desktop · x64 Download Desktop

A newer cross-platform interface, suited to first-time users and anyone who wants a consistent layout across desktop operating systems.

WPF · x64 Download classic WPF

The established, stable version with the familiar WPF interface for Windows, suited to users who prefer its existing workflow.

The download is a ZIP archive. Extract it completely, then run the installer inside. Don’t launch it from your archive utility’s preview window.

Check your system type before installing

In Windows Settings, open “System → About” and check your system type and processor information. Both downloads on this page are x64. Choose based on the architecture your current Windows installation can run, not your computer’s brand or screen size. If your device uses another architecture, check system compatibility first; being able to download the installer doesn’t mean it will run.

Save the archive somewhere accessible and extract it completely, then follow the installation prompts. If a runtime prompt appears on first launch, follow the requirements for the interface version you chose. Runtime dependencies can differ between versions, so instructions for another version may not apply. Administrator access is usually unnecessary for managing subscriptions; grant permission only if prompted for TUN or system networking components.

Switching versions and making your first connection

Desktop and WPF mainly differ in their interface and layout; this doesn’t mean a particular server configuration will work with either version. Before switching, export your settings and close the old client, then launch the new one and import them. Don’t run both versions at once on the same local port, as this can cause startup failures, an unavailable proxy, or browser connection errors.

After installation, import an existing subscription or a single server configuration, select a server, then decide whether to enable the system proxy. The system proxy directs applications to the local client; global or bypass-mainland-China routing rules control how traffic is sent afterward. They are separate settings. For step-by-step instructions, see the v2rayN setup guide.

Check	Requirement and guidance
Operating system and architecture	Windows; the available download is x64. Check the installer prompts for supported Windows versions.
Package	Extract the ZIP archive completely, then run the installer inside.
Runtime	Install the dependencies requested by Desktop or WPF, as applicable.
Configuration	Have a subscription URL or server settings ready; the client does not provide a server.

macOS · Download v2rayN

Check your chip in “About This Mac,” then choose the Apple Silicon or Intel download.

v2rayN

v2rayN for macOS 7.24.1

Apple Silicon · arm64 Download for Apple Silicon

Choose this if “About This Mac” shows an Apple chip. The native package is the best match for your processor.

Intel · x64 Download for Intel

Choose this if “About This Mac” shows an Intel processor. Don’t infer the chip type from the computer’s purchase year.

Both downloads are DMG files. Open the disk image, follow the window’s instructions to install the app in Applications, then launch it from there.

Identify your chip and install the app

Open “About This Mac” from the Apple menu and find “Chip” or “Processor.” Apple Silicon uses arm64; Intel uses x64. Computers with the same model name may have different chips, so check what your system reports. Even with a matching package architecture, your macOS version must meet the app’s requirements; matching architectures alone doesn’t guarantee compatibility.

After downloading the DMG, open the disk image and follow the on-screen instructions. Installing the app in Applications gives you a consistent place to launch it from, rather than running it from a temporarily mounted disk image. Once installation is complete, you can eject the disk image. Before updating or removing the client, quit the app and make sure your settings are backed up.

First launch and network permissions

If macOS shows a developer verification or app-opening warning, first confirm the file’s source and that you chose the correct package, then check the Privacy & Security settings. Allow access only for the app you’ve verified. Don’t disable system-wide security just to install a client. If the warning differs from what you expect, keep the full message; it’s more useful for troubleshooting than repeatedly downloading the file.

macOS may ask for permission the first time you set up the system proxy or use a network mode that requires additional access. You’ll still need to import a valid configuration, select a server, and check your routing; granting permission doesn’t mean the connection is ready. Before quitting, check whether the system proxy has been restored. If your browser still connects to a local proxy port after the app closes, review your system network proxy settings.

Check	Requirement and guidance
System and chip	macOS; choose Apple Silicon or Intel based on “About This Mac.”
Package format	DMG disk image; follow the installer window to move the app into Applications.
System compatibility	Check the app’s installation and runtime prompts for the minimum macOS version.
Network permissions	Grant permissions for the mode you use; importing a configuration and authorizing system access are separate steps.

Android · Download v2rayNG / v2flyNG

v2rayNG is the recommended choice. Most mainstream phones released after 2015 use arm64; try the universal build if you’re unsure about your device’s architecture.

v2rayNG

Recommended Xray core 2.2.6

arm64-v8a Download v2rayNG arm64

For devices that support arm64 apps; the preferred option for most newer Android phones.

Universal Download v2rayNG universal

Includes components for multiple architectures. Choose this if you’re unsure of your device’s architecture; the download is usually larger than a single-architecture package.

The version shown on the card and the package path come from separate manifest fields. The version listed here is 2.2.6, while the current file name shows 2.3.11. Check the downloaded file and the app’s About screen to confirm the package version.

v2flyNG

Alternative V2Fly core 1.10.31

arm64-v8a Download v2flyNG arm64

Choose this alternative if you need the V2Fly core ecosystem and your device supports arm64 apps.

Universal Download v2flyNG universal

For devices with an unknown architecture or another supported architecture. Check system compatibility before installing.

Supported protocols and transports depend on the client core and its version. If you need a specific feature, check your configuration requirements before choosing an alternative client.

Choosing an architecture and granting install permission

A device’s release year is only a rough guide. Check its processor architecture and which app architectures the operating system can run. Some devices may have a capable processor but still restrict supported app architectures. If the arm64 package is incompatible, check your device documentation before trying the universal build. A universal package won’t bypass every OS version requirement.

When you open an APK, Android may ask you to allow the browser or file manager you’re using to install apps. Grant permission only to the current source, and revoke it afterward if you prefer. If installing over an existing client fails, check the app source, signing, and version. Uninstalling may erase settings, so back them up first; don’t make uninstalling your first step.

Connection permission and background operation

The first time you tap Connect, Android shows a VPN connection request. This is the system permission for the client to handle your device’s traffic; the installer does not include a remote server. Import an existing configuration before connecting, and check whether another VPN app is running. Network handling can conflict between apps, so identify which one is currently managing your traffic.

If the connection drops when the screen locks, check battery optimization, background activity, and network access restrictions, then review the client logs. Switching to v2flyNG won’t automatically fix permission issues or guarantee that every configuration can be migrated directly. For instructions on importing subscriptions and choosing routes, see the v2rayNG user guide. For protocol terms, see Quick Reference.

Check	Requirement and guidance
Operating system and architecture	Android; check for arm64 support first. See the installer prompts for the required Android version.
Package format	APK; the arm64 download is for a single architecture, while the universal build includes components for multiple architectures.
Install permission	Grant permission to the app you’re using to open the APK. Don’t leave installation permission enabled for unrelated apps.
Connection permission	Approve Android’s VPN request on first connection and check background restrictions if needed.

Linux · Download v2rayN

Check your distribution’s package format, then choose x64 or arm64. These downloads are for the graphical desktop client.

v2rayN

v2rayN for Linux desktop 7.24.1

x64 · deb Download x64 DEB

For x64 desktop systems that use DEB packages and meet the dependency requirements.

For arm64 devices: Download DEB →

x64 · rpm Download x64 RPM

For x64 desktop systems compatible with this RPM package and its dependencies.

For arm64 devices: Download RPM →

DEB and RPM are different package formats; changing a file extension won’t convert one into the other. The RPM file name specifies its target environment, so check distribution compatibility before installing.

Package format doesn’t guarantee distribution compatibility

DEB and RPM are two different package formats. Check the system’s built-in installer or package manager before choosing. Even distributions that use the same format can differ in system libraries, dependencies, or target environment, which may prevent installation. For RPM packages with a target environment in the file name, follow the dependency results reported by the package installer. Don’t force an installation by ignoring missing dependencies.

The x64 packages are for common 64-bit desktop processors; file names may use amd64 or x86_64. arm64 packages may use aarch64. These terms describe processor architecture, not package format. Match the architecture first, then the distribution’s package management system, to avoid choosing a package that installs but can’t run.

Desktop environment and proxy settings

v2rayN is a graphical client that requires an available desktop session and compatible graphical runtime. A server with only a terminal isn’t suitable just because it can install the package. After installation, launch the app from the application menu, check that your configuration directory is writable, and import an existing subscription. Don’t run the entire client with elevated privileges long-term to work around directory permissions.

Desktop environments and apps may handle system proxy settings differently. After setting a system proxy in the client, check browsers, terminal programs, and other apps individually; they may not use the same proxy. If you need TUN, see the permissions and routing guidance in Advanced Configuration. Don’t troubleshoot the desktop proxy, environment variables, and TUN as if they were one setting.

Check	Requirement and guidance
Runtime	A Linux graphical desktop session and the runtime dependencies listed by the installer.
Processor architecture	x64 corresponds to amd64 / x86_64; arm64 corresponds to aarch64.
Package management	Choose a DEB or compatible RPM package for your distribution. Don’t force the installation past dependency checks.
Configuration permissions	Your current user must be able to write to the configuration directory; grant additional network permissions as required by the mode you use.

Installation prep

Back up your settings before updating

A first-time installation and an in-place update require different preparation. For a fresh install, choose the right architecture and have your existing configuration ready. Before updating, quit the old client, save your settings, and check where the new version will be installed. Don’t back up only the app while overlooking its configuration directory.

Subscription URLs may contain access credentials, and backups may include server settings. Store them securely. When troubleshooting, don’t share full subscription links, account details, or complete configurations publicly. If you need to share logs, include only the relevant excerpts and redact sensitive fields.

Compare the three clients and find the right fit →

What to check after installation

Make sure the app launches correctly
Resolve runtime, directory permission, and system authorization issues before importing a configuration. Troubleshoot startup problems separately from connection problems.
Import a configuration you’re authorized to use
Check that subscription groups imported successfully and select a server. A successful installation doesn’t mean you’re ready to connect.
Configure the connection and routing
Enable the system proxy or connection permissions as needed, then check the routing mode. Change one type of setting at a time so you can trace the results.

Download questions

Package selection and update guide

For connection modes, subscription imports, and DNS troubleshooting, see Getting Started and the FAQ.

Which should you choose: the v2rayN Desktop or classic WPF version for Windows?

If this is your first time using v2rayN, try Desktop, which features a newer cross-platform interface. Choose the classic WPF version if you prefer the familiar Windows layout. Before switching, back up your settings and close the other version to avoid both instances using the same local port.

What’s the difference between arm64 and universal builds on Android?

For most phones released after 2015, arm64 is usually the best choice, but check your device’s actual architecture and Android version. The universal build includes components for multiple architectures and can be worth trying if you’re unsure. If Android reports that the package is incompatible, check the architecture, OS version, and signing source of the installed app. Don’t repeatedly try to install over it.

Can I connect as soon as I install the client?

The client lets you manage local settings and connections, but the installer does not include a working subscription or server. You’ll need a subscription URL or server configuration you’re authorized to use. Import it, choose a server, then configure the system proxy, routing, or Android VPN permission as needed.

What should I back up before updating the client?

Use the client’s backup or export feature to save subscription groups, custom routing rules, and DNS settings. Backups may contain subscription URLs and connection credentials, so store them somewhere secure. Close the client before updating, keep a copy of the old settings, and check that they load correctly afterward.

Why might the version shown on a card differ from the downloaded file name?

The version shown on a card and the package paths for each architecture come from separate manifest fields and may update at different times. Don’t rely on the card alone to identify a package version. Check both the downloaded file name and the app’s About screen. If they differ, verify the target architecture and required features before installing.

What should I do if a download doesn’t start?

Check your browser’s downloads list, save location, and permission prompts, then refresh the page and try the selected link again. Avoid clicking several package links in quick succession. If it still fails, note the platform, link name, and browser message, then try again later. Don’t rename a file extension to make another format run as an installer.