Clash for Android Guide: Add Subscriptions and Switch Nodes

Clash for Android makes subscription-based proxy management much easier than manually entering server addresses, ports, UUIDs, and transport settings. Once the app is connected to a valid subscription, you can download a profile, test available nodes, select a proxy group, and switch servers without editing YAML by hand. However, first-time users often get stuck at the same points: they paste the wrong subscription URL, import a profile but forget to activate it, mistake latency for actual connectivity, or switch a node without enabling the system VPN.

This practical Clash for Android guide explains the complete workflow from start to finish. You will learn how to add a subscription, update its profile, understand the main controls, test proxy nodes, choose a suitable server, and troubleshoot the most common connection failures. The instructions apply broadly to Clash-compatible Android clients, especially apps based on the Mihomo or Clash.Meta core. Button names may vary slightly between releases, but the underlying process is nearly identical.

What You Need Before Adding a Subscription

A subscription is usually a URL that returns a Clash-compatible configuration. It may contain proxy nodes, proxy groups, routing rules, DNS settings, and other profile options. The URL is normally generated by your service provider and is often called a subscription link, Clash link, configuration URL, or profile URL.

Before opening Clash for Android, prepare the following items:

• A valid subscription URL: Copy the complete HTTPS address from your provider’s account page. Do not copy only the visible text label or a shortened preview.
• A compatible profile format: Confirm that the provider supports Clash, Clash Meta, Mihomo, or a format that the Android client can convert.
• An active account or remaining traffic: Some providers return an empty profile when the account has expired, reached its traffic limit, or exceeded the device limit.
• A temporary internet connection: The first profile download requires ordinary internet access. If the subscription URL cannot be reached, Clash cannot import it.
• Permission to create a VPN connection: Android will display a system prompt the first time the client starts its local VPN service.

Subscription links are sensitive credentials. Anyone who obtains the URL may be able to download your profile and use the included nodes until the provider revokes or regenerates the link. Avoid posting it in screenshots, public chat rooms, issue trackers, or browser history shared with other people. If you accidentally expose it, open your provider dashboard and reset the subscription URL if that option is available.

Also check whether your Android client is designed for the same core as the profile. A modern Mihomo-based client can usually handle common Clash configurations and additional protocols, while older clients may reject newer fields. If the import succeeds but the profile shows errors, the problem may be a core compatibility issue rather than a bad subscription.

How to Add a Subscription in Clash for Android

The exact interface differs between Clash for Android builds, but the general sequence is: open the profiles page, add a remote profile, paste the URL, give it a recognizable name, and download it. Do not start with the large proxy switch on the home screen; importing a profile normally happens under Profiles, Configurations, or a similarly named section.

1. Open Clash for Android and grant any initial storage or notification permissions requested by the app.
2. Open the Profiles or Configurations page.
3. Tap the add button, plus icon, or New Profile action.
4. Select Remote, URL, or Import from URL.
5. Paste the complete subscription URL into the address field.
6. Enter a short name such as My Provider or Personal Nodes.
7. Tap Download, Fetch, or Import.
8. Wait for the download and parsing process to finish.
9. Tap the imported profile to make it active, if the client does not activate it automatically.

A successful import usually displays the profile name, the time it was downloaded, and a count of proxies or proxy groups. If the profile appears in the list but has no nodes, open it and inspect the error message. A profile can be downloaded successfully while still being unusable because the response is an HTML login page, a provider error, or a format intended for another client.

profile name: My Provider
source: remote subscription URL
format: Clash / Clash Meta / Mihomo
download status: successful
proxies: several nodes
proxy groups: selector, url-test, or fallback
rules: provider-defined routing rules

Some clients show a separate Use, Set as Active, or checkmark control. Downloading and activating are two different operations: downloading stores the configuration locally, while activating tells the Clash core which configuration should control traffic. If you have several profiles, always verify that the intended one is marked active before testing a node.

If the URL contains characters such as ?, &, or a long token, copy it without adding spaces or quotation marks. Android clipboard managers and messaging apps can occasionally insert line breaks. When in doubt, paste the URL into a plain text field first and confirm that it is one continuous line beginning with https://.

Update the Profile and Check Its Contents

Subscriptions change over time. Providers may add new nodes, remove expired servers, change ports, or update routing rules. The local profile saved in Clash for Android does not automatically become current unless an update task is configured or you manually refresh it. After importing a profile, look for a refresh icon, a three-dot menu, or an Update action next to its name.

To update a remote profile:

1. Open the profiles or configurations page.
2. Find the profile that contains your subscription.
3. Tap the refresh icon or open its menu and choose Update.
4. Wait until the new profile is downloaded and parsed.
5. Confirm that the profile remains selected after the update.
6. Return to the proxy page and check whether the node list has changed.

If the client supports scheduled updates, an interval of several hours or one day is usually more practical than refreshing repeatedly. Very frequent requests can trigger provider rate limits and waste battery. A daily update is sufficient for most personal subscriptions, while users who depend on frequently rotated nodes may choose a shorter interval provided their provider permits it.

After an update, review the profile rather than assuming every change is harmless. Look at the proxy groups and identify which group controls normal traffic. Common names include Proxy, 🚀 Proxy, 节点选择, Auto, or a provider-specific name. The group shown on the main proxy page is often a selector containing individual nodes and another automatic group.

It is also useful to identify the final routing rule. A configuration that ends with MATCH,Proxy sends unmatched traffic through the proxy group, while MATCH,DIRECT sends unmatched traffic directly. This explains why some applications may work through Clash while others do not. The profile may intentionally use direct connections for local services, banking apps, games, or regional websites.

How to Test and Choose a Working Node

After activating a profile, open the Proxies page. You will normally see one or more proxy groups followed by a list of individual nodes. A group is not necessarily a server. It is a decision layer that may contain servers, automatic tests, or other groups. To use a specific node, open the group that handles general proxy traffic and select the node inside it.

Many Android clients provide a latency test button, often shown as a speedometer, signal icon, or lightning symbol. A test sends a small request to a target URL and measures the response time. The result is useful, but it is not a complete quality score.

• Low latency: The test endpoint responded quickly, but this does not guarantee good streaming or download speed.
• High latency: The route may be far away or congested, although it can still be usable for browsing.
• Timeout: The node did not respond within the test period. It may be offline, overloaded, blocked, or incompatible with the current network.
• Unavailable: The profile may contain an invalid address, expired credential, unsupported protocol, or incorrect TLS setting.

Test several nodes instead of choosing the first green result. Select candidates from different regions and compare their latency, stability, and real-world performance. A nearby node is often a good starting point, but the shortest geographic distance does not always produce the best route. Network congestion, transit providers, server load, and the destination’s location can matter more than distance.

When available, an automatic group such as url-test can select the node with the lowest measured latency. A fallback group prioritizes nodes in a fixed order and moves to the next one when the current node fails. A manual selector gives you direct control. For beginners, a sensible method is to use an automatic group for ordinary browsing and keep a manual group available when a website or application performs poorly.

Do not change DNS, TUN mode, routing mode, or fake-IP settings simply because one node has a high ping. First test another node and confirm that the Clash service is running. Changing several advanced options at once makes it difficult to identify the actual cause.

How to Switch Nodes and Enable Traffic Routing

Switching servers in Clash for Android normally takes only a few taps, but there are two separate controls to understand: the selected node and the running service. Selecting a node changes the route inside the active proxy group. Starting the service enables Clash to intercept Android traffic. You need both actions for the change to affect applications.

1. Open the Proxies page.
2. Locate the group used by the final proxy rule, commonly named Proxy or Auto.
3. Tap the current node or group selection.
4. Choose another node from the list.
5. Wait for the selection indicator to move to the new node.
6. Return to the home screen and enable the Clash service or VPN switch.
7. Accept Android’s VPN connection prompt if it appears.
8. Open a website or application and verify the result.

If the client is already running, the new selection usually applies to new connections immediately. Existing connections may continue using the old route until they close. To force a clean test, close the target application from Android’s recent-apps screen and reopen it. You can also use the client’s connection page to inspect active connections and confirm which rule and proxy group are being used.

Clash for Android commonly offers several operating modes:

• Rule mode: Uses the profile’s rules to decide whether each domain goes through a proxy or connects directly. This is the best default for most users.
• Global mode: Sends traffic through the selected proxy group whenever the application supports the intercepted traffic type. It is useful for testing, but may interfere with local services or region-specific apps.
• Direct mode: Bypasses the proxy. Use it to confirm whether a problem belongs to the network or to the proxy configuration.

For normal daily use, start with rule mode. If one service does not work, temporarily compare rule mode with global mode. If global mode works but rule mode does not, the issue is probably a routing rule, DNS resolution result, or application-specific bypass. If neither mode works, test the node itself and check whether the VPN service is actually active.

Troubleshooting Common Android Problems

The most efficient troubleshooting method is to change one variable at a time. First confirm the profile, then the selected node, then the VPN service, and finally the routing or DNS settings. The following sequence avoids unnecessary configuration changes.

The Subscription Cannot Be Downloaded

Check that the device has internet access without Clash running. Open the provider’s website or another ordinary website, then retry the profile update. If the link still fails, verify that it has not expired and that it was copied completely. A provider may also restrict downloads by IP address, user agent, or request frequency. In that situation, wait briefly or generate a new link from the provider account.

The Profile Imports but No Nodes Appear

Open the profile details and inspect the parser error. The downloaded content may be an HTML authentication page rather than YAML. It may also be a sing-box, V2Ray, or another format that the selected Clash core cannot parse. Use the provider’s Clash-specific export option. If the profile is encrypted or requires a conversion backend, follow the provider’s official instructions instead of manually guessing fields.

The Node Tests but Apps Have No Internet

Confirm that the profile is active and that the VPN switch is enabled. Android may show a key icon when the VPN service is running. If the service stops immediately, check whether another VPN, firewall, ad blocker, or battery-management tool is competing for the VPN slot. Android normally allows only one VPN service to control traffic at a time.

Battery optimization can also suspend the proxy client in the background. Open Android’s app settings, find the Clash client, and set battery usage to an unrestricted or non-optimized option if your device frequently stops the service. Do this carefully on phones with aggressive background management, because the exact menu differs between manufacturers.

Only Certain Apps or Websites Fail

This usually points to routing, DNS, or application compatibility rather than a completely dead node. Compare rule mode and global mode, then inspect the connection log if the client provides one. The log may show whether the request was matched by DIRECT, sent to the selected proxy group, rejected by a rule, or resolved incorrectly.

Some banking, payment, game, and streaming applications detect VPN interfaces or reject data-center IP addresses. Other apps use their own DNS stack, QUIC, certificate pinning, or a separate network process that a basic VPN mode may not handle perfectly. Do not assume that switching ten nodes will fix an application designed to reject proxy traffic.

Every Node Times Out

First update the subscription and check the account status. Next, try a different Wi-Fi or mobile network. If all nodes fail only on one network, the network may be blocking the server ports or the subscription provider’s domain. If all nodes fail on every network, inspect the profile’s expiration, core compatibility, and transport settings. A time or date error on the Android device can also break TLS certificates, so enable automatic date and time.

A Simple Daily Workflow for Reliable Use

Once the initial setup works, daily operation should remain simple. Keep one active profile, one preferred manual node, and one automatic group if the subscription provides it. Avoid changing advanced settings unless you have a specific symptom to diagnose. Most users do not need to edit the imported YAML, rewrite DNS settings, or enable every experimental feature.

A practical routine looks like this:

1. Update the subscription according to the provider’s recommended schedule.
2. Check whether the active profile still contains nodes and proxy groups.
3. Test the automatic group or compare two or three preferred nodes.
4. Select the node that offers the best combination of stability and speed, not merely the lowest number.
5. Enable the Clash VPN service and confirm the Android VPN indicator.
6. Use rule mode for normal browsing.
7. Switch to another node when the current route becomes unstable or congested.
8. Disable the service when you no longer need it, especially on metered mobile data.

It is also worth keeping a small record of which nodes work well for different purposes. One server may be stable for general websites, another may perform better for video, and a third may be more reliable on mobile data. This is normal: node performance depends on destination, time of day, carrier routing, and current server load.

Remember that a successful latency test is only the beginning. Evaluate a node by opening the services you actually use, watching for repeated reconnects, and checking whether downloads remain consistent for several minutes. If performance changes frequently, an automatic group with a sensible test interval can reduce manual work. If the automatic choice changes too often, use a manual selector or a group with a switching tolerance to prevent unnecessary flapping.

Clash for Android is most approachable when you separate the workflow into four clear actions: download the profile, activate the profile, select a node, and start the VPN service. After those foundations are correct, node switching is straightforward and troubleshooting becomes much less mysterious. Keep the subscription private, update it periodically, and prefer measured, repeatable tests over random configuration changes.