Client & package selection
Choose your operating system, then your architecture. Use v2rayN on desktop, v2rayNG on Android, or v2flyNG as an alternative with a different core.
One client, two interfaces. Both downloads below are for x64 systems.
Desktop uses a newer cross-platform UI, ideal for first-time users and anyone who wants a consistent experience across desktop operating systems. WPF is the classic, stable edition with the familiar Windows interface. Install either one; you don't need both to use different protocols.
| Check | Selection and requirements |
|---|---|
| System architecture | The Windows packages on this page are for x64. Check Settings → System → About under System type. An x64 package is not a native arm64 build. |
| Windows version | Use a Windows version that still receives security updates. Follow the installer prompts for specific OS and runtime requirements. |
| Folder and permissions | Extract to a writable folder, not a restricted location. Standard system proxy and TUN features have different permission requirements; grant only the permissions needed for the feature you use. |
Quit any running proxy client before installing to avoid conflicts over listening ports or system proxy settings. After installing v2rayN, open Subscription Group Settings, create a group, enter your subscription URL, then select Update Subscription. To import a single share link, use the server import option from the clipboard. Don't paste a full configuration JSON where a subscription URL is expected.
For your first connection, start with the system proxy. Select a server and check the logs to confirm it starts normally. Common local SOCKS and HTTP ports in some versions are 10808 and 10809, but use the values shown in your settings. Configure TUN only if an app doesn't follow the system proxy and you need to route its traffic. Back up your settings before switching between Desktop and WPF, and don't let both editions write to the same configuration.
Open About This Mac and choose the DMG that matches your chip.
Choose arm64 for Apple silicon and x64 for Intel Macs. Check the chip or processor listed in About This Mac—not when you bought the computer or which browser you're using. v2rayN uses its cross-platform desktop interface on macOS.
| Check | Selection and requirements |
|---|---|
| Apple Silicon | If About This Mac shows an Apple chip, choose the arm64 DMG for the matching architecture. |
| Intel | If About This Mac shows an Intel processor, choose the x64 DMG. An arm64 app isn't a substitute. |
| System and permissions | Use a macOS version that still receives security updates and check the app's minimum OS requirement. macOS may ask you to confirm a security prompt the first time you open the app. |
Don't run the app from the mounted disk image. Copy it first, eject the image, then launch v2rayN from Applications. If macOS blocks it, confirm you trust the download source, then follow the prompt in System Settings → Privacy & Security. Don't disable macOS security entirely just to skip this step.
Import a subscription and update the server list before enabling the system proxy. Then test your browser connection. The system proxy doesn't cover every terminal app; command-line tools may need their own proxy settings. TUN requires permissions and routing changes, so first verify that the standard proxy works, then follow the documentation to configure TUN. Quit the old app before updating and keep a recoverable backup of your settings.
macOS setup guide →Recommended: v2rayNG. Alternative: v2flyNG. Choose one; you don't need to connect both.
For everyday Android use, start with v2rayNG. Most mainstream phones released since 2015 use arm64; if you're unsure of the system architecture, choose the universal build. Supported protocols and transports depend on the subscription configuration and bundled core. Installing a client won't fill in missing server settings.
Choose v2flyNG if you need a configuration from the v2fly core ecosystem. It's a standalone Android client, not an add-on for v2rayNG. The two apps may not support exactly the same configuration fields. Check compatibility before importing links that rely on specific core features.
| Check | Selection and requirements |
|---|---|
| arm64 | For ARM devices that support 64-bit apps. Most newer mainstream phones qualify, but device age alone doesn't confirm system architecture. |
| Universal build | Consider this option if you're unsure of your architecture. A universal package doesn't bypass the app's minimum Android version requirement. |
| Installation and connection | Temporarily allow the browser or file manager you're using to install apps. When connecting, grant VPN permission when prompted by Android. |
After downloading the APK, open it from Downloads or your file manager. If installation fails, check the specific error: architecture mismatch, an outdated Android version, insufficient storage and a signature conflict each require a different fix. Don't uninstall the old app as a first step. Export any settings you need and check whether an update from the same source will work, so you don't lose subscriptions or routing rules.
After installing, add your subscription URL under Subscription Settings, save it, return to the main screen and update the list. Then select a server and connect. Android will ask for VPN permission the first time. This lets the app create a local interface to route traffic; it doesn't confirm that the remote connection works. If the connection drops when the screen locks, check battery optimization and background activity restrictions. Change settings only for apps that need it.
Android setup guide →Choose a package format for your distribution, then check whether you need x64 or arm64.
Choose deb for Debian, Ubuntu and other distributions using the deb package system. Choose rpm for distributions using the RPM package system, and check that your distribution and dependencies are compatible. The primary downloads below are x64; use the arm64 links for ARM desktops. A graphical desktop session is required.
| Check | Selection and requirements |
|---|---|
| Package system | deb and rpm packages aren't interchangeable by changing the file extension. Open each package with your system's software installer. |
| Runtime dependencies | Your distribution must meet the package's declared dependencies, system library requirements and desktop runtime requirements. If dependencies are missing, check the installer's details first. |
| Proxy and permissions | Whether apps use the desktop system proxy depends on each app. TUN also requires network interface, routing and permission setup. |
Check your architecture and distribution in system information, then use the graphical software installer to install the package and handle dependencies. If the installer reports that a system library is too old, don't force past the dependency check or mix in core libraries from another distribution. Sharing a package format means distributions use the same type of package manager; it doesn't guarantee that every build runs on every distribution.
After starting v2rayN, import a subscription, choose a server, and confirm the core and local listener are running before setting a proxy. Browsers, terminal tools and desktop apps may handle proxies differently. If an app bypasses the proxy, check its own network settings first. To route more apps through TUN, follow the documentation and configure permissions as needed. Avoid running your entire desktop session with elevated privileges.
Linux setup guide →AFTER / INSTALL
Separate installation issues from connection issues. Opening the client only confirms that the app started; subscriptions, server settings and traffic routing still need to be checked.
Quick start guideAll three clients manage proxy settings; the package itself doesn't provide a connection service. First prepare a subscription URL, individual share link or full configuration file that you're authorized to use, and choose the matching import option. Subscription URLs usually go in subscription settings; share links can be imported from the clipboard or scanned; full JSON files need the appropriate configuration import option. Re-downloading the client won't fix an import format mismatch.
Subscription links may contain access credentials. When asking for help, share the error type, menu path and relevant log lines—not the full URL in a public forum. After importing, update the list. If it's empty, check that the URL is complete, the group isn't filtered out and the client can reach the subscription service.
Select the server you intend to use and check the logs for configuration parsing or port conflicts. On desktop, start by setting the system proxy; on Android, confirm the connection and grant VPN permission. The system proxy works for apps that follow system settings. TUN is a separate way to route traffic. Don't keep switching between them before you understand what each does.
Test both the target app's connection and whether local network access, DNS resolution and routing behave as expected. Rules may send some requests directly; that isn't necessarily a problem. Configure routing rules only when you need more control, and back up your working settings first. Don't mistake a routing issue for an installation package problem.
Quit the client before replacing files or installing an update to avoid file access conflicts. Back up subscription groups, routing rules and custom settings first, especially when switching editions, installation sources or devices. If Android reports a signature conflict, check where the old app came from and how to export its data. Uninstalling may also delete local settings.
The client UI version and core version are different things. Xray and V2Fly are both part of the Project V ecosystem, but their protocols, transports and configuration fields don't always match. Reusing advanced settings just because the clients have similar names can prevent startup. Choose the right platform when downloading, then match your configuration to the supported protocol. See the concept reference for details.
DOWNLOAD / FAQ
Check the package type first, then troubleshoot system permissions, configuration imports or proxy routing.