Project V, V2Fly & Xray
Client names, core families, and proxy protocols refer to different layers. Understanding what each one controls is more useful for migration and troubleshooting than memorizing a software name.
The Project V Ecosystem and Graphical Clients
Project V is the open-source ecosystem behind a set of proxy tools and related capabilities, with V2Ray among its widely used projects. Graphical clients build on this kind of core functionality to provide interfaces for subscription management, server selection, and configuration. The interface stores settings; the running core establishes connections, applies routing, and handles DNS resolution. So seeing a protocol listed in a client does not guarantee every transport combination is supported by the selected core.
v2rayN, v2rayNG, and v2flyNG are all open-source client projects, but they are not just different skins for the same program. Desktop and Android differ in permissions, network access, and background operation, so their settings won't always match. When following configuration instructions, check the client name, core, and specific feature. Don't assume a configuration file can be imported unchanged into another client.
V2Fly and Xray: What Each Core Supports
The V2Fly community continues to maintain V2Ray-related implementations, while Xray is another core project that grew out of V2Ray. They share some protocol and configuration concepts, but each has features and fields that evolve independently. Choose based on the server's requirements: check whether the core supports the protocol, transport, security layer, domain parameters, and other options you need. Similar names don't guarantee full compatibility.
Desktop v2rayN provides options for configuring multiple cores. On Android, v2rayNG uses the Xray core and v2flyNG uses the V2Fly core; choose according to your existing configuration. If you need a specific protocol extension, check core support before choosing a client. For basic subscriptions and everyday connections, starting with a compatible default combination is usually easier to maintain than switching cores frequently.
Open-Source Licenses and Subscription Privacy
Open source means a project's code is published under a license; use, modification, and distribution must still comply with its terms. V2Fly's V2Ray and Xray-core use MPL-2.0. Client projects have their own license terms, so a core's license does not automatically cover every graphical client or bundled component. Before redistributing or modifying software, review the licenses for the projects you use and their third-party components.
Open-source code and the trustworthiness of a remote service are separate issues. A client does not determine how a subscription provider handles accounts, connections, or service logs, nor does it guarantee that servers will be available. Treat subscription links like account credentials. Before sharing screenshots, exporting configurations, or submitting logs, remove authentication fields, subscription URLs, and account-identifying information. The configuration examples on this site explain how settings relate to one another; they do not include usable server details.
Update Order and Configuration Maintenance
Client updates, core updates, rule data updates, and subscription refreshes address different things. Client updates affect the interface and configuration generation; core updates may change protocol support or behavior; rule data updates affect classification and matching; subscription refreshes sync remote server parameters. One update succeeding does not mean the others are complete. When troubleshooting, identify exactly what changed most recently.
Before updating, record your working configuration and custom rules. Afterward, check that the core starts, then test existing connections and key services. If an issue appears only after adding a rule, roll that rule back first. If the core won't start, check the error log for the fields and file paths it mentions. Don't assume every problem is a subscription issue. For a systematic approach to subscriptions, routing, DNS, and custom outbounds, read the advanced configuration manual. For specific how-to questions, browse the FAQ by category.