Project V: How the Client and Core Work Together
The early Project V used V2Ray as its core for handling network proxying. The core listens for local connections, matches routing rules, and establishes outbound connections. The graphical client provides an interface for managing subscriptions, server lists, and common settings. This division of responsibilities continues today: update a subscription group or switch the active server in the client, and it generates the configuration the core needs—no need to edit the entire file by hand every time.
In everyday conversation, “install V2Ray” might mean installing a client or configuring a core. Know which one you mean before following a guide. If you can’t find a menu, check the client and interface version. If the core won’t start, look at the specific configuration fields and runtime logs. These issues call for different troubleshooting steps; a similar-looking interface doesn’t mean the same setup instructions will apply.
V2Fly and Xray: Related Projects with Different Paths
V2Fly is a community-maintained continuation of the V2Ray core. Xray evolved from V2Ray code and developed into a separate core family. They share some protocols and configuration concepts, but their supported transports, security options, and fields aren’t identical. v2rayN can use different cores depending on the configuration, but that doesn’t mean every server can be switched freely between them. For mobile clients, start with the requirements of your existing servers rather than comparing interfaces alone.
For example, if your provider specifically requires REALITY or XTLS Vision flow control, first confirm that your chosen core and client support those features. Then check the server protocol, transport, and security settings. Simply switching cores while keeping incompatible parameters may leave a server visible in the list but unable to connect. For a side-by-side feature comparison, see our three-client comparison.
What’s Open Source: Interfaces, Cores, and Configuration Formats
v2rayN, v2rayNG, and v2flyNG are all open-source graphical clients. v2rayN is for desktop, v2rayNG uses the Xray core, and v2flyNG is an Android alternative based on the V2Fly core. Clients and cores are maintained separately, and bundled components may have their own open-source licenses; check the license information for the specific package. Open source describes the code and distribution terms, not how third-party subscription services or servers are operated.
VMess, VLESS, and Trojan are proxy protocols that servers may use. REALITY is a security mechanism in the Xray ecosystem, not a proxy protocol on the same level as those three. When reading server details, distinguish the protocol, transport, and security settings, then check which ones the core supports. To find out whether a field is entered by the client or interpreted by the core, start with the quick reference.
Updates: Keep Client Updates Separate from Subscription Updates
Updating the package replaces the client program and may also change the core, dependencies, or interface. Updating a subscription fetches the latest server list from your provider. If an older server disappears after an update, check whether the provider removed it and whether you need to select a new active server. If the interface still opens after migrating an old configuration but the core won’t start, check whether the parameters used to generate its configuration are still supported.
Before upgrading, note your main settings and proxy mode, and back up anything you want to keep using the client’s built-in method. After upgrading, retest with an existing server to make sure the program works before changing your rules. Don’t rewrite traffic routing while migrating. If the guide’s interface doesn’t match yours, rely on the messages, core logs, and system requirements. Compare installation steps and common limitations by platform in the complete installation guide.