Project V Ecosystem Explained: V2Fly, Xray, and GUI Clients

Explore Project V, V2Fly, and Xray, plus how v2rayN, v2rayNG, and v2flyNG use their cores and which open-source licenses apply.

At a glance

Project V is the project name; V2Fly and Xray represent two core development paths, while v2rayN, v2rayNG, and v2flyNG are GUI clients that configure and run those cores. If you're migrating a subscription or seeing “import succeeded but can't connect,” first distinguish subscription format, core support, and system traffic routing. Then decide whether to switch clients or cores, or check your local settings.

How Project V, V2Fly, and Xray Are Connected

Project V began in 2015, with V2Ray serving as the project's core program for handling network connections. It separates traffic entry, forwarding, and routing decisions: inbounds accept connections, routing rules select an outbound, and outbounds connect directly or establish a remote connection using the configured node. A core can use multiple inbounds and outbounds, so V2Ray is neither the name of a specific network protocol nor a desktop app.

2015
Project V launched
2020
Xray-core forked

After the original project handed off maintenance, the V2Fly community continued developing the V2Ray core. In today's documentation, v2fly/v2ray-core refers to this maintenance branch, not a separate GUI. Xray-core forked from V2Ray's codebase in 2020 and has since developed independently. Both paths retain concepts such as inbounds, outbounds, and routing, but have their own versions and configuration definitions. A JSON config that works in an older guide cannot be assumed to work with the other core just because the field names look familiar.

How v2rayN, v2rayNG, and v2flyNG Use Their Cores

A GUI client stores subscriptions, parses nodes, selects the active configuration, and assembles node and local settings into a config the core can read. The core accepts connections, selects outbounds based on routing rules, and handles the remote handshake. Seeing a node name in the interface only confirms that the client read some subscription data; verify separately that the core starts and can connect with the original parameters.

Core Integration in Three GUI Clients
ClientPlatformHow it runsWhat to check first
v2rayNWindows、macOS、LinuxGenerates a runtime config and launches the corresponding core process.The core selected for the active node, its version, and local listener settings.
v2rayNGAndroidUses a mobile wrapper to run the Xray core; proxy mode can route traffic through the system VPN service.The core version in the app, VPN permission, and per-app proxy scope.
v2flyNGAndroidUses a mobile wrapper to run the V2Fly-maintained V2Ray core; proxy mode can also route traffic through the system VPN service.Whether the node's protocol and transport settings are supported by that core version.

In v2rayN, open Settings → Parameter Settings and check the local listening port. If the current SOCKS or mixed inbound is shown as 127.0.0.1:10808, enter that address in apps where you configure the proxy manually. If the port has changed, use the value shown in the interface. This is a local entry point, not the node server's port. If the core is running but an app still connects directly, check whether it reads the system proxy or is covered by TUN routing.

VMess, VLESS, and REALITY: Choose a Core That Fits the Node

VMess and VLESS are node protocols; WebSocket is a transport; TLS and REALITY are connection security settings; and xtls-rprx-vision is a VLESS flow value. A subscription link can include all of these fields. Seeing “VLESS” alone doesn't tell you whether the core is compatible. Check the transport, security type, and flow, and make sure the client passes all settings through to the core.

Xray Core

Recommended

Choose Xray first when a node explicitly uses VLESS, REALITY, and Vision together. After importing it, check the node details for security set to reality and flow set to xtls-rprx-vision. Confirm that required server parameters, such as the public key, were retained.

Best for: Nodes confirmed to use REALITY and Vision together.

V2Ray Core Maintained by V2Fly

If your existing node uses VMess, WebSocket, and TLS and the server is configured for V2Fly, start by testing that setup with the same core. Check the node's WebSocket path, request host, and TLS server name. Changing the client interface alone is no reason to change the node protocol.

Best for: Existing V2Fly configs where you need to preserve VMess node settings during migration.

Quick check: Test the settings with one node first

During migration, start with a node that works on the original device. If the new device reports a config error, compare the protocol, transport, security type, and flow on both devices, then check the matching core version. Don't clear fields or disable certificate verification just to make the config pass.

Migrating One Subscription Between Desktop and Android

A subscription link usually updates the node list; it doesn't transfer the entire client configuration. The same link may show different numbers of nodes on each device: a client might skip records it can't parse, or the subscription service might return different formats depending on the request. Even with identical nodes, check routing, DNS, system proxy, and per-app settings on each device.

Approach: Compare both devices using the same node

Desktop: v2rayN
  • Add the subscription URL under Subscription Groups, then update the relevant group. Select a known working node from the list.
  • Check which core the node actually uses. Keep the existing routing rules unchanged and test access to the same destination through the system proxy.
Android: v2rayNG or v2flyNG
  • Choose a core that supports the node settings. Add the same subscription URL under Subscription Group Settings, then update the subscription from the main menu.
  • Select the matching node and grant VPN permission. If per-app proxying is enabled, make sure the app you're testing is included.

First confirm that the same node connects on both devices. Then adjust routing, DNS, or per-app settings one at a time.

  1. Node doesn't appear in the list: Check that you selected the right subscription group and that the update completed without errors. Then confirm the subscription returned a format the client can parse. There's no need to change routing yet.
  2. Node appears, but the core won't start: Check the startup log first. An unknown field or unsupported transport points to the core version or generated config; a listener address conflict points to a local port issue.
  3. The core is running, but some apps can't connect: Check the system proxy, TUN, and per-app scope first, then review routing matches and DNS. If the log shows a remote handshake failure, check the node settings, system clock, and remote connectivity one by one.

Open-Source Licenses: Check the Core and Client Separately

Open-source licenses define how code can be used, modified, and distributed. Network protocols such as VMess and VLESS define how the two ends of a connection communicate. They aren't linked one-to-one. A client using a particular core doesn't mean the client code, core code, and every dependency in the installer share the same license.

Download v2rayN