Choose your operating system, then confirm the processor architecture. Use v2rayN on desktop and v2rayNG on Android. Consider v2flyNG if you need the V2Fly core.
After installation, import a subscription or server configuration. New users can start with the user guide →
The primary download covers common architectures; other architectures and interface editions are listed alongside it.
The Desktop edition uses a next-generation cross-platform UI; the classic WPF edition keeps the familiar Windows interface. Both downloads are x64 archives. Extract the files, then run the installer inside.
For a first installation, try Desktop. Choose the classic WPF edition if you prefer the traditional layout. Don’t run both clients at the same time, as they may conflict over local listening ports.
| Item to check | Before you install |
|---|---|
| Operating system | Windows 10 or Windows 11 that still receives system updates is recommended. |
| Processor | This page provides x64 installers; check compatibility separately for ARM devices. |
| Runtime components | If the installer reports a missing runtime, install the required component as prompted. |
| Permissions | Standard system proxy and TUN mode have different permission requirements. Enable only what you need. |
Go to Settings > System > About and check System type. Don’t guess the architecture based on the device brand. Leave enough free space in the installation folder, and don’t launch the app from the archive preview window after extracting it.
Close any older client that’s running, then extract the downloaded files and open the installer. Choose an installation location in the setup wizard, then launch v2rayN from the Start menu. If Windows displays a security warning, check the file’s source and the warning details; don’t disable system-wide protection just to continue. If a runtime component is missing, note its name and architecture, then follow the installer’s instructions.
In the main window, open Subscription group > Subscription group settings. Enter a name and subscription URL, save, then update the current group. Seeing entries in the list means the import completed; you still need to select an available server and enable Auto configure system proxy. Menu locations may vary by edition. If yours looks different, follow the subscription import guide step by step.
Before switching from WPF to Desktop, back up your existing groups, custom routes, and other personal settings. Don’t assume both editions share the same user data. When you first launch the new interface, check that all subscriptions are present, the right server is selected, and the system proxy mode is as expected. Then close the old client and resume normal use.
Choose a DMG based on your chip. Use the Apple Silicon installer for M-series chips. If About This Mac shows an Intel processor, use the Intel installer.
Open About This Mac from the Apple menu to check your chip. The same macOS version can run on different processor architectures.
| Item to check | Before you install |
|---|---|
| macOS version | Use a macOS version that still receives updates. Check the installer’s current prompt for the minimum supported version. |
| Apple Silicon | M-series chips require the arm64 DMG. |
| Intel | Intel processors require the x64 DMG. |
| System permissions | Read and approve system permission prompts when you first use network features. |
Prefer the package that natively matches your chip; don’t assume translated execution is the default option. If the app won’t start, check the architecture, macOS version, and the specific system message.
Open the DMG and follow the on-screen instructions to move the app to Applications, then launch it from there. Don’t run it from inside the disk image long-term. Eject the disk image after installation to avoid opening an outdated copy later. If another version is installed, quit it and back up your settings before replacing it.
If macOS blocks the app on first launch, read the alert, then check the relevant entry under System Settings > Privacy & Security. Continue only if you’ve verified that the app comes from a trusted source, and use the option provided by macOS. Don’t run commands from unknown sources to change security settings in bulk, and don’t confuse system-level network permissions with your subscription account.
After importing a subscription, test browser access using the standard system proxy before trying features that require additional permissions, such as TUN. If the browser works but other apps don’t, first check whether those apps follow the system proxy settings instead of reinstalling the client. For desktop setup details, see the proxy modes chapter in the full manual.
An Android GUI client powered by the Xray core. Most mainstream phones released after 2015 should use arm64. If you’re unsure of your device’s architecture or the dedicated package isn’t suitable, try the universal version.
The universal version supports more architectures and is usually a larger download. Compatibility still depends on your Android version and the device’s app runtime environment.
For setups that specifically require the V2Fly core. Before choosing, confirm the protocol and transport used by your server. Don’t assume the two Android clients are interchangeable just because their interfaces look similar.
Check that your configuration is compatible before switching. If it relies on Xray-specific features, verify that the core supports them.
| Item to check | Recommendation | What to watch for |
|---|---|---|
| macOS version | Check the minimum requirement shown by the current APK installer. | Older Android versions may not be able to parse the installer. |
| Architecture | For most 64-bit devices, choose arm64. Check the device specifications if you’re unsure. | A mismatched architecture can cause installation to fail. |
| Installation permissions | Grant permission only to the browser or file manager you’re using for this installation. | Manage installation permissions separately for each app source. |
| Network permissions | Review the system VPN connection request the first time you connect. | Another VPN app may already be using the connection. |
When the download finishes, open the APK in your file manager and follow the system prompt to allow installation from that source. Grant permission only to the source you’re using; there’s no need to enable it for other apps. After installation, open the client and import a subscription or share link from a trusted source. When you connect for the first time, Android will show a VPN connection request. Approve it to establish the local VPN tunnel.
If the installer reports a signature mismatch, check whether the device already has the same app from another distribution channel. Don’t uninstall it just to bypass the warning; doing so may erase local settings. Back up your subscriptions and personal rules first, then decide whether to keep updating through the original channel or move to the new package. The universal version can help with some architecture issues, but it won’t resolve a signature conflict or an outdated Android version.
If the connection drops soon after you switch to another app, check whether battery management is restricting background activity, and make sure no other VPN app is running. v2rayNG and v2flyNG manage configurations and connections; they don’t provide subscription services. Choose based on how well the core matches your existing configuration. For details, see the client selection guide.
Choose deb or rpm for your distribution, then select the matching processor architecture. Most Intel and AMD desktop systems use x64; use the arm64 option below for ARM desktops.
deb and rpm are package formats, not proxy modes. Use your distribution’s software installer to handle dependencies.
| Item to check | Before you install |
|---|---|
| Desktop environment | Requires a desktop session that can run graphical applications. |
| deb package | For compatible distributions that use deb package management. |
| rpm package | The distribution must meet the package’s dependency and runtime library requirements. |
| Processor | amd64 and x86_64 refer to x64; aarch64 refers to arm64. |
The same package extension doesn’t guarantee compatibility with every distribution. If the installer reports unmet dependencies, note the missing components and system version. Don’t force the installation by ignoring dependency errors.
Open About in system settings and check your processor and distribution. Download the right package, open it with your system’s software installer, and complete the installation. The installer may request administrator authorization to write to system software directories; that’s normal. For everyday use, don’t run the entire graphical client as an administrator just for convenience.
After launch, import your configuration and check the network proxy settings in your desktop environment. Support for system proxies varies between desktop environments, and browsers, desktop apps, and terminals may not use the same proxy settings. So if the browser works but the terminal can’t connect, that doesn’t necessarily mean the server is down. First check whether the request reaches the client, then troubleshoot routing and the remote connection.
TUN mode interacts with system network interfaces and permissions, so enable it separately after verifying that the standard proxy works. Note your existing settings before making changes, and avoid letting multiple network management tools modify routes at the same time. If you only need a proxy in your usual browser, start with the basic setup; there’s no need to enable every feature during installation.
Handle installation, import, and connection testing separately to make problems easier to pinpoint.
Get a subscription URL from a trusted source, then add it to a subscription group. Subscription links may contain access credentials, so don’t post the full URL in public forums or screenshots. Save it and run an update, then check the logs for a successful result. If the list is empty, first verify the URL and update status.
See how to import a subscription →Select an available server before enabling the system proxy. The system proxy sends traffic from apps that follow system settings to the client; routing rules determine where connections go next. These are separate settings, and the tray icon alone doesn’t confirm that every app’s traffic is being routed.
System proxy vs. routing rules →Visit the target service in a browser while checking the client logs. A latency test reflects only its specific test conditions; it doesn’t guarantee that your service will work. If the request doesn’t appear in the logs, check your local proxy settings first. If it appears but returns an error, troubleshoot the configuration and server status.
See the connection testing steps →Check the installer first, then troubleshoot configuration and network settings.
For a first installation, try Desktop, which uses a next-generation cross-platform interface. If you prefer the familiar layout, choose the classic, stable WPF edition. Both require a valid configuration. Back up your settings before switching, and don’t run both editions at once, as they may compete for the same local ports.
On Windows, check System type under Settings > System > About. On macOS, check the chip under Apple menu > About This Mac. On Android, check your device specifications; most mainstream phones released after 2015 use arm64. On Linux, find the processor architecture on the About page in system settings. Always use your device’s actual specifications.
The client installer doesn’t include a usable server configuration. Get a subscription URL or share link from a trusted source, save it in the subscription group settings, and update the subscription. Select a server, enable the system proxy, then check the logs and try accessing a site.
First make sure the installer architecture matches your device, then check available storage and whether installation is allowed from the current source. If you see a signature conflict, back up your settings and check where the installed app came from—don’t uninstall it right away. If the arm64 package isn’t suitable, try the universal version.
Back up your subscription groups, routing rules, and custom settings before updating. A routine upgrade from the same source usually preserves your configuration, but changing the installation method, user directory, or app signature may change where your data is stored. After upgrading, check your subscription groups and proxy mode before resuming normal use.
The displayed version and download link may be updated separately. Treat the version shown on this page as a reference, not definitive proof of the version you’ll install. After installation, check the client’s About screen. If you need to preserve your current setup, back up your configuration and note the installed version before upgrading.