Short answer

One of the most common encrypted proxy node types in subscriptions, with compact fields and broad client compatibility. 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, ss 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: ss
server / port
cipher / password
udp
plugin / plugin-opts
smux

When to Use It

Providers commonly include SS nodes in subscription profiles.
Useful when you want a simple and widely supported node format.
Often easier than newer protocols when a client only supports classic Clash syntax.

Support Checks Checks

Confirm the cipher and password match exactly.
If obfs, v2ray-plugin, shadow-tls, restls or kcptun is used, the client must support the plugin options too.
For games, voice or QUIC traffic, check whether udp is enabled.

Minimal Shape

proxies:
- name: "ss-node"
  type: ss
  server: server.example.com
  port: 443
  cipher: aes-128-gcm
  password: "password"
  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

Shadowsocks in Mihomo docs

Shadowsocks Protocol