Short answer

AnyTLS is one of the newer Mihomo outbound types, using TLS fields and idle-session options, so client/core version matters. 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, anytls 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: anytls
password
client-fingerprint
sni / alpn
idle-session-check-interval
idle-session-timeout
min-idle-session

When to Use It

The subscription explicitly contains anytls.
The client bundles a recent Mihomo core.
The provider documentation names AnyTLS rather than VLESS Reality.

Support Checks Checks

AnyTLS is sensitive to client core version.
Official docs state Mihomo does not support AnyTLS+Reality; ECH is the path for hiding SNI.
TLS fingerprint, SNI and ALPN should follow the provider profile.

Minimal Shape

proxies:
- name: "anytls-node"
  type: anytls
  server: server.example.com
  port: 443
  password: "password"
  client-fingerprint: chrome
  sni: example.com
  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

AnyTLS in Mihomo docs

AnyTLS Protocol