Which clients should use the Clash feed?

Use the Clash feed with Clash Verge Rev, FlClash, and other Mihomo-compatible clients that import remote YAML profiles.

What should I do if the Clash profile imports but nodes do not connect?

Refresh the profile, switch regions, and compare with the live status page before changing local client settings.

Clash Guide

Use https://raw.githubusercontent.com/Au1rxx/free-vpn-subscriptions/main/output/clash.yaml as the primary Clash subscription URL.

Use this page when you need a Clash YAML subscription URL that can auto-update inside Clash Verge Rev, FlClash, or other Mihomo-compatible clients.

https://raw.githubusercontent.com/Au1rxx/free-vpn-subscriptions/main/output/clash.yaml

Use the raw URL if your client supports automatic refresh. Use the latest release asset if you want a stable downloadable file instead.

Open your Clash-compatible client and go to the profile or subscription area.
Create a new remote profile, subscription, or profile from URL entry.
Paste the Clash subscription URL exactly as shown above.
Import the profile, then trigger a manual refresh once the first sync completes.
Choose a node that shows healthy status and apply your preferred routing mode.

Make sure your client actually supports remote YAML subscriptions instead of single-node imports only.
Refresh the profile after the first import so the newest public nodes are pulled in.
If one region is slow, switch nodes before changing global app settings.
If every node fails at the same time, compare with the live status page before assuming your client is broken.