Clash for Android: How To Add Subscriptions And Switch Nodes

What You Need Before Starting

Clash for Android is a mobile proxy client that lets you import a subscription, select proxy nodes, and decide how different apps and websites should connect. The basic workflow is straightforward, but the first setup can feel confusing because the app separates profiles, proxy groups, operating modes, and the Android VPN permission. Understanding how these parts fit together will help you avoid the most common “the subscription imported, but nothing works” situation.

Before opening the app, prepare an Android phone running a reasonably recent version of Android, a Clash-compatible application such as Clash for Android or an actively maintained Mihomo-based Android client, and a valid subscription URL from your proxy provider. Clash itself does not include proxy nodes. The client is only the tool that reads your configuration and sends traffic through the servers listed in that configuration.

A subscription link commonly begins with https:// and may contain a long token. Treat that URL like a password: anyone who obtains it may be able to view your server list or consume your provider’s traffic quota. Do not post it in a public chat, screenshot it with the token visible, or paste it into an untrusted conversion website.

Understand the Main Clash for Android Sections

Names vary slightly between the original Clash for Android interface and newer Mihomo-based clients, but the underlying concepts are usually the same. The Profiles or Subscriptions screen stores configuration files. The Proxies screen displays proxy groups and individual nodes. The Logs or Connections screen helps you see whether an app is using DIRECT, a proxy group, or a selected server. The Settings area contains network, DNS, system notification, and application behavior options.

A profile is more than a list of servers. It can contain proxy definitions, proxy groups, routing rules, DNS settings, and general options. When you select a profile, Clash loads those settings into its core. If you import a subscription but never activate the profile, the nodes may appear in storage while the running service continues to use an older configuration.

Proxy groups are another important idea. A provider may give you groups named “Proxy,” “Auto,” “Fallback,” “Streaming,” or “Singapore.” A group can contain multiple nodes and may use manual selection, latency testing, fallback behavior, or automatic URL testing. Selecting a group is therefore not always the same as selecting a physical server. You may first choose a group, then choose a node inside that group.

Android also requires a local VPN service for Clash to capture application traffic. When you tap the start button, Android normally displays a system confirmation asking whether the app may create a VPN connection. This permission is separate from the subscription import. A valid profile will not proxy traffic until the Clash service is running and Android has accepted the VPN request.

Step-by-Step: Import a Clash Subscription

The following process is the practical core of Clash for Android subscription setup. Interface labels can differ between releases, so look for equivalent actions such as Add, New Profile, Import from URL, Download, or Update.

1. Copy the correct URL. Sign in to your proxy provider’s dashboard and locate the Clash-compatible subscription link. If several links are available, choose the one labeled Clash, Clash Meta, or Mihomo. Avoid copying a browser page URL or a single-node share link unless your provider explicitly says it is supported.
2. Open the profile screen. Launch Clash for Android and enter Profiles or Subscriptions. Tap the plus button or the add-profile action, then choose the URL-based import option.
3. Paste the subscription. Insert the complete HTTPS address. Check that there are no spaces before or after the link. Some Android keyboards add invisible characters when pasting, so deleting the final character and typing it again can help when a URL appears correct but fails.
4. Save and download. Give the profile a recognizable name, such as the provider name and month. Tap Download, Fetch, or Confirm. Keep the app open until the request finishes, especially when Android is restricting background activity.
5. Activate the profile. Tap the newly downloaded profile so it becomes the active configuration. A checkmark, highlighted row, or active indicator normally confirms the selection.
6. Start the VPN service. Return to the main screen and tap the start switch. Approve Android’s VPN permission dialog. If the client asks whether to allow notifications, granting that permission is useful because the persistent notification can show whether the service is still running.

After activation, open the Proxies page and check whether groups and nodes are visible. A successful import usually shows names, protocol information, or latency controls. If the profile is present but the node list is empty, the provider may have returned an incompatible format, an expired account response, or a configuration whose nodes are generated only after authentication.

If the Subscription Does Not Import

Start by testing the URL in the Android browser. The result may be a YAML document, a text download, or a provider response that the browser cannot display neatly. The important point is whether the server responds. If the browser cannot reach the address, try switching between Wi-Fi and mobile data. Captive portals, DNS filtering, expired domains, and provider-side outages can all prevent the profile download.

If the browser works but Clash reports a parse error, verify the format. A standard Clash configuration generally contains sections such as proxies, proxy-groups, and rules. A V2Ray JSON file, a raw Shadowsocks URI, or a QR-code share string may be valid for another application but not directly importable as a Clash profile. Ask the provider for the exact Clash-compatible link rather than repeatedly changing random client settings.

For TLS errors, check the phone’s date, time zone, and certificate behavior. Do not permanently disable certificate validation to force an import. If a provider’s certificate is expired or issued for a different domain, the safer solution is to obtain a corrected subscription URL from the provider. Also check whether a work, school, or public Wi-Fi network is intercepting HTTPS traffic.

How to Switch Nodes and Test Connection Quality

Once the subscription is active, node switching normally happens from the Proxies screen. You may see a top-level group such as PROXY containing several countries, regions, or server names. Tap the group first, then select the node you want. Depending on the group type, the client may immediately apply the choice or ask you to confirm it.

Do not choose a node only because its name contains a familiar location. A nearby server is often a good starting point, but actual performance depends on congestion, routing, protocol overhead, and the destination you are accessing. A node with the lowest ping may not provide the best video performance, and a server that responds quickly to a test URL may still be unsuitable for a particular streaming or gaming service.

1. Open Proxies. Locate the group used by your active rules. If you change a group that no rule references, your traffic may not change at all.
2. Run a latency test. Use the group’s test button if available. Wait for several results instead of selecting the first green number.
3. Choose a stable candidate. Prefer a node with consistent results and no repeated timeout mark. Moderate latency with reliable connections is usually better than an unstable ultra-low result.
4. Verify the active selection. Look for the checkmark or highlighted node. Then open Logs or Connections and confirm that new requests are assigned to the expected group.
5. Test a real task. Load a normal webpage, refresh an application, or play a short video. A latency test alone does not prove that DNS, HTTPS, UDP, and the target service all work correctly.

When a node fails, switch to another node in the same group before editing the entire profile. If every node fails, the problem may be the subscription, the current network, DNS resolution, or the VPN service itself. If only one website fails while other sites work, the destination may be blocking that server or the provider’s rules may be sending the request through the wrong policy.

Rule, Global, and Direct Modes Explained

Clash for Android typically offers three operating modes: Rule, Global, and Direct. The mode determines how requests are assigned, but it does not replace the node selection inside a proxy group. In other words, switching from Rule to Global may change routing behavior, while choosing a different node changes the outbound server used by proxy traffic.

Rule mode

Rule mode is the best default for everyday use. Clash examines each request against the rules in the active profile. A domestic domain may use DIRECT, an advertising domain may be rejected, and an overseas domain may be sent to a proxy group. This reduces unnecessary proxy traffic and often improves speed for local websites, banking services, shopping apps, and nearby content platforms.

Rule mode depends on the quality and order of the configuration’s rules. The first matching rule normally wins, so a broad rule placed too early can send traffic somewhere unexpected. When troubleshooting, open the connection log and read the matched rule, policy group, and final node. This is more useful than repeatedly changing servers without checking what the client actually decided.

Global mode

Global mode sends traffic through the selected proxy policy instead of applying the usual split-routing rules. It is useful for short diagnostic tests. For example, if a website fails in Rule mode, switching temporarily to Global mode can reveal whether the rule set is incorrectly classifying the domain as DIRECT.

Global mode can also be convenient on a restrictive network, but it is not always the fastest permanent choice. Local services, update servers, payment pages, and private network addresses may work poorly when every request is sent through a remote node. Remember to return to Rule mode after testing if you want normal traffic separation.

Direct mode

Direct mode bypasses the proxy and connects through the normal Android network. Use it to confirm whether the underlying Wi-Fi or mobile connection works without Clash. If a website loads in Direct mode but fails in Rule mode, investigate the selected node, proxy group, DNS behavior, or matching rule. If it fails in both modes, Clash may not be the cause.

Android Permissions, Battery Settings, and Stability

Android may suspend background applications to save power. If Clash works for a few minutes and then stops, open the app’s battery settings and select an unrestricted or non-optimized option where your device manufacturer provides one. The exact path differs between Android versions and brands, but it is commonly found under Settings, Apps, Clash, Battery, and Background usage.

Keep the persistent VPN notification enabled while diagnosing connection problems. The notification can reveal whether the service is active, disconnected, or waiting for user approval. Some Android skins also provide an “auto start” permission or background launch control. If the service disappears after the screen turns off, check those controls in addition to ordinary battery optimization.

Android allows only one VPN service to operate as the active system VPN at a time. If another VPN, firewall, DNS filter, ad blocker, or security application is running, it may compete with Clash. Disable the other VPN temporarily during testing. Private DNS can also affect results because it may resolve domains outside the path you expect. For a clean diagnosis, note the current Private DNS setting and change it only when you understand what the client’s DNS configuration requires.

Some apps do not honor Android’s ordinary system proxy settings, which is why the VPN-based mode is important on mobile. However, applications may still use certificate pinning, their own encrypted DNS, or a separate network stack. A working Clash browser test does not guarantee that every app will accept the same route. Use the connection log to check whether the app creates visible requests and whether those requests match the intended policy.

Maintenance and Common Mistakes

Subscription management is not a one-time task. Providers may add nodes, remove expired servers, change group names, or update rule providers. Open the Profiles screen periodically and use Update rather than importing duplicate copies. If automatic updates are supported, choose an interval that fits your provider’s quota policy. Excessive updates can waste traffic allowance without improving performance.

• Imported but not selected: The downloaded profile exists, but an older profile is still active. Tap the new profile and verify the active indicator.
• Selected a node in the wrong group: Your rules may reference a different group. Check the policy shown in the connection log.
• VPN permission was denied: Return to the main screen and start the service again, then approve Android’s system prompt.
• All nodes show timeout: Test the subscription URL, switch networks, check the system clock, and confirm that the provider account has not expired.
• Only one application fails: Look for app-specific DNS, certificate pinning, QUIC behavior, or a rule that sends the application DIRECT.
• Battery optimization stops the client: Allow background activity and keep the VPN notification visible while testing.
• Configuration becomes invalid after an update: Keep a copy of the last working profile and contact the provider before deleting it.

A useful long-term setup is to keep Rule mode as the normal profile, select a stable general-purpose group, and save a known-good backup node for emergencies. Use Global mode only as a diagnostic or special-purpose choice, and use Direct mode to separate a Clash problem from an ordinary network problem. This gives you a repeatable troubleshooting path instead of relying on guesswork.

Start with a Cleaner Android Proxy Workflow

Some alternative mobile proxy tools make subscription management difficult by hiding the active profile, offering limited node-group visibility, or requiring repeated manual edits when a provider changes its configuration. Others may expose many advanced switches without clearly showing whether Android’s VPN service is running. These issues are especially frustrating when you only want to import a subscription and switch to a responsive node.

Clash provides a clearer separation between profiles, proxy groups, routing modes, logs, and the Android VPN service. With Rule mode for everyday traffic, Global mode for controlled testing, and Direct mode for comparison, you can identify problems without changing everything at once. If you want a practical client with flexible subscription handling and transparent node selection, Download Clash for free and try the workflow described above.