VMess vs. VLESS: Encryption, Performance, and How to Choose a Subscription

Learn how VMess and VLESS differ in authentication, encryption, and transport, and how to identify protocol types in v2rayN subscriptions.

At a glance

If your subscription includes both VMess and VLESS, check the protocol type in v2rayN’s server list, then open the node details to verify the transport, security settings, and core compatibility. This guide explains how to read encryption=none and tell whether a speed difference is actually due to the protocol.

Authentication and encryption: The same UUID doesn’t mean the same protocol

Both protocols use a UUID to identify users, but that doesn’t make their configurations interchangeable. VMess and VLESS use different request formats and authentication mechanisms. Copying the same address, port, and UUID from a VMess node to a VLESS node will work only if the server has a matching VLESS inbound and all other settings are correct.

Transport settings: Check all three when choosing a node

Check these three fields separately in the node details: protocol is VMess or VLESS; transport may be TCP (called RAW in some interfaces), WebSocket, or gRPC; and transport security depends on the configuration, such as TLS or REALITY. The same protocol can use different transport combinations. If a node has a VLESS flow-control setting such as xtls-rprx-vision, keep the value provided by the subscription; it is not a universal speed boost switch.

Keep using a subscription node that’s already been tested

Recommended

Stick with a node that connects reliably and has transport security settings that meet your needs. Don’t change its type just because the name mentions another protocol. When testing an alternative, keep routing, DNS, and app proxy settings unchanged so you can pinpoint the source of any issue.

Best for: users with a working node who want to minimize variables

Try a VLESS node from your subscription

Confirm that your current core supports the node’s transport, security settings, and flow control, then test it with the subscription settings unchanged. If your current node uses VMess + WebSocket + TLS and the alternative uses VLESS + TCP + REALITY, several settings have changed at once. The results compare those two node configurations, not the protocols alone.

Best for: users with complete subscription settings who want to evaluate an alternative

Bottom line: Make sure your core supports the full configuration

If the logs show that a configuration isn’t supported, first identify whether the issue is with the transport, security settings, or flow-control field. Then choose a compatible node or core. Changing the protocol type to VMess or disabling certificate verification won’t fix a mismatch with the server’s settings.

Performance: Test connection setup and sustained transfers separately

Compared with VMess using payload encryption, VLESS with encryption=none skips one layer of protocol payload encryption and decryption. That’s a difference in processing, not a guaranteed speed increase. Results also depend on the outer handshake, transport overhead, core implementation, and the processor’s support for encryption instructions. If network throughput is already limited by the connection, reducing local processing may not improve download speeds.

128 bits
UUID length; not a measure of link encryption strength
443
Common port for remote TLS; check the node details
10808
Common local inbound port in v2rayN; verify it in the settings
  1. Keep variables constant: Use the same server, destination, transport, and transport security settings where possible. On desktop, keep the system proxy or TUN mode unchanged. If subscription endpoints use different regions or routes, note which node works better in your current environment rather than attributing the result to the protocol.
  2. Test new connections: Start a fresh connection for each test to avoid the browser reusing an existing one. Alternate between the two nodes for five tests each, recording failures and the median time to first byte for successful requests. This timing also includes the destination site’s response time; it is not a pure protocol handshake measurement.
  3. Test sustained transfers: Use the same test file to measure throughput during the steady-state phase, and monitor CPU usage by the core process. If connection times are similar but large-file throughput differs, first check for test-source throttling, network fluctuations, and CPU saturation before deciding whether to switch nodes.

Check subscription protocols in v2rayN’s type column, not the node remarks

A subscription URL fetches a list of nodes and is usually an HTTPS link. Its prefix won’t tell you which protocols the list contains. In v2rayN 7.x, go to “Subscription Group” → “Subscription Group Settings” to check the subscription source, then return to the “Subscription Group” menu to update the relevant group. Menu labels may vary slightly between builds. After updating, check the “Type” column in the server list. If it isn’t visible, double-click a node to open its settings; there’s no need to save any changes.

How to check: Identify the protocol on desktop and confirm compatibility on Android

v2rayN on desktop
  • Find the node under its group and check its type, server port, transport, and security settings. Treat the protocol name in the remarks as a label only.
  • If you have a single share link, common prefixes are vmess:// and vless://. For troubleshooting, you can record the prefix and field names, but don’t share the full link or UUID.
v2rayNG / v2flyNG on Android
  • v2rayNG uses the Xray core. Check that the current core supports the node’s flow-control or security settings before testing the connection.
  • v2flyNG uses the V2Fly core. If a node requires a specific Xray feature, its presence in the list doesn’t mean it will work. If the configuration is incompatible, use another node in the same group with supported settings.

A successful update only means the client retrieved the subscription. Verify separately that a node can start and connect.

Common issues: Wrong type, update timeouts, and lost connectivity after switching

Why does the Type column say VMess when the remarks say VLESS?

Trust the type shown in the node details. First make sure you’re checking the group you just updated, not an older group with a node of the same name. If they still don’t match, ask your subscription provider to confirm the entry. Don’t change the protocol to match the remarks.

Does a subscription update timeout mean VLESS is incompatible?

First, distinguish subscription requests from node connections. If the update itself times out, check whether the subscription URL is valid and whether the update request uses a direct connection or a proxy. If you have a working node, try updating through the proxy. Check protocol and core compatibility only after the node has been imported.

After switching nodes, websites won’t load in the browser. What should I check first?

Start the node, make a request, and check the earliest error in the core log. If the configuration won’t load, check the core first. For TLS handshake or certificate errors, verify the system clock and server name. If the core is running but the app isn’t routing through it, check the system proxy or TUN status. For apps with manually configured proxies, check the local inbound port under “Settings” → “Parameter Settings”; don’t enter the node’s remote port.

My VMess node has been stable. Should I switch to VLESS?

There’s no need to switch just because the protocol is different. Keep the working node and try a VLESS entry from your subscription with all settings included. Compare connection success rates, time to first response, and long-connection stability in the apps you use—not the peak from a single speed test. If there’s no improvement, keep the original node.

Download v2rayNChoose a platform and installer