If a subscription includes multiple protocols, first check whether your device can run the node's complete configuration. Then compare how quickly pages load initially, how long connections take to recover after a network change, and how much load each option puts on your device. There's no need to switch from a stable node just for a different protocol name. For a new node, use the table below to check encryption, transport, and core support, then test it against your needs.
Protocol Comparison: Encryption, Handshakes, and Transport
Think of a node in three layers: VMess and VLESS are proxy protocols; TCP and WebSocket determine how data is transported; TLS and REALITY define how a connection is protected and authenticated. For example, “VMess + WebSocket + TLS” is not a choice between three protocols—it's a combination that must match on both ends. Handshake overhead also depends on the combination: opening a TCP connection, establishing a TLS session, and upgrading to WebSocket can all add to initial connection time. Reusing an existing connection avoids repeating those steps.
| Protocol | Encryption and Authentication | Handshake and Transport | What to Check in the Client |
|---|---|---|---|
| VMess | Modern VMess uses AEAD to protect request headers; the security setting separately determines how the data is encrypted. | Can use TCP or WebSocket; enabling TLS adds a separate TLS connection handshake. | Check the UUID, system time, transport type, and whether the node still relies on an older authentication configuration. |
| VLESS | A common encryption=none configuration uses a UUID to identify the user; VLESS itself does not encrypt traffic. Use matching TLS, REALITY, or another secure configuration for traffic over the public internet. | Common options include TCP with TLS or REALITY, and WebSocket with TLS. Vision is a flow-control mode, not a transport type. | Check that the core supports the node's specified transport, security type, and flow together; VLESS support alone is not enough. |
| Trojan | In standard use, password authentication and proxy requests are sent over a TLS channel. | A typical setup uses TCP with TLS. The proxy request is sent after TLS is established, with no separate password-negotiation round. | Check the password, server name, and certificate validation. If importing a less common transport variant, confirm that the core supports it. |
| Shadowsocks | With AEAD, the protocol encrypts and authenticates data. Both ends must use matching encryption methods and keys. | A native TCP configuration does not require a separate TLS handshake. If the node adds another encapsulation layer, account for the overhead of that specific setup. | Check which method is used—legacy AEAD or Shadowsocks 2022—the key format, and whether UDP forwarding is needed. |
TLS protects the connection between the client and proxy server; it does not turn HTTP traffic to the destination website into HTTPS. A node using port 443 does not necessarily use TLS, and the port alone says nothing about its protocol or speed.
Choosing for Everyday Browsing, Mobile Networks, and Low-Powered Devices
These recommendations assume the nodes come from the same service and the server has the corresponding configurations enabled. You can't change an existing node's protocol on the client side alone. Differences between servers, egress points, and routes also shouldn't be attributed to the protocol itself.
Choose from the Configurations Available to You
VLESS: Try It First When Both Ends Are Compatible
RecommendedIf both desktop and Android can run the same configuration provided by the server, use it as your baseline for everyday browsing. Import it with TLS if that's what the server specifies. If it specifies REALITY or Vision, confirm that your core supports the required settings.
Best for: choosing a new everyday node when compatibility has been confirmed on all your regular devices
VMess: Keep a Subscription That Works
If you already have a stable VMess node using WebSocket and TLS, check the hostname and path when moving to another client. If it fails only on a new device, check automatic date and time settings and the time zone first, then review the logs. There's no need to switch protocols as a first step.
Best for: keeping your existing subscription and minimizing configuration changes when switching devices
Trojan: Use an Existing TLS Node
If the server provides a standard Trojan configuration, consider it for mobile networks. Test it on Wi-Fi, mobile data, and after switching between the two. An existing TCP connection usually has to be re-established after a network change; switching to Trojan won't eliminate that.
Best for: testing recovery on mobile networks when a TLS node is already available
Shadowsocks: Compare Load on Low-Powered Devices
If the server offers a native AEAD configuration, use the same download task to compare client CPU usage and device temperature. Encryption acceleration varies by processor, so fewer layers do not necessarily mean lower power consumption.
Best for: low-powered devices and long-running sessions, after confirming the method and UDP support
Client Compatibility: Check the Actual Core and Node Fields
A successful import only means the client accepted the link; it doesn't guarantee the core can start with that combination. Check the protocol, transport, and security settings together, especially when a subscription works on one device but fails on another.
- v2rayN: On desktop, open the imported node's edit window and check fields such as “Transport Protocol” and “Transport Layer Security.” Names can vary by version; check the core identifier in the logs after startup. If the server specifically requires Xray's REALITY or Vision, make sure the node is using an Xray core that supports that combination.
- v2rayNG: In the Android configuration list, tap the node's edit icon and check its address, port, transport, and security settings. It uses the Xray core, but whether your installed version recognizes the subscription's options depends on the edit screen and startup logs.
- v2flyNG: It uses the v2fly core. Don't assume it supports everything listed for v2rayNG. For nodes with Xray-specific settings, use a configuration the provider explicitly says is compatible rather than deleting parameters to force an import.
When checking port, UUID, or key fields, first identify what each one is for. The fixed values below are for checking formats—not node speed test results or recommended defaults to enter manually.
2022-blake3-aes-128-gcm2022-blake3-aes-256-gcmBottom Line: Troubleshoot Startup Failures Separately from Slow Speeds
After switching to a node that fails, check the first error logged at that time. If the log reports an unsupported field or encryption method, check the core version and subscription settings. If the core starts normally, check whether the system proxy or Android VPN is routing traffic from the app you're testing; compare connection speeds only after that.
How to Test Speed: Measure Initial Loads, Reconnection, and Throughput Separately
Latency figures in a client list rarely reflect how every app will feel. For browsing, the time to the first response matters most; for downloads, sustained throughput is key. When switching networks on the go, focus on how long it takes to reconnect. Ranking all four protocols by a single metric can lead to the wrong choice.
- Keep test conditions consistent. Use configurations on the same server and egress point where possible. Test with the same device, destination website, and routing rules, and make sure all candidates use the proxy. If you can't keep the egress point fixed, use the results only to choose between the nodes available to you.
- Alternate five initial-load tests. Give each candidate the same fresh-connection conditions—for example, close and reopen the browser, disable cache in the developer tools' Network panel, and record the main document's time to first byte. Compare medians and track timeouts separately; don't count failed attempts as zero milliseconds.
- Test recovery after switching networks on its own. On a phone, switch from Wi-Fi to mobile data. Once the system shows the new network is connected, measure how long it takes for a webpage to respond successfully. Repeat three times per candidate, distinguishing “client is running” from “apps are actually back online.”
- Use the same file to measure throughput. Choose the same large test file and compare sustained download speeds. On a low-powered device, use the same 30-second observation window and note process CPU usage. Keep routing rules and VPN mode unchanged so differences in traffic coverage aren't mistaken for encryption overhead.
Common Issues: Import Failures, Certificate Errors, and UDP Problems
Troubleshoot by Symptom
Why does the same subscription work on my computer but not on Android?
Open the matching node on both devices and compare the protocol, transport, security type, and flow control settings. Check first whether Android reports an unsupported option. If the fields match but the browser still can't connect, check that the Android VPN is running and that the app is included in per-app proxy routing.
Trojan reports a certificate name mismatch. Should I turn off certificate validation?
Keep certificate validation enabled. Compare the server name supplied by the provider in the subscription with the SNI in the node editor. Even if the connection address is an IP, don't remove the domain included in the subscription. If the name is correct and the error persists, ask the provider to check the certificate configuration.
Shadowsocks loads webpages, but voice calls won't connect. Why?
First check whether the voice app is routed through the proxy, then check the node, the client's traffic-routing mode, and whether the core supports UDP forwarding in the current configuration. A working webpage only confirms that the relevant web request can get through; it doesn't verify the app's UDP path. On desktop, enabling only the system proxy won't route UDP traffic for some apps.
If VLESS is set to none, should I turn off TLS too?
No. encryption=none means that a common VLESS configuration does not add encryption at the protocol layer. Transport-layer security in the node editor is a separate setting. If the subscription specifies TLS or REALITY, keep that setting and its associated parameters.