Practical position
Xray-core belongs to the Project X / Xray ecosystem and is common in VLESS, REALITY, XTLS, VMess and Trojan deployments. It is not a Clash YAML core.
Positioning
Xray JSON, common in v2rayN, NekoRay/NekoBox-style clients and server configs.
| Item | Meaning |
|---|---|
| Status | Project X |
| Profile format | Xray JSON, common in v2rayN, NekoRay/NekoBox-style clients and server configs. |
| Protocol check | Use the core/protocol matrix |
Best Use Cases
- When a provider gives VLESS Reality or Xray JSON configuration.
- Understanding why Xray JSON needs a supported import format as Clash YAML.
- Comparing Mihomo and Xray handling of VLESS/Reality 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.
- Xray-core is not a Clash client and not Mihomo.
- A VLESS Reality link working in an Xray client does not guarantee direct Clash import.
- Share-link parsing differs across clients.