This article addresses the practical question of “how to import a subscription into Clash”: starting from the moment you get a subscription link, it walks you through importing the configuration, updating nodes, selecting a proxy mode, and explains why your IP, DNS, and browser environment can affect access results after connecting. It is suitable for ordinary users using Clash for the first time.
1. What to prepare before importing a subscription
Clash itself is just a client and needs to be used together with a valid subscription link or configuration file. You can use your own existing provider subscription, or refer to the free node page provided on this site for testing. Before importing, confirm three things: the client is installed, the subscription link has not expired, and the system time is correct. Many “import failed” issues are not caused by the software itself, but by an invalid link or a network that cannot access the subscription address.
- Common Windows clients: Clash Verge, older replacement branches for Clash for Windows, etc.
- Common macOS clients: Clash Verge, ClashX Meta, etc.
- Common Android client: Clash Meta for Android.
2. How to import a subscription into Clash
- Open the Clash client and go to the Profiles / Configuration page.
- Find buttons such as “New Profile,” “Import from URL,” or “Import from URL.”
- Paste your subscription link, and it is recommended to name it “freevpn-test” or another easy-to-recognize name.
- Click download, save, or update, and wait for the configuration to finish loading.
- Go back to the proxy or node page, select a node, then switch to Rule, Global, or Direct mode.
- Turn on the system proxy switch, visit a test website in your browser, and confirm that it is working.
If what you received is a yaml configuration file rather than a subscription link, you can choose “Import from File.” After a successful import, remember to click Update Subscription once to avoid using outdated node information.
3. After importing the subscription, how to check IP, DNS, and browser environment
A successful Clash connection does not necessarily mean all traffic is being routed through the proxy as expected. It is recommended to check IP, DNS, and the browser environment separately. IP represents the exit address seen by websites; DNS is responsible for domain name resolution; and the browser environment includes language, time zone, WebRTC, cache, and account status.
If you have enabled Rule mode, domestic websites may still connect directly while foreign websites go through the proxy, which is normal. If your test IP still shows your local address, first confirm whether your current browser is using the system proxy, or whether Clash’s system proxy switch is turned on. If the IP has changed but some websites still cannot be opened, it may be related to DNS pollution, rule matching, or the availability of the node itself.
It is recommended to enable the DNS module in settings or use the client’s default enhanced mode; do not enable multiple VPNs, accelerators, or proxy plugins at the same time, otherwise traffic conflicts are likely to occur. On the browser side, you can first test in an incognito window and disable WebRTC plugins or proxy extensions to avoid old cache affecting your judgment.
4. Troubleshooting common failures
- Download failed: check whether the subscription link is complete, whether it contains spaces, and whether the browser can open the link.
- Import succeeds but no nodes appear: the subscription source may be returning an empty configuration; try another link or wait for an update.
- Nodes show timeout: switch to other nodes, or check your local network, firewall, and system time.
- Web pages open but are very slow: try changing nodes or switching Rule/Global, and avoid interference from browser plugins.
- The software shows connected but apps do not work: confirm whether the app uses the system proxy, and enable TUN mode if necessary.
Overall, the core process of importing a subscription into Clash is “paste the link on the configuration page → update → select a node → enable the system proxy → check IP/DNS.” When problems occur, do not only look at node latency; also check the proxy mode, DNS settings, and browser environment at the same time, as this makes it easier to identify the cause.