This article addresses “how to import a subscription into Clash” and common issues after importing, such as being unable to connect, websites not loading, your IP staying the same, and DNS leaks. Follow the steps below to import your subscription, then check that your IP, DNS, and browser settings are working as expected.
1. Prepare the Clash client and subscription link
Clash is a popular proxy client. Different versions are available for Windows, macOS, Android, and other platforms, including Clash Verge and Clash Meta for Android. Before using a client, make sure it is still actively maintained, and avoid installers from unknown sources.
A subscription link is usually a URL beginning with http or https that contains configurations for multiple nodes. This site also curates free nodes and subscription details for testing, but free nodes can be unreliable. If a connection fails, try switching nodes before troubleshooting the client.
2. Steps to import a subscription into Clash
- Open the Clash client and go to the Profiles / Configuration page.
- Look for an option such as “New Profile,” “Download from URL,” or “Import from URL.”
- Paste in your subscription link and name the profile—for example, “freevpn-x.”
- Click Download, Save, or Update, and wait for the configuration file to finish downloading.
- Return to the proxy page, select a node, and start testing in Rule or Global mode.
- Enable System Proxy, then visit an IP lookup website in your browser to confirm the connection is working.
If you get an error during import, try opening the subscription link in your browser. If it downloads text, the link is likely working. If it does not open, the link may have expired, your network may be blocking it, or the subscription service may be temporarily unavailable.
3. How IP, DNS, and browser settings are related
Many users assume that importing a subscription means everything is working, but there are three things to check. First, your IP: after connecting to a node, the IP shown by a lookup website should change to the node’s region. Second, DNS: if DNS requests still go through your local provider, you may encounter domain spoofing, slow loading, or privacy leaks. Third, your browser settings: cached data, WebRTC, and proxy settings in extensions can all affect the results.
- IP unchanged: Check that the system proxy is enabled and that your browser is not using a separate proxy extension.
- DNS issues: Enable the built-in DNS in Clash settings or switch to the enhanced mode recommended by your client.
- Only the browser fails: Clear the cache, disable other proxy extensions, and test in an incognito window.
- Apps connect, but websites do not load: Switch from Rule to Global mode to rule out routing issues.
4. Connection troubleshooting checklist
If you have imported a subscription into Clash but it is not working, check the following in order: whether the subscription can be updated, whether the node is available, whether the client’s clock is correct, whether the system proxy is enabled, and whether your firewall is blocking the client. On mobile, also make sure VPN access is allowed. Some devices from Chinese manufacturers restrict background activity, so you may need to exempt Clash from battery optimization.
A subscription may also include nodes that use different protocols, such as VLESS, VMess, Trojan, or Shadowsocks. You do not need to understand all the settings—just make sure your client supports the protocol. If some nodes are marked “unsupported,” your current Clash core may be incompatible. Try a client that uses the Clash Meta core instead.
5. Recommended usage
For everyday browsing, use Rule mode so that domestic websites connect directly while overseas websites go through the proxy. You can temporarily use Global mode to test a node. After updating your subscription, first choose a node with low latency that can access the websites you need, then continue using it. If you cannot access a website, do not keep reinstalling the client. Update the subscription, switch nodes, and check your DNS and browser proxy settings first.