Choose your operating system, then check your CPU architecture. Use v2rayN on desktop; v2rayNG is the recommended Android client, with v2flyNG as an alternative.
7.24.1
Choose Desktop for the newer cross-platform UI, or classic WPF to keep the familiar Windows interface.
Both downloads are ZIP archives. Extract the entire archive before running the installer; don't launch it from the archive preview.
If you're new to v2rayN, start with Desktop. Its cross-platform interface makes it easier to keep a similar workflow across desktop systems. Choose WPF if you're familiar with the classic menus and want to stick with your existing workflow. The choice is about the interface and runtime, not different servers bundled with either installer.
After installation, open the main window and confirm the client starts normally before adding a subscription group. If Windows reports a missing runtime component, follow the installer's specific instructions; a startup failure doesn't necessarily mean the subscription URL is at fault. Export or back up your configuration before switching versions. Don't assume both builds automatically share all settings.
7.24.1
Open the Apple menu and choose About This Mac. Select the DMG that matches the entry under Chip or Processor.
Choose Apple Silicon for an Apple M-series chip and Intel for an Intel processor. Both installers are DMG files.
Open the downloaded DMG, drag v2rayN to Applications, then launch it from there. Don't run it from the disk image long-term, as shortcuts may stop working once the image is ejected. Before updating, quit the client and then replace the app to avoid a warning that it's still in use.
If macOS blocks the app on first launch, check the app name in the alert, then look in System Settings → Privacy & Security for an option to open it anyway. The button location varies by macOS version. If macOS says the app is damaged or incompatible with your architecture, recheck your Mac's chip and the downloaded file. Don't disable macOS security protections.
Open the main window before importing a subscription. The tray option “Set system proxy automatically” configures apps that follow the system proxy settings; TUN may require additional permissions. A successful installation, selecting a server, and enabling the proxy are three separate steps—check each one.
2.2.6
Uses the Xray core. Most mainstream phones released since 2015 can start with arm64, but check which app architectures your device supports.
Try the universal version if you don't know your device's architecture or the arm64 installer reports incompatibility. It still requires a compatible Android version and the necessary installation permissions.
1.10.31
Uses the v2fly core. Choose it if you need to stay within the V2Fly configuration ecosystem, and first check that your existing protocols and transport options are supported.
These Android clients manage configurations separately. Save your subscription and any important settings before switching; don't assume your configuration will migrate automatically.
After downloading the APK, open it in your system file manager. If Android asks whether the current browser or file manager can install apps, grant permission only to the source you're using. You can revoke it after installation. If you see “App not installed,” note the full message and check the architecture, available storage, Android version, and signature compatibility with any existing installation.
The first time you connect, Android will usually show a VPN permission dialog. Make sure the request comes from the client you just installed before continuing. Multiple apps using the VPN connection at the same time can conflict, so leave only one running while troubleshooting. If the connection drops when the screen locks, check battery optimization and background activity settings; there's no need to change every battery-saving option upfront.
7.24.1
Choose deb or rpm for your distribution, then check whether your system uses x64 or arm64. The main downloads below are for x64 desktop systems.
Choose deb for Debian, Ubuntu, and similar distributions; choose rpm for Fedora, RHEL, and related distributions. Check package-format and distribution compatibility separately.
After downloading the package, open it with your distribution's software installer and review the dependency and permission prompts. Launch the graphical interface once the client appears in your desktop menu. If the installer reports unmet dependencies, check your distribution version, package architecture, and system library requirements. Don't force the installation by ignoring dependencies.
Whether Linux apps follow the system proxy depends on the desktop environment and the apps themselves. After enabling “Set system proxy automatically,” check browsers and terminal apps separately, as they may behave differently. If you need TUN, review the permissions and network interface requirements first. On managed devices, follow your organization's access policies.
When upgrading, stick with the same package format and architecture to avoid mixing packages from different distribution branches. If you change desktop environments or user accounts, check access to the configuration directory again. First confirm that the main window works and settings can be saved; then troubleshoot subscriptions and connectivity.
The installer sets up the app; subscriptions, servers, and traffic routing require additional configuration.
Before upgrading, note which client you're using, your subscription groups, and your routing mode. Prefer the client's backup or export feature; save any manually edited rules separately. Backups may contain server addresses and connection credentials. Don't store them in a publicly shared folder or include a full subscription URL in screenshots or support requests.
If the old version still works, back up your configuration before installing the update. After updating, check that your subscription list is complete, the correct server is selected, and local ports haven't changed. Don't delete the old configuration just because the app starts successfully.
Prepare a subscription URL you're authorized to use. In v2rayN, open Subscription Group Settings, add a name and URL, save, then update the subscription. On Android, use the subscription settings in your chosen client. A subscription URL is a configuration source, not a regular webpage to keep opening in a browser.
After the update completes, select a server and make sure the current core supports its protocol and transport options. If the update fails, check that the URL is complete and hasn't expired, and review the network path used for the update. Reinstalling the client repeatedly usually won't fix an expired subscription URL.
Follow the steps to import a subscription →Selecting a server determines which configuration handles traffic; it doesn't mean your apps are already using the proxy. On desktop, start with “Set system proxy automatically” so apps that follow the system proxy settings use the client's local proxy. “Do not change system proxy” preserves the existing system settings; it does not enable the proxy.
TUN routes traffic through a virtual network interface. It's useful for apps that don't follow system proxy settings, but requires extra attention to permissions, routing, and DNS. Test one traffic-routing method first, then add settings only as needed. When troubleshooting, change one option at a time to identify what affects the result.
View system proxy settings →First confirm the main window is running, then check that the subscription updated and a server is selected. Finally, test a website in the app you need to use. A latency test is only one part of connection diagnostics; it doesn't predict how websites, video, or downloads will perform. Test each app you actually use.
If your browser still can't connect after you exit the client, check whether the system proxy is still pointing to a local port that is no longer active. Before turning off the proxy, clear the system proxy settings and disable TUN, then exit the client. If you encounter a port conflict or DNS issue, note the exact message and troubleshoot it step by step. Don't run multiple clients and keep switching between them.
View configuration troubleshooting →The version shown on each client card identifies its current release; the downloaded filename may use a different release label. Don't assume two clients are from the same release series just because their filenames contain similar version numbers. v2rayN, v2rayNG, and v2flyNG have separate release cycles, so their version numbers don't indicate relative feature sets or connection quality.
Downloads on this page are listed by operating system and architecture; there isn't one minimum OS version that applies to every release. OS version, desktop environment, runtime components, and app architecture can all affect installation. If your device is managed by an employer or school, make sure this type of network tool is allowed before installing it or granting permissions.
v2rayN, v2rayNG, and v2flyNG are graphical clients. Xray and V2Fly are related core families that handle protocols and transport. Choose a client based on your operating system, then check core compatibility with your existing configuration. Installing a client doesn't provide a server or create a working subscription.
Choose the right installer before configuring your connection.
Open the Apple menu and choose About This Mac. If Chip shows an Apple M-series chip, choose Apple Silicon. If Processor shows Intel, choose Intel. Match the installer to your Mac's hardware, not your browser or subscription type.
Desktop uses a newer cross-platform interface, making it a good choice for first-time installs and users who want a consistent experience across desktop systems. The classic WPF version retains the familiar Windows interface for users who prefer their existing workflow. Both downloads are x64 packages. Back up your configuration before switching.
Most mainstream phones released since 2015 can start with arm64, but check which app architectures your device supports. The universal version includes multiple architectures and can help if your device's architecture is unclear or the arm64 installer reports incompatibility. The Android version and installation permissions must still meet the requirements.
The client manages configuration and starts the proxy; the installer does not include a working server. You'll need a subscription URL or server configuration that you are authorized to use. Import it, select a server, then configure the system proxy or enable TUN if needed.
Exit the client first, then use its backup or export feature to save your configuration. Note your subscription groups, custom routing rules, and local listening ports. Backups may contain connection credentials, so keep them somewhere you control. After updating, verify your subscriptions, servers, and proxy status before deleting old files.
Use deb packages on Debian, Ubuntu, and similar distributions; use rpm packages on Fedora, RHEL, and related distributions. Then choose x64 or arm64 to match your system. The same package format does not guarantee compatibility with every distribution; check dependency and system library requirements before installing.