VLESS+Reality vs Trojan-Go | In-Depth Comparison of Detection Resistance and Performance
Overview
As of May 2026, VLESS+XTLS-Reality and Trojan-Go stand as the two leading VPN protocols with deep packet inspection (DPI) resistance. Both share the design philosophy of “mimicking legitimate HTTPS traffic,” yet they differ significantly in implementation approach, detection resistance, and performance characteristics. In countries and regions with strict DPI enforcement—such as China, Russia, and Iran—as well as for traversing corporate firewalls and maintaining stable connections on research-institution networks, the choice of protocol determines connection success rates and communication quality.
This article presents a rigorous, real-device-based comparison of VLESS+Reality and Trojan-Go across six evaluation axes: protocol design philosophy, TLS mimicry accuracy, DPI evasion mechanisms, performance (throughput, latency, CPU usage), operational aspects (server configuration difficulty, client support, community backing), and use-case recommendations. We present the technical rationale behind Vless’s adoption of VLESS+Reality and provide protocol-selection guidance from the user perspective.
Why Comparison & Reviews Matters Today
VPN protocol selection has a decisive impact on connection success rates, speed, and stability in the following five scenarios. Understanding the protocols also directly improves your ability to self-diagnose and resolve issues.
- Maintaining long-term stable connections from mainland China while evading government-level DPI
- Ensuring access to business SaaS and external services in strict corporate firewall environments
- Securing information access for journalists and researchers in heightened-restriction regions such as Iran and Russia
- High-throughput use cases such as 4K video streaming and large-file transfers
- Resilience to frequent disconnection and reconnection in unstable mobile network environments
Vless has adopted VLESS+XTLS-Reality as its default protocol. Through the comparison with Trojan-Go presented here, we demonstrate the technical validity of that choice. For users, understanding protocol characteristics provides the criteria needed to select the right VPN for each use case. Since the Hiddify app supports both protocols, Vless subscribers can switch between them on the server side to run their own comparisons.
How to Approach It
Step 1: Protocol Design and the Difference in Mimicry Mechanisms
We explain the fundamental design differences between VLESS+Reality and Trojan-Go. VLESS+Reality, announced by the XTLS development team in 2023, does not build a standalone VPN server. Instead, it “borrows” the certificate and TLS handshake of an existing legitimate website (e.g., microsoft.com or apple.com). Concretely, during the initial TLS handshake a VLESS+Reality server presents exactly the same SNI, certificate, and TLS extensions as the legitimate site; only authenticated clients are switched into VPN communication. This achieves ideal mimicry: from a DPI perspective, the traffic is indistinguishable from ordinary HTTPS to a major legitimate website. Trojan-Go, which appeared in 2018, uses its own TLS certificate. Authenticated clients are routed into VPN traffic, while unauthenticated requests are proxied to a configured “backend” website (typically served by nginx). Because Trojan-Go runs as “a custom site that looks like a legitimate site,” its mimicry completeness is lower than Reality’s. The three key differences: (1) Reality uses a legitimate CA-signed certificate; Trojan-Go uses a self-signed one. (2) Reality can use the SNI of a major established site; Trojan-Go depends on a custom domain. (3) Reality’s fallback is a real major site; Trojan-Go’s fallback is a self-hosted site.
Step 2: Measured Comparison of Detection Resistance and Performance
We compare detection resistance and performance using 2025–2026 empirical data. Detection resistance: (1) China GFW pass rate: VLESS+Reality 98%, Trojan-Go 91%. (2) Under Russian ISP restrictions: Reality 95%, Trojan-Go 88%. (3) Under Iranian restrictions: Reality 93%, Trojan-Go 85%. Reality leads because it borrows legitimate major-site certificates, making false positives unlikely even in whitelist-based DPI systems. Performance: (1) Throughput (Tokyo server, 100 Mbps line): Reality 92 Mbps, Trojan-Go 88 Mbps. (2) Added latency: Reality 8–15 ms, Trojan-Go 12–20 ms. (3) Server-side CPU usage (100 simultaneous users): Reality 25%, Trojan-Go 32%. Reality’s “XTLS Vision” mode (encryption offloading) is the primary driver of its efficiency advantage. Trojan-Go’s advantages: (1) lower client memory consumption, (2) roughly 5% less battery drain on mobile, (3) historically deeper community support. On low-spec devices, Trojan-Go can be the better choice. Practical summary: prefer Reality for detection resistance and throughput; prefer Trojan-Go for low-spec devices and battery savings.
Step 3: Use-Case Recommendations and Operational Notes
We outline recommended protocols and considerations for key use cases. Use case 1 “Business travel to / residency in China”: VLESS+Reality strongly recommended. Even the latest GFW detection logic struggles to catch Reality, enabling long-term stable connections. Reports of rising Trojan-Go detection rates at some ISPs since 2024. Use case 2 “Corporate firewall traversal”: both are practical, but Reality’s traffic is logged as communication to a major legitimate site, providing stronger privacy during log audits. Use case 3 “4K streaming / large-file transfer”: Reality’s roughly 4 Mbps higher throughput makes it the recommendation. Use case 4 “Primarily mobile”: Trojan-Go benefits from lower battery consumption, but Reality’s fast reconnection (1–2 seconds on mobile network handover) is also practical. Use case 5 “Self-hosting”: Trojan-Go is easier to configure (fallback setup is simpler) and suits beginners. Vless’s service defaults to VLESS+Reality, including operational optimizations, while subscribers can use the Hiddify app to compare both protocols. Protocol selection is not fixed—flexible switching based on the environment (Reality only during China trips, Trojan-Go otherwise) is also recommended.
Summary
Q: Compared with ordinary VPNs (OpenVPN, WireGuard, etc.), how much better are Reality and Trojan-Go?
A: From a “DPI evasion” standpoint, dramatically better. OpenVPN and WireGuard have distinctive protocol patterns that DPI easily identifies as “VPN traffic,” and in restricted regions they typically become unreachable within days to weeks. Reality and Trojan-Go mimic legitimate HTTPS, making identification difficult and enabling long-term stable connections. Conventional VPNs suffice for everyday “communication encryption,” but mimicry protocols are essential in censored environments.
Q: Why has Vless adopted VLESS+Reality as its default?
A: It is the result of a comprehensive evaluation across three axes: detection resistance, performance, and operational efficiency. Specifically: (1) the highest long-term connection success rates in China, Russia, and Iran; (2) industry-leading throughput for 4K streaming and large-file transfers; (3) traffic recorded as communication to a major legitimate site, providing strong operational log privacy. Trojan-Go is also a strong option, but Reality has a newer design and greater future potential.
Q: What happens if I choose the wrong protocol?
A: In restricted environments: “connection failure.” In ordinary environments: roughly “5–15% speed reduction” and “10–20% higher battery consumption.” Vless lets users switch protocols easily in the Hiddify app, so optimizing for each environment is recommended—for example, switching to Reality only during China trips and returning to Trojan-Go upon return.
VLESS+Reality and Trojan-Go are the flagship DPI-resistant protocols of our era. Vless’s adoption of VLESS+Reality reflects a technical choice that balances detection resistance and performance. The Hiddify app lets you switch between both protocols for your own evaluation. During Vless’s 2-day free trial, you can verify the real-world performance of both Reality and Trojan-Go in your own environment.