Client installers / platforms and architectures
Choose your operating system, then check your device architecture. Use v2rayN on desktop and v2rayNG on Android.
Installers are grouped by platform. Your position on the page is preserved when you switch platforms, so you can return directly next time.
One client, two interfaces. Both downloads below are x64 installers.
Windows · x64 7.24.1
Desktop uses a newer cross-platform UI. The classic WPF edition retains the traditional layout and workflow. For a first install, start with Desktop; choose WPF if you’re used to the classic interface.
After downloading the ZIP archive, extract all its contents before running the installer. Don’t launch it from the archive preview window.
Quit any old client that’s running, including its system tray process, before extracting the download. If the installer needs to write to a system location, approve the permission prompt. You don’t need to run the client as an administrator all the time just to import a subscription. If a security warning appears, verify the program and download source instead of disabling system protection.
Menus may be in different places in Desktop and WPF, but subscription groups, subscription updates, and the system proxy remain key parts of initial setup. Save your existing configuration before switching interfaces, then check routing, custom DNS, and local listening settings during migration. Don’t run both interface versions at once or let them compete for the same ports, and don’t let two clients take turns changing the system proxy.
Opening the main window doesn’t mean you’re connected. Add a subscription group and update it, then confirm that configurations appear in the list and select one. Set the system proxy and routing mode, then test access in a browser. If the log reports a port conflict, check for another client process still running before considering a reinstall.
Check your chip in About This Mac, then choose Apple Silicon or Intel.
macOS · DMG 7.24.1
If About This Mac shows an Apple chip, choose Apple Silicon (arm64). If it shows an Intel processor, choose Intel (x64). Don’t use the year you bought the Mac as a substitute for checking its chip.
Open the DMG, copy the app to Applications, then launch it. Quit the old process before updating so you don’t keep using a temporary copy from the disk image.
Open the downloaded disk image and copy the app to Applications. Once copied, you can eject the disk image and launch the app from Applications. This avoids updating one copy while continuing to run another. If the app is already installed, quit the old process from the menu bar before responding to any replacement prompt.
If macOS shows a security warning the first time you open the app, read the full message and confirm the file’s source before using the available option under System Settings → Privacy & Security. Button names and locations can vary by macOS version. Not every launch failure is a permissions issue: check for an architecture mismatch, an unsupported macOS version, or an incomplete app copy as well.
After installation, import a subscription and select a configuration before deciding whether to let the client manage the system proxy. The system proxy only affects apps that follow the relevant system settings; it doesn’t route all traffic the same way. If other apps can’t connect after you quit the client, check for leftover proxy settings in Network settings and restore them as needed.
Choose v2rayNG first. Consider v2flyNG if you need to use an existing V2Fly configuration.
Android · Xray core 2.2.6
Use it to import a subscription, choose a configuration, and connect through a proxy on your phone. Most phones released since 2015 will typically use arm64; choose Universal if you’re unsure which app architecture your device supports.
The version shown on the page may not match the installer filename because updates can take time to appear. The manifest lists version 2.2.6, while the current download filename is marked 2.3.11. Check the installed version in the client.
Android · V2Fly core 1.10.31
For users who need to keep using V2Fly core configurations. Before choosing, check the protocols and transport settings in your subscription; don’t assume v2flyNG and v2rayNG support identical features or configuration fields.
Before switching clients, keep your subscription URL and note your per-app proxy and DNS settings separately. These settings may not migrate with the subscription.
| Item | What to check |
|---|---|
| arm64 | For devices that support arm64-v8a apps. The processor’s marketing name alone isn’t enough to confirm compatibility. |
| Universal edition | Includes multiple architectures, making it a good choice if you’re unsure which one your device supports. Android must still meet the app’s system requirements. |
| Install permission | If prompted, allow the browser or file manager you’re using to open the APK to install apps. |
| Connection permission | Read and approve the system VPN connection request when you connect for the first time. |
After downloading the APK, open it from your browser’s downloads or a file manager. If prompted, grant install permission to the app opening the file—not to every app on the device. You can revoke this permission after installation. If Android says the package can’t be parsed, check that the download is complete, the architecture matches, and your system version meets the package requirements.
The first time you connect, Android will ask to create a VPN connection. This is how the client routes traffic; it doesn’t mean you need to buy an additional system feature. If another app using the same system VPN connection is active, disconnect it before starting this client. Importing a subscription and approving a connection are separate steps; completing one won’t complete the other.
If the connection drops when your phone’s screen turns off, check background activity and battery restrictions next. Don’t start by disabling every battery-saving feature. Menu names vary by device; try allowing the client to run in the background as needed, then see if that helps. Adjust per-app proxy, routing, and DNS settings one at a time so you can identify the cause of any change.
Check whether your distribution uses deb or rpm packages, then confirm whether your system is x64 or arm64.
Linux · graphical desktop 7.24.1
Debian- and Ubuntu-based distributions typically use deb; distributions in the RPM ecosystem use rpm. The primary downloads below are for x64. Use the corresponding links below for arm64 devices.
Installer for arm64 devices
Open the package with your distribution’s software installer. Matching package formats don’t guarantee that every version of every distribution includes the required dependencies.
Open the correct package in your file manager and let the system software installer handle it. If the system opens an archive tool instead, choose the software installer from the file’s Open With menu. Installation may require permission to write to the system application directory. Run the client as a regular desktop user so that configuration files don’t become writable only by an administrator.
The distribution build tag in an RPM filename must be checked against your system; “supports rpm” alone doesn’t guarantee compatibility. If the installer reports missing dependencies or an outdated runtime library, check your distribution’s package documentation first. Don’t force the app to run by replacing core system libraries. Apply the same approach to deb packages: check system requirements before installing.
After opening the client for the first time, import a subscription and select a configuration, then check your desktop environment’s network proxy settings. Proxy behavior varies between desktop environments, and some apps have their own proxy settings. If a browser works but other apps don’t, check whether those apps follow the system proxy instead of assuming the installer is at fault.
The installer deploys the client. You still need to configure a subscription and proxy mode, then verify the connection in the client.
If you already use a client, note your subscription groups, update method, routing mode, and custom DNS settings. Use the client’s backup or export feature if available. Subscriptions usually contain server configuration, not every local setting, so copying the subscription URL alone isn’t a complete migration.
Quit the old client before updating to avoid locked files or background processes still running the previous version. After updating, check that your configuration is still there, then test the connection. Don’t delete the original configuration folder until you’ve confirmed the migration worked. Don’t upload a full backup to a public location.
v2rayN, v2rayNG, and v2flyNG are tools for reading configuration. Downloading a client doesn’t create a subscription or usable configuration. Once you have a valid subscription URL, save it in a subscription group and update it. Only after the update provides configurations and you select one can you proceed to connect.
If a subscription update fails, check that the URL is complete and hasn’t expired, and that your current update method can reach the subscription source. Installers and subscription URLs serve different purposes; don’t paste an installer download link into the subscription URL field.
Import subscription → Update groups → Select a configuration → Set proxy mode → Verify access.
To determine whether a configuration will work, consider both the client interface and its core capabilities—not just the software name.
Project V is an important starting point in the open-source proxy ecosystem. V2Fly and Xray represent different core development paths within it. Graphical clients bring subscription management, configuration selection, and proxy settings together in one interface, but actual connection support depends on the core in use and the protocols it supports.
v2rayN manages configuration on desktop. On Android, v2rayNG uses the Xray core, while v2flyNG uses the V2Fly core. They’re open source, but their menus, configuration fields, and supported features aren’t necessarily identical. Choose an installer based on your OS and architecture, then choose a configuration based on its protocol and core.
If a client can read a subscription format, that only confirms it can parse the data. The current core must also support the protocols, transport methods, security layers, and extra parameters in each configuration, and these must match the server. When switching between core families, don’t blindly try to make a configuration work by deleting fields you don’t recognize.
If a configuration type isn’t supported, first check the subscription documentation and the client’s core settings, then decide whether to update or switch configurations. For details on VMess, VLESS, Trojan, Shadowsocks, and REALITY, see the protocol reference; you don’t need to look for a separate core download.
Read about protocols and choosing a core →Check the installer first, then troubleshoot configuration. Expand a question below for answers.
For a first install, try Desktop, which uses a newer cross-platform interface. The classic WPF edition keeps the traditional Windows interface and may suit users who prefer its familiar layout. Both require you to import a valid subscription. Back up your settings before switching, and don’t let both clients control the system proxy at the same time.
Most phones released since 2015 will typically use arm64, but check which app architectures your device supports. Universal includes multiple architectures and is worth trying if you’re unsure or the arm64 package isn’t compatible. Universal does not mean faster connections, and it doesn’t bypass Android version requirements.
No. The client reads and uses configuration; you’ll need to obtain a subscription URL separately. After installation, save the URL in the subscription group settings and update the subscription. A completed download or a successful launch doesn’t mean your connection is ready to use.
The version label and installer link come from separate manifest fields, so they may not update at the same time. First confirm that the download is for the right client, OS, and architecture, then check the actual installer and the version shown in the client. Don’t assume a package is from the same release as your existing installation based only on the page’s version label.
Follow the installer and in-app update instructions for your current version; don’t delete existing data without checking first. Quit the client and back up subscription groups, routing rules, and custom settings before updating. If switching interface types or core families, check configuration compatibility before deciding whether to migrate.
Make sure the subscription has updated, a usable configuration is available, and one is selected. On desktop, check that the system proxy is enabled. On Android, check that you approved the VPN connection request. Then review the routing mode, system clock, and client logs instead of repeatedly reinstalling to troubleshoot.