VMess vs. VLESS vs. Trojan vs. Shadowsocks: Proxy Protocols Compared

Compare encryption, handshake overhead, transport options, and REALITY support across four popular proxy protocols, with practical guidance for everyday browsing, mobile networks, and low-powered devices.

At a Glance

If you already have a subscription, first confirm the complete configuration provided by the server, then choose a client core that supports that exact combination. If you control both ends, compare connection setup time, recovery after interruptions, and device load. This guide is for readers who want to reuse a configuration across desktop and Android, or decide whether switching protocols is worthwhile.

Authentication and Encryption Across Four Protocols

Protocol, transport, and transport security are three separate settings. The protocol defines how the peers exchange requests and verify identity; the transport determines how bytes are delivered, such as over raw TCP or WebSocket; and a security layer such as TLS protects the connection. Two nodes on the same port can use entirely different combinations.

Trojan

Recommended

If the server maintains a trusted certificate and explicitly offers Trojan access, try the configuration it provides first. A typical setup sends proxy requests over a TLS connection, with the server authenticating the client using a password. The client must still verify the server certificate.

Best for: everyday browsing with an existing, stable Trojan over TLS service

VMess

VMess uses a UUID to identify users and defines its own authentication and encryption mechanisms. Existing VMess over WebSocket deployments can continue to be used; if TLS is added, verify the domain, certificate, and path separately. If authentication fails, check the system clock as well.

Best for: keeping a proven VMess configuration without rebuilding the server for migration

VLESS

Common configurations use a UUID. When the client's encryption is set to none, data is not protected by protocol-level encryption, so verify the security layer used in the actual setup. For a REALITY configuration, kernel support for VLESS alone does not guarantee compatibility.

Best for: setups where the server provides a complete configuration and the client core supports the exact combination

Shadowsocks

Shadowsocks protects proxy traffic using a shared key and a specified encryption method. Traditional AEAD methods and Shadowsocks 2022 methods are not interchangeable, and their key formats may differ. A basic setup does not need a separate TLS layer, but deployments with an additional transport require a separate compatibility check.

Best for: setups where both ends support the same method and you want to connect with fewer configuration options

Rule Out Incompatible Combinations First

Before comparing speed, note the protocol, transport, and security layer provided by the server. If the client does not support any part of the setup, remove that combination from consideration first; a speed test cannot fix a protocol mismatch.

Handshake Overhead and What a Port Tells You

443
The default HTTPS port does not determine the proxy protocol
1 RTT
Typical overhead for a standard initial TLS 1.3 handshake, excluding TCP setup
128 / 256 bits
Key lengths for AES-128-GCM and AES-256-GCM

RTT is the time required for a round trip. When establishing a new TLS connection over TCP, TCP setup comes first, followed by the TLS handshake. WebSocket using an HTTP/1.1 Upgrade also requires an upgrade request. By contrast, a basic Shadowsocks TCP connection without an additional TLS layer does not require a TLS handshake, but still incurs TCP setup, proxy processing, and the cost of connecting to the destination server. The figures in the tiles describe protocol requirements and configuration, not benchmark results for the four protocols.

Transport Options and REALITY Support

REALITY is not a fifth protocol alongside these four. When reading a configuration, break a common VLESS with REALITY setup into two parts: protocol is set to VLESS, and streamSettings.security is set to REALITY. Use the server provider's details for the server name, key-related parameters, and short ID. A standard TLS node cannot be turned into a REALITY node just by changing the client's security setting.

When troubleshooting a WebSocket node, check the path, HTTP Host, and TLS server name separately. The path matches the service endpoint, Host may be used for reverse-proxy routing, and the TLS server name affects the handshake and certificate verification. These values may happen to use the same domain, or the server may specify them separately. If certificate verification fails, fix the domain or trust chain rather than disabling verification.

Everyday Browsing, Mobile Networks, and Low-Powered Devices

Evaluate the Same Candidate Configurations in Each Usage Environment

Desktop Browsing and Low-Powered Devices
  • Use v2rayN to verify your existing connection first, then compare another setup offered by the same server. If the current configuration is stable, there is no need to switch just for a different protocol name.
  • Open the same webpage and download the same file, recording first-response time, transfer speed, and CPU usage. Pause other demanding tasks when measuring CPU usage.
Android on Mobile Networks
  • Use v2rayNG or v2flyNG to filter options by core compatibility, then open the same test page over both Wi-Fi and a cellular network.
  • After switching networks, send a new request and note recovery time and failures. Do not assume a TCP-based connection will remain active when the device's network address changes.

Change one variable at a time. If you cannot keep the server fixed, record the results as a comparison between two connection setups rather than attributing the difference to the protocol alone.

If only one app cannot connect, first check whether its traffic is being routed through the proxy. The desktop system proxy affects only apps that follow that setting, while Android per-app settings may exclude the app being tested. Retry with the same app and identical routing and DNS settings before assessing the protocol. If the logs show an authentication failure, check the UUID, password, or encryption method. If they show a timeout, first check the address, port, and network reachability. These errors require different troubleshooting steps.

Download clientsChoose v2rayN or v2rayNG for your platform