Clash compatibility with popular proxy apps

Short answer: Clash directly reads mihomo-format YAML configurations and HTTPS profile URLs that return mihomo YAML, including standard Clash / mihomo YAML used by Stash. Servers and nodes from sing-box, Surge, Quantumult X, Shadowrocket, or Loon can be reused through a compatible profile URL or parameter-based node entry.

Choose the app you use now

Current app	Recommended configuration path	Node path	Details
Clash / mihomo	Use standard mihomo YAML directly	Use directly	mihomo compatibility
sing-box	Use a profile URL that returns mihomo YAML, or prepare YAML	Add supported protocol parameters	sing-box compatibility
Surge	Use a profile URL that returns mihomo YAML, or recreate nodes	Shared protocols include Snell	Surge compatibility
Quantumult X	Use a profile URL that returns mihomo YAML	Parameter-based entry also works	Quantumult X compatibility
Shadowrocket	Use a profile URL that returns mihomo YAML	Parameter-based entry also works	Shadowrocket compatibility
Stash	Use standard Clash / mihomo YAML directly	Use directly	Stash compatibility
Loon	Use a profile URL that returns mihomo YAML	Parameter-based entry also works	Loon compatibility

Three kinds of compatibility

1. Configuration-file compatibility — direct reuse of complete configurations.
2. Remote-profile compatibility — receiving mihomo YAML from an HTTPS profile URL.
3. Protocol interoperability — connecting directly to the same server.

Clash provides broad remote-profile and protocol interoperability. Product-specific settings can be recreated with mihomo YAML, Clash rules, and the corresponding features.

What can Clash import directly?

Source	Result
mihomo YAML configuration	Import directly
HTTPS profile URL returning mihomo YAML	Add the URL directly; Profile User-Agent is configurable
Standalone node links such as ss://	Convert to mihomo YAML or recreate the node from its parameters
Base64 node list	Convert to mihomo YAML before import
QR code containing an HTTPS profile URL	Scan to add a remote configuration

See the complete protocol list.

How remote requests identify Clash

When the Clash client retrieves a remote Profile or an HTTP Proxy Provider or Rule Provider, it sends this User-Agent by default:

User-Agent: clash.meta/<core> Hako/v<app>.<build> Darwin/<release> <model>

• <core> is the bundled Hako / mihomo core version.
• <app> and <build> are the Clash app version and internal build number.
• <release> is the Darwin kernel release, not a product version such as “macOS 26” or “iOS 26.”
• <model> is the Apple hardware model identifier, not the device name chosen by its user.

The current clients produce values in this form:

macOS  clash.meta/1.19.30 Hako/v1.0.2.33 Darwin/25.6.0 Mac16,5
iOS    clash.meta/1.19.30 Hako/v1.0.1.1 Darwin/25.6.0 iPhone18,2
tvOS   clash.meta/1.19.30 Hako/v1.0.3.1 Darwin/25.6.0 AppleTV6,2

The Profile or Provider server receiving the request can see these version and device details. The header does not contain an account, a user-assigned device name, or an advertising identifier, but it does expose the exact app build, Darwin release, and hardware model.

A custom or compatibility User-Agent selected for the Profile replaces the default form. When a Provider explicitly configures a User-Agent request header, the Provider value takes precedence. The value seen in server logs can therefore differ from the default above.

Frequently asked questions

Can I reuse my Shadowrocket remote profile?

Yes when the provider returns mihomo-compatible YAML from the HTTPS profile URL. Recreate Shadowrocket rules, modules, and app settings with Clash rules and the corresponding features. See the dedicated Shadowrocket compatibility guide.

Can I use the same provider profile URL?

Yes, if the provider can return mihomo-compatible YAML. Clash can change its Profile User-Agent for panels that select an output format by client name.

Can I keep using the same server?

When the protocol and all required parameters are supported, the same server works directly.

Does compatibility mean affiliation?

Brand names identify configuration and protocol compatibility. Clash and Hako are developed and maintained independently.