Client downloads · Choose your platform

V2Ray client downloads

v2rayN for desktop; v2rayNG and v2flyNG for Android.

Confirm your operating system, then choose the processor architecture and package format. Download links are in the client cards below. Add your nodes, subscription, and routing settings after installation.

Free to use Open source First-time setup guide →

Choose a package by platform

Compare client editions →

v2rayN

Windows · x64 · 7.24.1

Top pick

Download Desktop · x64 Download classic WPF · x64

The Desktop edition has a modern cross-platform UI; WPF keeps the classic, stable desktop interface. Start with Desktop for your first install. If you’re familiar with WPF menus, subscription groups, and tray controls, you can stick with the classic edition. Both downloads are v2rayN clients; don’t run them at the same time.

Both downloads are ZIP archives. When the download is complete, extract the archive to its own folder, then open the installer and follow the prompts. Don’t launch the app from the archive preview. Keep configuration backups outside the installation folder so they’re easier to restore when changing versions.

On first launch, add a subscription URL or import a share link, update the subscription, select a node, then configure the system proxy. The system proxy mainly affects apps that follow system proxy settings; it doesn’t route every app automatically. For other modes, read the guide’s notes on permissions and routing first.

Before switching between Desktop and WPF, save your subscription groups, custom routes, and local listening ports. Don’t assume every setting will transfer automatically.

Windows system requirements

Check	What to look for
Operating system	Windows 10 or 11 with current support is recommended. Check the installer prompts for exact compatibility requirements.
Architecture	This page provides x64 packages. Check your system type under Settings → System → About.
Package format	The ZIP contains an installer. Extract the full archive before running it.
Runtime components	If the installer reports missing runtime components, install those it specifies. Repeatedly changing nodes won’t help.

An installer that won’t start and a node that won’t connect are different issues. Get the client running first, then check the subscription, proxy mode, and logs.

View the desktop setup guide →

v2rayN

macOS · DMG · 7.24.1

Recommended

Download for Apple silicon · arm64 Download for Intel · x64

Open About This Mac from the Apple menu and check the chip or processor listed. Choose the Apple silicon version for an Apple M-series chip, or the Intel version for an Intel processor. The two DMGs target different architectures; choose based on the processor, not the screen size or appearance of your Mac.

Open the DMG and follow its instructions to move the app into Applications, then launch it from there. Eject the disk image when installation is complete. If macOS shows a security warning, verify the app you’re opening and follow the system’s confirmation steps; you don’t need to disable security protections.

After importing nodes, check which one is selected and confirm the proxy mode. Some features require system permissions; understand what they do before granting access. If the connection drops after waking from sleep or switching networks, restore the network and reconnect, then check DNS and node status.

When moving to another device, export your configuration first. The app and its user settings are stored separately, so copying the app alone may not bring over subscriptions and rules.

macOS system requirements

Check	What to look for
Operating system	Use a macOS version that still receives security updates. Check the app’s startup prompt for the minimum supported version.
Apple Silicon	Apple M-series chips require the arm64 package.
Intel	Intel processors require the x64 package.
Install location	Move the app to Applications rather than running it from the DMG long-term.

If you chose the wrong architecture, check your chip details and download the correct version; there’s no need to change your subscription. Once the app starts, check your connection settings.

View the import and connection guide →

v2rayNG

Android · Xray core · 2.2.6

Top pick

Download v2rayNG · arm64 Download v2rayNG · universal

Most mainstream phones released after 2015 can use arm64. Choose the universal version if you’re unsure of your device’s architecture or the system reports that the arm64 package is incompatible. Some devices have 64-bit processors but run a 32-bit system, so check which package actually installs.

v2rayNG uses the Xray core and works with common share links and subscription workflows. To install the APK, Android may ask you to allow your browser or file manager to install apps. Grant permission as needed, then revoke it in system settings after installation. The first connection also requires VPN permission.

After importing nodes, select the one you want before starting the connection. If another app is using the device’s VPN connection, stop it first. If the connection drops repeatedly in the background, check battery management and background activity restrictions rather than just cycling through nodes.

The universal version supports multiple architectures and usually takes up more download space. Its wider compatibility—not connection speed—is what sets it apart from the arm64 version.

v2flyNG

Android · v2fly core · 1.10.31

Alternative

Download v2flyNG · arm64 Download v2flyNG · universal

v2flyNG is an alternative client powered by the v2fly core. Choose it if you already have a V2Fly configuration and want to compare how that core behaves, after confirming protocol compatibility. Similar names don’t mean another client’s advanced settings can be copied over unchanged.

Choose an architecture the same way as above: arm64 for most newer phones, or universal if you’re unsure. After installation, check your subscription groups, node settings, and routing rules again. Before migrating settings that rely on core-specific extensions, review the documentation for those fields.

You can install both clients to compare configurations, but enable only one at a time when testing connections. This avoids conflicts over the VPN connection.

Android system requirements

Check	What to look for
System compatibility	Check the Android installer prompt for the minimum OS version and package compatibility.
arm64	For mainstream devices that support 64-bit apps.
Universal version	Supports multiple architectures and is a good choice when you’re unsure which one your device uses.
Install permission	Allow the current app source to install APKs. Revoke the permission when you’re done.
Connection permission	Approve the system VPN prompt on first connection, and check whether another VPN app is active.

If Android says “App not installed,” check for an architecture mismatch, insufficient storage, or a signature conflict with an existing installation. Uninstalling may remove local settings, so back them up first.

Compare the two Android clients →

v2rayN

Linux · deb / rpm · 7.24.1

Recommended

Download deb package · x64 Download rpm package · x64

For arm64 devices: deb · arm64 rpm · arm64

Choose the package format for your distribution, then select the processor architecture. Debian- and Ubuntu-based systems typically use deb; distributions with RPM package management use rpm. Compatibility also depends on your distribution version and system libraries, not just the file extension.

Most Intel and AMD desktops use x64; devices with a 64-bit ARM processor use arm64. In package names, amd64 and x86_64 both refer to the standard x64 architecture—they don’t indicate a specific processor brand.

Open the downloaded package with your system’s software installer and review any dependency warnings before installing. If required dependencies can’t be met, check whether the package supports your distribution rather than forcing installation by ignoring them. The GUI client needs a working desktop session.

After installation, launch the client from the app menu, import your subscription, and select a node. System proxy behavior varies by desktop environment. If a browser connects but other apps don’t, check whether those apps follow the desktop proxy settings before changing modes.

When updating, preserve your user configuration and close the client first. Follow the client’s instructions for network modes that require extra permissions; avoid running the everyday GUI as an administrator.

Linux system requirements

Check	What to look for
Desktop environment	Requires a working graphical desktop session and the system libraries needed by the app.
deb	For compatible distributions that use Debian package management.
rpm	For compatible distributions that use RPM package management.
Processor	x64 corresponds to amd64 / x86_64; arm64 corresponds to aarch64.
Dependencies	Check dependencies with your software installer. Matching package formats don’t guarantee compatible system libraries.

Get the app installed and running before troubleshooting connections. Changing routes won’t help if the client won’t open.

View the routing fields reference →

Configuration steps after installation

View the full guide →

01 / IMPORT

Import a subscription or share link

The client and node configuration are provided separately. Get your own subscription URL or share link, and know the difference between adding a subscription group and importing a node from the clipboard: a subscription URL retrieves and updates a group of nodes, while a share link usually describes one connection. After importing, confirm the node appears in the list before continuing.

Subscription URLs may contain access credentials. Don’t post them in public comments or screenshots. When sharing a problem, include the error message but hide the full URL and identifying details.

02 / CONNECT

Choose a node and proxy mode

Select a node with clear settings, then use the default or guide-recommended routing mode to establish a basic connection. On desktop, check the system proxy status; on Android, approve the VPN permission. Avoid changing DNS, routes, transport, and ports all at once during your first test, or it’ll be hard to tell what caused a failure.

Proxy mode determines how traffic enters the client; routing rules determine which outbound connection handles it. They operate at different stages and aren’t interchangeable.

03 / REVIEW

Check the logs and save your settings

After connecting, open an app you need to use and check that its requests appear in the logs. For timeouts, connection refusals, or resolution failures, troubleshoot in this order: local listener, routing match, then remote connection. Once the basic connection works, export your configuration or make a backup before adding custom rules one at a time.

Logs may contain domain names, addresses, and connection settings. Remove sensitive details before sharing troubleshooting information. If you temporarily enable verbose logging, restore the usual log level when you’re done.

Download and installation FAQs

What else do you need after downloading a client?

You’ll need a working node share link, subscription URL, or compatible configuration. The installer includes the client, not ready-to-use remote connection details. After importing your configuration, select a node, set the proxy mode using the guide, and check the logs.

Which v2rayN edition should you choose: Desktop or classic WPF?

For a first install, start with the Desktop edition and its modern cross-platform interface. Choose classic WPF if you prefer its familiar menus or want to keep your existing workflow. Both are v2rayN clients. Back up your subscription groups and custom rules before switching.

Should you download the arm64 or universal Android version?

Most mainstream phones released after 2015 can use arm64, but check that your system supports 64-bit apps. Choose the universal version if you’re unsure of your device’s architecture or arm64 is reported as incompatible. Universal APKs are usually larger because they include multiple architectures; they aren’t faster.

Can v2rayNG and v2flyNG use the same subscriptions?

Check that both the subscription format and node protocols are supported by your chosen client. v2rayNG uses the Xray core, while v2flyNG uses the v2fly core, and their supported configuration fields differ. A subscription appearing in the list doesn’t guarantee every node will work; check each node’s settings and logs after importing.

How do you keep your settings when updating the client?

Use the client’s export or backup feature to save your configuration, and note your subscription groups, custom routes, listening ports, and DNS settings. Close the client before updating. After the upgrade, test a known working node before changing anything else.

The client installed but won’t connect. Should you try a different package?

First check that a node is selected, the subscription is valid, system proxy or VPN permissions are enabled, and the system clock is correct. If the client starts normally, use the logs to check ports, DNS, and node settings rather than replacing the installer right away. Check the package type first only if the architecture is incompatible or the app won’t start.