Short answer

Hysteria is UDP/QUIC-oriented and can help on high-latency or unstable links, but it depends heavily on UDP availability. 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, hysteria 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: hysteria
auth-str
protocol
up / down
sni
obfs
ports

When to Use It

The provider supplies hysteria nodes.
UDP is available but the network quality is unstable.
The profile includes upload/download bandwidth parameters.

Support Checks Checks

Workplace, campus or some mobile networks may restrict UDP.
Wrong up/down values can hurt speed or stability.
Port hopping, obfs and SNI details should be kept intact.

Minimal Shape

proxies:
- name: "hysteria-node"
  type: hysteria
  server: server.example.com
  port: 443
  auth-str: "password"
  protocol: udp
  up: "30 Mbps"
  down: "200 Mbps"

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

Hysteria in Mihomo docs

Hysteria Protocol