v2rayN for desktop · v2rayNG / v2flyNG for Android

V2Ray client downloadsPlatforms, architectures, and packages

Choose your operating system first, then your processor architecture. Use v2rayN on desktop; v2rayNG is the recommended Android option. For the V2Fly core, see v2flyNG.

Free, open-source clients Bring your own subscription or nodes Setup after installation →

Windows downloads

v2rayN offers Desktop and classic WPF versions. Both downloads below are for x64; check your system type before downloading.

v2rayN Recommended

Windows · Multi-core desktop client · 7.24.1

Download Desktop · x64

A next-generation cross-platform UI. A good starting point for a first install, with subscriptions, active nodes, and routing managed in the graphical interface.

Download classic WPF · x64

The stable classic version with the familiar Windows WPF interface. Best for users who prefer the traditional layout and workflow.

Extracting, installing, and loading configuration

Both downloads are ZIP archives. Once the download finishes, extract it to a dedicated folder, then run the installer from that folder. Don’t launch it from the archive preview. Keep the installation path stable, and make sure your account can write to the relevant directories if the app needs to save configuration.

Desktop and WPF differ mainly in UI technology and layout; neither determines whether a node is faster. Back up subscriptions and custom rules before switching, exit the old client, then start the new one. Don’t run both versions at once, as they may compete for the same local listening port. After importing your configuration, check the active node, system proxy, and routing mode again.

Windows installation requirements

Check	Package requirements	Where to check and what to do
Processor architecture	x64	Open Settings → System → About and check System type.
System and runtime	Must meet the selected client package’s requirements	Check the installer’s messages for system and runtime requirements. “64-bit” alone doesn’t confirm compatibility.
Files and permissions	Extract the files, then run the installer	Choose a folder you can write to. TUN features may require additional permissions.
Connection setup	A valid node or subscription	Import your configuration, select a node, set the system proxy, and check the logs.

The system proxy only affects apps that follow the system proxy settings. To route traffic from other apps, check whether the client supports TUN and whether it meets your needs. Installation, service startup, and traffic being routed are separate steps. See the Windows setup guide for details.

macOS downloads

v2rayN provides DMG packages for Apple Silicon and Intel. Choose the architecture for your chip; your subscription and node type don’t affect this choice.

v2rayN

macOS · Multi-core desktop client · 7.24.1

Download Apple Silicon · arm64

For Macs with Apple M-series chips. Open About This Mac from the Apple menu and check the Chip field.

Download Intel · x64

For Macs with Intel processors. Choose the native architecture for your hardware to avoid extra compatibility layers.

Installing a DMG and opening the app for the first time

Open the disk image and follow the instructions to move the app into Applications, then launch it from there. Don’t run the app from the mounted disk image long-term, or you may lose access after updating or ejecting the image. When you open it for the first time, read the system prompts and confirm the app name, source, and action. Don’t disable system-wide security just to bypass a prompt.

After importing a subscription, select a node, check that the client starts its core successfully, then enable the system proxy. The system proxy and TUN route traffic differently: the former relies on apps following proxy settings, while the latter uses a virtual network interface and may need extra permissions. For your first connection, verify the system proxy path before enabling more features. This makes permission, DNS, and routing issues easier to isolate.

macOS installation requirements

Check	Package requirements	Where to check and what to do
Apple Silicon	arm64 DMG	About This Mac shows an Apple M-series chip.
Intel processor	x64 DMG	About This Mac shows an Intel processor.
System compatibility	Follow the package requirements and system prompts	Once the architecture matches, check that your current macOS version can run the app.
Network permissions	Grant permissions for the features you enable	Check the system proxy settings. If you use TUN, also check its interface and permissions.

Quit the running app before updating to avoid having old and new processes open at the same time. If your settings don’t appear after replacing the app, first check whether you launched a copy from a different folder instead of importing all your subscriptions again. See the macOS setup guide for platform-specific details.

Android downloads

v2rayNG uses the Xray core and is the recommended Android client. v2flyNG uses the V2Fly core as an alternative. These are separate apps, each with its own configuration.

v2rayNG Recommended

Android · Xray core · 2.2.6

Download v2rayNG · arm64

Recommended for most phones released since 2015. Make sure your device supports arm64 apps.

Download v2rayNG · Universal

Choose the universal package if you’re unsure of your device’s architecture. It supports multiple architectures but still requires a compatible system.

Installing the app and approving VPN access

After downloading the APK, open it with the system installer. If prompted to allow app installs from your browser or file manager, grant permission only to the source you’re using. Once installed, open v2rayNG, add a subscription group, and refresh the node list. You can also import a share link compatible with its core.

Select a node and start the connection. The first time, Android will ask you to authorize the VPN connection. This creates a local interface for routing traffic; it doesn’t mean the node is connected. Check the app logs and test an actual request. If the service stops when the screen is off, check battery optimization and background restrictions before assuming the subscription is invalid.

v2flyNG Alternative

Android · V2Fly core · 1.10.31

Download v2flyNG · arm64

For devices that support arm64 apps. Choose this version if you need V2Fly core behavior and compatible configuration.

Download v2flyNG · Universal

An alternative if you’re unsure of your device’s architecture. Check system requirements and existing apps before installing.

Checklist for switching clients

v2flyNG and v2rayNG have similar names but use different cores by default. A subscription being readable doesn’t mean every protocol, transport setting, or core-specific field will work. When switching, test one clearly compatible node first, then move over custom DNS and routing rules. Don’t overwrite one app’s native configuration file with another app’s.

When switching connection apps, stop the VPN service in the current client before starting the other one. Android typically allows only one standard VPN service at a time; switching between apps that request control can cause the connection state to change repeatedly. To compare the clients, keep the node, network, and request the same, then use the logs to identify any differences.

Android installation requirements

Check	Package requirements	Where to check and what to do
App architecture	arm64 or universal package	Choose an architecture supported by your device’s system, not just the processor’s marketing name.
Android version	Must meet the APK’s installation requirements	Check your Android version in Settings and read the installer prompts.
Install permissions	Allow installs from the current source	Follow the system prompts to grant permission. You can revoke permission for that source after installation.
Connection and background use	VPN permission and reliable background operation	Check for other VPN services, battery restrictions, and client logs.

If you see “App not installed,” check whether an app with the same name is already installed, whether the signing certificate matches, and whether there’s enough free space. If you need to uninstall and reinstall, first export any configuration you’ll need to restore so you don’t lose your subscription groups. See the Android setup guide for next steps.

Linux downloads

v2rayN provides deb and rpm packages. Choose a format for your distribution, then select x64 or arm64 for your processor.

v2rayN

Linux · Graphical desktop client · 7.24.1

Download deb · x64

Commonly used on Debian and Ubuntu-based systems. In a filename, amd64 means x64 architecture; it isn’t limited to a particular processor brand.

Download rpm · x64

Commonly used on Fedora and RHEL-based systems. Installability also depends on your distribution version and package dependencies, not just the file extension.

arm64 packages: Download deb · arm64 Download rpm · arm64

Installing with a graphical package manager and checking dependencies

Open the package with your distribution’s software installer. Review the dependency and architecture information before confirming installation. Renaming a deb file to rpm, or vice versa, won’t convert it; matching package formats also don’t guarantee that every distribution version meets the dependencies. If installation fails, save the full error details and check for missing components or system compatibility issues. Don’t force the installation by ignoring dependencies.

v2rayN is a graphical desktop client, and the packages on this page are intended for systems with a graphical session. After installing, launch it from the app menu, import a subscription, and check the local listening port. Different desktop environments may handle system proxy settings differently; a working browser proxy doesn’t mean every app is routed. Before enabling TUN, check the client’s capabilities, interface permissions, and existing network rules.

Linux installation requirements

Check	Package requirements	Where to check and what to do
Package format	deb or rpm	Check your distribution’s documentation or graphical package manager.
Processor architecture	x64 or arm64	x86_64 and amd64 mean x64; aarch64 means arm64.
Desktop and dependencies	A graphical session and the package’s required components	Review the installer’s dependency prompts and check your distribution version.
Proxy and permissions	Configure for your desktop environment and proxy mode	Check the system proxy, TUN, and per-app proxy settings separately.

If the desktop icon opens but the core doesn’t start, check the client logs for the specific error. Port conflicts, incompatible configuration fields, and insufficient permissions require different fixes; reinstalling the client usually won’t resolve these configuration issues. See the Linux setup guide for details.

After installation

Subscriptions, nodes, and proxyVerify the connection step by step

01 / Import

Load your own configuration

The client package doesn’t include usable nodes. Get a valid subscription or share link, import it, and check that the node list appears. Subscription URLs, share links, and native JSON use different import methods. If the returned content doesn’t match, check the format first instead of repeatedly clicking refresh.

02 / Start

Select a node and traffic mode

Select an active node and start the service, then check the logs for startup errors. On desktop, enable the system proxy; on Android, approve the VPN connection. Check permissions separately if you need TUN. For your first setup, use one clear connection path to avoid stacking multiple proxies.

03 / Verify

Check the results of a real request

Test the connection by browsing and checking your exit IP, then review requests and routing entries in the logs. A “connecting” status only means the service or interface has started; it doesn’t confirm the remote node is reachable. If something fails, check node connectivity, DNS resolution, and app traffic routing separately.

Read the subscription import and first connection guide →

Download FAQs

Package formats and requirementsSix questions to ask before and after downloading

Desktop or classic WPF: which Windows version should you choose?

For a first install, start with Desktop, which uses a next-generation cross-platform UI. If you prefer the familiar Windows interface and workflow, choose the stable classic WPF version. Both require you to import your own nodes or subscription. Back up your settings before switching, close the old app, then check the listening port and proxy settings in the new one.

Should you download the arm64 or universal Android version?

Most phones released since 2015 support arm64, but choose based on the app architectures supported by your device. If you’re unsure, try the universal version. If the installer reports an incompatibility, check your Android version, processor architecture, and any existing app signature instead of downloading the same package repeatedly.

How do you choose between Apple Silicon and Intel packages on macOS?

Open About This Mac from the Apple menu and check the chip or processor field. If it shows an Apple M-series chip, choose the Apple Silicon arm64 package; if it shows an Intel processor, choose the Intel x64 package. Choose based on your Mac’s hardware, not your subscription format or node.

Can you connect right after installing the client?

The client reads configuration and routes traffic; the installer does not include a usable subscription or node. After installation, import a valid configuration, select an active node, and start the service. Then enable the system proxy or approve the VPN connection, depending on your platform. Finally, verify the connection with a browser request, your exit IP, and the client logs.

What settings should you keep before updating?

Back up subscription groups, custom routing rules, DNS settings, and local listening settings. Note which core and proxy mode you currently use. Exit the running client before updating; afterward, check that your existing configuration was loaded correctly before testing the connection. Subscription URLs and configuration files may contain credentials, so store backups securely.

Can you install a Linux deb package using rpm, or vice versa?

Choose the package format used by your distribution; changing the file extension is not enough. Debian and Ubuntu-based systems generally use deb, while Fedora and RHEL-based systems generally use rpm. Match the package to your x64 or arm64 architecture as well. A compatible format does not guarantee that dependencies are met. If the installer reports missing dependencies, check your distribution version and the full error details.

For a feature-by-feature comparison, see the three-client comparison. For platform-specific instructions, see the complete installation and setup guide.