Explore three open-source clients, four platform downloads, and English setup documentation in one place. Choose a client for your device first, then import a subscription and configure system proxy and routing.
Browse guidance by task stage. Choose a topic on the left to see its scope, recommended sequence, and relevant documentation on the right.
For desktop devices, start with v2rayN. On Windows, choose between the modern desktop edition and the classic edition; on macOS, select an installer for your processor architecture; on Linux, use the entry matching your distribution’s package format. On Android, v2rayNG is the primary choice and uses the Xray core; choose v2flyNG when you need the V2Fly core. Keeping the operating system, client, and core separate helps prevent downloading the wrong file based on similar names. The download center also explains how to identify your architecture and what is required before installation, making it useful for first-time installs and device changes.
Platform links take you to the appropriate download panel rather than distributing files directly from the homepage. On the download page, review system requirements, installer differences, and processor details. This helps avoid choosing a desktop file on a mobile device or the wrong architecture on a desktop.
CLIENTS · v2rayN / v2rayNG / v2flyNG · WINDOWS / macOS / ANDROID / LINUX
A subscription URL usually contains connection configurations maintained by a service provider. After copying the URL, create a subscription group in the client, update it, and then select the configuration you want to use from that group. Pasting a URL without updating the group will not create selectable connection entries; continuing to use an old configuration after an update will not switch to the new content. The guide lists menu names separately for desktop and Android and explains the differences between clipboard import, manual entry, and subscription updates.
After importing, verify the selected configuration before choosing a system proxy mode. A subscription URL is persistent configuration data and should not appear on public pages, screenshots, or shared documents. When moving to another device, recreate the group and update it there instead of copying the entire client runtime directory between operating systems.
WORKFLOW · GROUP → UPDATE → SELECT → CONNECT
Routing rules determine which outbound receives traffic based on domains, address ranges, inbound tags, and network type. DNS configuration resolves domain names to addresses and can assign different DNS servers to different domain sets. They often appear together, but operate at different stages: resolution results may be used for routing matches, while routing may determine which outbound handles a query. The configuration guide breaks down the JSON structure in the order of inbounds, outbounds, routing, dns, and policy, making each field’s level easier to locate.
Most users should start with the client’s built-in predefined routes and add only a few rules as needed. Save and reload the configuration after changes, then verify each rule with a specific domain. Adding many rules at once increases the chance of conflicts and makes ordering harder to assess. The more specific a rule is, the more important it is to confirm its match order in the list.
CONFIG · routing / dns / outbounds · XRAY / V2FLY
When a connection fails, first confirm that the client has started with the current configuration. Then check whether the subscription group was updated, whether the configuration is hidden by a filter, and whether the system clock is accurate. Next inspect local port usage, system proxy status, firewall permissions, and runtime logs. Layered troubleshooting is more effective than repeatedly clicking Connect: a stopped client is a process-layer issue, a configuration that will not start is a parameter-layer issue, and a local port conflict is a system-layer issue. If only some apps fail to connect, continue by checking proxy mode or per-app settings.
The help page organizes checks under “cannot connect at all,” “browser not affected,” “subscription update issues,” and “DNS resolution issues.” Record when the error occurred, which platform was in use, and what settings were changed, then compare that time with the logs to narrow the scope. When restoring settings, change one item at a time so you can identify which change produced the result.
CHECK · PROCESS → PROFILE → PORT → SYSTEM PROXY → LOG
The homepage does not list individual installer files. Choose an operating system first; the download page then explains the client, processor architecture, and package format.
v2rayN is the primary choice for Windows desktops. The download page explains when to use the modern cross-platform desktop interface versus the classic WPF interface. Before installing, confirm the Windows version and runtime requirements, then choose the interface that fits your workflow. If migrating an old setup, back up the subscription URL and custom routing first, then restore them item by item in the new client.
Go to downloadsmacOS uses the v2rayN desktop client. Installers are separated for Apple Silicon and Intel processors, so the device’s appearance alone is not enough to identify the correct file. Check the chip or processor name in System Information, then open the matching download entry. After installation, grant any required network permissions and confirm that the client’s menu bar status matches the system proxy status.
Go to downloadsThe primary Android option is v2rayNG, which uses the Xray core; v2flyNG is the alternative client for the V2Fly core. Most recent devices can start by checking the arm64 installer. If the architecture is unclear, review the universal-build notes. After installation, allow the client to establish a local VPN connection and adjust background permissions according to the system’s policies to prevent the connection from being reclaimed after the screen locks.
Go to downloadsLinux desktops use v2rayN, with deb or rpm packages selected according to the distribution. Debian, Ubuntu, and derivatives generally use deb; Fedora, RHEL, and related derivatives generally use rpm. Processor architecture still needs to be confirmed separately. If the system proxy does not take effect after installation, check the proxy settings of the current desktop environment instead of looking only at the client connection status.
Go to downloadsUse this workflow for your first connection. The complete guide covers platform-specific menus, system permissions, and troubleshooting steps separately.
Identify your operating system first, then choose the matching client. Windows, macOS, and Linux use v2rayN; Android primarily uses v2rayNG, while v2flyNG is for the V2Fly core. Desktop installers also require a processor architecture or package format selection. After installation, launch the client and confirm that the main window, tray icon, or status area opens normally before importing a subscription.
If the first launch prompts for permissions, follow the system instructions to allow network connections and system proxy operations. Do not copy the entire runtime directory from an old device before installation is complete: paths, permissions, and runtime environments differ across systems. The key items worth preserving are usually the subscription URL, custom routing approach, and a small amount of manual configuration.
Copy a valid subscription URL and add a new group in the client’s subscription manager. Give the group a recognizable name, save it, and run a subscription update. Selectable configurations appear only after the update completes. If the list is still empty, first confirm that you are viewing the newly created group, then check filters, URL completeness, and messages in the update log.
When you have many configurations, create groups by purpose, but avoid adding the same URL repeatedly to different groups. After updating, select one configuration for the current connection and verify that basic details such as the protocol, address, and port are complete. The provider maintains the subscription content, while the client reads and converts it; if fields are incompatible, first confirm that the client and core type meet the subscription requirements.
Select a configuration and start the client, then choose system proxy, global proxy, or per-app mode according to your device. On desktop, check both the client’s runtime status and the system proxy status; on Android, confirm that the system allows a local VPN connection. Once connected, run a basic test in a browser before checking other apps, so an app-specific proxy setting is not mistaken for a client-wide failure.
If the browser works but other apps do not, check whether each app follows the system proxy, has independent network settings enabled, and is covered by the current routing rules. If no apps can connect, return to the client logs and investigate configuration startup, port usage, DNS resolution, and remote responses in that order. Change one setting at a time and verify the result before moving on.
Clients, cores, and protocols are separate layers. Keeping them distinct makes installer selection and configuration troubleshooting more straightforward.
Project V established an open-source ecosystem centered on the V2Ray configuration model, proxy protocols, transport methods, and routing capabilities. The GUI clients users interact with are not the entire system; they provide an interface for managing configuration, core processes, and system proxy settings. Clients handle subscription imports, configuration selection, log viewing, and system proxy switching, while the core usually handles connection establishment, protocol processing, routing matches, and DNS queries.
Similar interface names do not necessarily mean the same core is being used, and using the same core does not mean every client has identical menus. When troubleshooting, record the client name and platform first, then confirm the core family and configuration protocol. Simply saying “V2Ray cannot connect” is usually not enough to identify where the failure occurs.
V2Fly continues to maintain core implementations, configuration structures, and related components from the V2Ray ecosystem. Xray developed along similar configuration lines while adding its own supported protocols, security layers, and transport capabilities. They share many concepts, including inbounds, outbounds, routing, DNS, policies, and logs, but specific fields, available protocols, and default behavior may differ. Before using a configuration example, confirm which core it targets; do not apply it solely because the file extension matches.
v2rayNG primarily works with the Xray core, while v2flyNG corresponds to the V2Fly core. On desktop, v2rayN can provide the client interface and configuration management, with available capabilities depending on the selected core and current configuration. The documentation clearly identifies core coverage: shared concepts appear in the fundamentals, while differing fields are explained separately in the configuration guide.
v2rayN, v2rayNG, and v2flyNG are maintained through public code, release records, and license files. GUI clients turn core parameters, subscription content, and system network settings into an operable interface. Desktop clients emphasize multiple windows, tray status, system proxy controls, and configuration editing; the Android clients focus on the local VPN interface, per-app proxying, background operation, and mobile network changes.
Open-source development means feature changes can be understood through release notes, documentation, and code evolution, but projects do not need to release on the same schedule. A client update may change the interface or subscription handling, while a core update may add protocol capabilities or alter connection behavior. After an upgrade changes settings, read the relevant client’s release notes before deciding whether to migrate the old configuration.
Routine updates do not require replacing every component at once. Update the client when release notes identify a compatibility requirement, protocol-support change, or known issue fix. Before updating, record the client name, configuration groups, custom routes, and system proxy mode. Afterward, load the existing configuration, verify a basic connection, and then restore complex rules. This sequence helps distinguish installation issues, configuration issues, and core behavior changes.
The service provider updates subscriptions; each project maintains its own client and core; this site organizes download links and English operating guides. These three update sources are independent. A change in subscription content does not require reinstalling the client, and a changed client interface does not mean the subscription has stopped working. Identify which layer changed first, then use the relevant documentation.
Articles are organized around practical tasks. Protocol guides explain how to choose; installation guides cover first-time setup; troubleshooting guides provide a step-by-step checking order.
This guide explains the practical differences between VMess and VLESS from three angles: encryption, transport overhead, and server requirements. Most users do not need to rewrite protocol parameters manually; follow the subscription information and server configuration. If manual selection is necessary, consider the client’s supported range and security-layer requirements.
Read the article →Check per-app proxy coverage, connection heartbeats, Mux settings, the system’s battery-optimization allowlist, and vendor background restrictions one by one. The article distinguishes continuous client operation, frequent reconnects, and repeated system wake-ups to help determine whether battery use comes from network activity, configuration policy, or background management.
Read the article →This comparison organizes four protocols by handshake method, transport overhead, server requirements, and client support. It is for users who need to understand subscription details or deployment parameters, emphasizing that the protocol, transport, and security layers are separate choices—not one setting—and that no single metric fits every scenario.
Read the article →