Choose an installer · Check your system and architecture first

V2Ray Client Downloads

v2rayN desktop and Android client downloads

Choose your operating system first, then select an interface edition or CPU architecture. Use v2rayN on desktop. For Android, start with v2rayNG; consider v2flyNG if you need compatibility with an existing V2Fly configuration.

See how to import a subscription after installation →

Choose a package by platform

Each download button links to a specific file. Switching platforms updates the page URL’s anchor, making it easy to save or share the selected platform.

v2rayN

Windows · x64 · 7.24.1

Top pick Free & open source

Desktop edition

Download Desktop · x64

A new-generation cross-platform UI. A good starting point for first-time installs, with a layout closer to the other desktop editions.

v2rayN-Desktop-Setup-x64-7.24.1.zip

Classic WPF edition

Download classic WPF · x64

The classic, stable edition with the familiar Windows interface. Choose it if you prefer the established layout.

v2rayN-Setup-x64-7.24.1.zip

Windows system and installation requirements

Check	What to look for
CPU and system architecture	Both downloads on this page are x64. Check “System type” in Windows Settings; don’t rely on the processor brand alone.
Operating system and runtime	Use a supported, maintained version of Windows 10 or Windows 11. Check the installer’s notes for the specific minimum version and runtime requirements.
Files and permissions	Extract the ZIP fully before running the installer. Standard use and TUN mode have different permission requirements.

After downloading, extract the archive to a writable folder, then run the installer from there. Running it directly from the archive preview may prevent it from reading required files. If the installer reports a missing runtime, check which component it requires. Don’t confuse a missing dependency with a subscription connection failure.

Desktop and WPF are different interface editions, not separate subscription services. If you already have settings, export or back up your servers, subscription groups, and custom routing rules before switching. Don’t run both editions while they manage the system proxy; port conflicts and overwritten proxy settings make troubleshooting harder.

After launching the client for the first time, import a valid configuration, select a server, and test a standard proxy connection. There’s no need to enable TUN right away. Once the basic connection works, configure routing and DNS as needed. This helps separate installation issues from configuration problems and system-wide traffic interception.

See how to import a subscription in v2rayN →

v2rayN

macOS · 7.24.1

Free & open sourceDesktop client

Apple Silicon · arm64

Download for Apple Silicon

Choose this package if About This Mac shows an Apple chip.

v2rayN-arm64.dmg

Intel · x64

Download for Intel

Choose this package if About This Mac shows an Intel processor.

v2rayN-64.dmg

macOS system and installation requirements

Check	What to look for
Chip type	Apple Silicon uses arm64; Intel uses x64. Check About This Mac for your chip or processor details.
macOS version	Make sure your macOS version meets the selected release’s requirements. Check compatibility before installing on an older system.
Install location and permissions	Open the DMG and follow its instructions to install the app in Applications. The first time you launch it, follow macOS prompts to confirm the app source and grant any required permissions.

Don’t guess the chip type from the year you bought the Mac. Models from the same year can use different architectures; check the chip information in About This Mac. Apple Silicon users should choose the native arm64 package, while Intel users should choose x64. The wrong architecture may prevent the app from opening or require an additional compatibility layer.

Open the disk image and follow the installer window’s instructions to place the app, then launch it from Applications. Don’t rely on running the app directly from a mounted image; it may become unavailable when you eject it. If macOS shows a source or permissions prompt, verify the downloaded file and the app you’re opening, then follow the system instructions. Avoid methods that disable protections in bulk.

Launching the client doesn’t automatically enable the system proxy. Import a configuration, select a server, and check the current proxy mode first. TUN also requires the right permissions and network settings. If the standard proxy works but TUN can’t route traffic, focus on permissions, routing, and the network stack—not on downloading the same installer again.

See TUN permissions and configuration →

v2rayNG

Android · Xray core · 2.2.6

Top pickFree & open source

arm64 build

Download v2rayNG · arm64

A good choice for most mainstream phones released since 2015, but confirm that the system supports arm64.

v2rayNG_2.3.11_arm64-v8a.apk

Universal build

Download v2rayNG · universal

Choose this if you’re unsure of the architecture or need compatibility with other supported architectures. The package is usually larger.

v2rayNG_2.3.11_universal.apk

v2flyNG

Android · V2Fly core · 1.10.31

AlternativeFree & open source

arm64 build

Download v2flyNG · arm64

For users who have confirmed their configuration works with the V2Fly core and whose device supports arm64.

v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Universal build

Download v2flyNG · universal

This is another architecture option for the same client; it doesn’t change the core family.

v2flyNG_1.10.31-fdroid_universal.apk

Android system and installation requirements

Check	What to look for
Device architecture	Check for arm64 support first. A 64-bit processor doesn’t necessarily mean the device’s operating system supports the corresponding apps.
macOS version	The minimum Android version depends on the selected package. A universal build isn’t necessarily compatible with every older system.
Installation and connection permissions	Grant install permission to the app opening the package when prompted. On the first connection, approve Android’s VPN permission. Run only one client that intercepts traffic at a time.

Choose between v2rayNG and v2flyNG based on the core and configuration you need, not the package size. v2rayNG uses the Xray core; v2flyNG uses the V2Fly core. The two core branches don’t support exactly the same protocols and configuration fields. Similar-looking interfaces don’t mean the same configuration will work in both clients.

After downloading the installer, open it from your file manager or download list and grant the necessary permission only to that install source. If an update reports a signature conflict, don’t uninstall the existing app right away. First save your subscription and manually added server settings, then check the original install source. Uninstalling may remove app data; reinstalling won’t restore settings that weren’t backed up.

The first time you connect, Android usually shows a VPN permission prompt. Approve it so the client can route traffic according to its settings. If another similar connection is running, stop it before starting this client. During connection testing, check whether background restrictions are affecting the app. Adjust its background settings after the test so a sleep-related interruption isn’t mistaken for a server failure.

See how to import a subscription on Android →

v2rayN

Linux · 7.24.1

Free & open sourceDesktop GUI

deb · x64

Download deb · x64

For compatible distributions using the deb package management system, such as Debian and Ubuntu.

v2rayn_7.24.1_amd64.deb

rpm · x64

Download rpm · x64

For distributions that use rpm and meet the package’s current dependencies.

v2rayN-7.24.1-1.el10.x86_64.rpm

For arm64 devices, choose the matching package

Download deb · arm64 → Download rpm · arm64 →

Here, arm64 and aarch64 refer to the same target architecture; amd64 and x86_64 correspond to x64. These labels aren’t tied to a specific processor manufacturer.

Linux system and installation requirements

Check	What to look for
Package management system	First identify whether your distribution uses deb or rpm, then check that it meets the package’s dependencies. The same file extension doesn’t guarantee compatibility with every distribution.
CPU architecture	For x64, choose an amd64 or x86_64 package; for arm64, choose an arm64 or aarch64 package.
Desktop and permissions	This is a GUI client and requires a working desktop environment. Install it with your system package manager; enabling TUN requires additional permissions.

The package format is only the first check; your distribution version and dependencies determine whether installation will work. If an rpm filename includes a build-environment label, read the installer’s dependency warnings first. Don’t force the installation by ignoring missing dependencies. Once your package manager reports success, launch the client from the desktop application menu and confirm that the interface and core load correctly.

If your device uses an ARM processor, don’t download the default x64 package. Check the system architecture and choose the arm64 package below. Architecture information in a container, remote session, or compatibility environment may differ from the desktop environment actually running the client. Use the architecture of the system where the client will run.

Desktop environments handle system proxy settings differently. First test the client’s local proxy, then check whether your apps use the system proxy; some apps require separate configuration. TUN routes a wider range of traffic but also involves permissions, routing, and DNS. Don’t change multiple system network settings before you’ve verified the standard proxy.

See DNS and routing configuration →

Configuration steps after installation

Make sure the program opens before setting up a connection. Installation errors and network errors happen at different stages: if the program won’t start, check the architecture, dependencies, and install permissions first. If it starts but can’t connect, check the subscription, server settings, and client logs. Downloading the installer again usually won’t fix an expired subscription URL.

Before importing a subscription, make sure the URL is complete and comes from a source you’re authorized to use. Don’t include spaces or line breaks when copying it, and don’t mistake a management page URL for a subscription URL. After the subscription updates successfully, select a server and test the connection. Seeing servers in the list confirms the import worked, but doesn’t guarantee the remote service is available.

Once the standard proxy connection works, configure routing rules, DNS, and TUN. Change one category at a time and note the original settings. That way, if something goes wrong, you can return to the last working state instead of guessing which of several changes caused it. If you use many custom rules, keep a simplified configuration as a baseline.

A backup should include more than subscription URLs. Manually added servers, custom outbound settings, edited configuration files, and filtering rules may not come back when you refresh a subscription. Save these items and note your current working proxy mode and port settings. After updating, test the default connection first, then restore advanced features one at a time to narrow down compatibility issues.

When troubleshooting, note which step failed and keep the complete error text. Logs and screenshots may contain subscription URLs, account details, and server information; hide sensitive data before sharing. Don’t publish your full configuration for testing or post links that contain access credentials in public discussions. For more help with request errors and subscription updates, visit the Help Center.

Download and installation FAQs

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

For a first install, start with Desktop, which uses a newer cross-platform interface. The classic WPF edition keeps the familiar Windows layout. Both require you to import your own connection settings. Before switching, back up your subscriptions, servers, and custom rules. Don’t let both editions manage the system proxy at the same time.

Should you download the arm64 or universal Android build?

Most mainstream phones released since 2015 are likely to support arm64, but check the architecture supported by your device’s operating system. Choose the universal build if the architecture is unclear or you need compatibility with other supported architectures; it’s usually larger. If Android reports that the package is incompatible, check the architecture and system requirements instead of reinstalling the same file.

Do I need a subscription or server settings after installing the client?

Yes. The client reads your settings and establishes a connection; the installer does not include a working server. Have a subscription link you’re authorized to use or individual server details ready, then import them using the quick-start guide. Subscription URLs may contain credentials, so hide the full URL and account details when troubleshooting or sharing screenshots.

What should I check first if installation fails?

Note your OS version, CPU architecture, installer filename, and the complete error message. On Windows, check that files are extracted and look for runtime requirements. On macOS, make sure the package matches your chip. On Android, check install permissions and signature conflicts with an existing app. On Linux, confirm the package format and dependencies suit your distribution. Don’t disable system protections or delete unbacked-up settings.

What should I save before updating the client?

Save your subscription groups, manually added servers, custom routing rules, DNS settings, and custom configuration files. Quit the client before installing the update, and don’t run another version during the process. After updating, test a standard proxy connection first, then restore TUN or custom rules one at a time to make compatibility issues easier to pinpoint.

Why does the client’s displayed version differ from the installer filename?

The version shown on a client card and the installer link come from different fields in the release manifest, so they may temporarily be out of sync. Check both the filename and platform notes before downloading. After installation, use the version shown on the client’s About page. Don’t infer protocol compatibility from the filename alone; feature support depends on the client and its core.