Protocol Support Table

Compare cores, clients and protocol types in one place before troubleshooting missing nodes or unsupported subscription fields.

How to use this table

This is a practical compatibility map for choosing a client and troubleshooting subscriptions. “Yes” still means you must check the exact client build, core version and provider syntax.

Protocol Support Table

Protocol / TypeClashPremiumMihomosing-boxXray-coreV2Ray-coreiOS clientsNotes
ShadowsocksYesYesYesYesYesYesCommonClassic SS nodes have broad compatibility.
ShadowsocksRYesYesYesUsually noUsually noUsually noPartialSSR mainly appears in older subscriptions.
SnellYesYesYesUsually noUsually noUsually noPartialOften seen in Apple-oriented or older profiles.
VMessYesYesYesYesYesYesCommonCheck TLS, WS, gRPC and transport fields.
VLESS / RealityNoNoYesYesYesPartialPartialReality, flow and fingerprint fields are version-sensitive.
TrojanYesYesYesYesYesPartialCommonSNI, ALPN and certificate verification matter.
AnyTLSNoNoYesYesUsually noUsually noLimitedNewer protocol; verify core version first.
MieruNoNoYesUsually noUsually noUsually noLimitedOne of the newer Mihomo types.
SudokuNoNoYesUsually noUsually noUsually noLimitedMihomo docs list type: sudoku.
Hysteria / Hysteria2NoNoYesYesUsually noUsually noPartialDepends heavily on UDP/QUIC availability.
TUICNoNoYesYesUsually noUsually noPartialv5-style configs are version-sensitive.
WireGuardNoYesYesYesUsually noUsually noPartialPremium, Mihomo and sing-box syntax differ.
TailscaleNoNoYesEndpoint supportUsually noUsually noLimitedCloser to tunnel/endpoint capability.
SSHNoNoYesYesUsually noUsually noLimitedOften used for chaining or tunneling.
MASQUENoNoYesUsually noUsually noUsually noLimitedModern Mihomo outbound type.
TrustTunnelNoNoYesUsually noUsually noUsually noLimitedModern Mihomo outbound type.
OpenVPNNoNoYesUsually noUsually noUsually noLimitedHandled as a Mihomo outbound type.
HTTP / SOCKSYesYesYesYesYesYesCommonBasic outbound or chained proxy.
DIRECT / DNS / PoliciesYesYesYesSimilar featuresRouting featuresRouting featuresClient-specificNames can look similar while syntax differs.

Decision Rules

  • For most modern Clash-compatible clients, start from Mihomo compatibility.
  • For sing-box clients, use sing-box JSON and avoid pasting Clash YAML directly.
  • For VLESS Reality, compare Mihomo, sing-box and Xray field support before blaming the subscription.
  • For iOS clients, check the client documentation and the parsed node fields because built-in cores vary.

Reference Sources