Clash for Windows
Start by choosing a client, then complete subscription import, rule-based routing, and DNS setup. The page follows common workflows, making it useful for first-time installation and quick troubleshooting.
Browse six commonly used capabilities. Select a card to see its key actions below, or switch with the left and right arrow keys or the circular buttons.
After importing, run a manual update and check the timestamp and configuration status. If the list is empty, first check the subscription URL, network access, and returned content. If nodes appear but cannot connect, continue with the proxy group, proxy mode, and system proxy. Separating subscription issues from connection issues can significantly shorten troubleshooting. For the complete workflow, follow the user guide step by step.
Clash usually evaluates rules from top to bottom. The first match determines which proxy group handles the request. When editing rules, verify the target domain, rule type, and proxy group name, then check the final fallback entry. Rule mode suits everyday use; Global mode is better for temporarily testing an egress; Direct mode helps determine whether a problem comes from the proxy path.
A configuration may contain multiple proxy-group layers. For example, a service rule may first enter “Auto Select,” which then chooses an egress from several nodes. Before switching a node in the interface, confirm which group the current rule actually references. Use manual selection when you need predictable control, latency testing when you want automatic comparison, and failover when you need a backup path.
DNS configuration is not just about server addresses. You also need to confirm where queries originate, how results are passed to the rule system, and whether Fake-IP works with LAN services. After making changes, test ordinary domains, proxied targets, and local device names separately. If some apps work while others fail, check whether those apps use their own encrypted DNS.
System proxy settings are clear and easy to disable, making them a good starting point for first-time setup. Once the subscription, nodes, and rules work, enable TUN as needed for games, command-line tools, or apps that ignore the system proxy. If access changes afterward, check permissions, routes, DNS, and LAN bypass settings one at a time instead of changing several parameters together.
A request typically passes through DNS resolution, rule matching, proxy-group selection, and the target connection. During troubleshooting, note the time and target domain, then compare them with the error location in the logs. If the error occurs during resolution, switching nodes usually will not help. If a rule matched but the egress is unexpected, return to the rule order and proxy-group settings.
Installation methods, network permissions, and background behavior differ by platform. Open the relevant platform first, then compare graphical clients and system requirements.
For everyday desktop use, choose Clash Plus, Clash Verge Rev, FlClash, or review the archived Clash for Windows documentation. After installation, configuration usually starts with subscription import, proxy-group selection, and the system proxy.
Go to downloadsBefore downloading, distinguish between Intel and Apple Silicon. On first launch, you may also need to confirm system security prompts, network extension permissions, and proxy access. The platform page lists clients by chip architecture to help you avoid downloading an incompatible installer.
Go to downloadsAndroid clients use the system VpnService to create a local virtual network. Along with importing a subscription, pay attention to VPN authorization, background operation, and battery-saving policies. If the connection drops after the screen locks, check the system's background restrictions first instead of repeatedly changing the configuration.
Go to downloadsiPhone and iPad users can get Clash Plus from the App Store. After adding a subscription, allow the system to create a VPN configuration. Confirm the connection status in both the client and the system status area. The platform page also lists official-site information and basic setup notes.
Go to downloadsDesktop users can choose Clash Verge Rev or FlClash for a graphical interface. Servers, routers, and command-line environments are better suited to using the Mihomo core directly. Before downloading, confirm the distribution, processor architecture, and whether desktop tray support is required.
Go to downloadsThe Clash ecosystem combines rule systems, proxy cores, graphical clients, and configuration resources. Understanding these layers is more useful than memorizing the location of a particular button: interfaces may change, while configuration structure, rule-matching logic, and network troubleshooting methods remain reusable.
Clash for Windows was once a popular Clash graphical client for Windows users, offering configuration management, proxy modes, proxy groups, connection logs, and system proxy controls. After the original project stopped being maintained, existing installers and historical documentation remained useful for reference, but new devices are better served by actively maintained clients. This site labels archived clients separately from actively updated alternatives so their maintenance status is clear.
Graphical clients handle subscription management, settings, tray actions, and system integration, while the core usually parses rules and processes traffic. Mihomo continues and expands the Clash configuration ecosystem, and many newer clients use it as their core component. When troubleshooting, determine whether the issue is in the interface, configuration, system network, or core layer; comparing client appearance alone cannot explain every connection difference.
Common YAML sections, proxy groups, and rule syntax are similar across many clients, but supported settings, override mechanisms, and core capabilities can differ. Before migrating a configuration, preserve the original file, then check the core in use, supported fields, and local overrides. When errors appear, start with indentation, field names, and references; this is usually more effective than replacing the entire file.
Client downloads are centralized on the download page, while platform differences are organized under their respective tabs. The guide follows a continuous path from installation to verification, and the advanced section covers proxy groups, rule sets, DNS, TUN, Fake-IP, and local overrides. This structure makes it easier to look up information at the right depth and avoids mixing interfaces from different clients in outdated tutorials.
git clone https://github.com/Fndroid/clash_for_windows_pkg.git
Work through the complete sequence, from the subscription URL and configuration update to proxy-group selection and system proxy verification. Each step explains what result to expect and what to check first if the result differs.
Open the user guideThe advanced manual covers proxy-group types, rule-set subscriptions, DNS, TUN, Fake-IP, domain sniffing, local overrides, and merging multiple subscriptions. It is intended for users who already have a basic connection working.
View advanced usageInstallation, subscription, rule, and network-stack symptoms can look similar, but they require different troubleshooting sequences. Use the four items below as quick entry points.
First confirm that no characters are missing from the subscription URL and that the URL is reachable in a browser or client. Then update the configuration manually and review the message. If the response is empty, unsupported, or requires additional authentication, fix the subscription source first. Only after the configuration loads successfully should you move on to proxy groups and connection tests. See Troubleshooting for more steps.
Rule mode is usually best for daily use, sending different traffic to direct or proxy policies according to the rules. Global mode sends more requests to the selected proxy group and is useful for temporarily testing an egress. Direct mode helps determine whether an access problem is related to the proxy path. Switching modes changes traffic decisions; it does not repair an expired subscription or incorrect DNS configuration.
Some apps do not read the operating system proxy settings and may use an independent network stack. First confirm that ordinary apps such as browsers work through the proxy, then determine whether the target app needs TUN capture. Before enabling TUN, understand the changes to permissions, routes, and DNS, and preserve the original settings so you can roll back individual changes if LAN access becomes abnormal.
Archived documentation can still help with historical setups, but new installations should compare actively maintained graphical clients. Focus on operating-system support, core type, subscription management, TUN support, and update methods rather than searching only for an identical interface. The download page lists options including Clash Plus, Clash Verge Rev, and FlClash by platform, with archived status clearly marked.
Starting from real network symptoms, these articles explain detection methods, configuration locations, and verification steps. They are best read by issue after the basic installation is complete.
Use online testing sites and local packet captures to confirm whether DNS bypasses the proxy, then inspect the resolution path through nameserver, fallback, and fake-ip.
TroubleshootingExplains why Android clients depend on VpnService and how authorization, background restrictions, and battery-saving policies affect persistent connections.
PlatformsBreaks down traffic flow, use cases, and common mistakes for the three modes, with guidance for everyday use and temporary troubleshooting.
Getting Started