Protocol, transport, and security are not the same thing.

In the app, a connection is assembled from multiple layers. The user-facing protocol may be VLESS, VMess, Trojan, Shadowsocks, or WireGuard. The transport may be TCP, WS, XHTTP, gRPC, Socket Custom, or V2K. Security may be `none`, `tls`, or `reality`, depending on the route.

Protocols Socket Custom V2K Public servers

Accepted inputs

What the app can import directly

Input type	Accepted by app	Typical use	Notes
vless://	Yes	Direct link import	Supports standard query fields and the custom type=v2k branch when present.
vmess://	Yes	Direct link import	Imported as a personal/custom entry when used outside the official catalog.
trojan://	Yes	Direct link import	Common with TLS and WS/gRPC style transports.
ss://	Yes	Direct link import	Used for personal import and also for public server feeds exposed inside the app.
Xray JSON	Yes	Manual/custom mode	Imported as raw JSON for advanced use; the app then adapts manual fields where possible.
.v2k	Yes	Portable config package	Supports both plaintext and protected packages, preserving advanced Socket Custom and V2K fields.

Core families

Base protocols the app understands

VLESS

Lean protocol family commonly used with TLS, REALITY, WS, XHTTP, gRPC, and now V2K. Good default for most catalog routes and advanced manual setups.

VMess

Still accepted for compatibility and import workflows, especially where legacy subscriptions or older personal setups are involved.

Trojan

Often used as a TLS-friendly route family with WebSocket or other HTTP-like transports. Supported both in manual flow and link import.

Shadowsocks

Supported for direct import and public server feeds. Especially relevant for public externally indexed servers surfaced by the app catalog.

WireGuard

Supported as a catalog/runtime family where the route defines WireGuard peer details. It is not handled through normal VLESS/VMess link parsing.

Transport layer

Transports available in the app

Transport	What it does	Typical security	When to use it
TCP	Direct stream transport with optional HTTP header behavior.	`none`, `tls`, `reality`	Simple routes or REALITY/TCP setups.
WS	WebSocket transport with host/path routing.	`tls`, `none`	Common CDN and reverse-proxy setups.
HTTP / H2	HTTP/2-style transport variants.	`tls`	Routes that are explicitly provisioned for HTTP/2 behavior.
gRPC	gRPC transport with service name and related knobs.	`tls`	Stable HTTP/2 deployments and CDN-friendly designs.
HTTPUpgrade	HTTP upgrade style flow with extra header control.	`tls`, `none`	Routes that explicitly expect HTTP upgrade semantics.
XHTTP	Xray HTTP transport with richer mode/XMUX controls.	`tls`, `reality`, `none`	Advanced HTTP-based deployments that need more control than standard WS/gRPC.
KCP	mKCP / UDP-based family.	`none`	Special cases only; less common in the app’s mainstream catalog flows.
Socket Custom	HTTP RAW payload branch implemented inside the app/runtime.	Usually `none` or `tls` depending on route	Carrier/firewall payload workflows similar to injector behavior.
V2K	Custom V2K transport family with `stream`, `poll`, and `carrier-poll` modes.	Own auth/AEAD model inside V2K settings	Advanced session tuning and carrier-sensitive fallbacks.

Security layer

Security options you will see most often

none Direct

Used when the route is intentionally plain, or when the outer disguise happens in another layer such as Socket Custom or specific HTTP-style behavior.

tls Standard secure edge

Most common security layer for standard routes. Works with SNI, fingerprint, ALPN, and mainstream CDN/proxy edges.

reality Advanced anti-censorship

Used on routes provisioned for REALITY. Requires its own public key / short ID parameters and is not interchangeable with plain TLS routes.

Positioning

Why the app is more than a stock Xray client

Custom transport work. Socket Custom and V2K are not stock “turn on and forget” presets. They are custom transport branches added on top of Xray-style connection workflows.

Config packaging. The `.v2k` format preserves advanced transport fields, protected exports, and Store publication in a way that normal link sharing does not.

Catalog-aware compatibility. The app understands server capability, config compatibility, CDN type, personal entries, and public server sources instead of treating every route as a generic raw text import.

If you are here for payload work, open Socket Custom. If you are here for carrier-sensitive session tuning, open V2K.

Open Socket Custom Open V2K Open public servers