Xray vs. V2Fly: Core Differences, Project Origins, Protocol Support, and Client Compatibility

Compare the V2Fly and Xray branches of Project V, their protocols and features, and how to choose between v2rayNG and v2flyNG for your nodes.

At a glance

If your subscription imports successfully but you’re unsure which core to use, open a node and check its protocol, transport, security layer, and flow control. Common configurations in this guide show when the two cores are interchangeable, when to keep the original settings, and how to tell whether fields were lost during import, the core lacks support, or the connection itself failed.

How Project V, V2Fly, and Xray are related

Project V is the starting point for understanding this project lineage, with V2Ray as its core connection software. The V2Fly community continues to maintain the V2Ray core. Xray forked from this codebase in 2020 and has developed independently since. Release numbers aren’t directly comparable: a higher version number in one project doesn’t mean it includes features added to the other around the same time.

2020
The year Xray forked
443
Common TLS port on the remote server; not enough to identify the core

The app and the core aren’t the same thing. v2rayNG and v2flyNG are Android clients that use the Xray and V2Fly cores, respectively. The app reads subscriptions, provides the editing interface, and generates the configuration; the core establishes connections and applies routing. Even if the core recognizes a field, the active configuration may be incomplete if the client drops it during import. When troubleshooting, note both the app version and core version—not just one.

Compatibility: VMess, VLESS, REALITY, and Vision

You can’t tell whether a different core will work just by looking at the start of a share link. VMess and VLESS are protocols; WebSocket is a transport; TLS and REALITY are security-layer options; and xtls-rprx-vision is a VLESS flow-control value. Each serves a different purpose. Two nodes that both use VLESS may have very different core requirements.

Node configurationHow to chooseCheck first
VMess + WebSocket + TLSBoth cores have relevant support. Start with the one you’ve already confirmed works.Remote port, WebSocket path, request Host, and TLS server name.
VLESS + WebSocket + TLSVLESS alone doesn’t mean you need Xray. Check the target version and the imported configuration.Path, security layer, and any additional flow-control requirements.
VLESS + REALITY + VisionOf the two cores compared here, choose an Xray version that supports this combination.Check that the REALITY server name, public key, short ID, and Vision flow control are preserved as configured.
Experimental configuration for a specific V2Fly versionVerify against the V2Fly version and configuration format specified in the original setup; don’t assume Xray can read it as-is.Check that the field structure, inbound and outbound tags, and rule references are all intact.

Bottom line: compare imported fields before testing the connection

If the original node specifies REALITY but the imported configuration shows TLS or no security layer, stop before running a speed test. Check whether your client and core support the original combination. Don’t change the security layer to force the node into a different configuration.

Don’t copy the same domain into every field, either. The server address determines where to connect; the TLS server name is used for the relevant handshake and verification; and the WebSocket request Host belongs to the HTTP request. These may match in some setups and differ in others. Even if the remote port is 443, that tells you nothing about the other fields—and doesn’t mean your system proxy should use that port.

Choosing between v2rayNG and v2flyNG

If your Android device needs nodes that use REALITY or Vision, start by checking that combination in v2rayNG. If your subscription contains only standard VMess nodes that already work reliably in v2flyNG, there’s no need to redo your per-app proxy settings just to change cores. The recommendations below are for subscriptions that need to support both standard nodes and Xray-specific configurations—not a performance ranking for every subscription.

v2rayNG · Xray core

Recommended

First test a node in your subscription that only the Xray core supports, then spot-check standard nodes to make sure their transport settings survive the client’s import.

Best for: mixed subscriptions that require REALITY or Vision

v2flyNG · V2Fly core

Keep your verified VMess nodes and local rules. For custom configurations that specify a V2Fly version, first check which version is actually bundled with the app.

Best for: stable existing V2Fly setups with no Xray-specific node requirements

The same subscription may show a different number of entries in each app. The importer may skip entries it doesn’t recognize, or the subscription provider may return different content for different requests. Match nodes by name and connection settings before comparing them. Matching entry counts don’t prove the configurations are identical: a missing option may not make the entire node disappear.

How to test the same node on desktop and Android

Test method: keep the original configuration and test each device separately

Desktop: v2rayN
  • Open the target node’s edit window from the main list, and distinguish the remote port from the local listening port.
  • In versions with this menu layout, go to Settings → Parameter Settings to review the local listening configuration. Then check the startup log to confirm which core is running.
Android: v2rayNG or v2flyNG
  • Make sure VPN permission has been granted, then check that your test browser isn’t excluded by per-app proxy rules.
  • Compare the protocol, transport, security layer, and flow control with the desktop setup. Test the same destination and note whether the failure occurs during startup or connection.

Use the same network where possible and change only one variable at a time. The same subscription doesn’t mean both devices have the same DNS, routing, or app coverage.

  1. First, check whether the configuration loaded. If startup reports an unknown transport type or unsupported flow control, check the core version and the generated configuration first. The remote connection hasn’t been attempted yet, so a speed test can’t point to a server issue.
  2. Next, find out how far the remote connection gets. For a timeout, check the address, port, and current network. If you see a specific handshake error, compare the security layer, server name, and related settings. Changing several settings at once makes it impossible to identify the cause.
  3. Finally, confirm that app traffic reaches the core. A desktop browser that isn’t using the system proxy or an Android browser excluded from the VPN can make the client appear to work while webpages remain inaccessible. Confirm which apps are covered, then check DNS and routing.

For a meaningful speed comparison, keep the node, network, destination, and test method consistent. A single latency test reflects the response to a specific destination at that moment; it doesn’t measure sustained downloads, and network fluctuations don’t prove a core difference. If your current setup is stable, switch and retest only when you’ve found a specific missing feature or a reproducible problem.

Download clients