Proxy setup

Clash V2Ray Subscription Import Guide 2026

Match URI/Base64 node subscriptions, Clash/Mihomo YAML, or sing-box JSON to your client. Follow v2rayN and Clash Verge Rev setup guides and troubleshoot imports, routing, and DNS.

Updated: 2026-10-25

View node subscriptions and formats

Direct Answer

Choose the client for your input: v2rayN accepts supported URI/Base64 node subscriptions, Clash Verge Rev uses Clash/Mihomo YAML, and native sing-box uses JSON compatible with its core version. These formats are not interchangeable.

Choose the client

Use v2rayN for supported node subscriptions or Clash Verge Rev for compatible Clash/Mihomo YAML with proxy groups and rules. Check protocol and core-version support before importing.

Import subscriptions

A successful fetch does not prove format compatibility or connectivity. This project provides ordinary node subscriptions, not ready-to-use YAML or native sing-box JSON profiles.

Fix routing issues

Check the node and proxy mode, then investigate rules, DNS, and protocol parameters using the reported error. Change one setting at a time; global mode does not guarantee that every app is routed through the proxy.

Steps

Identify URI/Base64, Clash/Mihomo YAML, or sing-box JSON input and follow the matching client guide below.
Use the supported subscription or profile import option. Obtain a compatible configuration or prepare it locally; do not submit private subscriptions to public converters.
Update the subscription or profile and check that the expected nodes or groups appear. Fetching successfully does not prove that a node works.
Select a node or group where available, enable the documented system-proxy or VPN mode, and test actual access.

Checklist

The subscription is reachable and its format matches the client and core version.
System time and certificate validation are correct.
System proxy, TUN, or VPN mode is enabled.
DNS is not controlled by another app or browser setting.

Troubleshooting

Subscription refresh fails

For fetch errors, check the URL and network. For parse errors, check the required format and core version, then investigate proxy loops.

Rule mode breaks some sites

If supported, compare with global mode, then check the affected app, routing rules, and DNS. The mode name alone does not prove traffic coverage.

Connected but no traffic

Check system proxy, route mode, and node parameters.

Node subscription addresses GitHub primary and Cloudflare backup, with the same ordinary subscription format. v2rayN setup Import supported node subscriptions and check the connection. Clash Verge Rev setup Import compatible Clash/Mihomo YAML and check proxy groups and rules. sing-box configuration Use native JSON compatible with the installed core. Shadowrocket Android Android proxy client setup. VPN leak test Verify the connection. Stable VPN trials Move beyond free nodes.

FAQ

Should I choose Clash or V2RayN?

Choose by format: v2rayN accepts common node subscriptions, while Clash Verge Rev uses Clash/Mihomo YAML. Both require compatible protocols, core versions, and routing settings.

What is the difference between global and rule mode?

Rule mode follows the configured routing rules. Global-mode coverage depends on the client and its system-proxy or VPN integration; it does not guarantee that every app uses the proxy.

Why can subscriptions fail to refresh?

Fetch errors can involve an incomplete or expired URL, network access, or proxy loops. Parse errors can indicate a format or core-version mismatch.