Practical position
Many iOS clients use built-in or proprietary implementations. They may support Clash-compatible profiles, their own rule syntax or subscription links, but protocol support depends on the client version.
Positioning
Client-specific syntax, Clash-compatible profiles or converted subscriptions.
| Item | Meaning |
|---|---|
| Status | Client-specific |
| Profile format | Client-specific syntax, Clash-compatible profiles or converted subscriptions. |
| Protocol check | Use the core/protocol matrix |
Best Use Cases
- Using iOS clients such as Shadowrocket, Quantumult X or Stash.
- When a subscription works on desktop but has a problem on iOS.
- Checking whether an App Store client supports a newer protocol.
Compatibility Notes
Protocol support depends on the selected core, client build, operating-system permissions and profile syntax. Treat provider subscription names as hints, then verify the actual parsed node fields in the client log.
- An iOS client can support part of Clash syntax without using Clash in its name.
- Supporting Clash subscriptions does not mean supporting every Mihomo protocol.
- iOS network permissions, VPN mode and certificate limits affect behavior.