Clash for Android Setup Guide

Once the client is installed and you have a subscription link, follow these four steps to connect for the first time. Select the right profile, then check that traffic is routed as expected by testing real requests.

Step 1: Import and select a subscription profile

Get a Clash subscription link from your configuration provider, or use a local YAML profile. A subscription link lets the client fetch a profile; it is not the provider’s login page or a share link for a single node. Copy the full link, including its path and any parameters after the question mark. Don’t include line breaks, leading or trailing spaces, or punctuation from a chat message. If the provider offers several import options, choose one explicitly marked for Clash or mihomo. Subscription links may contain account details, so don’t show them in screenshots, screen recordings, or support requests.

Add a profile from Profiles

Open Clash Meta for Android, tap Profiles on the home screen, then tap the plus button in the top-right corner. To use a subscription, choose URL and enter a recognizable name, such as Work or Personal, then paste the full link into the address field. Check the start and end of the link for missing characters before saving. For your first setup, leave options such as the update interval at their defaults. Tap Save in the top-right corner and wait for the client to fetch and parse the profile. To import a local profile, choose File when adding a source, use the system file picker to find the YAML file, and import it. Local files aren’t automatically updated when the upstream subscription changes; to use a newer version, import or replace the file.

Check the list and select the new profile

When the new entry appears, tap it and check that the selection indicator has moved to the new profile. This is especially important if you already have an older subscription: importing a profile doesn’t switch to it, and keeping the old entry won’t prevent you from using the new one. You can leave the old profile in place until the new one passes the connection check, then decide whether to remove it. Return to the home screen and make sure Profiles shows the name you just selected. The rules and groups you see next come from this profile. If the displayed name doesn’t match, check the selection in the profile list.

If you see an error after saving or the list doesn’t show a new entry, first work out which of these happened: if fetching failed, check your phone’s network, the full link, and whether the subscription is still valid. If fetching succeeded but the profile couldn’t be parsed, check that the provider returned a client-readable profile, not a login page or another format. Don’t keep adding entries with the same name; that makes it harder to tell which profile is active. If you still can’t import it, see Frequently Asked Questions for help with subscription updates and profile parsing. Once the new entry appears and is selected, you’re ready to choose how requests are routed.

Step 2: Choose a proxy mode

For your first connection, choose Rule. In Rule mode, the client checks rules in the order listed and handles each request according to the policy specified by the first matching rule. A profile can send some services direct and route others through a proxy, so requests from the same phone may use different outbounds. Choose this mode to keep the subscription’s routing rules in effect, then verify that they work as expected in the final step.

Return to the home screen and check whether your version offers a mode selector before startup. If it does, choose Rule. In some versions, the mode control only appears on the Proxies screen after the service is running. Don’t edit the subscription just to find the setting: start the service and grant permission in the next step, then return to Proxies to check the active mode. The profile may specify Rule mode, but use the option shown in the interface while the service is running as the source of truth. If you switch profiles later, check the mode again rather than relying on your previous selection.

Rule mode and proxy groups are different

Global and Direct can be useful for comparison while troubleshooting, but you don’t need to switch between them during first-time setup. Global mode sends requests handled by the client to the global policy; check which outbound that policy actually selects. It doesn’t mean the client necessarily handles every app on your phone. Direct mode typically sends requests handled by the client straight out. After testing, switch back to Rule; otherwise, a page loading successfully won’t tell you whether the subscription’s routing rules matched. Direct mode is not the same as DIRECT in a proxy group: one changes how requests are handled at runtime, while the other is an outbound that rules or groups can select.

Once the service is running, open Proxies to see the groups defined by the subscription. The mode determines whether the client evaluates rules; a group determines which route to use when a rule points to it. Group names are set by the configuration provider and may differ from those in other guides. Find the group for the service you want to test. If you can choose a route manually, select a node you’re authorized to use and check that the selection updates. If the subscription uses an automatic group, leave its selection method as is for now. Don’t change every group to the same node just to make one service work; you’ll lose a useful point of comparison and make it harder to restore the original setup. For more on rule order and group references, see the user guide.

Step 3: Grant permission and start the connection

Return to the client’s home screen and make sure the profile selected in Step 1 is active, then tap the start control. The first time you start the service, Android usually asks to set up a VPN connection. Check that the app named in the prompt is the client you just opened, then approve the request and wait for the service to start. This permission lets the client receive traffic routed to it by Android’s VpnService. Approving the prompt allows a VPN connection to be created; it doesn’t confirm that a remote node is reachable.

After granting permission, stay on the home screen and check the status. When startup succeeds, the status should change from stopped to running. Some devices also show a VPN indicator in the status bar or on the system VPN screen. If you approved the request but the client still shows Stopped, check for a profile error, then see whether another local VPN app is already running, such as another proxy client or network filter. If there’s a conflict, stop the other service before starting this client. If your device is managed through a work profile or administrator policy, follow its rules rather than repeatedly revoking and granting permission.

Check the mode and outbound before switching to your browser

Once the service is running, open Proxies and make sure the active mode is Rule. If you couldn’t find the mode selector in Step 2, check it now. Then review the group you plan to use for testing. If you need to change nodes, change one option at a time and note the original selection so you can restore it and compare results. If the client offers a latency test, use it as a quick check that a node responds to the test address. A single test can’t prove that every site is reachable or that your browser’s current request will use that group.

For the first checks, keep your Wi-Fi or mobile data unchanged, and leave DNS, per-app routing, and battery optimization settings alone. Switch straight from the client to your browser to test. If the connection drops as soon as you leave the app, return to the home screen and check whether the service stopped. Only investigate battery optimization exclusions and background activity settings if the problem happens mainly when the app is in the background or the screen is locked. If the home screen still shows the service running but pages won’t load, don’t grant permission again; the next step is to check where each request went.

Step 4: Verify the connection and traffic routing

Run two comparison tests on the same phone, network, and browser. Based on the subscription’s rules, choose one everyday site expected to connect directly and one test site expected to use the proxy. Visit one destination at a time in a new tab and reload if needed, so you’re checking a new request rather than an old page already open in the browser. Note the destination and selected group for each request, then record the result. Two pages loading successfully doesn’t tell you whether they used different outbounds.

Match the results to the rules that applied

If your version shows connection details or logs, return to the client as soon as a test page loads and find the request by its time and destination hostname. A request expected to connect directly should show a direct outbound, such as DIRECT. For a request expected to use the proxy, check the matched rule, the group it specifies, or the node actually selected; available fields vary by client. A page may also request images and scripts from other domains. Check the main site hostname first, and don’t mistake a supporting resource for the main request. If a short-lived connection has disappeared, reload the page and check immediately. Don’t draw conclusions from a nearby log entry with a different destination.

You may see MATCH, which means none of the preceding rules matched and the fallback rule specifies the outbound. Seeing MATCH isn’t a problem by itself. If its outbound isn’t what you expected, check that you selected the right profile, that the mode is Rule, and that the requested hostname matches the rule’s format. If the client doesn’t show matched rules, compare your public IP before and after using a service you know is routed through a proxy group. Run both checks on the same network and using the same lookup page. A changed IP only shows that this lookup saw a different outbound; it doesn’t prove all traffic uses the proxy. An unchanged IP could mean the lookup service was routed direct.

Go back to the step that matches what you observed

If both types of request fail, first check whether your phone can reach sites that normally connect directly when the client is stopped, then return to Step 3 and check the service status. If direct requests work but a proxied request fails despite matching the right group, check the group’s selected node and try a different one, changing only one at a time. If traffic uses an unexpected outbound, return to Step 2 and check the mode and group; there’s no need to reimport the subscription. If there’s no corresponding request in the logs, make sure the browser sent a new request, then see Frequently Asked Questions to check whether the app is covered. For DNS, app routing, or system proxy settings on another platform, follow the user guide one step at a time.

Your first setup is complete when the client stays running, both comparison requests load, and connection details or test results confirm the expected outbounds. Note the active profile name, mode, and key groups. After updating a subscription or changing routes, repeat both checks; they make it easier to spot what changed than the VPN icon alone.