Protocol comparison
Trojan and VLESS can both appear inside TLS-oriented proxy deployments, but Trojan authenticates with a password while VLESS uses an identity such as a UUID and may use TLS or REALITY.
Technical review: 2026-09-03 · PublicVPNList Editorial Team
Trojan establishes TLS and authenticates with its protocol password. VLESS delegates confidentiality and server authentication to its configured security layer, then uses its VLESS identity. A credential from one cannot be pasted into the other.
Trojan is commonly TCP with TLS and can be wrapped by supported transports. VLESS has a broad Xray ecosystem including TCP, WebSocket, gRPC and XHTTP plus REALITY and flow options. Compatibility must be checked at the client version, not inferred from the URL alone.
Trojan can be simpler when a conventional certificate-backed TLS deployment is wanted. VLESS is appropriate where its specific Xray transports or REALITY are deployed. Neither is automatically a full-device VPN; client TUN mode supplies that routing.
| Decision point | What to verify |
|---|---|
| Handshake and credentials | Keep certificate validation on for TLS profiles. |
| Transport choices | Validate VLESS REALITY fields as a complete set. |
| Operational choice | Preserve password or UUID without analytics or logs. |
A successful configuration or connectivity result proves only the tested technical behavior at that time. It does not prove a no-logging policy, legal status, operator identity or safety for sensitive accounts. Public profiles should be used for low-risk testing with end-to-end HTTPS.
Technical source: Trojan protocol documentation.