CORE LINEAGE / PROJECTS AND CORES
Project V, V2Fly, and Xray
Understand the ecosystem, core, and graphical client separately before checking protocol compatibility. Similar names do not mean their configurations are interchangeable.
EcosystemProject V / V2RayProtocol, transport, and routing foundations
CoreV2Fly · XrayHandles connections and parses configuration
Client interfacev2rayN · v2rayNG · v2flyNGManages subscriptions, servers, and user settings
Origins and development of the ecosystem
Project V is a useful starting point for understanding the V2Ray ecosystem. Its design separates inbounds, outbounds, transports, and routing so different connection methods can be combined. V2Fly continues the community development of V2Ray; Xray grew from related code and continues to evolve beyond shared capabilities. As a result, “V2Ray config” can mean a general concept in the ecosystem or a configuration that a specific core can read. Pay attention to the context in documentation.
This lineage explains why some basic settings look similar while support for newer features differs. A protocol name is only part of the picture; transport, security layer, and optional parameters matter too. For example, REALITY is a security-layer technology and should not be treated as a choice at the same level as VMess or VLESS. Check the full combination rather than importing a config just because you recognize an abbreviation.
How graphical clients and cores work together
v2rayN manages desktop server lists, subscriptions, and settings, then turns your selections into a configuration the core can run. v2rayNG is an Android client that uses the Xray core; v2flyNG offers an Android option based on V2Fly. All three are open-source projects. An option with the same name may still work differently depending on the core and platform implementation.
If the interface recognizes a share link, that only confirms the parsing step succeeded. Check the logs and test the connection to confirm that the core accepts the generated configuration and the remote server supports it. When troubleshooting, note the client and core versions separately; updating the client does not necessarily update every component. With multiple cores, confirm which executable is handling the active node.
Open-source licenses and usage
v2rayN, v2rayNG, and v2flyNG are licensed under GPL-3.0. The license sets the terms for using, modifying, and redistributing the code. Cores and other dependencies may have their own licenses, which should be reviewed separately. A free client and a paid remote service are different things; you still need server settings you are authorized to use.
Open-source projects improve through public code and community collaboration, but results still depend on the device, configuration source, and server status. Before use, check the rules that apply where you are, your network administrator’s requirements, and the service provider’s terms. This site collects download links and technical guides; it does not provide subscription accounts or guarantee any particular service quality based on protocol choice.
Updates and compatibility
Updates can change the interface, configuration fields, core behavior, or system dependencies. Read the release notes for your version and back up your current settings before upgrading. Afterward, test the connection and routing against the same destination. When moving between devices, use a share-link or subscription format supported by the target client. Copying a full config file may carry over platform-specific paths, listeners, or routing settings.
Subscription formats are not all interchangeable. Single-server share links, encoded link lists, and full configuration files serve different purposes. If a format is incompatible, ask the source for a suitable export first. Sending a subscription URL with access credentials to an unfamiliar online converter increases the risk of exposure. Before converting anything, identify the fields that must be retained and confirm the target core supports them.
If you are dealing with a failed subscription update, a browser that works while other apps do not, or local devices becoming unreachable after enabling TUN, troubleshoot the affected layer before reinstalling. The help center organizes answers by fundamentals, setup, usage tips, and troubleshooting, making it a quick reference while configuring the client.
Visit the help center →