Seele

Seele

Introduction to Several Clash GUIs and Similar Tools

Non-Clash Kernel#

v2raya#

Advantages:

  • Fully open source
  • Supports ss/ssr/v2ray subscription links
  • Can import servers individually
  • Kernel is optional and open source (v2ray-core/xray-core)
  • Compatible across all platforms

Disadvantages:

  • Cannot parse clash subscription links

Clash Kernel#

Clash for Windows#

Github: Fndroid/clash_for_windows_pkg

Advantages:

  • No need to install the clash kernel separately
  • Kernel is open source (optional [clash/clash premium])
  • Compatible across all platforms

Disadvantages:

  • Cannot import servers individually; configuration files can be modified separately but are too cumbersome for GUI users
  • GUI was once open source but is no longer open source

Clash Verge#

Github: zzzgydi/clash-verge

Advantages:

  • No need to install the clash kernel separately
  • Kernel is open source (optional [clash/clash premium])
  • Components are open source
  • Compatible across all platforms

WEB GUI#

All of the following are open source software and require manual configuration of the clash kernel and configuration files.

YACD#

Github: haishanh/yacd

Clash Dashboard#

Github: Dreamacro/clash-dashboard

Brief Evaluation#

In personal use, for users with airport subscriptions, the clash configuration file has become the mainstream and even the only subscription method. Therefore, v2raya is more suitable for users who build their own nodes or have good support for ss/ssr/v2ray subscription services.

Clash Verge provides the same experience as Clash for Windows, but Clash Verge has a higher degree of openness. Personally, I prefer Clash Verge.

The following is based on personal experience and does not possess universality or rationality.

From personal experience, I feel that the clash kernel is more efficient than v2raya or x-ray kernels, and the latency is also lower.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.