The graphical client is for entering and managing settings; the core establishes connections, handles protocols, and applies routing. Understanding the difference helps you decide whether to switch installers, fix node settings, or change the proxy entry point.
Project V and V2Fly
Project V organizes inbound connections, outbound connections, and routing into a composable network configuration. Inbounds determine how traffic enters the program, outbounds determine how it's sent, and routing directs traffic to the appropriate outbound. V2Fly is a community project that continues V2Ray development and maintains the V2Ray core and related documentation.
This division also explains common configuration issues: importing a node successfully only means the client can read the list. Whether a connection works depends on whether the core supports its settings. Whether a browser uses that connection depends on whether the app sends requests through the client. Check these three stages separately when troubleshooting; it's more effective than repeatedly updating the subscription.
Xray and protocol support
After splitting from the V2Ray codebase, Xray has developed independently. It shares some configuration concepts with V2Fly, but the two projects maintain their own features and settings. REALITY, for example, is a connection security layer setting, not a node protocol that replaces VMess or VLESS. Separating connection settings into protocol, transport, and security layers helps pinpoint which field is incompatible.
Before switching cores on desktop, check that the new core supports the node's transport, flow control, and security settings. Once the configuration loads, review the connection log. If startup fails, check the configuration and core combination first rather than changing the system proxy or repeatedly switching DNS.
Open-source clients and licenses
v2rayN, v2rayNG, and v2flyNG are open-source graphical clients. v2rayN manages desktop nodes and routing and can use supported cores. v2rayNG is for Android and uses the Xray core; v2flyNG is for Android configurations that require the V2Fly core. Similar interfaces or names don't mean advanced settings and configuration files are interchangeable.
Open-source licenses govern the use, modification, and redistribution of code; check each project's license and the licenses of bundled components for specific terms. Open-source client code is separate from who provides a subscription or how long its nodes remain available. Choose a client based on platform and core requirements, and check the subscription source and update status separately when troubleshooting.
Updating the client, core, and subscription
Client updates can change the interface, defaults, or runtime environment. Core updates can change supported protocol features, configuration parsing, or connection behavior. Subscription updates fetch the node list again. These updates aren't interchangeable. If the node list hasn't refreshed, reinstalling the program isn't the first step. If the core can't recognize a field, repeatedly refreshing the list may not help.
Before making changes, note the current node, system proxy mode, custom routes, and listening port. Update one layer at a time, then retest with the same node and app before moving on. If the connection fails, compare the old and new settings one by one. If you have questions about protocol names or configuration fields, start with the glossary.