Project V, V2Fly, and Xray: How v2rayN, v2rayNG, and v2flyNG Fit Together

Learn how Project V evolved into the V2Fly and Xray core branches, which core each client uses, and how to choose the right client.

At a Glance

Choose a client based on your device, then check which core your node requires. On desktop, with v2rayN, confirm which core the active node actually runs. On Android, choose v2rayNG if the instructions specify Xray, or start with v2flyNG if they explicitly require V2Fly. If a node imports but won’t connect, check the transport, security settings, and local proxy setup in turn.

How are Project V, V2Fly, and Xray related?

Project V was the original project ecosystem, with V2Ray serving as its core program for proxy connections and routing. The V2Fly community later continued development of the V2Ray core, whose codebase is commonly called v2ray-core. Xray forked from V2Ray in 2020 and has since been maintained independently; its codebase is called Xray-core. Although they share a common origin, their version numbers, feature development, and configuration fields no longer correspond one-to-one.

Core: Runs the configuration
The running core connects to remote nodes, handles encryption and transport, and applies routing rules. Whether a feature works depends on the core type, its version, and the configuration it actually receives.
GUI client: Manages and launches the core
Clients provide the controls for importing subscriptions, viewing node lists, and switching connections. They also convert interface settings into configuration the core can read. So “the core supports a field” and “this client correctly imports that field from a share link” are two different things.

If a guide only says “V2Ray supported,” don’t rely on the name alone. Look for the core name, tested version, and node parameters it specifies. If it only shows vmess:// or vless://, those prefixes identify the protocol, but not the transport, security layer, or core.

Core compatibility: v2rayN, v2rayNG, and v2flyNG

Clients and cores by platform
ClientPlatformRelationship to V2Fly and XrayWhat to check before use
v2rayNDesktopCan run multiple cores, including Xray. The client name alone doesn’t tell you whether V2Fly is running.Check the core type in the node editor, if your version shows it, then confirm it in the startup logs.
v2rayNGAndroidUses the Xray core.Check the bundled core version and whether the node editor preserves the required parameters.
v2flyNGAndroidUses the V2Fly core.Check the node against V2Fly configuration guidance; don’t apply Xray-specific settings without verification.

Keep the v2rayN client version separate from the version of the core currently running. Two PCs can both use v2rayN and still behave differently because of the node’s core type, the core bundled with the installer, or separate core updates. If the same link works on one PC but not the other, compare startup logs first, then node settings. Don’t mistake the client version for the core version.

Numbers that are easy to confuse while troubleshooting

2020
Year Xray forked from V2Ray
7.x
v2rayN series used in the desktop menu examples
10808
Common local inbound port for v2rayN; check your settings

In the v2rayN 7.x desktop app, open “Settings” → “Parameter Settings” to check the local listening port and the inbound type shown in the interface. For example, if the local port is 10808 and the node editor shows the remote port as 443, the first is for apps on your device to connect to, while the second is the server port used by the core. If the logs say the local listening port is already in use, check the process using it or change the local port. Don’t change the node’s 443.

Xray or V2Fly? Start with the full node settings

When you get a link, check more than the protocol: review the transport, security layer, and optional parameters too. For example, a VLESS node configured for TLS is not equivalent to one that explicitly specifies REALITY and xtls-rprx-vision. For WebSocket nodes, verify the path and the Host required by the server. Changing cores won’t fix an incorrect path.

Choose a core based on the node documentation

Xray core

Recommended

If the node documentation specifies Xray settings for VLESS, REALITY, and Vision flow control, first test with an Xray version that supports those fields. After importing, open the editor and check the security type, server name, public key, short ID, and flow control. A node appearing in the list doesn’t mean its configuration is complete.

Best for: Nodes whose documentation explicitly requires Xray or specifies the settings above.

V2Fly core

Stick with V2Fly if the node is configured according to V2Fly documentation and your current core connects reliably. For a VMess + WebSocket node, first verify the server address, port, path, and TLS setting against the existing configuration before considering a core change.

Best for: Existing configurations verified with V2Fly, or reproducing behavior under this core.

Bottom line: Test one node before switching cores

Keep the original node and save a separate copy for testing. Leave the server address, port, and transport settings unchanged; switch only to a core that meets the node’s requirements, then compare the initial connection logs and results. Get one node working before changing how you use the entire subscription. This helps avoid mistaking a subscription update failure for core incompatibility.

Using one subscription on desktop and Android: what should you check?

A shared subscription lets both devices fetch nodes from the same URL, but it doesn’t sync local ports, system proxy settings, per-app settings, or routing rules. Even if the same node name appears on both, check that the imported transport and security settings match. Don’t copy the entire desktop core configuration to a phone: local listening addresses, file paths, and routing resource references may only work on the original device.

First connection checks on both devices

Test whether traffic from each device is routed through the same node

Desktop (v2rayN)
  • Import the subscription and select a node. Check the startup logs for the expected core and any local listening errors.
  • Test with an app that follows the system proxy. If the app has its own proxy settings, enter the local inbound type and actual listening port.
Android (v2rayNG or v2flyNG)
  • Choose a client based on the node documentation. On the main screen, tap “+” in the top-right corner and import the same node share link from the clipboard. Menu wording varies slightly by version. This helps rule out subscription update issues.
  • On first launch, approve the system VPN request. If per-app proxying is enabled, check that the app you’re testing is included.

Once both devices connect, add routing rules back one at a time. If only certain apps or websites have problems, check the proxy scope and rule order before replacing the node.

Common questions about versions, imports, and connections

Why does v2rayN have “v2ray” in its name but show Xray in the logs?

The name refers to the GUI client; the logs show which core was launched. After enabling a node, look in the main window’s log area for the core name and version reported at startup. Check again after switching nodes, especially if different nodes specify different core types.

Why can both Android clients import a node, but only one connect?

Open the node editor in both clients and compare the protocol, port, transport, and security type field by field. Then check the first relevant error on the failing side. If security fields are missing after import, check the app version and share-link format. If the logs say a setting isn’t supported, switch to the core specified by the node documentation or update the app.

Does updating the client always update the core too?

Not necessarily. Desktop clients may manage cores separately, so an updated client version doesn’t mean the running core has changed. Note the current core and version before updating, then reconnect and compare the logs. Use the same node for both tests, and avoid changing the subscription and routing rules at the same time.

Does a subscription update timeout mean I chose the wrong core?

First distinguish fetching the subscription from connecting to a node. Test with a saved node share link. If it connects but the subscription still times out, check whether the subscription URL has expired and whether the update request is using the expected network route or proxy. If the list updates but nodes won’t connect, check the node fields and core logs.

Download clients