Short answer

Snell is common in some Apple-ecosystem clients and provider profiles, with version, PSK and obfuscation options being key. 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, snell 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: snell
server / port
psk
version
obfs-opts
udp

When to Use It

The subscription explicitly provides Snell nodes.
The iOS or macOS client states Snell support.
The provider requires a specific Snell version.

Support Checks Checks

The version must match the server.
Wrong PSK or obfs host often appears as a handshake connection symptom.
Not every Clash/Mihomo GUI fully supports Snell.

Minimal Shape

proxies:
- name: "snell-node"
  type: snell
  server: server.example.com
  port: 443
  psk: "pre-shared-key"
  version: 3
  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

Snell in Mihomo docs

Snell Protocol