Skip to the guide
Quick Start · 4 Steps

How to Import a Clash Subscription and Connect

Go from subscription link to verified access. Allow about 10 minutes for the initial setup. First get one connection working, then adjust advanced options.

01 Import subscription 02 Choose a mode 03 Connect 04 Verify it works

Before You Start: Get a Client and Subscription Link

Install a client for your operating system and make sure your regular internet connection works. A Clash client reads configuration files, matches rules, and routes traffic. The subscription link comes from your service provider; the two are not interchangeable. Installing a client alone does not give you a working proxy. Get a Clash- or mihomo-compatible subscription from your provider before continuing.

To copy your subscription, find the relevant link on your provider’s website. Don’t copy the account page URL from your browser’s address bar. If the page offers formats for different clients, choose one compatible with your app. Subscription links often contain personal access credentials, so don’t post the full URL in group chats, public screenshots, or unfamiliar online converters. When asking for help, share the error message but hide sensitive parts of the link.

For your first setup, use just one subscription and temporarily quit any other proxy or VPN clients. That makes it easier to identify which client is responsible for system proxy settings, connection logs, and changes in access. If your computer is managed by your organization, check that you’re allowed to change proxy settings or install network services. On mobile, disconnect any existing VPN before opening the client you plan to use.

01 Import a Subscription and Activate the Configuration

Add a Remote Profile and Paste the Full URL

Open Clash Verge Rev and go to Configuration in the sidebar. Find the option to create, add, or import a profile. If asked to choose a type, select Remote. Give it a short, recognizable name, such as “Daily subscription.” Paste the link you copied into the subscription URL field. Check that the entire URL is there, with no extra spaces, line breaks, or quotation marks, then save or confirm the import.

Some versions have a URL field directly on the Configuration page; paste the link and click Import without looking for a separate Remote option. On mobile, tap the plus button and choose “Import from URL” or a similar option. Wait for the download to finish. A new profile card, profile name, or update timestamp confirms that the client received the configuration. Don’t click Import repeatedly, or you may end up with several profiles with the same name and lose track of which one is active.

Set the Imported Configuration as Current

A profile appearing in the list doesn’t necessarily mean it’s active. Click its card or open the card menu and choose an option such as Use or Activate. Once you see a selected border, current-profile label, or checkmark, open the Proxies page. You should see the groups and available proxies defined by the subscription. Group names depend on the configuration; they may be in another language or use a name other than PROXY. There’s no need to rename them to match this guide.

If your provider supplies a local YAML file, import the file and select it from where you saved it. A local file and a remote subscription can both load a configuration, but a local file won’t receive provider updates automatically just because of its filename. If you plan to use a remote subscription, check the auto-update interval in the profile settings and start with the client’s or provider’s recommended value. There’s no need to set a very short interval just to connect for the first time.

If the import fails, first determine whether the download failed or the configuration could not be parsed. For a download failure, check the link, your network, and whether the subscription is still valid. For a parsing failure, check that the format is compatible; a webpage URL or link for another type of node can’t be used directly as Clash YAML. Don’t start making large manual edits to the configuration just to see if they help. Look up specific errors in the Help Center. To learn how configuration files are structured, see the configuration reference.

02 Choose Rule Mode and a Proxy Target

Start with Rule Mode for Everyday Use

Open the client’s Proxies page or the mode selector on its home screen. Find the Rule, Global, and Direct options, and select Rule. In this mode, the active configuration determines whether each connection goes direct, uses a proxy group, or follows another policy. Rule mode doesn’t send every app through a proxy, and selecting it doesn’t route system traffic on its own. You’ll enable the system connection in the next step.

Global mode sends traffic handled by the core through the global policy. It can be useful for a quick comparison, but it won’t automatically route apps that bypass the client. Direct mode sends connections handled by the core straight to their destinations and usually isn’t the right choice for everyday subscription proxy use. For your first setup, stay in Rule mode so you can assess the result without changing the mode and system settings at the same time.

Choose an Available Target in the Proxy Group

After selecting a mode, check the proxy groups in the active configuration. Open the group that handles proxy traffic and select an available proxy from your provider. If the subscription uses an automatic selection group by default, you can keep it for now. Make sure the group points to the expected proxy or automatic group—not DIRECT. Some configurations have separate groups for video, downloads, and other uses. There’s no need to change them all during initial setup; keep the defaults.

If the client offers a connection test, run it to rule out obviously unavailable options. A successful test only means the test destination was reachable at that moment; it doesn’t guarantee that every site or app will work. A timeout also depends on the destination and your network. Choose one target first so you have a clear baseline for the access test. If you switch targets, wait for the connection to re-establish before testing. Existing long-lived connections in open pages may still use the previous route.

When you’re done, return to the home screen and confirm that the imported profile is still active and the mode is still Rule. Editing rule syntax, nested proxy groups, or automatic selection settings isn’t necessary for your first connection. To change how a particular site is routed, see the configuration reference for how rules map to proxy groups. Leave the original subscription unchanged for now to avoid losing edits when it updates.

03 Connect and Grant System Permissions

Desktop: Test in a Browser with the System Proxy

On the Clash Verge Rev home screen or in Settings, confirm that the core is running, then enable System Proxy. If the page has a separate Start button, start the core before enabling the system proxy. This setting changes your operating system’s proxy configuration; only browsers and apps that respect it will send their connections through the client. Check that the switch stays on and that no error appears. Don’t rely on the tray icon alone.

For your first test, leave TUN off and use the system proxy in a browser. If the system proxy works, you don’t need to enter a proxy address manually or change ports based on another guide. If your browser has a proxy-switching extension, set it to follow the system settings so it doesn’t override the system proxy. Client ports vary by version; if you do need to enter one manually, use the listening port shown in your client.

If the browser works but an app ignores the system proxy, consider the client’s TUN mode. TUN routes more traffic through a virtual network interface and may require installing a service, elevated permissions, or driver approval. Follow the client’s instructions, and don’t repeatedly toggle multiple network settings. TUN may not capture every app in every situation; exceptions can require checking routes and app behavior. See the Help Center and configuration reference for setup details.

Mobile: Allow the VPN Connection

Android and iOS clients usually create a system VPN connection when you tap Start, Connect, or the main-screen toggle. Make sure the configuration is selected, then connect. When the system first asks for VPN permission, confirm that the request is from the client you’re using and approve it as prompted. Return to the client and check for a running or connected status. The system may also show a VPN icon in the status bar or settings. Selecting a profile alone won’t route traffic if you deny permission.

Keep the client running during the test and disconnect other VPNs that route traffic. If the connection tends to drop when the phone is locked, finish this test first, then check battery management and background restrictions. Don’t change every power-saving setting at once before the connection works. Desktop clients also need to keep running in the background: closing a window may only minimize it to the tray, while quitting the app usually stops the core. These actions aren’t the same.

04 Verify It Works and Keep Your Settings

Test Access, Then Check the Connection Log

Keep the client connected and open a new browser window or tab. Visit a site that normally works directly to confirm your basic connection is still working, then visit a site that should use a proxy under the active configuration. Use a new page rather than relying on a cached one. Once the page loads fully and you can follow its links, return to the client and check the connection log for that visit.

On the client’s Connections page, find the domain and check its matched rule, policy target, or connection chain; the available fields vary by client. Some connections end quickly and disappear, so watch the page while refreshing the site. In Rule mode, DIRECT is expected for sites that connect directly. A site expected to use a proxy should map to a proxy group and its target. One DIRECT entry doesn’t mean the entire client is inactive.

To check the exit IP, you can use a reputable IP lookup site as an additional reference and compare it with the expected exit for your selected proxy. However, the browser may reuse a connection, the rules may send the lookup site direct, and the proxy and your local network may be in the same region. A location label alone isn’t enough. Consider the website result, connection log, and IP information together rather than relying only on the system VPN icon. To test an app, make a new request inside the app itself.

If Something’s Wrong, Change One Thing at a Time

If the client doesn’t show any connection to the site, go back one step and confirm that the system proxy or mobile VPN is on. Check whether the browser is overriding the system settings. If the connection appears but a site expected to use a proxy shows DIRECT, revisit step two and check the mode, proxy group, and configuration rules. If the connection reaches a proxy but fails, check the subscription’s validity, proxy availability, and client error messages. Don’t change the mode, DNS, and ports all at once.

If only a few sites fail, test another site that should clearly use a proxy, then try another available target in the same group. Change one setting at a time and reopen the page to see what changes. If you temporarily switch to Global mode for comparison, switch back to Rule afterward. If the site works in Global but not Rule mode, focus on the rules and group selection instead of assuming the client needs reinstalling. For a more detailed troubleshooting process, visit the Help Center.

Once everything works, note the profile name, Rule mode, and selected proxy group so you can keep this working setup. If something changes after a subscription update, compare it with these settings. Remote subscription updates usually replace the content provided by the service. For persistent custom rules, use the override method supported by your client rather than editing the remote source directly. Once the basic connection is stable, follow the configuration reference.

Finally, know how to disconnect. On desktop, turn off the system proxy before quitting the client to avoid leaving a manual proxy setting that points to a stopped service. On mobile, disconnect in the client or the system VPN settings. To test disconnecting and reconnecting, turn off the connection, open a new page, then reconnect and repeat the checks. You’ve now completed all four parts: subscription, mode, system routing, and access verification. Next time, just confirm the profile is valid and connect.