Check your app’s bundled core
The generator exports YAML for compatible Clash-family clients. WireGuard/AWG extensions and MASQUE are separate capabilities. Support for ordinary Clash profiles does not establish support for every protocol available in the generator.
Check your installed core against the mihomo protocol documentation below. This guide does not claim that every release of Clash Verge, Clash Meta or another frontend supports every generated field. If a field is rejected during import, inspect the reported field and core version first.
Choose what the exported profile contains
Set Config format to Clash. The Clash protocol control selects the proxy types written to the file. Combined mode offers alternatives in one group; it does not combine two connections for more speed or automatically fix an unreachable proxy.
| Mode | Exported choices |
|---|---|
| WireGuard / AWG | A WireGuard proxy with your selected AWG extensions |
| MASQUE | MASQUE QUIC and H2 entries; AWG options do not apply |
| WireGuard / AWG + MASQUE | AWG, MASQUE QUIC and MASQUE H2 in one selectable group |
Import the YAML and choose a proxy
Use a local profile import rather than a subscription-URL field. The generated .yaml contains credentials, so keep it private. Menu labels depend on the app.
- Generate a Clash configuration and download the .yaml file. For an initial test, use All sites and the default endpoint.
- Import the local file into your client and activate that profile. If parsing fails, check compatibility instead of repeatedly registering new credentials.
- Open the Cloudflare proxy group and select an exported AWG or MASQUE entry. QUIC and H2 are separate choices.
- Configure system proxy or TUN according to your app’s documentation if you want application traffic to enter the profile. Importing a proxy alone does not necessarily route every app.
- Test a site, then inspect the client’s connection log and routing decisions. Change one protocol mode or endpoint at a time.
Understand the generated routing rules
The YAML uses rule mode. Selected IP ranges go through the Cloudflare group; remaining traffic uses DIRECT. All sites and Specific sites therefore create different route lists. Your app’s own proxy/TUN settings determine which traffic reaches those rules.
MASQUE-only export uses dedicated MASQUE endpoint settings. A manually entered WireGuard address and its ports are not interchangeable with a MASQUE connection. An “unknown proxy type: masque” error points to checking core support before changing DNS.
If a profile imports and a proxy connects but a particular application fails, check whether the application uses the system proxy and whether its destination matches the routes. Follow the troubleshooting guide for separating DNS, routing and transport failures.
Official references
Client interfaces can change. Check menu actions and protocol support against the documentation for your installed app.