What’s the difference between VMess and VLESS? A quick guide to UUIDs, encryption, and alterId

Compare VMess and VLESS authentication, built-in encryption, and time checks. Learn which fields to verify when importing a proxy node.

At a glance

VMess and VLESS both use a user ID, but their authentication formats differ. VMess has protocol-level encryption and relies on clock synchronization for authentication. Common VLESS configurations use encryption=none, with the connection protected by an outer security layer. When importing a node, check the protocol, address, port, and ID first, then verify the transport and outer security settings. Don’t switch protocols to fix a single field.

Why can’t you switch protocols if the UUID is the same?

A UUID is a common format for a user ID, not a protocol identifier. The server can recognize a user only if that ID is registered in the matching inbound configuration. Changing a VMess entry to VLESS sends a different initial request, even if the address, port, and UUID stay the same. The server won’t treat it as the original request.

Import the protocol configured on the server

Recommended

vmess:// indicates VMess, and vless:// indicates VLESS. After importing a subscription, check the protocol shown for each entry. Don’t infer it from the subscription URL’s prefix.

Best for: connecting with an existing subscription or share link

Set up a separate protocol on the server

An administrator must configure a new inbound and provide the matching client settings. Keep the existing node for comparison, verify the new one works, then decide whether to migrate.

Best for: administrators providing two configurations to check device compatibility

A subscription can contain multiple protocols, and two entries can have similar names. Names are just labels in the list. To troubleshoot, open the specific entry and check its protocol and destination address. Don’t infer settings from labels like “Fast” or “Backup.” A UUID acts as a credential, so hide the full ID and subscription URL before sharing log screenshots.

Protocol-level encryption and outer TLS are separate

VMess AEAD’s authentication header and the encryption setting for the data are separate mechanisms. A VMess encryption value shown in the client editor, such as auto, doesn’t tell you whether outer TLS is enabled. In common VLESS configurations, encryption=none means VLESS encryption is disabled for that setting; it doesn’t mean the outer layer is also set to none. Available fields can vary between core versions. Don’t overwrite values supplied by the server based on an outdated guide.

Configuration layerValues to checkCommon misinterpretations
Protocol and accountVMess or VLESS, user ID, and protocol-specific fieldsThe same UUID can’t convert an entry from one protocol to another.
TransportFor example, TCP or WebSocket; WebSocket may also require a path and HostA WebSocket path and the TLS server name are separate fields.
Outer securitySecurity type and any required parameters, such as the server nameVLESS encryption=none can be used alongside outer TLS.

A destination website using HTTPS only means that the connection to the website uses HTTPS. It doesn’t replace the security settings for the connection between the client and proxy server. A port number alone doesn’t prove that TLS is enabled, either. If a handshake fails because the name doesn’t match, check the server name and address provided by the administrator instead of bypassing certificate validation.

alterId and time checks: which values need changing?

0
alterId value for modern VMess AEAD configurations
36
Character count of a standard hyphenated UUID
443
HTTPS default port—not a fixed port for proxy nodes

alterId is a legacy parameter from an older VMess authentication scheme. It isn’t part of the UUID or a connection count. Modern AEAD nodes typically use 0. If an older shared configuration has a nonzero value and won’t work with your current core, ask the administrator to confirm the server’s authentication method and provide an updated configuration. Changing the client-side value alone won’t change the server.

VMess authentication uses time information. If the client and server clocks are too far apart, authentication can fail even with the correct UUID. Devices showing different time zones aren’t necessarily a problem; what matters is whether they show the same actual time. VLESS doesn’t use VMess’s time-based authentication and has no alterId field. However, an incorrect system date can still cause certificate validity checks to fail when TLS is enabled.

Importing on desktop and Android: check the entry, then the core

A successful subscription update means the client received the subscription contents; it doesn’t mean every entry will work. An import screen showing VLESS doesn’t necessarily mean the current core version supports every option that entry requires. When troubleshooting across devices, test the same entry on both to avoid mixing up issues from different nodes.

Compare the same entry on both devices

Desktop: v2rayN
  • Open the target entry in the server list and check its address, port, user ID, and protocol.
  • Check the core and version in use, then compare the transport type and outer security fields.
  • Select the target entry, test it on its own, and review the logs for that time.
Android: v2rayNG or v2flyNG
  • v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. Supported fields depend on the core version in use.
  • After importing, check that values such as the path and server name were preserved, especially for entries you edited manually.
  • If it fails only on Android, compare the entries and cores on both devices first, then check whether the system has granted VPN connection permission.

The same subscription doesn’t mean the same runtime environment. First confirm that both devices have the same entry selected, then compare logs and core support.

Common questions after importing

VLESS shows encryption as none. Should I change it?

First check whether you’re looking at the protocol encryption field or the outer security field. If the administrator provided the entry with encryption=none, leave it as is and check outer settings such as TLS separately. Don’t change both fields.

The node uses port 443. Why is the TLS handshake still failing?

Open the entry and check the port and outer security type, then verify that the server name matches the one provided by the administrator. An open port only means the underlying connection can be established. If the logs specifically report a certificate validity error, check the system date.

It connects on my computer, but my phone says the same subscription isn’t supported. What should I do?

Compare the core names and versions on both devices, and note which field the logs report as unsupported. If the option isn’t implemented by the core, ask the administrator for a compatible node or use a client version that supports the configuration. Don’t simply delete the field causing the error.

Will switching to VLESS always make it faster?

You can’t tell from the protocol name alone. If the server provides two comparable entries, keep the device, network, test destination, and time period consistent. Alternate between the entries and test several times, then compare latency and throughput. If they use different servers or transport paths, the results can’t be attributed to the protocol alone.

Download v2rayNWindows / macOS / Android / Linux