Short answer

Hysteria2 is the newer Hysteria generation and commonly appears as hy2 or hysteria2 in modern subscriptions. 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, hysteria2 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: hysteria2
password
sni
obfs / obfs-password
ports
up / down
skip-cert-verify

When to Use It

The subscription contains hy2, hysteria2 or hysteria2://.
The provider requires Hysteria2 client capability.
UDP is available and weak-network performance matters.

Support Checks Checks

Older clients may support Hysteria but not Hysteria2.
obfs-password is not the same as password.
Certificate, SNI, port-hopping and bandwidth fields should follow the subscription exactly.

Minimal Shape

proxies:
- name: "hy2-node"
  type: hysteria2
  server: server.example.com
  port: 443
  password: "password"
  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

Hysteria2 in Mihomo docs

Hysteria2 Protocol