clashsg.com › about

About This Site

Site scope, Clash's open source ecosystem background, content maintenance principles, and usage notes — all on one page.

What This Site Covers

clashsg.com is a Clash client download and configuration documentation site for English-speaking users. There are three core parts: platform-organized client installer links (Windows / macOS / Android / iOS / Linux and the mihomo core), step-by-step guides from installation to subscription import, and a configuration reference covering YAML structure, proxy nodes, proxy groups, and rule syntax. The goal is simple: let users handle downloading, configuring, and troubleshooting in one place instead of hopping between scattered posts.

Clash Open Source Ecosystem Background

Clash is an open source proxy core built around rule-based traffic routing. After the original core repository was archived, the community fork Clash Meta continued development and was later renamed mihomo. It keeps iterating on protocol support, DNS routing, and TUN mode, and is now the default core for mainstream GUI clients (Clash Plus, Clash Verge Rev, FlClash, and others). This site's documentation is based on mihomo core behavior, with differences from the original core noted separately where relevant.

Content Maintenance Principles

  • Download links only point to official release channels and app store listings; links are checked periodically and removed if broken.
  • Tutorial steps are published only after being verified on the actual platform, and screenshots/descriptions are updated when the UI changes.
  • Configuration examples use real, runnable syntax rather than pseudocode; version numbers and commands are kept in sync with current releases.

Disclaimer

This site only provides download guidance and technical documentation for open source software, and does not provide any network access service. When using proxy tools, follow the laws and regulations of your jurisdiction and take responsibility for your own usage.

Feedback and Corrections

If you find a broken link or an outdated step, check the troubleshooting section of the tutorial docs and the glossary to confirm concepts first; for field-level configuration questions, refer to the field descriptions in the configuration reference.