Updated Jun 8, 2026

Clash Protocol Center

A complete map of common and newer Clash/Mihomo outbound types. Use it to understand what a subscription node name means, which fields matter, and why support depends on the client core.

Browse Protocols Protocol Support Table Outbound Docs

Read this first

Protocol support is not only a website list. It depends on the actual core bundled by your client, the subscription syntax emitted by the provider, and whether the operating system allows the required network behavior such as UDP, TUN or certificates.

How to Read This List

If a subscription imports successfully but shows node list, first check whether the client supports the protocol type.
If nodes appear but do not connect, compare TLS, SNI, Reality, WebSocket, gRPC, QUIC and UDP-related fields.
DIRECT, DNS and built-in policies are outbound behaviors, not provider-operated remote nodes.
Proxy groups organize nodes; they are not protocols themselves.

Classic and common

ssClassic proxies

Shadowsocks

One of the most common encrypted proxy node types in subscriptions, with compact fields and broad client compatibility.

Core fields: type: ss / server / port / cipher / password / udp

ssrClassic proxies

ShadowsocksR

SSR is the ShadowsocksR node format, often found in older subscriptions or providers maintaining legacy client compatibility.

Core fields: type: ssr / server / port / cipher / password / protocol / protocol-param

snellClassic proxies

Snell

Snell is common in some Apple-ecosystem clients and provider profiles, with version, PSK and obfuscation options being key.

Core fields: type: snell / server / port / psk / version

vmessV2Ray / Xray

VMess

VMess is a common V2Ray-family protocol and often appears with TLS, WebSocket, gRPC or HTTP/2 transports.

Core fields: type: vmess / uuid / alterId / cipher

vlessV2Ray / Xray

VLESS

VLESS is increasingly common in newer Xray-family subscriptions and is often paired with TLS, Reality, WebSocket or gRPC.

Core fields: type: vless / uuid / flow / tls / servername

trojanV2Ray / Xray

Trojan

Trojan commonly appears as a TLS-shaped connection. It is simpler than VMess/VLESS, but certificate and SNI details still matter.

Core fields: type: trojan / password / sni / servername / alpn

http / socksBasic outbounds

HTTP / SOCKS

HTTP and SOCKS are basic outbound proxy types, often used for chaining, LAN gateways or connecting Clash to an existing proxy.

Core fields: type: http / socks / server / port / username / password / tls

Newer and QUIC/UDP

anytlsNewer protocols

AnyTLS

AnyTLS is one of the newer Mihomo outbound types, using TLS fields and idle-session options, so client/core version matters.

Core fields: type: anytls / password / client-fingerprint / sni / alpn

mieruNewer protocols

Mieru

Mieru is a newer proxy node type in Mihomo, with TCP/UDP transport, port range, multiplexing and traffic-pattern options.

Core fields: type: mieru / server / port or port-range / transport / username / password

sudokuNewer protocols

Sudoku

Sudoku is a newer Mihomo protocol type with AEAD, padding, table and HTTP mask options.

Core fields: type: sudoku / key / aead-method / padding-min / padding-max

hysteriaQUIC / UDP

Hysteria

Hysteria is UDP/QUIC-oriented and can help on high-latency or unstable links, but it depends heavily on UDP availability.

Core fields: type: hysteria / auth-str / protocol / up / down

hysteria2QUIC / UDP

Hysteria2

Hysteria2 is the newer Hysteria generation and commonly appears as hy2 or hysteria2 in modern subscriptions.

Core fields: type: hysteria2 / password / sni / obfs / obfs-password

tuicQUIC / UDP

TUIC

TUIC is a QUIC-based proxy protocol, commonly seen in v5 profiles and best used with newer client cores.

Core fields: type: tuic / uuid / password / congestion-controller

trusttunnelNewer protocols

TrustTunnel

TrustTunnel is a newer Mihomo outbound type with TLS fields, health checks, QUIC and connection reuse options.

Core fields: type: trusttunnel / username / password / health-check / udp

VPN and tunnels

wireguardVPN / tunnels

WireGuard

WireGuard is a VPN-style tunnel that can be used as an outbound node in Clash/Mihomo, with fields closer to tunnel configuration.

Core fields: type: wireguard / private-key / server / port / ip / ipv6

tailscaleVPN / tunnels

Tailscale

The Tailscale outbound lets Mihomo route traffic into Tailnet/Headscale scenarios and is closer to networking mesh use cases.

Core fields: type: tailscale / hostname / auth-key / control-url

sshVPN / tunnels

SSH

The SSH outbound forwards traffic through an SSH server, useful when you already have an SSH jump host or private-network path.

Core fields: type: ssh / server / port / username / password

masqueVPN / tunnels

MASQUE

MASQUE is a tunnel-style outbound based around HTTP/3/QUIC ideas, with key, IP, MTU, DNS and congestion-control fields.

Core fields: type: masque / private-key / public-key / ip / ipv6 / mtu

openvpnVPN / tunnels

OpenVPN

The OpenVPN outbound connects to an OpenVPN server and includes certificate, authentication, protocol, MTU and remote DNS fields.

Core fields: type: openvpn / server / port / proto / username / password

Basic outbounds and policies

direct / dnsBasic outbounds

DIRECT / DNS

DIRECT exits directly, while the DNS outbound sends DNS requests to the internal DNS module; neither is a remote node protocol.

Core fields: type: direct / type: dns / udp / interface-name

DIRECT / REJECT / PASSPolicies and routing

Built-in Policies

Built-in outbound policies include DIRECT, REJECT, REJECT-DROP, PASS and COMPATIBLE, and are used as rule outcomes.

Core fields: DIRECT / REJECT / REJECT-DROP / PASS

select / url-test / fallback / load-balance / relayPolicies and routing

Proxy Groups

Proxy groups are not node protocols; they organize nodes for manual selection, testing, fallback, load balancing or relay chains.

Core fields: type: select / type: url-test / type: fallback / type: load-balance

Reference Sources

The protocol inventory follows the current Mihomo documentation for outbound proxies, built-in policies and proxy groups.