VMess vs. VLESS in Shadowrocket: Encryption, Overhead, and Setup

Compare VMess and VLESS encryption, overhead, and iPhone performance, with a field-by-field guide to configuring each in Add Server.

At a glance

VMess offers protocol-level payload encryption; VLESS does not encrypt payloads itself, so connection protection depends on the security layer in use. Assuming you already have a service provider and subscription, this guide explains the differences between protocols, transports, and TLS in Shadowrocket, then walks through each Add Server field. Choose the protocol to match the server configuration: changing Type cannot turn a VMess connection into VLESS.

VMess vs. VLESS: Protocol, Transport, and Encryption

A server entry in Shadowrocket consists of several layers. VMess and VLESS are proxy protocols; TCP and WebSocket are transports; TLS is a security layer that protects the transport. These are separate settings and are not interchangeable. When using VLESS, you still need to verify the transport and TLS settings.

What to checkVMessVLESS
AuthenticationUses authentication parameters such as a UUID; older configurations may also include an Alter IDUses UUID authentication; does not use VMess Alter ID
Protocol-level payload encryptionSupports options such as AES-128-GCM and ChaCha20-Poly1305, depending on the configurationNo general protocol-level payload encryption; common configurations use encryption set to none
TransportMust match the server's TCP, WebSocket, or other transport settingsMust also match the server's transport settings
Outer security layerCan be combined with TLS; the protocol name alone does not indicate whether TLS is enabledCommon deployments rely on TLS or another specified security mechanism; do not overlook this layer
Can you just change Type?No. The server must provide an endpoint and complete parameters for the selected protocol

A UUID is an identity credential, not an encryption algorithm. Two configurations can use the same UUID yet differ completely in protocol, port, transport, or security layer. Do not assume configurations are interchangeable just because their UUIDs match.

VMess AEAD refers to authenticated encryption. Modern VMess configurations typically use an Alter ID of 0; do not copy nonzero values from older documentation into a new configuration. VLESS has no corresponding Alter ID parameter, and you should not add one just to fill in a field.

Encryption and TLS: none Does Not Mean the Entire Connection Is Unencrypted

To determine whether a connection is encrypted, consider the full protocol stack. In VLESS, none describes the protocol's own encryption setting. If TLS is correctly configured on the outer layer, traffic is still encrypted between the client and the TLS termination point. Conversely, port 443 does not prove that TLS is enabled; the port number only identifies where the service is listening.

443
A common TLS port is not a TLS toggle
0
Common Alter ID value in modern VMess configurations
3 layers
Check the proxy protocol, transport, and security layer separately

The comparison below applies only to configurations that explicitly use standard TLS. If your existing configuration uses another security mechanism, keep its original parameters rather than applying standard TLS toggle combinations. TLS certificate validation verifies the identity of the endpoint; disabling validation is not a routine way to fix certificate issues.

TLS enabled with certificate validation

Recommended

For connections where the server explicitly provides standard TLS. Keep certificate validation enabled, and make sure Server Name matches the server requirements and certificate name.

Use for: everyday configurations with a valid certificate and standard TLS

TLS disabled

Use only when the server explicitly requires this configuration. VLESS does not add payload encryption on its own; do not disable TLS just to clear a handshake error.

Use for: checking an existing configuration that explicitly does not use standard TLS

TLS enabled, certificate validation skipped

This may bypass certificate errors, but it also removes normal server identity verification. Fix the certificate, domain, or device time instead of leaving this setting enabled.

Use for: identifying a risky setting in an existing configuration and planning a fix

How to decide: check the security layer before comparing protocol names

When VLESS uses none, check TLS and certificate validation. When the port is 443, check the TLS toggle too. Do not save a configuration after changing only the encryption dropdown.

Transport Overhead and iPhone Performance: The Protocol Name Isn't Enough

VLESS has a lightweight protocol design, but that does not mean every VLESS connection is faster than VMess. Real-world speeds also depend on network congestion, server load, round-trip latency, packet loss, transport encapsulation, and device conditions. If VMess and VLESS connect to different servers, even a large speed-test gap cannot be attributed to the protocol alone.

VMess protocol-level encryption adds processing and data overhead; adding TLS can introduce further processing. VLESS does not perform the same payload encryption, reducing that part of the workload, but TLS, WebSocket, and other transport processing still apply. The actual difference depends on the hardware, implementation, and full configuration, so there is no universal speed improvement percentage.

  1. Keep local conditions consistent. Test on the same iPhone, using the same Wi-Fi network and location. Record cellular and Wi-Fi results separately rather than combining them.
  2. Keep the destination and routing consistent. Use the same test destination and confirm in the connection log that traffic is going through the selected server. If a rule sends the test destination through DIRECT, the result does not represent proxy speed.
  3. Separate new connections from sustained downloads. Time to first content is more sensitive to DNS, TCP, and TLS handshakes; long downloads also depend on bandwidth and congestion control. One latency figure cannot represent both experiences.
  4. Change one setting at a time. A meaningful comparison is possible only if your provider offers both protocols on the same route. Run each test three times, record the middle result, and note whether the transport and TLS settings match.

When comparing battery use on iPhone, keep screen brightness, test duration, and background activity consistent as well. A brief speed test does not predict all-day battery life. If the device gets noticeably warm, stop repeated testing and wait for it to cool before continuing; otherwise, temperature changes may be mistaken for protocol differences.

Add Server Setup: Check Each Field Against the Server Configuration

If you already have a subscription, keep the imported entry and create a copy for testing. To add a server manually, open the add menu on Home and select Add Server; the fields shown depend on Type and transport settings. Select VMess or VLESS first, then enter the remaining parameters.

Field or parameterWhat to enterCommon mistake
TypeSelect the protocol your provider explicitly specifies: VMess or VLESSChanging only the protocol name while leaving all other parameters unchanged
Address / PortEnter the server domain or IP address and the actual portPasting the full subscription URL into Address, or forcing the port to 443 whenever TLS is mentioned
UUIDEnter your authentication value exactly as provided, checking for leading or trailing spacesMissing a character when copying, or using sample credentials
EncryptionFor VMess, follow the configuration; for VLESS, keep none if requiredApplying a VMess encryption option to VLESS
Alter IDUse only with the corresponding VMess configuration; modern configurations typically use 0Copying a value from an old tutorial, or assuming a higher value is more secure
TransportMatch the actual transport, such as TCP or WebSocketAssuming every TLS connection must use WebSocket
TLS / Server NameEnable TLS as required by the server and enter the corresponding TLS nameReplacing Server Name with Address by default, causing the certificate name to mismatch
Host / PathEnter WebSocket settings exactly as provided, including the leading slash in PathConfusing Host with Server Name, or omitting the query string from Path
FlowFill this in only if the VLESS configuration explicitly requires it and the current combination supports itAdding the same value to every VLESS connection

Address is the address the client connects to; Server Name is generally used for TLS SNI and certificate name validation; WebSocket Host is an HTTP request header. They may be identical or intentionally different, depending on the server configuration. Replacing all three with the same domain can break a working configuration.

For VLESS configurations with a specific Flow or other security parameters, keep all required fields intact. If a required field is missing after import, first check whether Shadowrocket supports that combination of parameters, then confirm the configuration with your provider. Do not remove key parameters to “simplify” it into ordinary VLESS.

Can't Connect After Import? Check Authentication, Handshake, and Transport in Order

An enabled connection switch only means the client has started processing the connection; it does not prove that the selected server has authenticated successfully. Keep the original entry while troubleshooting. Select the entry to test on Home, and temporarily use Proxy under Global Routing to isolate rule effects. Restore your usual Config afterward.

“VMess works. Why does changing Type to VLESS break the connection?”

Restore the original Type. VMess and VLESS use different handshake and authentication formats, so the server must provide a separate, matching VLESS configuration. Get the corresponding parameters from your provider and add a new entry; do not overwrite a VMess entry that still works.

“The port is 443. Why am I still getting a TLS error?”

Check that TLS is enabled as specified, then verify Server Name, certificate validity, and the device date. On iPhone, check the time settings under Settings → General → Date & Time. If the certificate has expired, the server needs to be fixed.

“The latency test shows a value, but webpages won't load. Why?”

First confirm that you ran a latency test, not a full webpage load, then check the routing record for the current connection. If traffic is going through DIRECT, temporarily switch Global Routing to Proxy and test again. If it is already using the selected server, check DNS, authentication, and transport parameters.

“Why did my manually edited fields change after a subscription update?”

A subscription entry may be regenerated during an update. Keep the original subscription entry and create a separate local copy to test your changes. Ask your provider to correct the subscription content. Do not assume a temporary edit has changed the server configuration.

Errors also need to be understood by layer. If authentication fails immediately, check the UUID, Type, and VMess authentication parameters first. For a TLS handshake failure, check the security layer. If WebSocket returns a 404, 400, or similar response, verify Host, Path, and reverse proxy settings. These are troubleshooting priorities, not definitive causes based on an error code alone.

Choosing and Keeping a Configuration: Preserve All Required Parameters

If your only working configuration is VMess, keeping it is more reliable than changing the protocol yourself. If your provider offers both protocols, first confirm that each can establish a stable connection, then compare time to first content, sustained transfers, and failure rates under the same conditions. Do not decide based only on a shorter name, a newer protocol, or a single speed test.

Bottom line: Keep the Working Entry, Then Test One Variable at a Time

Keep the original subscription entry and create a copy for the candidate configuration. Change one setting at a time and use logs to confirm the actual route. If authentication or handshake errors occur, restore the original value rather than layering multiple problems into the same entry.

Download Shadowrocket