GUI Clients · Platforms and Architectures

V2Ray Client Downloads

Choose v2rayN for desktop and v2rayNG for Android.
Check your operating system and CPU architecture before choosing an installer.

Open source Free to use Installation and subscription setup guide →

Windows installers

One v2rayN client, two interfaces. Choose Desktop for a first install, or WPF if you prefer the classic workflow.

v2rayN

Recommended 7.24.1

Desktop edition

A next-generation cross-platform UI for first-time users and anyone who wants a consistent desktop experience.

Download v2rayN · Desktop x64

ZIP archive · Extract all files before running

Classic WPF edition

The familiar Windows interface for experienced users who want to keep the classic workflow.

Download v2rayN · WPF x64

ZIP archive · Choose either Desktop or WPF

Extract, install, and launch

Extract the entire archive to a local folder you can write to, then open the included installer or launcher. Don't run the app from the archive preview or extract only the executable; it may need files in the same folder to start. If the installer reports a missing runtime, check its name and architecture, then install the required version.

Desktop and WPF are interface options, not subscription types. Export a backup before moving an existing setup to the other interface. When testing the new interface, exit the old client to prevent both from changing the system proxy. When you're done, clear the system proxy in the client before exiting to avoid leftover proxy settings disrupting your next browser session.

Windows requirements and checks

Item	Check before installing
CPU architecture	Both downloads on this page are x64. Check System type under Settings > System > About. An x64 installer isn't a native installer for other architectures.
Windows and runtime	Use a supported, up-to-date version of Windows. Check the installer prompts for the minimum OS version and runtime requirements.
Folder and permissions	Choose an extraction folder you can write to. System proxy and network permissions may be controlled by device policies; a regular launch doesn't normally require administrator rights.

If the window closes immediately, check that the archive was fully extracted and the runtime is compatible, then review the logs. Repeated downloads usually won't fix a port conflict with another program.

macOS installers

Open About This Mac in the Apple menu and check the Chip or Processor information to choose the right architecture.

v2rayN

7.24.1

Apple Silicon

For a Mac showing an Apple M-series chip in About This Mac. Choose the native ARM64 installer.

Download v2rayN · Apple Silicon

DMG disk image · ARM64

Intel

For a Mac showing an Intel processor in About This Mac. Don't rely on the computer's appearance or purchase year.

Download v2rayN · Intel x64

DMG disk image · x64

Install location and network permissions

Open the disk image and follow its instructions to move the app to Applications, then launch it from there. Don't run it from the mounted image long-term; the app may become unavailable when you eject it. If macOS shows a security warning on first launch, check the file's source and the warning details in System Settings. Don't disable macOS security protections.

If only some apps can access the network after you connect, check whether those apps use the system proxy. A standard system proxy is different from a mode that routes all device traffic, which may require additional permissions. Start with the standard proxy to verify the connection, then configure advanced network permissions if needed.

macOS requirements and checks

Item	Check before installing
Chip architecture	Choose ARM64 for Apple M-series chips and x64 for Intel processors. Use the native installer that matches your device.
macOS compatibility	Minimum macOS versions vary by app and runtime. If macOS reports an incompatibility, check the requirements rather than repeatedly trying different downloads.
Network settings	Make sure your current network service allows proxy changes. Company- or school-managed devices may require administrator approval.

After copying settings from an old device, recheck local paths, proxy ports, and permissions. Configuration files can be imported, but platform-specific settings may still need adjustment.

Android installers

Start with v2rayNG. Consider v2flyNG if you need compatibility with the V2Fly core; each app manages its own settings.

v2rayNG

Recommended Xray core 2.2.6

arm64 edition

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

Download v2rayNG · arm64

APK · arm64-v8a

Universal edition

An alternative if you're unsure of your device's architecture. Includes resources for multiple architectures and is usually a larger download.

Download v2rayNG · Universal

APK · Universal

Installation permissions and first connection

Once the download finishes, open the APK from your browser's download history or a file manager. If Android asks you to allow installs from this source, grant permission only to the app you're using to open the file; you can revoke it after installation. On the first connection, review the VPN permission prompt and confirm the client name before allowing it. Granting permission doesn't guarantee that your subscription settings are valid.

Import and select a profile before starting the connection. Android generally allows only one user-level VPN service at a time, so another VPN connection may be replaced or blocked. If the connection drops after you switch to another app, check battery optimization, background activity, and the manufacturer's battery-saving settings. Avoid changing a lot of network settings at the outset.

v2flyNG

Alternative · V2Fly core 1.10.31

arm64 edition

For devices that support ARM64 apps and setups that need compatibility with the V2Fly core.

Download v2flyNG · arm64

APK · arm64-v8a

Universal edition

Choose this if you're unsure of the device architecture. Before switching clients, check that the required protocols and transport features are supported by the configuration.

Download v2flyNG · Universal

APK · Universal

v2flyNG isn't an add-on for v2rayNG. To switch, import your subscription or settings again; don't assume custom settings work identically in both clients. Core features also differ. If a field isn't supported, check your configuration requirements instead of assuming the installer caused a subscription error.

Android requirements and checks

Item	Check before installing
App architecture	Use arm64 if possible. A 64-bit processor doesn't necessarily mean the device's OS supports 64-bit apps. If you're unsure, try the Universal version.
Android version	The minimum Android version depends on the APK. The Universal version supports more architectures; it doesn't lower the required Android version.
Installing over an existing app	The same app may have different signing keys across distribution channels. If you see a signature conflict, back up your settings before considering uninstalling the old app.
VPN permission	The first connection requires VPN permission from Android. For the app to keep running, you may also need to adjust its battery optimization settings.

Linux installers

Choose deb or rpm for your distribution, then confirm x64 or ARM64. These downloads are for the desktop GUI client.

v2rayN

7.24.1

deb package

For distributions that use deb packages. Before installing, check that the package manager can resolve all dependencies.

Download v2rayN · deb x64 ARM64 device: Download deb arm64 →

rpm package

For distributions that use rpm packages and meet this package's dependencies. The file extension alone doesn't guarantee compatibility.

Download v2rayN · rpm x64 ARM64 device: Download rpm aarch64 →

Distribution dependencies and desktop session

Open the downloaded package with your distribution's software installer and review the dependency check before proceeding. x64 may appear as amd64 or x86_64 in filenames; ARM64 may appear as arm64 or aarch64. Don't rename a file extension to convert package formats, and don't force installation by ignoring dependencies.

The rpm filename includes a target distribution identifier; that doesn't mean it will run on every rpm-based system. If the installer reports that system libraries are too old, check whether your distribution is supported. After installing, launch the app from your current desktop session and test the connection without elevated permissions. Desktop system proxy settings, an app's own proxy, and terminal environment variables are separate; check each one as needed.

Linux requirements and checks

Item	Check before installing
Package format	Choose deb or rpm for your distribution. Compatibility depends on the package metadata and system dependencies.
CPU architecture	x64 corresponds to amd64 or x86_64; ARM64 to arm64 or aarch64. Native packages aren't interchangeable across architectures.
Desktop environment	A working desktop session and the graphics libraries required by the app are needed. These instructions aren't intended for command-line-only servers.
Proxy coverage	Whether the system proxy works depends on your desktop environment and target apps. Terminal tools may need separate configuration.

If installation succeeds but the window won't appear, check your desktop session and graphics dependencies first. If the window opens but connections fail, check your configuration, ports, DNS, and routing.

Set up the client after installation

Installation is only the first step. Import settings, verify the connection, and adjust routing separately to make problems easier to diagnose.

Import a subscription or share link

The client doesn't come with working proxy servers. Confirm that your configuration source is trusted and the details are current, then import them through subscription management, the clipboard, or a QR code. A subscription URL retrieves a set of configurations that can be updated; a single-node share link usually imports just one. They aren't interchangeable.

Subscription URLs may contain credentials. Don't post the raw URL, QR code, or a screenshot of your full configuration publicly.

Select a profile and test the connection

After updating, select a profile, check that its local port is available, and enable the proxy mode you need. Desktop apps differ in whether they follow the system proxy; mobile clients require system VPN permission. Test one specific app first so a localized issue isn't mistaken for a complete connection failure.

For your first test, don't run multiple proxy clients or change DNS, routing, and core settings at the same time.

Adjust routing and save a backup

Once the basic connection works, set direct and proxy rules for your needs. Rule order affects which rules match, and changing DNS resolution may affect IP-based rules. Change one group of settings at a time and note what happens before and after. When everything is stable, export a backup so you can restore it after an upgrade or migration.

To use settings on another device, import them manually and recheck file paths, local ports, and platform permissions.

Read the complete Getting Started guide → Troubleshoot connection issues by symptom →

Download and upgrade FAQs

First distinguish installation issues from connection issues. Opening the client doesn't mean your configuration is ready.

Which should you choose: v2rayN Desktop or classic WPF?

For your first install, choose Desktop, which uses a next-generation cross-platform interface. The classic WPF edition is for users familiar with the original Windows interface and workflow. You don't need to install both. Export your settings before switching, and avoid enabling the system proxy in both clients or using the same local ports at the same time.

Should I download the arm64 or Universal Android version?

Most mainstream phones released since 2015 should use arm64, but check which app architectures your device supports. Some devices may support only other architectures. If you're unsure or see an architecture incompatibility warning, try the Universal version. It won't bypass Android version requirements or resolve an APK signature conflict.

Why can't I connect after installing the client?

The client manages settings and establishes connections; the installer doesn't include a subscription or account. Get configuration details from a trusted source, import a subscription or share link, update and select a profile, then choose a proxy mode. First make sure the connection works, then adjust routing and DNS as needed.

What settings should I keep before upgrading?

Before upgrading, use the client's export or backup feature to save subscription groups, custom routing, DNS settings, and local port details. Exit the old client before installing the update. When switching clients, don't overwrite the entire data directory; import your settings again and check for platform-specific differences. Backups may contain credentials, so store them securely.

What should I do if a download is interrupted or the system blocks installation?

If a download stops, check your connection, available disk space, and browser download history before retrying the installer. If the system blocks installation, read the warning and identify whether it's due to an architecture mismatch, insufficient permissions, a signature conflict, or a security policy. Don't disable system protections. On managed devices, contact your administrator first.

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

The displayed version and download link come from different fields in the release manifest, so they may not update at the same time. Don't rely on the filename to identify the installed version. Check the client's About page after installation. If the version isn't what you expected, keep your existing settings and wait for the manifest to update or check the download link again.