Project V ecosystem clients

V2Ray client downloads

Choose an installer by OS, architecture, and core.

Choose v2rayN for desktop; for Android, start with v2rayNG, or consider v2flyNG for V2Fly configurations. Clients provide the interface and configuration management; connection support also depends on the core, server settings, and version in use.

First install and import guide → Core and protocol compatibility →

InstallersChoose by platform

Check your device’s operating system first, then confirm its processor architecture. The links below are for the selected platform; version details appear on each client card.

v2rayN

Recommended

Windows x64 downloads. Desktop uses a modern cross-platform UI; the classic WPF edition keeps the traditional Windows interface for users who prefer familiar workflows.

Download Desktop · x64 Download classic WPF · x64

7.24.1Xray / V2Fly compatibility depends on the version

Both editions serve the same desktop use cases; they aren’t separate proxy protocols. If you’re installing for the first time, start with Desktop. Choose WPF if you want to keep the classic interface and workflow. Existing configurations depend on the selected core and supported fields, not just the interface edition.

These downloads are ZIP files. Extract the archive to a separate folder, then run the installer inside; don’t launch it from the archive preview. Use a clearly named folder so you can distinguish application files from backups and update packages later.

If you already have the client, quit the old process from the system tray before updating. Afterward, check your subscription groups, routing mode, and system proxy status. If you keep both editions installed for comparison, don’t let both instances change the system proxy or use the same local listening port.

System and installation requirements

Requirement	What to check
Operating system	A modern Windows desktop OS; check the current installer for its minimum supported version
Processor	x64; an x64 package is not a native ARM64 package
Installation format	ZIP archive; extract it and run the installer
Runtime requirements	Install any required runtime indicated by the installer
Proxy permissions	System proxy and TUN have different permission requirements

In Windows, go to Settings → System → About and check System type. A 64-bit-capable processor doesn’t necessarily mean the installed OS is 64-bit; use the system’s reported information.

The system proxy mainly affects apps that honor the OS proxy settings. Enable TUN only if needed and follow the client’s instructions for the required permissions. You don’t need to change every network interception setting just to import a configuration.

Continue to desktop setup →

v2rayN

Desktop client

Choose a DMG installer based on your Mac’s processor. Use the ARM64 download for Apple Silicon and the x64 download for Intel.

Download Apple Silicon · ARM64 Download Intel · x64

7.24.1DMG installer

Open About This Mac and check whether it lists a Chip or Processor. Choose the Apple Silicon package for an M-series chip, or the x64 package for an Intel Mac. Don’t rely on the purchase year: different models from the same year may use different processors.

Open the DMG and follow the disk image window’s instructions to move the app to Applications, then launch it from there. Don’t keep running it from the mounted disk image; you could lose access to the app when you eject it or confuse its install location during an update.

If macOS shows a security alert on first launch, check the download link, file source, and alert details before following the system’s approval process. Don’t disable system security entirely just to launch the client. If the alert indicates an architecture or OS version mismatch, choose a compatible installer instead.

After importing a configuration, test with the regular system proxy in apps that support it before considering TUN. A successful launch only means the app can run on your system; it doesn’t guarantee that the current core supports every transport and security-layer combination in your subscription.

System and processor requirements

Requirement	What to check
Operating system	macOS; check the current application package for its minimum supported version
Apple Silicon	M-series chip; choose the ARM64 package
Intel	Intel processor; choose the x64 package
Installation format	DMG disk image; follow the prompts to move the app to Applications
Network permissions	Grant the permissions required by macOS and your chosen proxy mode

Prefer an installer that matches your device’s native architecture rather than relying on compatibility translation. If the app won’t launch, note your macOS version, chip type, and full error message to determine whether the issue is with the runtime environment or configuration.

Turn off proxy control in your current network tool before switching to another. When multiple tools change system proxy settings, their interface toggles may not reflect the settings actually in use.

Troubleshoot installation and connection issues →

v2rayNG

Recommended

An Android graphical client primarily designed for the Xray core. Before choosing it, confirm that it supports the protocols, transport, and security layer required by your server configuration.

Download v2rayNG · arm64 Download v2rayNG · Universal

2.2.6Xray core

Most mainstream phones released after 2015 are best served by the arm64 package, but some devices may run an OS that doesn’t support 64-bit apps. If you’re unsure of the architecture, try Universal. If installation still fails, check the OS version and error message instead of repeatedly downloading the same file.

APK install permission applies to the app that starts the installation, such as your browser or file manager. Grant permission only to the app you’re using, then review it again in system settings after installation. The first time you connect, the system will separately ask whether to allow a VPN connection.

After importing a share link or subscription, select a configuration and connect. For initial testing, keep the default routing, confirm the connection and DNS resolution, then add app-specific routing, rules, or custom DNS one at a time to help pinpoint issues.

v2flyNG

Alternative · V2Fly core

An alternative Android client built for the V2Fly core. Consider it if you already use V2Fly configurations and workflows and have confirmed that the required features are supported.

Download v2flyNG · arm64 Download v2flyNG · Universal

1.10.31V2Fly core

The two Android clients may have similar interfaces and import workflows, but their core capabilities aren’t necessarily the same. If a configuration depends on a feature specific to one branch, a successful link import doesn’t prove it will connect. Check that all fields are preserved and supported.

When migrating, keep the original client and back up its configuration. Import a known configuration into the new client and test it before switching over. Don’t let both clients control the VPN at once; Android typically allows only one VPN connection, and the later one may replace the earlier connection.

If only subscription updates are failing, first check the subscription URL, access conditions, and error message. You don’t need to switch core families right away. Choosing a client addresses compatibility and management needs; it can’t replace correct server settings.

Android system and installation requirements

Requirement	What to check	Check before installing
OS version	Check the current APK’s minimum OS requirement	Find your Android version in Settings
arm64	Device and OS must support ARM64 apps	Usually the best choice for mainstream phones released after 2015
Universal	For an unknown architecture or another supported architecture	Does not bypass the minimum OS requirement
Install permission	Allow the current browser or file manager to install apps	Review the specific permissions requested by the system
Connection permission	Allow the system VPN request when connecting for the first time	Don’t run alongside another VPN connection

If an update reports a signature mismatch, don’t uninstall the existing app right away. Back up your configuration and confirm where the existing app came from and which update path to use. If background connections drop frequently, review battery optimization and background activity settings; don’t assume every disconnection is caused by the protocol.

v2rayN

Linux desktop client

Choose deb or rpm for your distribution, then check whether your system is x64 or ARM64. The primary downloads below are for x64 desktops.

Download deb · x64 Download rpm · x64

For ARM64 devices: deb · ARM64 rpm · ARM64

7.24.1Desktop graphical environment

Debian- and Ubuntu-based distributions typically use deb packages; Fedora- and RHEL-based distributions typically use rpm. Package format is only the first compatibility check. Packages may also depend on specific system libraries and distribution versions, so rpm support alone doesn’t guarantee compatibility.

Check your processor architecture in the system’s About or hardware information. amd64 and x86_64 in package names indicate the common x64 architecture; arm64 and aarch64 indicate ARM64. Architecture and distribution are separate requirements, and both must match.

After downloading, open the package with your distribution’s graphical software installer. Review dependency and compatibility notices before installing. If the installer reports missing dependencies, check your distribution version rather than forcing the installation.

This download is for a desktop graphical client, not a terminal-only server. Whether the system proxy affects an app depends on the desktop environment and whether the app reads those settings. For broader traffic routing, assess TUN permissions, routes, and DNS behavior separately.

Distribution and runtime requirements

Requirement	What to check
Runtime environment	A Linux desktop system with a working graphical environment
deb package	Debian- and Ubuntu-based distributions; package dependencies must also be met
rpm package	Fedora- and RHEL-based distributions; check the supported distribution versions
Processor	x64 or ARM64, matching the selected package
Installation permissions	The system software installer requests administrative permissions when needed

Read package manager notices separately from client logs: the former cover installation and dependencies; the latter cover runtime and connections. Verify installation and startup first, then troubleshoot subscriptions, routing, and security-layer settings to keep issues separate.

Review protocol and core compatibility →

Configure after installationStart with a basic working connection

The installer, connection configuration, and proxy mode are three separate steps. Complete them in order to make troubleshooting easier.

Import a subscription or share link

A share link saves one connection configuration; a subscription URL retrieves and updates a set of configurations. Add the URL through the subscription manager—don’t enter it as a server address. After importing, check that the protocol, port, transport, and security-layer settings are all present.

Subscription URLs may contain access credentials, so hide the full address before sharing a screenshot or asking for help. Installing a client doesn’t provide a usable server; you’ll need a configuration you’re authorized to use.

View import instructions →

Choose a proxy mode

On desktop, start with the system proxy and test apps that honor proxy settings. On Android, approve the VPN request when prompted. The system proxy and TUN are different modes, and not all apps use the system proxy automatically.

Keep routing simple during initial testing and avoid running multiple proxy tools at once. Add app-specific routing or a virtual network interface only when needed, checking routes, DNS, and permissions as you go. Don’t change several settings at once before testing.

Learn about proxy modes and routing →

Restore settings after testing

Test a known configuration first, then restore custom rules, DNS, and other preferences. Importing a link only confirms that the client recognized some of its contents; it doesn’t prove the core supports every field. Check the connection and logs to verify the result.

Back up your configuration and subscription details before updating. If an error occurs, record the full message, the steps that led to it, and the proxy mode in use. Troubleshoot installation, subscription, and connection failures separately; this is usually more effective than repeatedly switching installers.

Find solutions by symptom →

Download and update FAQ

Common questions about choosing installers, migrating configurations, and version information.

After downloading a client, do I also need a subscription or connection configuration?

Yes. The installer provides a graphical interface and configuration management, but no ready-to-use server configuration. Get a subscription URL or share link you’re authorized to use, import it, select a configuration, then set up the system proxy or the app’s VPN mode.

For Windows, should I choose Desktop or the classic WPF edition?

If you’re new to the client, start with Desktop, which uses a modern cross-platform interface. If you prefer the traditional Windows interface, choose the classic, stable WPF edition. The difference is not processor architecture. Back up your subscriptions, routing rules, and custom settings before switching, and don’t let both editions control the system proxy at once.

For Android, should I choose arm64 or Universal?

Most mainstream phones released after 2015 are best served by the arm64 package, but confirm that the device’s OS supports 64-bit apps. If you’re unsure of the processor or OS architecture, try Universal. It won’t fix installation issues caused by an outdated OS, insufficient storage, or a signature conflict.

Can I use the same configuration in v2rayNG and v2flyNG?

Don’t assume compatibility based on the client name alone. v2rayNG primarily targets the Xray core, while v2flyNG is designed for the V2Fly core. Check support for the share-link format, transport, and security-layer fields in each client. Configurations that rely on Xray-specific features may not work with V2Fly.

The version shown on the page differs from the installer filename. Which should I trust?

The version shown on the page comes from the download manifest’s version field; the file itself comes from a download entry in that same manifest. They may be updated at different times. A filename doesn’t confirm the installed version; after installation, check the client’s About or version information.

How do I keep my subscriptions and routing settings when updating?

Use the client’s export or backup feature to save your configuration, and separately note custom routing, DNS, and proxy settings. Quit the client before updating, then check that your configuration is intact afterward. Backups may contain subscription URLs and connection credentials; store them securely and don’t upload them publicly.