Clients / Cores / Protocols
The Project V, V2Fly, and Xray Ecosystem
These names refer to different layers. A client provides the interface, a core handles network connections, and a protocol defines how they communicate. Understanding how the three fit together is more useful than memorizing a download name.
Graphical clientsv2rayN · v2rayNG · v2flyNG
↓
Connection and routing coresXray · V2Fly
↓
Communication protocols in the configurationVLESS · VMess · Transport and security settings
Project V: From Network Tools to a Client Ecosystem
Project V is a useful starting point for understanding V2Ray’s background. Its core idea is to organize proxy connections, routing, and transport capabilities into configurable modules. In everyday discussions, “V2Ray” may refer to a specific core or to a broader set of tools using related protocols. That’s why a search for the same name can lead to very different downloads. This site clearly separates graphical clients from background programs that don’t offer a click-to-use interface.
V2Fly continues development and community maintenance of implementations related to V2Ray. Xray builds on related technology but has developed its own implementation and features. They share technical roots, but configuration fields, feature support, and protocol extensions don’t always match. When following a guide, check which client and core it covers. Similar menus only mean the interfaces look alike; they don’t prove that the underlying behavior is identical.
Three Open-Source Clients: Choose an Interface and a Core
v2rayN is an open-source graphical client for desktop, handling subscription management, node selection, parameter generation, and core startup. It can work with different cores; exact support depends on how the client integrates them and which core you choose. The desktop and classic WPF editions differ first in interface technology and platform coverage. A newer interface doesn’t mean the same node will connect faster.
v2rayNG is an open-source Android client using the Xray core; v2flyNG is an open-source alternative using the V2Fly core. Their workflows have similarities, but your choice should depend on node requirements and feature compatibility. If your configuration includes specific extension parameters, first confirm the core supports them, then choose a client. For a side-by-side look, see Client Comparison. There’s no need to keep migrating subscriptions just because the names look alike.
Open-Source Licenses: Code Rights and Service Terms
Open source means the source code is available under a license that allows people to read, use, modify, or distribute it within the license terms. Clients, cores, and their dependencies may each use different licenses; refer to the license included with each project for specific conditions. Readable code supports technical review and community collaboration, but users should still consider download sources, system permissions, configuration contents, and how the service handles requests.
Client software and subscription services are separate. Open-source clients may be free to use, while subscription fees, validity periods, and node availability depend on the service provider. This site provides download links and configuration guides; it doesn’t sell nodes or manage service accounts. If a subscription stops working, check the URL and service status first. Reinstalling the client repeatedly usually won’t fix a server-side problem.
Updates: Apps, Cores, and Rules Are Separate
“Update” can mean at least three things: upgrading the client app, updating the core that establishes connections, or refreshing the node list in a subscription. Routing may also rely on rule data such as GeoIP and GeoSite, which has its own update process. Updating a subscription won’t upgrade the app, and upgrading the app won’t fix an expired subscription URL. Identify what needs updating before choosing a menu.
Before changing your setup, back up subscription groups, routing rules, and manually added nodes, and save a configuration that still works. After an update, check your subscription, default node, and proxy mode one by one. If something goes wrong, review the specific error in the logs to determine whether it’s a compatibility issue or a permission change. Don’t overwrite every setting while troubleshooting. The menu paths on this page help you find features; if the interface changes, use the current client’s feature names and descriptions.