This guide covers the practical steps for importing a subscription into Clash: getting the subscription link, adding it to the client, updating nodes, and checking whether your IP, DNS, and browser settings are working properly after connecting. It’s designed for first-time Clash users to follow step by step.
1. What to prepare before importing a subscription
Clash is just a client; you need a subscription link to use it. A subscription is usually a URL containing configurations for multiple nodes. You can use a subscription from a service you already have, or check out the free node resources on this site for testing. Note that free nodes may not be reliable, so we recommend using them only for temporary learning and connectivity tests.
- Make sure you’ve installed a Clash client, such as Clash Verge, Clash for Windows, or a Clash Meta client.
- Get a working subscription link, usually one that starts with http or https.
- Check that your computer’s clock is correct and that no other software is using the system proxy.
2. How to import a subscription into Clash: general steps
- Open the Clash client and go to the Profiles / Configuration page.
- Click “New,” “Import,” or “Download from URL.” The wording may vary slightly between versions.
- Paste the subscription link into the URL field. You can name the configuration—for example, “freevpn-test.”
- Click Download or Save and wait for the client to fetch the configuration file.
- Return to the configuration list and select the imported configuration to enable it.
- Go to the proxy page and select a node. For testing, start with Rule or Global mode.
- Enable the system proxy, then visit an IP lookup site to check whether your outgoing IP has changed.
If no nodes appear after importing the subscription, click “Update Subscription” once. If the list is still empty, the link may have expired, the subscription address may be unreachable from your network, or the subscription format may not be supported by your client.
3. How IP, DNS, and your browser environment affect things
Many people assume that if Clash connects successfully, websites will automatically work as expected. In fact, your IP, DNS, and browser environment also matter. Your IP determines which outgoing address websites see. If it hasn’t changed, the system proxy may be off, your browser may not be using the proxy, or you may have selected a direct connection mode.
DNS translates domain names into addresses. DNS problems can let you connect to a node while preventing websites from loading, or cause some domains to resolve to the wrong address. You can enable the built-in DNS in Clash settings or switch to a common public DNS provider. Avoid running multiple proxy apps at the same time, as they may repeatedly override your DNS settings.
Your browser environment includes your cache, extensions, WebRTC, language, and time zone. If the same node works on your phone but not in your desktop browser, try an incognito window, disable proxy extensions, clear the cache, or test another browser. If you want to reduce inconsistencies that could affect your privacy, you can disable settings related to WebRTC leaks.
4. Troubleshooting import and connection failures
- Download failed: Check that the subscription link is complete and contains no extra spaces. Try opening it in a browser.
- All nodes time out: Switch to a different network or update the subscription and try another node.
- Connected but websites won’t load: Make sure the system proxy is enabled and that the current mode isn’t Direct.
- Only the browser is affected: Disable browser proxy extensions and test using the system proxy.
- Some websites aren’t working properly: Switch between Rule and Global modes to see whether the issue is caused by the rules or DNS.
To sum up, importing a subscription into Clash comes down to pasting the link into the configuration page, downloading and enabling it, selecting a node, and turning on the proxy. If things don’t work as expected after connecting, don’t focus only on the node itself. Also check whether your IP has changed, whether DNS is working properly, and whether your browser is actually using the proxy. Following these steps in order should help you quickly identify the problem.