Practical position
V2Ray-core is the core project in the Project V ecosystem. Many early VMess/V2Ray clients and server profiles are built around it, with routing and JSON syntax different from Clash YAML.
Positioning
V2Ray JSON, often used for VMess/VLESS, routing and transport configuration.
| Item | Meaning |
|---|---|
| Status | Project V |
| Profile format | V2Ray JSON, often used for VMess/VLESS, routing and transport configuration. |
| Protocol check | Use the core/protocol matrix |
Best Use Cases
- Check VMess/V2Ray share links or JSON.
- Migrating from a V2Ray client to a Clash/Mihomo client.
- Understanding why subscription conversion may rewrite fields.
Compatibility Notes
Protocol support depends on the selected core, client build, operating-system permissions and profile syntax. Treat provider subscription names as hints, then verify the actual parsed node fields in the client log.
- V2Ray-core JSON is not Clash YAML.
- VMess link fields can be converted by clients, but the result must be checked.
- Old VMess settings may not fit current security or compatibility expectations.