Choose v2rayN for desktop and v2rayNG for Android.
Check your operating system and architecture before importing a subscription and configuring the proxy.
CLIENT SHELF
Switch platforms to see the right downloads. The package format and processor architecture must both match. Being able to open the client doesn’t mean a subscription or proxy is configured.
A modern cross-platform UI. Recommended for first-time installations and anyone who wants a consistent desktop interface.
Download v2rayN · Desktop Windows x64 · ZIP packageKeeps the familiar, stable interface. A good fit if you’re used to the classic menus, tray controls, and settings layout.
Download v2rayN · WPF Windows x64 · ZIP package| Check | What to look for |
|---|---|
| Operating system | Use a supported version of Windows 10 or 11. Check the release notes and installer prompts for specific compatibility details. |
| Processor architecture | The Windows download on this page is x64. Go to Settings → System → About and check your system type. |
| Package format | Extract the ZIP file to a complete folder before running the installer. Don’t launch it from the compressed archive. |
| Permissions and runtime | Install any required runtime components as prompted. TUN mode may require administrator privileges. |
Before installing, exit the old client and check that it isn’t still running in the taskbar notification area. Fully extract the archive, then run the installer and follow the prompts. Don’t drag out a single program file; it may need other files in the same folder. If the interface opens but the core exits immediately, check the log panel and note the first clear error before investigating a port conflict or missing runtime.
Desktop and WPF differ mainly in their interface and layout. Switching editions isn’t a general fix for network problems. During initial setup, run only one client instance to avoid both editions changing the system proxy. After updating your subscription, select a server and use the tray menu to enable “Set system proxy automatically.” Test TUN separately if you need to route traffic from more applications.
If About This Mac shows an M-series chip, choose arm64 to match your processor.
Download v2rayN · arm64 Apple Silicon · DMG packageIf About This Mac shows an Intel processor, choose x64. Don’t use the arm64 package.
Download v2rayN · Intel x64 Intel · DMG package| Check | What to look for |
|---|---|
| macOS version | Use a supported version of macOS. Check the release package notes and installer prompts for the minimum version. |
| Chip type | Apple menu → About This Mac: choose arm64 for an M-series chip or x64 for an Intel processor. |
| Installation location | Open the DMG, move the app to Applications, then launch it from there. |
| Network permissions | Follow system prompts for system proxy and TUN permissions. After granting access, check the proxy status. |
Open About This Mac from the Apple menu to check your chip type, then download the matching DMG. Open the disk image, copy the app to Applications, and wait for the copy to finish before launching it. Running the app directly from the disk image can make it unclear which copy is in use and where updates are installed. Eject the disk image after installation.
If macOS blocks the first launch, read the specific message under System Settings → Privacy & Security. Verify the download source and app identity before deciding whether to continue. Don’t disable system-wide security to launch a single app. After opening the client, import a subscription and test a server. If your browser still isn’t using the proxy, check that the proxy address and port in Network settings match the client’s local listener.
If the connection drops after waking from sleep or switching networks, make sure the client is still running, then check the proxy and TUN status. Before quitting the client, you can clear the system proxy to avoid pointing it at a local port that’s no longer active. Menu locations may change between versions, but the setting meanings and verification steps remain the same.
Recommended for most phones released since 2015. Check which app architectures your device supports.
Download v2rayNG · arm64 arm64-v8a · APK packageChoose this if you’re unsure of your device’s architecture. It supports multiple architectures and is usually larger than a single-architecture package.
Download v2rayNG · Universal Universal · APK package
For configurations that specifically require the V2Fly core. Check that the server protocol is supported by the selected core before installing.
Download v2flyNG · arm64 arm64-v8a · APK packageChoose this to support more device architectures. Package architecture affects installation compatibility, not server configuration requirements.
Download v2flyNG · Universal Universal · APK package| Check | What to look for |
|---|---|
| macOS version | Check the minimum Android version in the installer and the release notes for your package. |
| App architecture | Choose arm64 for most devices. If you’re unsure or see an architecture mismatch, choose Universal. |
| Installation permissions | Allow “Install unknown apps” only for the browser or file manager you use to open the APK. |
| Connection permissions | Approve the system VPN prompt on first connection. Avoid running another VPN app at the same time. |
After downloading the APK, open it from your downloads list or file manager. If Android asks you to authorize the source, grant permission in that app’s settings and return to the installer. You can revoke the permission after installation. If you see “App not installed,” check for an architecture mismatch, an outdated Android version, or a signature conflict with an installed app. Don’t keep downloading the same file.
If you have subscriptions or custom rules, don’t uninstall the old app right away. Use its export or backup feature to save your configuration first, then decide whether a reinstall is necessary. v2rayNG and v2flyNG use different cores; similar names don’t mean every protocol and field is interchangeable. For VLESS or REALITY configurations, check support in the selected client’s current core. In most cases, start by testing with v2rayNG.
After installation and configuration import, the system will ask for VPN permission when you connect for the first time. This creates a local traffic forwarding tunnel; it doesn’t mean your subscription is valid. Test actual access after turning on the connection. If it often disconnects when the screen is locked, check battery optimization, background activity, and network restrictions for the client. Test again after each change so you can identify the cause.
For distributions that use deb packages. Check your system architecture and dependencies before installing.
Download v2rayN · deb x64 ARM devices: deb arm64For distributions that use rpm packages. Even within the rpm ecosystem, check runtime library compatibility.
Download v2rayN · rpm x64 ARM devices: rpm arm64| Check | What to look for |
|---|---|
| Desktop environment | This page provides a graphical client and requires a Linux environment that can run desktop applications. |
| Processor architecture | Choose x64 for x86_64 / amd64, or arm64 for aarch64 / arm64. |
| Package format | Debian and Ubuntu usually use deb; Fedora usually uses rpm. Check that the package targets your environment. |
| Dependencies and permissions | Use your system’s software installer to check dependencies. TUN also requires virtual network interface support and appropriate network permissions. |
Check your processor architecture in the system’s About or hardware information page, then confirm your distribution’s package format. Open the downloaded deb or rpm with your system’s software installer, review the dependencies, and install. Using the same package format doesn’t guarantee that a package will run on every distribution. If the installer reports a missing runtime library, check your distribution version and the package’s target environment instead of forcing the installation.
After installation, open v2rayN from the application menu. On a regular desktop, run it in your current user session rather than launching the entire app with elevated privileges to bypass a single permission prompt. Verify the local listener and system proxy before setting up TUN. Desktop environments handle system proxies differently; some apps may need to be set to use the system proxy or configured with the local address manually.
If TUN fails to start, check the logs for permission, virtual network interface, or routing errors and address the specific issue. Don’t enable TUN in multiple proxy apps at the same time. Before switching distributions or devices, back up subscription groups and custom routes separately. Don’t carry over paths, network interface names, or permissions from an old system without checking them.
CLIENT & CORE
Project V laid the foundation for the V2Ray ecosystem. V2Fly continues development of a related core, while Xray is another core in the ecosystem. Graphical clients manage configuration, run a core, and provide the interface. Support for specific protocols and transports depends on the core and version in use.
v2rayN, v2rayNG, and v2flyNG are free, open-source clients. Use v2rayN on desktop and, in most cases, v2rayNG with its Xray core on Android. Consider v2flyNG if you specifically need the V2Fly core. Downloading a client doesn’t provide a server; you’ll need a subscription separately.
If a protocol field isn’t recognized, don’t switch packages at random. Check the share link type, core support, and log errors before deciding whether to update the client. For help choosing, see the comparison of the three clients; for setup across platforms, see the complete installation guide.
AFTER INSTALLATION
First establish a connection you can test, then adjust routing and traffic handling. Change one type of setting at a time so it’s easier to troubleshoot and roll back.
STEP 01
On desktop, open “Subscription Group Settings,” create a group, and enter the subscription URL. Example format: https://example.com/sub?token=xxxx. Save it and update the subscription. If you haven’t set up a proxy yet, try “Update subscription (without proxy).” If the service requires a specific network, follow its instructions for choosing an update method.
On Android, choose the subscription option in the Add menu or import from the clipboard. A subscription URL and a single share link are different types of content; use the matching option. After updating, check that servers appear in the list. If it’s empty, check the update result before changing the system proxy.
STEP 02
Select a server from the list and check its address, port, protocol, and transport settings. Imported subscriptions usually provide these fields, so there’s no need to guess. For manual setup, match each field to the server details, especially TLS, SNI, and REALITY settings.
A latency test reflects only the conditions under which it was run and doesn’t replace a real access test. If it fails, distinguish DNS errors, connection timeouts, and handshake errors, then use the logs to investigate. Don’t share screenshots containing subscription URLs, identity fields, or a complete configuration.
STEP 03
On desktop, first use the system proxy to test browser access. Make sure its port matches the client’s local listening port and no other program is changing the proxy. On Android, approve the system VPN prompt and check the connection status in the app.
The system proxy doesn’t automatically cover every app. If an app still connects directly, check whether it uses the system proxy before deciding whether to enable TUN. TUN requires permissions, a virtual network interface, DNS, and routing; don’t enable it before confirming a basic connection works.
STEP 04
Choose a routing mode that fits your needs, such as “Bypass mainland China,” then check that apps requiring direct access and those requiring a proxy behave as expected. Routing rules control traffic flow; they won’t fix a server that’s no longer working. Save your current working configuration before editing custom rules.
When setup is complete, test web access, commonly used apps, network switching, and connectivity after exiting the client. Before upgrading, note your local port, subscription groups, and rule sources. For step-by-step instructions, read the subscription import and connection guide.
DOWNLOAD FAQ
For a first installation, choose Desktop for its modern cross-platform interface. If you prefer the familiar classic interface and workflow, choose the stable WPF edition. Both are v2rayN. When trying either edition for the first time, import your subscription and verify the system proxy before migrating other settings.
For most phones released since 2015, arm64 is usually the best choice, but check which app architectures your device supports. If you’re unsure or the arm64 package is reported as incompatible, choose Universal. It supports more architectures and is usually larger. Switching package architectures won’t fix subscription or connection issues.
The client reads configuration and forwards traffic; the installer does not include a usable server. Prepare a subscription URL, share link, or configuration file that you manage or have obtained legally, then add it through the subscription group or import menu. Subscription URLs contain access credentials, so don’t publish them or include them in support screenshots.
First check your operating system, processor architecture, and package format, then read the system message. Fully extract ZIP files on Windows; choose the right package for Apple Silicon or Intel on macOS; check installation permissions and signature conflicts on Android; and review package manager dependency and distribution compatibility messages on Linux.
Before updating, use the client’s backup or export feature and note your subscription groups, routing mode, and local listening port. Exit the old client, then install a package compatible with your system. After updating, confirm your configuration is still there, refresh subscriptions, and test the connection. When switching interface editions, don’t overwrite incompatible configuration files.