PROJECT / BACKGROUND
Project V is an ecosystem, not a single installer
V2Ray originated in the Project V ecosystem, which has evolved around proxy protocols, transport methods and routing capabilities. In everyday searches, “V2Ray client” often means a GUI app using related technology, not one specific desktop application. Understanding the distinction helps you tell client names on download pages apart from protocol names in configuration files and core names in logs.
V2Fly continues community development of projects related to V2Ray, while Xray is another core that developed from the same roots. They share some technical background, but their features, parameters and extension support don't always match. If the same subscription behaves differently across clients, the cause may be the import format, core capabilities or how the client generates its configuration—not necessarily an invalid URL.
This site separates downloads from setup guides: the download center helps you choose a platform and installer, tutorials explain the interface, and the complete handbook covers concepts and troubleshooting. This site provides setup guidance, not proxy services or subscription accounts. To test a connection after installing a client, you'll still need a compatible configuration that you're authorized to use.
CORE / COMPATIBILITY
V2Ray core comparison: start with protocol support
The core handles protocols, connection setup, DNS and routing; the GUI turns your input into a core configuration. To assess compatibility, check the protocol, transport and security settings together. “Supports VLESS” does not mean every VLESS combination is supported. If a setting is missing, first check whether the current client and selected core support it.
v2rayN's multi-core management makes it easier to work with different configurations on desktop, but switching cores doesn't automatically convert every parameter. On Android, choose v2rayNG or v2flyNG according to the configuration requirements from your service provider. There's no need to switch a working setup just because the name is different. Test a different core for a specific capability, and keep the working option as a fallback.
If startup fails, check the log entry closest to the failure time. Determine whether it points to an unsupported field, a configuration parsing error or a remote connection failure. The first two are more likely to be local compatibility issues; the last may involve the network path or service status. Classify the error before switching cores so you can tell whether the change helped.
Read more about cores and the ecosystem →
PROTOCOL / TRANSPORT / SECURITY
Understand protocols, transports and REALITY separately
VMess, VLESS and Trojan are common protocol names in configurations, each with its own transport and security parameters. REALITY is a related security mechanism; it cannot replace the server address, port or user ID. If an imported configuration appears in the interface but fails to connect, check whether its transport and security parameters were recognized correctly instead of changing only its display name.
Subscription conversion adapts formats; it doesn't add capabilities a core lacks. Some extension fields may be lost during conversion, so prefer subscriptions from a clear source that directly support your client. If conversion is necessary, check how the tool handles data and where sensitive information goes. Avoid giving a complete access-bearing URL to an unfamiliar third-party site.
For initial setup, use a share link or QR code the client can recognize directly to reduce manual entry errors. If you need to edit settings by hand, compare each field with your provider's instructions, especially the domain, security layer and transport path. More toggles do not make a client setup better; they only help when they match the server settings.
See protocol and parameter details →
MAINTENANCE / RECOVERY
Maintenance order: updates, backups and TUN
Open source means the code can be inspected, used and modified under the terms of its project license. It does not mean every derivative build has the same features. All three clients come from the open-source ecosystem; when discussing free use, distribution or modification, consider the separate licenses for each client, core and related component. Proxy service terms are set separately by the provider.
Before updating, note your platform, client edition and selected core, and export any configuration you need. Subscription updates sync server configurations; client updates change the interface or features; rule data updates are a separate maintenance task. Don't treat these as the same action. Subscription sync is not a substitute for a local backup: routing, custom DNS and interface preferences may not be included in the subscription.
TUN affects how system network traffic is routed, so enable it only after verifying a basic connection. Beforehand, learn how to turn it off, restore the original system proxy and check for other virtual network interfaces. If something goes wrong, exit TUN and test the regular proxy. If that works, focus troubleshooting on traffic capture, routing or DNS instead of reinstalling the entire client.
Read about TUN and routine maintenance →