A curated reference for choosing Clash clients, completing setup and configuration, managing subscriptions, and applying proxy rules, with download links organized by platform.
Clash Downloads serves both everyday and technical users who want to learn about Clash. It brings together client information for Windows, macOS, Android, iOS, and Linux, along with practical guidance on importing subscriptions, system proxies, TUN, DNS and routing, and rule-based traffic splitting. Content is organized by platform and stage of use. For questions or feedback, continue with the FAQ or Getting Started guide.
Clash is the name of a proxy software ecosystem built around rule-based traffic forwarding. The original project provided a foundation for related clients and configuration formats. Clash Meta extended that approach with broader protocol, rule, and networking capabilities. The community-maintained Mihomo core that followed now handles much of the parsing and traffic forwarding inside many clients. A graphical client manages the interface and system integration, while the core executes the configuration; they are separate layers.
Download pages list clients and system requirements by platform, while links and available entry points are updated against the build inventory. Guides prioritize steps that can be reproduced clearly and explain differences caused by system permissions, client interfaces, and core capabilities. For subscriptions, rules, or DNS, each page explains the scope of an issue before providing checks, rather than treating one configuration as a universal answer for every network environment.
Proxy client connectivity depends on the network environment, service provider, system permissions, and the policies of the target service. This site explains software features, configuration methods, and troubleshooting approaches; it makes no quality guarantees for node services or third-party subscriptions. Before installation, verify the client source, system version, and permission requirements. Before importing a subscription, review the provider’s terms of service, privacy policy, and traffic limits.
This site does not invent team details, company addresses, or personal contact information. Content is updated based on client version changes, core behavior, and feedback from real-world use. When upstream project names, maintenance status, or platform support change, the relevant pages are revised accordingly.