CLIENT SHELF / DOWNLOAD
Choose by operating system and architectureFor desktop, choose v2rayN; for Android, start with v2rayNG. Check your processor architecture, then download the matching package.
v2rayN / x64 / ZIP
The Desktop edition uses a newer cross-platform UI. The classic WPF edition retains the familiar Windows interface and is a stable choice for users who prefer traditional workflows. Both let you manage server settings, subscription groups, and routing; choose the interface you prefer.
| Item | What to check | Recommended action |
|---|---|---|
| Processor | This page provides x64 installers | Check System type under Settings → System → About. Don't rely on the device name alone. |
| Operating system and runtime | Check the requirements for the current release | Install system updates first. If a runtime component is missing at startup, install the component specified in the error message. |
| Install location | A local folder you can write to | Extract the entire archive before running the app. Do not launch it from the archive preview window. |
| Permissions | Handle standard settings separately from traffic capture | Test the basic proxy first. Elevate permissions for TUN or service-related actions only when the client asks. |
Once the download is complete, extract the archive to a permanent folder and check for the installer or launch file inside. An archive format does not necessarily mean the app is portable; follow the instructions for the files in the package. On first launch, create a subscription group, paste your link, update the subscription, then select a server. Do not keep switching system proxy settings before importing a configuration—you do not yet have a working outbound setup.
When upgrading from an older version, quit the client from the system tray and back up your settings first. Desktop and WPF may handle their interfaces and data differently, so use the client's export and import features when migrating. Once the system proxy is enabled, typically only apps that honor system proxy settings will use it. For traffic from other apps, see the Windows setup and configuration guide.
v2rayN / ARM64 · X64 / DMG
Open About This Mac from the Apple menu. If it lists an Apple M-series chip, choose Apple Silicon; if it lists an Intel processor, choose the Intel package. Use the information shown on your device rather than guessing based on its purchase year.
| Item | What to check | Recommended action |
|---|---|---|
| Processor architecture | Apple Silicon or Intel | Check the Chip or Processor field in About This Mac. |
| Operating system version | Check the minimum requirement for the current release | If macOS says the app is incompatible, check your system version and package architecture first. |
| Install location | Applications folder | Open the DMG and follow the instructions in the window. Launch the app from your Applications folder. |
| Network permissions | Grant permissions for the features you use | System proxy and TUN have different permission requirements. Review each system prompt carefully. |
Open the downloaded disk image and move the app to your Applications folder, then launch it from there. Avoid running it long-term from a mounted disk image; updates, path access, and saving settings may not work as expected. If system security settings block the first launch, verify the download source and review the relevant notice under Privacy & Security. Do not disable security protections system-wide just to launch one app.
After importing a subscription, select a server and check the client logs before enabling the proxy mode you need. If you switch Wi-Fi networks, dock adapters, or wired connections, you may need to check your system proxy settings again. Before quitting, clear the system proxy settings configured by the client to prevent your browser from sending requests to a local port that is no longer listening. See the macOS setup and configuration guide for details.
v2rayNG · v2flyNG / APK
An Android GUI client with subscription import, server selection, and routing options. Most mainstream phones released after 2015 are best served by arm64. If you are unsure of your device's architecture or the installer reports an incompatibility, consider the universal version.
For users whose existing configurations depend on v2fly core behavior. Before choosing, check that the protocols and transport features your configuration needs are supported. Do not assume a configuration can be migrated based on the client name alone.
| Item | What to check | Recommended action |
|---|---|---|
| App architecture | arm64 or universal | A 64-bit processor does not necessarily mean the system can run 64-bit apps. Check your system's support as well. |
| Operating system version | Minimum version specified by the installer | If the installer reports an incompatible version, check your Android version instead of repeatedly installing the same file. |
| Install permissions | Allow app installs from this source | Grant this permission temporarily to the browser or file manager you are using. |
| Service permissions | System VPN approval and background activity | Grant permission when prompted on first connection. If the connection keeps dropping, check battery optimization and background restrictions. |
After saving the APK, open it from your browser's download history or a file manager. If prompted to allow installs from this source, grant permission to the current source only; you can revoke it afterward. An installation failure is not always an architecture issue. It may also be caused by insufficient storage, an outdated Android version, or a signature mismatch with the installed app. Read the installer's message before deciding what to try next.
After first launch, add a subscription, update it, and select a server. When you start the proxy service, Android displays a VPN permission dialog. This is system approval for the client to handle traffic; it does not mean the installer includes a remote server. If another VPN service is running, stop it before testing. If the connection drops frequently when the screen locks, check background activity, battery optimization, and your device manufacturer's power-saving settings. See the Android setup and configuration guide.
v2rayN / DEB · RPM
Debian- and Ubuntu-based distributions typically use deb packages; distributions such as Fedora and openSUSE that use RPM package management typically use rpm packages. The same package format does not guarantee identical dependencies, so meet all system library requirements reported by the installer.
| Item | What to check | Recommended action |
|---|---|---|
| System architecture | x64 or ARM64 | Check your system information: amd64 and x86_64 correspond to x64; aarch64 usually corresponds to ARM64. |
| Package format | deb or rpm | Choose your distribution's native package format. Use the installer's dependency check to confirm compatibility. |
| Runtime environment | A supported graphical desktop and system libraries | Check dependencies with your software installer and resolve any missing ones before launching the app. |
| Proxy permissions | Desktop proxy settings or TUN | GNOME, KDE, and individual apps handle system proxy settings differently. Test them separately. |
Download a package that matches your distribution and architecture, then open it with your system's software installer so it can check dependencies. If system libraries are too old, do not force the installation by ignoring dependencies. First confirm that your distribution meets the package requirements. After installation, launch v2rayN from the app menu and manage subscriptions and settings as a regular user.
Not all Linux desktop apps honor system proxy settings. Browsers, desktop apps, and terminal programs may each use a different proxy source, so seeing the client running does not mean all app traffic is being routed through it. Start by testing an app known to honor proxy settings, then configure environment variables or TUN permissions as needed. Set up launch at startup only after you have verified a manual connection; this makes startup issues easier to diagnose. See the Linux setup and configuration guide.
INSTALL → IMPORT → VERIFY
Handle installation, configuration, and connection testing separately. Change one type of setting at a time to make log errors easier to track down.
01 / INSTALL
Check your operating system, architecture, disk space, and folder permissions. Once the app opens, confirm that it can save settings before importing a subscription. If startup fails, resolve the runtime issue first; repeatedly changing subscriptions will not help diagnose the app itself.
02 / IMPORT
Add a subscription link you are authorized to use to a group, update it, then check the server list. Subscription URLs may contain access credentials; do not share screenshots or forward them. If the list is empty, check the update logs and URL format first, then confirm the subscription is still valid.
03 / VERIFY
Select a server and start the service. Check the logs for configuration errors before enabling the mode you need. Test one app first, then check routing and DNS. When troubleshooting, record what happened and any error messages; avoid changing the server, proxy mode, and DNS settings all at once.
DOWNLOAD / FAQ
Desktop uses a newer cross-platform interface and suits users who want a consistent experience across desktop platforms. WPF is the classic, stable edition for users familiar with the traditional Windows interface. Both options here are x64 packages; check your system type before installing.
Most mainstream phones released after 2015 are best served by arm64, but check which app architectures your device supports. Choose the universal version if you are unsure of your device's architecture or the arm64 installer reports an incompatibility. Universal packages generally include more architectures and may be larger.
The installer provides the client app, not a subscription or server. Obtain a subscription link or server configuration you are authorized to use, import it, update the subscription, then select a server and check the logs.
Use the client's export or backup feature to save your configuration first. Note your subscription groups, routing rules, custom DNS settings, and listening ports, then quit the client. Do not assume data directories are interchangeable between interface versions or different clients.
Check your browser's download history, available disk space, and save permissions, then retry the same installer link. A static download link remains available if the page script cannot load the version list. If the issue persists, note when it happened, your platform, package format, and the browser message before checking your network or download settings.
Import a subscription and verify a basic connection first, then choose system proxy or TUN based on your needs. Desktop TUN may require elevated permissions; Android requests system VPN approval when the proxy service starts for the first time. Before switching modes, pause other network tools that might capture the same traffic.