Package selection / subscription import

V2Ray Client Downloads
Choose a package for your operating system

Choose v2rayN for desktop and v2rayNG for Android. Check your processor architecture before downloading the right package. After installation, open subscription groups and import your existing subscription.

Choose a platform and package ↓

Choose a platform and client

Choose an operating system, then check the architecture and package format on its card. Version details change as downloads are updated; compatibility also depends on your device and environment.

v2rayN / Windows

Recommended7.24.1

Choose an interface edition on the same client card. Desktop uses a modern cross-platform UI. The classic WPF edition retains the traditional Windows interface and is a stable classic option. Stick with WPF if you’re used to it, or start with Desktop for a first install.

Desktop edition

x64 · ZIP Download Desktop edition

A modern cross-platform UI. Download the ZIP, extract it, then run the installer inside. Don’t launch it from the archive preview.

Classic WPF edition

x64 · ZIP Download classic WPF edition

The stable classic Windows edition. Save your subscription URL and custom routes before switching interface editions, so interface differences aren’t mistaken for a lost subscription.

Windows requirements and installation

Check	Requirements and actions
System and architecture	For Windows x64. Check Settings → System → About for your system type. For older Windows versions, confirm compatibility with the current release separately.
Installation environment	Make sure you have enough space to extract and install the package. If the installer reports a missing runtime component, install the component it specifies.
Permissions	Use the system proxy as needed. TUN uses a virtual network adapter and routing, and usually requires administrator privileges.

Exit any running instance before extracting and installing the package. On first launch, check the logs for core startup errors before adding a subscription group. If a port is already in use, look for another proxy process; don’t run two clients that compete for the same listening port.

The system proxy only affects apps that follow the system proxy settings. Opening the client’s main window doesn’t mean browser traffic is being proxied. After importing a subscription and selecting a node, review system proxy settings, then test access to a real site.

v2rayN / macOS

7.24.1

Open About This Mac from the Apple menu and check the Chip or Processor field. Choose Apple Silicon for an M-series chip, or Intel if it lists an Intel processor. Don’t guess based on the Mac’s appearance, purchase year, or package size.

Apple Silicon

arm64 · DMG Download Apple Silicon package

For M-series chips. Use the native architecture package to reduce startup issues caused by a mismatch with your hardware.

Intel

x64 · DMG Download Intel package

For Intel processors. If macOS says the app can’t run, check the architecture and system compatibility first, then review the installation.

macOS requirements and first launch

Check	Requirements and actions
Processor	Apple Silicon uses arm64; Intel uses x64. Check About This Mac to confirm.
System compatibility	The current DMG is still subject to macOS version and runtime requirements. Check the package requirements before installing on an older system.
Network permissions	Follow system prompts when changing the system proxy or enabling TUN. If administrator credentials are requested, make sure you understand the action first.

Open the DMG, copy the app to Applications, then launch it. Avoid running it from the mounted disk image long-term; updates, permissions, and configuration paths can be harder to manage. If macOS blocks the first launch, verify the file’s source and package type, then use the security settings provided by macOS. Don’t disable system-wide security to install the client.

After the subscription updates successfully, choose a node and test it. If you switch between Wi-Fi, Ethernet, or other network services, check the proxy status for the active service again. Before quitting the client, undo any system proxy changes you made so apps aren’t left pointing to a stopped local port.

v2rayNG

RecommendedXray core2.2.6

For Android, v2rayNG is the recommended choice. It uses the Xray core and supports configurations that need its protocols and transports. Most phones released after 2015 use arm64, but some devices have app architecture limits; check what your system supports.

arm64 package

arm64-v8a · APK Download v2rayNG arm64

For common Android devices that support 64-bit apps. Leave enough storage for the download, then approve the VPN connection request when you first connect.

Universal package

universal · APK Download v2rayNG universal

For devices with an unknown architecture or another supported architecture. A universal package won’t work around compatibility limits in an outdated Android version.

v2flyNG

AlternativeV2Fly core1.10.31

Choose v2flyNG if your configuration specifically requires the V2Fly core. Its core support differs from v2rayNG’s, so a node name alone doesn’t tell you whether a configuration is compatible. Check the requirements before switching clients for a specific protocol or transport combination.

arm64 package

arm64-v8a · APK Download v2flyNG arm64

For devices that support arm64 apps. Import your subscription separately after installation; settings from another client won’t necessarily transfer automatically.

Universal package

universal · APK Download v2flyNG universal

For other supported architectures or devices whose architecture you haven’t confirmed. Before switching clients, save your subscription URL and note any per-app proxy settings.

Android requirements and installation permissions

Check	Requirements and actions
App architecture	Choose arm64 if your device supports arm64 apps. If you’re unsure, try the universal package and check system compatibility.
Installation permissions	Follow the system prompts to allow the current browser or file manager to install apps. You can turn off permission for that source after installation.
Connection setup	Approve the system VPN request the first time you connect. Other active VPN apps may conflict with the connection.
Background operation	Adjust battery optimization and background restrictions as needed. If the connection drops when the screen locks, check the system’s process management settings first.

If you see “App not installed,” don’t delete the existing client right away. Check storage, package architecture, the installed app version, and signature compatibility. If you need to uninstall and reinstall, export your configuration or save your subscription URL first. Uninstalling may erase the app’s data.

You can keep separate configurations in both clients, but only one client should establish a VPN connection at a time. After importing a subscription, select a node and start the connection, then check the status in the notification shade and test an actual request. See Android installation and setup for platform-specific steps.

v2rayN / Linux

7.24.1

First identify the package format used by your distribution, then choose the processor architecture. Common Intel and AMD desktop systems typically use x64; check whether an ARM desktop or development device uses arm64. Choose deb or rpm based on your distribution’s package management system, not personal preference.

deb package

x64 / amd64 · deb Download Linux x64 deb

For distributions that use the deb format. Open it with your system’s software installer so the package manager can check runtime dependencies.

ARM device: download arm64 deb →

rpm package

x64 / x86_64 · rpm Download Linux x64 rpm

For distributions that use the rpm format and have compatible dependencies. Matching package formats don’t guarantee compatibility with every system version.

ARM device: download arm64 rpm →

Linux requirements and dependency checks

Check	Requirements and actions
Package management	Debian- and Ubuntu-based systems generally use deb; Fedora- and RHEL-based systems generally use rpm. Check the specific dependencies too.
Processor architecture	amd64 and x86_64 usually mean x64; aarch64 usually maps to arm64. Don’t install packages for a different architecture.
Desktop environment	The graphical client requires an available desktop session and the relevant GUI runtime dependencies. This guide is not for installing it as a headless command-line server.
Network permissions	TUN requires permissions for a virtual network adapter and routing. Whether apps can read the system proxy also depends on the desktop environment and the apps themselves.

If the installer reports unmet dependencies, save the full message and check your distribution version and package architecture. Don’t force the installation past dependency errors or add another distribution’s repositories to your system. After installation, launch the client in a normal desktop session, check that its configuration directory is writable, then enable network features one at a time.

If the client is connected but an app still connects directly, first check whether the app reads the desktop system proxy. To route traffic from more apps, consider TUN mode and check for existing VPNs, container networking, and custom routes. Avoid having multiple network management tools change routes at the same time.

Import your subscription and test the connection

Set up the client in this order: configure, test, then route traffic. Troubleshoot installation and connection issues separately, and avoid changing several variables at once.

Save a subscription group

Open subscription group settings and enter an easy-to-recognize alias and the full subscription URL. The URL may contain a private token, so avoid copying extra spaces, line breaks, or punctuation added by a chat app. The https://example.com/sub?token=xxxx URL in this guide is for format illustration only; it won’t provide nodes.

View subscription import steps →

Update the subscription and test a node

After saving the group, update the subscription and confirm that the server list contains configurations. If the update fails, check whether the URL has expired, then choose whether to update through the proxy based on your network. Select a node and run a real connection latency test. TCPing only helps check whether a port is reachable; it can’t replace a real request test.

About real connection latency tests →

Choose system proxy or TUN

For a first desktop setup, start with the system proxy and identify which apps use it. If you need to route more traffic, learn about TUN permissions and routing changes first. On Android, approve the VPN connection request when prompted; then verify it with an actual site request and your exit IP.

View proxy mode settings →

Keep a recoverable configuration

Before updating the client, save your subscription URL, custom routes, and port settings. Manage nodes that can be re-fetched from a subscription separately from configurations you added manually. When something goes wrong, note the key error in the logs and determine whether it’s an installation, core startup, subscription update, or node connection issue. Reinstalling repeatedly isn’t a substitute for troubleshooting.

Check which clients are right for you →

Package selection FAQs

Check your operating system, architecture, and installation method first. For subscription updates and connection issues, see the FAQ.

Windows Desktop or classic WPF: which should you choose?

For a first install, start with the Desktop edition, which uses a modern cross-platform UI. The classic WPF edition is a stable Windows version for users who prefer the traditional interface. Both downloads are x64. Save your subscription URL and custom settings before switching, and don’t let both instances manage the system proxy at the same time.

Android: arm64 or universal?

Most phones released after 2015 will use arm64, but check which app architectures your device actually supports. Try the universal package for older devices, systems limited to 32-bit apps, or when you’re unsure of the architecture. If installation fails, check the Android version, available storage, and the signature of any existing app. Don’t keep installing over the old version.

What’s the difference between Apple Silicon and Intel packages for macOS?

The Apple Silicon package is for M-series chips; the Intel package is for Intel processors. Open About This Mac from the Apple menu and check the Chip or Processor field, then choose the matching DMG. The same package format doesn’t mean the same processor architecture, so use the native package for your Mac.

Linux: should you download deb or rpm?

Debian, Ubuntu, and related distributions generally use deb packages; Fedora, RHEL, and related distributions generally use rpm. Check whether you need x64 or arm64, and let your system’s package installer check dependencies. Distributions using the same format may still require different dependency versions, so don’t force an installation past dependency errors.

Why are there no nodes to connect to after installing the client?

The client manages configurations; its installer doesn’t include a subscription URL or nodes. Get a subscription URL you’re authorized to use, save it in a subscription group, and update the subscription. Then select a node and run a real connection latency test. Once it passes, configure the system proxy or enable TUN if needed, then check your exit IP.

What should you save before updating the client?

Save your subscription URL, subscription group aliases, custom routing rules, and port settings. Use the client’s export feature to back up configurations where available, then exit the old instance before installing the new package. After launch, check your subscriptions and routes, then run a real connection latency test again. Don’t share backup files or screenshots containing tokens.

V2Ray Client DownloadsChoose a package for your operating system

Choose a platform and client

v2rayN / Windows

Desktop edition

Classic WPF edition

Windows requirements and installation

v2rayN / macOS

Apple Silicon

Intel

macOS requirements and first launch

v2rayNG

arm64 package

Universal package

v2flyNG

arm64 package

Universal package

Android requirements and installation permissions

v2rayN / Linux

deb package

rpm package

Linux requirements and dependency checks

Import your subscription and test the connection

Save a subscription group

Update the subscription and test a node

Choose system proxy or TUN

Keep a recoverable configuration

Package selection FAQs

V2Ray Client Downloads
Choose a package for your operating system