Choose a client and package

V2Ray client downloads

Choose your operating system, then your architecture. Use v2rayN on desktop, v2rayNG on Android, or v2flyNG as an alternative core option.

Free to use Open source Compare the three clients →

Windows：v2rayN

Both installers below are for x64 systems. For a first install, consider the desktop version; choose WPF if you prefer the classic workflow.

v2rayN

Windows · x64 · 7.24.1

Recommended

Download Desktop · x64

A newer cross-platform UI, suited to first-time users and those who want a consistent experience across desktop systems.

Download Classic WPF · x64

A stable classic edition with a WPF interface, suited to users familiar with the traditional server list and settings layout.

The download is a ZIP archive. Extract all files before running the installer, following the package’s folder structure. Don’t launch it from the archive preview.

Read the v2rayN installation and setup guide →

System requirements and installation

Windows installation requirements
Check	What to look for	Instructions
System architecture	x64 Windows	Check System type under Settings → System → About. Don’t rely on the computer’s brand or model alone.
Windows compatibility	A Windows version supported by the current release	Check the installer and release notes for supported Windows versions and runtime requirements. Verify compatibility before installing on an older system.
Installation environment	Writable folder and enough free storage	Extract all files and install any required runtime components as prompted. Don’t overwrite files from the two interface versions in the same folder.
Permissions	Standard use and TUN require different permissions	You don’t need administrator privileges for standard configuration. Grant the requested permissions only if you enable the virtual network adapter feature.

The desktop and WPF versions differ primarily in their interface frameworks; that doesn’t mean one is inherently faster for a particular protocol. Protocol support also depends on the selected core and its version. Before migrating existing settings, export or back up servers, subscription groups, and routing rules, then import them into the new interface. Copying program files alone is not a complete data migration.

After installation, make sure the client opens normally before importing your configuration. To proxy browser traffic, check the system proxy status. To handle apps that ignore system proxy settings, consider TUN mode. These options cover different traffic, and a successful install doesn’t mean all app traffic has been redirected.

macOS：v2rayN

Check About This Mac to identify your chip. Apple Silicon and Intel Macs require different builds, so choose the one that matches your hardware.

v2rayN

macOS · DMG · 7.24.1

Download Apple Silicon · ARM64

For Apple M-series chips. Check the Chip entry in About This Mac to confirm your model.

Download Intel · x64

For Intel-based Macs. Choose this package if your device information lists an Intel processor.

Open the DMG and follow the prompts to install the app in Applications. Review first-launch permission and network access prompts individually.

See desktop setup steps →

System requirements and chip identification

macOS installation requirements
Check	What to look for	Instructions
Apple Silicon	ARM64 DMG	Choose the native-architecture package if your device has an Apple M-series chip.
Intel processor	x64 DMG	Choose the matching package if your device information lists Intel. Don’t infer the architecture from the computer’s appearance.
System version	Meets the current release requirements	If macOS says your system is too old, check the compatibility requirements. Re-downloading the same package won’t change the system’s limitations.
Feature permissions	Grant permissions for the features you use	TUN may require additional authorization. Installing the app and enabling the virtual network adapter are separate steps.

Not all Mac computers can run the same binary. The native-architecture build is usually the simplest choice; don’t default to another architecture just to match an older installation routine. After installing, launch the app from Applications and confirm it runs before importing subscriptions or configuring routes. This helps separate installation issues from connection problems.

If the system blocks the app, read the warning and identify whether it concerns the source, compatibility, or permissions. Then use the system’s app-specific controls to address it. Don’t disable device-wide security. When switching to a Mac with a different chip architecture, migrate configuration using a supported export method, but download the build that matches the new hardware.

Android: v2rayNG and v2flyNG

Start with v2rayNG. Choose v2flyNG if you need the V2Fly core. Check that your protocols and subscriptions are compatible with the app you choose.

v2rayNG

Android · Xray core · 2.2.6

Recommended

Download v2rayNG · arm64

A good first choice for most mainstream phones released after 2015, but confirm that your system supports 64-bit ARM apps.

Download v2rayNG · Universal

Supports more processor architectures, making it a useful choice when the device architecture is unclear or you need broader compatibility.

Routes traffic through Android’s VPN interface. You’ll need to approve the system prompt the first time you connect.

v2flyNG

Android · V2Fly core · 1.10.31

Alternative

Download v2flyNG · arm64

For devices that support 64-bit ARM apps and configurations that require V2Fly core compatibility.

Download v2flyNG · Universal

Consider this if you’re unsure of the processor architecture. Installation also depends on factors such as the Android version.

Don’t assume Xray-specific features are supported by V2Fly. Check that the core supports the features your configuration requires before importing it.

System requirements and installation permissions

Android installation requirements
Check	What to look for	Instructions
Processor and system	arm64 or universal	A 64-bit phone processor doesn’t guarantee that the system supports 64-bit apps. Check your device’s system capabilities.
Installation permissions	Grant permission to the source app	Grant permission only to the browser or file manager you’ll use to open the APK. You can revoke it afterward.
Windows compatibility	Meets the app’s current requirements	If Android can’t parse the package, check the system version, architecture, available storage, and whether the download completed.
Traffic routing	Android VPN permission	Usually, only one app using the VPN interface can be active at a time. Check whether another network tool is already using it.

An APK is an app installer; you still need to import a subscription or server settings after installation. The first time you connect, Android asks you to authorize a VPN connection. This allows the app to route traffic on your device; it doesn’t mean you’re connected to a working server. Check the selected configuration, then review the notification shade and client logs. Authorization alone doesn’t verify a connection.

The arm64 package is usually smaller than a universal build that includes multiple architectures, but package size doesn’t indicate feature completeness. If installation reports a conflict with an existing app, first check that it’s the same app and that the signing source matches. Back up your configuration before taking action. Don’t uninstall without understanding why; doing so may remove locally stored subscriptions, servers, and routing settings.

Background restrictions can interrupt mobile connections. Check battery optimization and background permissions only if you actually experience disconnects when the screen is off or the app is closed. There’s no need to grant every permission during installation. You can use v2rayNG and v2flyNG separately to check compatibility, but don’t enable traffic routing in both at once, or it may be unclear which configuration is active.

Linux：v2rayN

Choose deb or rpm based on your distribution’s package system, then check whether your processor is x64 or ARM64. Distribution and processor architecture are separate considerations.

v2rayN

Linux · Desktop GUI · 7.24.1

Download deb · x64

For compatible distributions that use deb packages, including Debian and Ubuntu-based systems.

Download rpm · x64

For rpm-based distributions that meet the package’s dependencies. Check compatibility before installing.

ARM64 devices: deb · ARM64 rpm · ARM64

Open the package with your system’s software installer. The same file extension doesn’t guarantee that every distribution meets the package’s dependencies and runtime requirements.

Read the desktop client setup guide →

System requirements and package formats

Linux installation requirements
Check	What to look for	Instructions
Desktop environment	A system that can run desktop applications	This page provides a GUI client for desktop use. It isn’t a server service package.
Package management	deb or rpm	Use your distribution’s native package format. Let the system installer check dependencies instead of mixing packages manually.
Processor architecture	x64 or ARM64	x64 may also be labeled amd64 or x86_64; ARM64 may also be labeled arm64 or aarch64.
Runtime dependencies	Meets the package’s declared requirements	If dependencies can’t be met, check your distribution version and package compatibility. Don’t force the installation by ignoring dependencies.

deb and rpm describe package formats; they don’t determine which proxy protocols are supported. Even distributions that both use rpm may have different base libraries and dependency versions, making a package incompatible with one of them. If the installer reports a dependency error, note the exact message and check your system version and architecture. Don’t try to work around it by renaming the file or changing its extension.

After installation, launch v2rayN from your desktop app menu and import your configuration as a standard user first. System proxy coverage depends on the desktop environment and whether each app supports proxy settings. TUN requires additional network permissions and routing configuration. Test the standard proxy first, then enable TUN if needed. Changing DNS, routes, and permissions all at once makes problems harder to track down.

Configuration steps after installation

Verify the installation, configuration import, and traffic routing separately. Confirm each step works before moving on.

Prepare your configuration

Import a subscription or server settings

The client doesn’t provide a connection endpoint. Get a subscription you’re authorized to use, add its URL to a subscription group, and update it. If you have a single share link, use the client’s clipboard import feature. Subscription URLs may contain account identifiers; treat them as sensitive and don’t post them in public forums or screenshots.

After importing, check that the protocol, transport, and security settings were recognized correctly. VLESS, VMess, and Trojan are distinct configuration types; changing a name won’t convert one into another. If you see an unfamiliar field, check the provider’s instructions and the selected core’s capabilities instead of guessing based on a similar name.

Explore protocol and core technical references →

Test traffic routing

Select a server and traffic-routing mode

Select the active server from the list, then enable the system proxy or connect on your mobile device. The system proxy mainly serves apps that follow system proxy settings; TUN uses a virtual network interface to cover more traffic. They aren’t speed settings. Start with the narrowest routing option that meets your needs, then adjust based on app behavior.

To verify a connection, check that the target service works and review the client logs and routing matches. A latency test doesn’t prove full access, and one failed test doesn’t automatically mean the installer is at fault. Check the configuration, server, DNS, routes, and app proxy settings in order. This is more effective than repeatedly reinstalling.

Follow the steps to make your first connection →

Upgrades and configuration migration

Updating the app doesn’t migrate your data. Check how configuration is stored before changing interfaces, devices, or cores.

Back up settings you can restore before upgrading

Use the client’s export or backup feature to save subscription groups, manually added servers, and custom routes. A subscription can be downloaded again, but that won’t restore manually edited fields. Also note the current core, DNS policy, system proxy mode, and TUN settings so you can check them after upgrading.

Quit the client before running the updater so it doesn’t hold files open. User data may be stored in different locations depending on how the app was installed. Don’t assume uninstalling preserves settings or that copying the program folder creates a complete backup. When migrating to a new device, transfer configuration files only through a trusted method and protect any sensitive data they contain.

Check which settings are active after upgrading

The first time you open the updated client, confirm that your subscription groups and server list are still there. Then check the active server, default route, and system proxy status. A core upgrade may change fields or behavior. Successful import doesn’t guarantee every feature still works as before, so verify using logs and real-world access.

If only one type of app has a problem, check whether it follows system proxy settings before switching installers. If two clients behave differently with the same subscription, check core support and subscription parsing. Once you’ve confirmed the configuration is restored and the connection works, remove old installation files and temporary exports containing sensitive data.

Download and installation FAQs

Answers to common questions about package selection, system permissions, upgrades, and backups.

Does downloading a client give you a working connection?

The client manages configuration and routes traffic; the installer does not include a usable server. You’ll need your own authorized server configuration or subscription. Import it, select a server, then configure the system proxy or TUN mode. Treat subscription URLs as sensitive and don’t share them publicly.

Which should you choose: the Windows desktop or classic WPF version?

For a first install, consider the desktop version, which uses a newer cross-platform interface. Choose WPF if you prefer the classic layout and want to keep familiar workflows. Menus and configuration storage may differ, so export your settings before migrating. Don’t mix program files from the two versions in one folder.

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

The arm64 build is for devices that support 64-bit ARM apps; most mainstream phones released after 2015 are good candidates. The universal build supports more processor architectures but is usually larger. Device age alone doesn’t determine compatibility. If arm64 won’t install, first check whether your system supports 64-bit apps, then try the universal build.

What should you do if installation fails or your system warns you about a risk?

Check the operating system, processor architecture, available storage, and compatibility first, then read the specific warning. On Android, grant install permission only to the app you’ll use to open the package. On desktop systems, follow app-specific prompts. Don’t disable device-wide security just to install, or repeatedly force installation without understanding the cause.

How can you keep subscription and routing settings when upgrading?

Export or back up your configuration in the client. Note the current core, routing rules, and DNS settings, then quit the client before upgrading. Don’t assume the program folder contains all user data. After upgrading, check subscription groups, the active server, system proxy, and TUN status. Remove old files only after confirming the connection works.

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

The version shown on the page and the download URL come from different fields in the version manifest, so they may briefly differ while it’s being updated. The filename identifies the package type; it doesn’t confirm the installed version. After installation, check the client’s About page. If details differ, verify the app name, platform, and architecture first.