By LitronSSHPublished 24 October 2026Updated 17 November 2026How we write and check our guides
VMess, VLESS and Trojan are three protocols from one family. They run on Xray, an open-source proxy platform that grew out of the V2Ray project, which is why apps often call them all "V2Ray". When this site lists one of them, its accounts come with their details and one or more share links, each with a QR code. Which of them are offered right now is shown in the list of services on the home page.
This guide explains how each one protects your traffic, what the settings on your account mean, and how to choose. For step-by-step import instructions, see Import VMess, VLESS and Trojan links.
Three layers: protocol, transport and security
It helps to think of every connection in this family as three layers stacked on top of each other. Your app and the server must agree on all three, or nothing gets through.
- The protocol (VMess, VLESS or Trojan): how your app proves which account it belongs to and where your traffic should go.
- The transport (such as WebSocket, gRPC or XHTTP): how that conversation is carried across the internet.
- The security layer (TLS, or none): whether everything is wrapped in the encryption HTTPS websites use.
The three protocols differ mainly in the first layer and share the other two, so one app handles all of them, and a share link carries every setting in one line.
VMess: the original, with its own encryption
VMess is the protocol V2Ray started with. Your account is identified by a UUID, a long random ID that works like a password. The app uses it to prove who it is, and VMess then encrypts the traffic itself, with a cipher named in the share link (usually "auto", which picks a modern one that suits your device).
So VMess normally keeps traffic encrypted even without TLS, but still use the TLS link whenever your account has one: the server's certificate proves that you reached the real server.
- It checks the time. Every connection carries a timestamp, and the server rejects clocks that are too far off. If your device's clock is wrong by more than a minute or two, VMess fails while other protocols still work. Turn on automatic date and time.
- Alter ID is a setting from older versions; modern VMess uses 0. The link sets it for you.
VLESS: lighter, and relies on TLS
VLESS is a newer, simpler design. It also identifies your account with a UUID, but in the usual setup it adds no encryption of its own (vless:// links normally contain the setting encryption=none). After the UUID check it passes your data through with very little extra work. It sends no timestamp either, so a clock that is a few minutes off does not break it.
That is why VLESS is called lighter: fewer extra bytes and less work for your processor, which is welcome on an older phone.
Trojan: a password inside HTTPS
Trojan adds no encryption of its own either. It was designed to sit inside an ordinary TLS connection, the kind your browser opens to any HTTPS website. Your app connects with TLS, then sends a hash of your account's password (a scrambled fingerprint of it, not the password itself), followed by your traffic.
The result is privacy: anyone watching the local network, such as other people on a public Wi-Fi, sees an encrypted TLS connection, not what you do inside it.
Without TLS, Trojan would send everything unencrypted, so always use a TLS link with it. Its password, like a UUID, comes inside the share link, so you never type it.
TLS, WebSocket and gRPC
TLS is the encryption behind HTTPS. It encrypts the connection and checks the server's certificate, so your app knows it reached the real server. TLS links normally use port 443. The SNI on your account is the server name your app sends at the start of the TLS handshake so the server presents the right certificate. Keep it as the server's own host, the Domain on your account.
WebSocket starts as an ordinary web request and then becomes a two-way channel. Every app in this guide supports it. It uses a path, a short part of the address such as /something, which must match the server exactly.
gRPC runs over HTTP/2, which can carry several streams over one connection. It uses a service name instead of a path.
The create form asks for a username and a duration, plus optional advanced settings. The result then lists a link for every connection the server offers, each labelled with its transport and port, for example "VMess TLS (ws · 443)", "VMess NoneTLS (ws · 8080)" or "VMess HTTP None (tcp · 2082)": start with the TLS link on port 443.
Side by side, and which to choose
| Feature | VMess | VLESS | Trojan |
|---|---|---|---|
| Account key | UUID | UUID | Password |
| Own encryption | Yes | No, relies on TLS | No, relies on TLS |
| TLS | Recommended | Always use it | Designed for it |
| Strict clock check | Yes | No | No |
| Extra work per packet | More | Very little | Very little |
| Link starts with | vmess:// | vless:// | trojan:// |
You can only choose among the ones listed when you visit: the list of services shows which of the three are offered right now. When you have a choice:
- Not sure? Start with VLESS on a TLS link over WebSocket. It is light, ignores small clock errors and works in every app listed in the questions below.
- Choose VMess if your app or an existing config only supports VMess, and keep your device's clock set automatically.
- Choose Trojan if you prefer a password to a UUID. It is as light as VLESS and also needs TLS.
- Connection drops often over WebSocket? Try another link from your result, such as gRPC or XHTTP (the newer name of SplitHTTP, labelled SPLIT in your result) if it lists one, and compare.
On a good line the three feel much the same; the distance to the server and your own connection matter more (see Choose a server location). Whichever you pick, follow your network's terms and the law, and keep to our acceptable use policy.





