GUI clients · Choose a package

V2Ray client downloads

Choose v2rayN for desktop and v2rayNG for Android.
Check your operating system first, then choose the interface, processor, and package format.

Four platforms Free, open-source clients Subscription required separately

Windows client

Two interfaces, one client. Both downloads below are for x64.

v2rayN

Recommended 7.24.1

Manage subscription groups, system proxy, routing rules, and TUN mode in one place. Start with Desktop for a new install, or choose WPF if you prefer the classic workflow.

Desktop edition

A next-generation cross-platform UI for users who want a consistent workflow across desktop operating systems.

Download Desktop · x64

v2rayN-Desktop-Setup-x64-7.24.1.zip

Classic WPF edition

The classic stable edition for Windows. Choose it if you’re used to the original window layout and menus.

Download classic WPF · x64

v2rayN-Setup-x64-7.24.1.zip

Extract, install, and launch

This download is a ZIP file. Once it’s downloaded, extract the entire archive, open the installer in the extracted folder, and follow the setup wizard. Don’t run it from the archive preview or extract just one file. After launch, check that the main window displays correctly before importing a configuration. This makes installation issues easier to distinguish from connection issues.

The two editions mainly differ in how their interfaces are implemented; neither will make your connection faster. Connection quality still depends on your server configuration, routing, and local network. Before switching from the classic interface, back up your settings and subscription groups, then close the old instance. Running both can cause conflicts over local listening ports or repeated changes to the system proxy.

Windows installation requirements

Check	Requirements and guidance
System architecture	Both downloads are x64. Open Settings → System → About and check System type; don’t guess based on the device’s appearance.
Runtime dependencies	Follow the installer and startup prompts. If a runtime is missing, check the runtime name and architecture shown in the message before installing it.
Write access	The configuration directory must be writable. Start the app without elevated permissions for normal use; grant administrator access for TUN only when prompted by the client.
Existing proxy software	Quit other apps that control the system proxy or virtual network adapters. Confirm one proxy method works before adding more settings.

macOS client

Open About This Mac and choose a package based on the chip or processor listed there.

v2rayN

7.24.1

The macOS client uses a cross-platform desktop interface. DMG downloads are available for Apple Silicon and Intel; choose the build that matches your Mac’s processor.

Apple Silicon

If About This Mac lists an Apple M-series chip, choose the arm64 package.

Download for Apple Silicon

v2rayN-macos-arm64.dmg

Intel

If About This Mac lists an Intel processor, choose the x64 package.

Download for Intel

v2rayN-macos-64.dmg

Install from the disk image

Open the DMG, copy the app to the Applications folder, then launch it from there. Don’t keep running it from the mounted disk image, as this can complicate updates, permissions, and file paths. Eject the disk image after copying. Test that the app opens before setting up subscriptions and proxy options.

macOS may show a security warning the first time you open the app. Check the file’s source and confirm you chose the right processor build, then review the relevant notice under System Settings → Privacy & Security. Don’t run commands from unknown sources to bypass restrictions. If the app opens but your browser isn’t using the proxy, check the system proxy status instead of repeatedly downloading a different build.

Quit the old version before updating and keep a backup of your settings. Replace the app, reopen it, and check that subscription groups, routing choices, and listening ports still match your needs. TUN requires additional permissions and network control; configure it separately after a regular proxy connection works.

macOS installation requirements

Check	Requirements and guidance
Processor	Apple Silicon uses arm64; Intel uses x64. Check About This Mac to confirm your processor.
System compatibility	Your macOS version must meet the current build’s requirements. If the app says your system is too old, address compatibility first rather than changing proxy settings.
Install location	Copy the app to Applications. Make sure your account can open it and write to its user configuration directory.
Network permissions	Grant the permissions requested by macOS. Check TUN permissions separately if needed; you don’t have to enable every feature on first launch.

Android clients

Start with v2rayNG. Consider v2flyNG if you need the V2Fly core ecosystem.

v2rayNG

Recommended 2.2.6

An Android GUI client using the Xray core, with share-link import, subscription management, and per-app proxying. Most mainstream phones released after 2015 can use arm64.

arm64

For systems that support arm64-v8a apps. Check the architecture supported by your system, not just the processor model.

Download v2rayNG · arm64

v2rayNG_2.3.11_arm64-v8a.apk

Universal version

Choose this if you’re unsure which architectures your device supports. It includes multiple architecture builds, so the file is usually larger than a single-architecture package.

Download v2rayNG · universal

v2rayNG_2.3.11_universal.apk

Install permissions and first connection

After downloading the APK, open it from your browser’s download list or a file manager. If Android asks you to allow installs from this source, grant permission only to the browser or file manager you’re using, and revoke it afterward if you like. If you see “App not installed,” note the exact message, then check available storage, architecture, and the existing app’s signing certificate. Don’t assume every installation failure is a network issue.

After importing a configuration, the first connection triggers Android’s VPN permission prompt. This system confirmation lets the client route traffic through VpnService. After granting permission, check that the intended configuration is selected. If the connection drops when the screen locks, adjust the client’s background restrictions in battery settings. Don’t change every battery-saving option up front.

v2flyNG

Alternative · V2Fly core 1.10.31

An alternative Android client using the V2Fly core. If your configuration depends on specific V2Fly behavior, first check that its protocols, transports, and related parameters are supported.

arm64

For phones that support arm64 apps. Back up your existing subscriptions and settings before installing.

Download v2flyNG · arm64

v2flyNG_1.10.31-fdroid_arm64-v8a.apk

Universal version

Use this if you’re unsure of your device’s architecture. A universal package still has system-version and configuration compatibility requirements.

Download v2flyNG · universal

v2flyNG_1.10.31-fdroid_universal.apk

Choosing between the two Android clients

v2rayNG and v2flyNG aren’t the same app under different names. They use different core ecosystems, and support for specific configuration options may vary. Don’t assume every share link will work identically in both; check the required protocol and transport support first. When testing, run only one VPN connection at a time to avoid confusing results caused by Android switching which app controls the connection.

Android installation requirements

Check	Requirements and guidance
App architecture	arm64 works on systems that support the relevant ABI. If you’re unsure, choose the universal version, and still check the installer’s system requirements.
Install permissions	Follow Android’s prompt to allow APK installs from the current source. For updates, check that the app ID and signing certificate are compatible.
VPN permission	Accept Android’s VPN request on first connection. If another VPN is active, decide which connection you want to keep first.
Background operation	If the connection drops when the screen locks, check battery optimization, autostart, and background activity permissions. Settings vary by device and Android version.

Linux client

Check your distribution’s package format first, then confirm whether your system is x64 or arm64.

v2rayN

7.24.1

The Linux GUI uses a cross-platform interface. The main downloads below are for x64; arm64 users can choose the matching package under each format.

deb package

For Debian, Ubuntu, and compatible distributions. Use your system’s package installer to resolve dependencies.

Download deb · x64

v2rayn_7.24.1_amd64.deb

For arm64: Download deb

rpm package

For Fedora, RHEL, and compatible distributions. Check that your distribution meets the dependency requirements before installing.

Download rpm · x64

v2rayN-7.24.1-1.el10.x86_64.rpm

For arm64: Download rpm

Check dependencies with your package installer

Open the downloaded package in your desktop environment. Review the package name, architecture, and dependencies shown by the installer before confirming. You can’t convert a deb to rpm just by changing the file extension. Even a matching extension doesn’t guarantee compatibility with your distribution version or system libraries. If you hit a dependency error, keep the full error message and address system compatibility first; don’t force the installation by skipping dependencies.

After installation, launch v2rayN from the applications menu. Import a working configuration and test a regular proxy connection before trying TUN. On Linux, desktop system proxy settings, the app’s own proxy settings, and virtual network adapter routing are separate layers. Some apps don’t use the desktop system proxy, so a working browser connection doesn’t mean every app is routed through the client.

Quit the client before updating and back up your user settings. Don’t alternate between accounts with different permissions to launch the same configuration, or you may run into directory ownership problems. For features that need elevated permissions, follow the client and system prompts. Running the entire desktop app as an administrator is not a general-purpose fix.

Linux installation requirements

Check	Requirements and guidance
Desktop environment	This page provides a GUI client. You’ll need a working desktop session and the graphical runtime dependencies required by the current build.
Package format	Choose deb or rpm based on your distribution. Don’t install across package systems by changing the file extension or ignoring dependencies.
Processor architecture	amd64 and x86_64 correspond to x64; arm64 and aarch64 correspond to 64-bit ARM. Choose the package that matches your system’s architecture.
Permissions and traffic routing	Test a regular proxy separately from TUN. TUN requires additional permissions and network settings; check for existing virtual network adapters and proxy apps first.

Configuration after installation

The installer provides the app, a subscription provides configuration, and proxy mode controls how traffic is routed. Check each separately to narrow down issues.

Get a subscription or share link

Installing the client doesn’t automatically add a working server. On desktop, add a URL under Subscription Group and update it; to import a single share link, use the Servers menu and import it from the clipboard. On Android, use the add menu to import a link, then update the subscription if needed. Check that the URL is complete and isn’t just the webpage where the subscription is hosted.
Choose one proxy method first

On desktop, start by checking System Proxy → Automatically configure system proxy, then choose a routing mode for your needs. Set up TUN only if you need to route apps that don’t use the system proxy. On Android, grant VPN permission first. Before using per-app proxying, check whether the app list defines apps to proxy or bypass so you don’t accidentally exclude the apps you want to route.
Test before changing routing or DNS

First, visit a site that should use the proxy, then check one that should connect directly. If something goes wrong, note the error type in the client log. Don’t change the server, DNS, routing, and TUN settings all at once. Change one setting at a time and retest. A successful latency test doesn’t guarantee every app can connect.

View the v2rayN setup guide →

Download and installation FAQ

First confirm you chose the right package, then check permissions and configuration. Expand a question below for guidance.

Which should I choose for Windows: Desktop or classic WPF?

For a fresh install, start with Desktop, which uses a next-generation cross-platform interface. If you prefer the classic interface, choose the stable WPF edition. Both manage proxy configurations. Back up your settings before switching, keep each edition in its own directory, and don’t let both instances control the system proxy at the same time.

Should I download the arm64 or universal Android version?

Most mainstream phones released after 2015 can use arm64, but check which app architectures your system supports. If you’re unsure, choose the universal version. If arm64 is reported as incompatible, don’t keep reinstalling the same file. Check the system architecture, available storage, and whether the installed app’s signing certificate is compatible.

Why don’t I have a server after downloading the client?

The installer contains the client app, not a subscription URL or server configuration. You’ll need a subscription or share link you’re authorized to use, then update it through a subscription group or import it from the clipboard. Subscription URLs may contain access credentials; keep them out of public screenshots, logs, and comments.

Do I need to uninstall the old client before updating?

Back up your settings, quit the old client, and make sure its background process has stopped. Follow the installer for desktop updates. Android apps can usually be installed over an existing version, provided the app ID and signing certificate are compatible. If you encounter a signature conflict, verify the download source first. Don’t delete unbacked-up data just to force the update.

What if an app won’t open after installation on macOS?

Make sure the installer matches your Apple Silicon or Intel processor, and copy the app to the Applications folder. If macOS blocks the first launch, verify the app’s source and check the Privacy & Security notice in System Settings. Keep macOS security protections enabled; don’t run unknown commands to bypass them.

Should I choose deb or rpm on Linux?

Choose deb for Debian, Ubuntu, and compatible distributions; choose rpm for Fedora, RHEL, and compatible distributions. Also check whether your processor is x64 or arm64. A matching package format doesn’t guarantee all dependencies are met, so review the installer’s dependency and distribution compatibility warnings before proceeding.

Installed successfully but having connection issues? See the FAQ or use the advanced guide to check routing, DNS, and TUN settings step by step.

V2Ray client downloads

Windows client

v2rayN

Desktop edition

Classic WPF edition

Extract, install, and launch

Windows installation requirements

macOS client

v2rayN

Apple Silicon

Intel

Install from the disk image

macOS installation requirements

Android clients

v2rayNG

arm64

Universal version

Install permissions and first connection

v2flyNG

arm64

Universal version

Choosing between the two Android clients

Android installation requirements

Linux client

v2rayN

deb package

rpm package

Check dependencies with your package installer

Linux installation requirements

Configuration after installation

Get a subscription or share link

Choose one proxy method first

Test before changing routing or DNS

Download and installation FAQ