Client Downloads / Choose an Architecture

V2Ray Client Downloads

v2rayNG for Android and v2rayN for desktop. Choose your operating system first, then your processor architecture.

All three clients are free and open source. After installation, import a server configuration or subscription URL that you're authorized to use.

See the installation and import guides →

Windows：v2rayN

For a fresh install, choose Desktop; to keep the classic interface, choose WPF. Both downloads below are x64 ZIP archives.

v2rayN

Recommended

Desktop client · 7.24.1 · Windows x64

Download Desktop · x64 Download classic WPF · x64

Desktop is the newer cross-platform UI. It's a good choice for first-time installs or if you want a consistent experience across desktop operating systems. WPF is the classic, established interface. Stick with it if you're already familiar with its server list, subscription groups, and settings. The main differences are in the interface and how features are organized; switching versions is not a general fix for server connection issues.

After downloading the ZIP, extract it to a separate folder and run the installer from there. Don't launch it from the archive utility's preview. Choose an install location your account can access. If a required component is missing, follow the system's guidance and check the specific error rather than repeatedly trying different client packages.

System requirements and pre-install checks

Check	Packages on this page	How to check
OS and architecture	64-bit Windows, x64	Check System type under Settings → System → About. Neither package is a native ARM build.
OS compatibility	Use a supported version of Windows 10 or 11 where possible	For older Windows versions, check the exact OS and runtime requirements. “64-bit” alone doesn't guarantee compatibility.
File format	ZIP archive	Extract all files before installing, and keep a backup of your existing configuration.
Connection handling	System proxy or the client's TUN mode	Only let one client manage the proxy at a time. For your first test, use the system proxy.

After launching the client, import your configuration, select a server, and then enable the system proxy. The system proxy affects only apps that honor that setting; if an app doesn't use the proxy, that doesn't necessarily mean the installation failed. To route more traffic, see the TUN and routing guide.

macOS：v2rayN

Check the chip name in About This Mac. Choose arm64 for Apple Silicon or x64 for an Intel processor.

v2rayN

Desktop

macOS client · 7.24.1 · DMG

Download Apple Silicon · arm64 Download Intel · x64

Apple Silicon chip names usually start with M; choose the arm64 package. If About This Mac shows an Intel processor, choose x64. Don't guess based on the case model, purchase year, or macOS version: different configurations of the same computer line may use different chips. Choosing the native architecture also avoids extra variables from compatibility translation.

Open the DMG and copy the app to Applications before launching it from there. If macOS shows a security warning the first time you open it, verify the download source, then check the specific message under System Settings → Privacy & Security. You don't need to disable system-wide security to run a client.

System requirements and pre-install checks

Check	What to check	Notes
Chip	Apple Silicon / Intel	Use About This Mac in the Apple menu to identify it; don't judge by the device's appearance.
OS version	Must meet the selected app package's minimum requirements	A matching architecture doesn't guarantee compatibility with an older OS. Check the installer prompts and app requirements.
Install location	Applications	Launch the app after copying it. Avoid running it long-term from a mounted disk image.
Network permissions	Grant permissions for the features you use	Read the permission prompt before changing the system proxy or enabling TUN.

If the app opens but your browser still uses its usual connection, check the system proxy toggle, active network service, and the browser's own proxy settings. Before updating, quit the old process and then replace the app. Keeping your subscription URL doesn't preserve every local rule, so also note your routing settings and custom DNS options.

Android: v2rayNG and v2flyNG

v2rayNG is the recommended choice. Most mainstream phones released since 2015 use arm64, but check the architecture supported by your system.

v2rayNG

Recommended

Xray core · 2.2.6 · Android APK

Download v2rayNG · arm64 Download v2rayNG · Universal

v2rayNG uses the Xray core and is suited to managing common share links, subscriptions, routing, and per-app proxy settings on Android. For VLESS or REALITY configurations, follow the provider's parameter requirements. Don't rely on the protocol name alone; check the transport, security type, and server name too.

The arm64 package is for devices whose system supports arm64-v8a apps. The universal version includes multiple architectures and is a good option if you're unsure. Some devices have a 64-bit processor but run a 32-bit-only app environment, so the purchase year and processor specs are only clues, not a substitute for checking compatibility.

v2flyNG

Alternative

v2fly core · 1.10.31 · Android APK

Download v2flyNG · arm64 Download v2flyNG · Universal

v2flyNG uses the v2fly core and is suited to existing configurations known to support it. It's a standalone app, not an add-on for v2rayNG. The clients may differ in features and supported parameters, so don't assume a configuration with core-specific fields will work in both.

When moving from another client, export the share links or subscription details you need, then check your routing, DNS, and per-app proxy settings one by one. Don't run both apps' VPN services at the same time. If only one configuration fails to connect, check its error log and parameter support before trying a different installer.

System requirements and pre-install checks

Check	Requirement or option	What to do
App architecture	arm64 / universal	If you're unsure which architecture your system supports, choose the universal version. The app must still meet the minimum OS requirements.
Install permission	Allow installs from this source	Grant permission only to the browser or file manager you're using, and turn it off after installation if you like.
VPN permission	Confirm on first connection	Android will show a connection request. The client can route the relevant traffic only after you approve it.
Background operation	Adjust for your device's battery settings	Check background restrictions only if the connection drops when the screen locks; there's no need to change every battery-saving option in advance.

If Android reports “App not installed,” check the OS version, app architecture, available storage, and signing certificate in that order. The universal version covers more architectures, but won't fix a signing conflict or an outdated OS. If the displayed version and filename temporarily differ, check the app's About page or your system's app information for the installed version.

Linux：v2rayN

Check which package format your distribution uses, then choose x64 or arm64. The primary downloads are x64 packages.

v2rayN

Desktop

Linux GUI client · 7.24.1 · deb / rpm

Download deb · x64 Download rpm · x64

ARM desktop devices: deb · arm64 rpm · arm64

Debian, Ubuntu, and distributions using similar package management systems typically use deb packages; distributions in the RPM family use rpm. Choosing the right format is only the first step: system libraries, the desktop environment, and software dependencies must also meet the requirements. RPM-based distributions don't all share the same runtime environment.

Open the package in your graphical file manager and let the system software installer handle dependencies. If it reports missing libraries or incompatible versions, read the error details rather than forcing the installation. After installing, launch v2rayN from the app menu and import your configuration. Whether the system proxy works also depends on your desktop environment and whether the target app honors the setting.

System requirements and pre-install checks

Check	How to choose	Notes
Processor architecture	x64 / arm64	amd64 and x86_64 refer to x64; aarch64 usually corresponds to arm64.
Package format	deb / rpm	Choose based on your distribution. Changing the file extension won't convert a package.
Runtime environment	Graphical desktop and required dependencies	These packages are for the graphical client. An installer that opens successfully doesn't guarantee all runtime dependencies are available.
Network permissions	System proxy / TUN	Test the configuration with a standard proxy first. For TUN, follow the client's prompts for any additional permissions.

If the app is running but only some apps use the proxy, check your desktop proxy settings and each app's network options. Before enabling TUN, rule out conflicts with other VPNs, virtual network adapters, and existing routing rules. Running a graphical client with elevated privileges shouldn't be your default workaround.

After installation

Import configuration, connect, and update

The installer gets the client running; server settings establish the connection. Verify each step in order to avoid misdiagnosing problems after changing several settings at once.

First connection: check that your configuration is complete

A single-server share link and a subscription URL are different things. To import a share link, copy it and use the clipboard import option. For a subscription URL, create a subscription group, enter the URL, and update it. Don't use a webpage's information URL as a subscription URL, and don't remove the transport or security parameters at the end of a link.

After importing, select a configuration and keep the basic routing and DNS settings for your first test. Then enable the system proxy or VPN. Open a site you normally use and check the logs to confirm the connection. A running indicator only means the client service has started; it doesn't confirm that the server, DNS, and route to the destination are all working.

Follow the steps to import a configuration and test the connection →

Update the client: back up before replacing

Before updating, export your configuration and save your subscription groups, routing rules, DNS, and per-app proxy settings separately. You can usually fetch server details again from a subscription, but it won't restore every local preference. Backups may contain server credentials; keep them somewhere secure and don't share them publicly.

Quit the old client before installing so background processes don't keep files in use. You can usually install over the existing version when it's the same app and the signing certificate is compatible. If there's a conflict, find out why before uninstalling and risking data loss. After the update, verify your existing configuration first, then enable new features one at a time to help identify upgrade-related issues.

View subscription, routing, and DNS settings →

Download FAQs

Package selection and compatibility

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

For a first-time install, choose Desktop, which features a newer cross-platform interface. If you already use the classic interface and it works well, you can stick with WPF. Back up your configuration before switching, and don't let both clients manage the system proxy at the same time.

Should you download the arm64 or universal Android version?

For most phones released since 2015, check for arm64 support and choose the arm64 APK if available. The device's release year is only a guide; the architecture supported by the OS is what matters. If you're unsure or arm64 isn't compatible, choose the universal version. It won't fix an incompatible OS version or signing conflict.

Why is there no server to connect to after installing the client?

The client reads configuration and establishes connections; the installer does not include a ready-to-use server configuration. Import a share link, QR code, or subscription URL that you manage or are authorized to use, then select a server and connect.

Do I need to uninstall the old version before updating?

You can usually install over the existing version if it's the same app, the signing certificate matches, and the OS allows the upgrade. Export your configuration first and note your subscription groups and routing settings. If you see a signing conflict, don't uninstall right away; verify the installer source and make sure your backup can be restored.

The version shown on the page doesn't match the installer filename. Which should I trust?

The version label and download path come from different fields in the release manifest, so they may temporarily differ during an update. To check the installed version, use the client's About page or your system's app information. Don't infer the installer version from the label on this page alone.

The client installed successfully, but webpages won't load. Should I download it again?

First check that your server configuration is valid and the system proxy or VPN is enabled. Review the logs for DNS errors, connection timeouts, and certificate issues. Troubleshoot the configuration and network path first; consider reinstalling only if the app won't launch, the file is damaged, or the package architecture is incompatible.