Short answer

TUIC is a QUIC-based proxy protocol, commonly seen in v5 profiles and best used with newer client cores. In real use, trust the provider subscription first and then verify whether the selected client core supports this exact type.

What It Means

In Clash/Mihomo configuration, tuic identifies the outbound type used by the node, policy or group. The same display name in a GUI can hide different transport fields, so the YAML or subscription output is more reliable than the node nickname.

Common Fields

type: tuic
uuid
password
congestion-controller
udp-relay-mode
sni
alpn

When to Use It

The subscription supplies tuic nodes.
The provider documents TUIC v5.
UDP is available and the client uses a Mihomo/Meta compatible core.

Support Checks Checks

TUIC v4 and v5 fields may differ.
uuid, password, congestion controller and UDP relay options must match.
Blocked UDP often appears as a timeout rather than a clear status message.

Minimal Shape

proxies:
- name: "tuic-node"
  type: tuic
  server: server.example.com
  port: 443
  uuid: 00000000-0000-0000-0000-000000000000
  password: "password"
  congestion-controller: bbr
  udp: true

Compatibility Notes

Client support changes with the bundled core. A maintained Mihomo-based client usually supports more modern node types than historical Clash clients, but mobile clients and iOS alternatives still vary by app and release.

If a subscription contains this type but the client filters it out, switch to a compatible client, ask the provider for a compatible subscription format, or use a converter only when you understand what fields are being changed.

Official Reference

TUIC in Mihomo docs

TUIC Protocol