[{"data":1,"prerenderedAt":630},["ShallowReactive",2],{"blog-\u002Fblog\u002Fclash-neihe-qubie-2026":3},{"id":4,"title":5,"author":6,"body":7,"category":615,"date":616,"description":617,"extension":618,"image":619,"meta":620,"navigation":621,"path":622,"seo":623,"stem":624,"tags":625,"__hash__":629},"blog\u002Fblog\u002Fclash-neihe-qubie-2026.md","Clash、Clash.Meta、mihomo、sing-box 有什么区别？一张表看懂你该装哪个","品牌图鉴编辑部",{"type":8,"value":9,"toc":600},"minimark",[10,14,21,32,128,140,147,150,154,160,166,176,185,197,200,216,221,223,227,234,305,315,318,325,327,331,334,339,344,347,362,366,373,377,380,382,386,391,442,451,457,459,463,546,553,555,558,564,576,582,592,594],[11,12,13],"h2",{"id":13},"先说结论",[15,16,17],"p",{},[18,19,20],"strong",{},"这四个名字不是四个并列的软件，而是一条演化线加一个独立项目：",[22,23,28],"pre",{"className":24,"code":26,"language":27},[25],"language-text","Clash（原核心） → Clash.Meta（社区分支） → mihomo（改名后的现名）\nsing-box（另起炉灶的独立项目，不是 Clash 的分支）\n","text",[29,30,26],"code",{"__ignoreMap":31},"",[33,34,35,54],"table",{},[36,37,38],"thead",{},[39,40,41,45,48,51],"tr",{},[42,43,44],"th",{},"名字",[42,46,47],{},"它是什么",[42,49,50],{},"现在的状态",[42,52,53],{},"你需要手动装吗",[55,56,57,76,94,113],"tbody",{},[39,58,59,65,68,73],{},[60,61,62],"td",{},[18,63,64],{},"Clash",[60,66,67],{},"最初的核心",[60,69,70],{},[18,71,72],{},"原仓库已于 2023 年底移除",[60,74,75],{},"不需要，也装不了",[39,77,78,83,86,91],{},[60,79,80],{},[18,81,82],{},"Clash.Meta",[60,84,85],{},"Clash 的社区增强分支",[60,87,88],{},[18,89,90],{},"已改名，这个名字不再使用",[60,92,93],{},"不需要，它就是 mihomo",[39,95,96,101,104,107],{},[60,97,98],{},[18,99,100],{},"mihomo",[60,102,103],{},"Clash.Meta 改名后的现名，事实上的现行核心",[60,105,106],{},"活跃维护",[60,108,109,112],{},[18,110,111],{},"通常不需要","，图形客户端内置了",[39,114,115,120,123,125],{},[60,116,117],{},[18,118,119],{},"sing-box",[60,121,122],{},"独立重写的代理内核，不是 Clash 分支",[60,124,106],{},[60,126,127],{},"看客户端，部分客户端可切换",[15,129,130,133,134,139],{},[18,131,132],{},"一句话回答\"我该装哪个\"","：装一个图形客户端（如 Clash Verge Rev），内核它自带。哪个平台装什么见 ",[135,136,138],"a",{"href":137},"\u002Fblog\u002Fclash-xiazai-guanfang-2026","Clash 下载 2026","。",[15,141,142,143,146],{},"📅 ",[18,144,145],{},"上表核对日期：2026-08-04。"," 项目归属与维护状态以你访问时仓库的实际情况为准。",[148,149],"hr",{},[11,151,153],{"id":152},"一为什么会有这么多名字","一、为什么会有这么多名字",[15,155,156,157,139],{},"理解这段历史能省掉很多困惑，因为",[18,158,159],{},"网上教程的写作年份决定了它用哪个名字",[15,161,162,165],{},[18,163,164],{},"2023 年之前","：只有 Clash 一个核心。当时的图形客户端（Clash for Windows、ClashX、Clash for Android）都调用它。",[15,167,168,171,172,175],{},[18,169,170],{},"2022 年前后","：社区分支 Clash.Meta 出现，加入了原版没有的东西——更多协议支持（如 VLESS、Hysteria）、更灵活的规则、",[29,173,174],{},"GEOSITE"," 分流等。当时的写法是\"要用 XX 协议就得换 Meta 内核\"。",[15,177,178,181,182,139],{},[18,179,180],{},"2023 年 11 月","：原核心仓库被移除，同期多个知名客户端停止维护。",[18,183,184],{},"Meta 分支成了唯一的延续",[15,186,187,190,191,193,194,139],{},[18,188,189],{},"之后","：Clash.Meta 改名为 ",[18,192,100],{},"，仓库归属 ",[29,195,196],{},"MetaCubeX\u002Fmihomo",[15,198,199],{},"⇒ 所以你看到的教程里：",[201,202,203,207,213],"ul",{},[204,205,206],"li",{},"写\"Clash 内核\"的，多半是 2023 年前的旧文",[204,208,209,210],{},"写\"Clash.Meta 内核\"的，说的是",[18,211,212],{},"现在的 mihomo",[204,214,215],{},"写\"mihomo\"的，是改名之后的",[15,217,218],{},[18,219,220],{},"它们指向同一个东西的不同阶段，不需要装三份。",[148,222],{},[11,224,226],{"id":225},"二mihomo-和-sing-box-的真实差异","二、mihomo 和 sing-box 的真实差异",[15,228,229,230,233],{},"这两个是目前实际在用的两个核心，关系是",[18,231,232],{},"并列","而不是继承。",[33,235,236,246],{},[36,237,238],{},[39,239,240,242,244],{},[42,241],{},[42,243,100],{},[42,245,119],{},[55,247,248,259,270,283,294],{},[39,249,250,253,256],{},[60,251,252],{},"出身",[60,254,255],{},"Clash 的延续分支",[60,257,258],{},"独立重写，不基于 Clash",[39,260,261,264,267],{},[60,262,263],{},"配置格式",[60,265,266],{},"YAML，沿用 Clash 语法",[60,268,269],{},"JSON，自成一套",[39,271,272,275,280],{},[60,273,274],{},"机场订阅兼容性",[60,276,277],{},[18,278,279],{},"绝大多数机场默认给的就是这个格式",[60,281,282],{},"需要订阅方提供 sing-box 格式，或用转换",[39,284,285,288,291],{},[60,286,287],{},"规则生态",[60,289,290],{},"现成规则集最多，社区教程最多",[60,292,293],{},"较新，规则集相对少",[39,295,296,299,302],{},[60,297,298],{},"上手难度",[60,300,301],{},"配置更宽松",[60,303,304],{},"JSON 严格，少个逗号就报错",[15,306,307,310,311,314],{},[18,308,309],{},"对多数人的实际含义","：机场发给你的订阅链接，默认格式基本都是 Clash（YAML）系的。",[18,312,313],{},"用 mihomo 系客户端最省事","，不需要做任何格式转换。",[15,316,317],{},"sing-box 的适用场景更偏向：想用它独有的特性、习惯 JSON 配置、或者订阅方明确提供了 sing-box 配置。",[15,319,320,321,324],{},"⚠️ 本站没有对两个内核做过性能对比测试，",[18,322,323],{},"这里不给\"谁更快\"的结论","——那需要统一口径的测试环境，而本站没有。上表比较的是格式兼容性与生态，这些是可以直接核对的事实。",[148,326],{},[11,328,330],{"id":329},"三什么时候才需要关心内核","三、什么时候才需要关心内核",[15,332,333],{},"绝大多数情况下你不需要碰它。但下面三种情况会撞上：",[335,336,338],"h3",{"id":337},"订阅导入后节点列表是空的或报解析错误","① 订阅导入后节点列表是空的，或报解析错误",[15,340,341],{},[18,342,343],{},"常见原因是内核版本太老，不认识订阅里的新协议或新字段。",[15,345,346],{},"排查顺序：",[348,349,350,353,356],"ol",{},[204,351,352],{},"确认客户端本身是不是已停更的老版本（CFW、原版 ClashX、Kr328 的 Clash for Android 都属于这类）",[204,354,355],{},"如果客户端支持切换内核，换到较新的 mihomo",[204,357,358,359],{},"还不行，把订阅链接在浏览器里直接打开，看返回的是不是 YAML 文本——",[18,360,361],{},"有时问题在订阅链接本身失效，不在内核",[335,363,365],{"id":364},"想用较新的协议","② 想用较新的协议",[15,367,368,369,372],{},"Hysteria2、TUIC、VLESS + Reality 这类协议，",[18,370,371],{},"老的原版 Clash 内核不支持","。这也是当年大家从原版换到 Meta 分支的主要原因。现在只要你用的是维护中的客户端，内核默认就已经支持了。",[335,374,376],{"id":375},"在软路由-服务器上跑","③ 在软路由 \u002F 服务器上跑",[15,378,379],{},"这种场景才是真的直接和内核打交道——没有图形界面，你下载的就是 mihomo 或 sing-box 的可执行文件本身。",[148,381],{},[11,383,385],{"id":384},"四版本号怎么看什么时候该更新","四、版本号怎么看，什么时候该更新",[15,387,388],{},[18,389,390],{},"mihomo 的发布页会同时挂着两类版本：",[33,392,393,406],{},[36,394,395],{},[39,396,397,400,403],{},[42,398,399],{},"类型",[42,401,402],{},"特征",[42,404,405],{},"建议",[55,407,408,424],{},[39,409,410,413,419],{},[60,411,412],{},"正式版（Release）",[60,414,415,416],{},"有明确版本号，如 ",[29,417,418],{},"v1.x.x",[60,420,421],{},[18,422,423],{},"日常用这个",[39,425,426,429,439],{},[60,427,428],{},"预发布 \u002F Alpha",[60,430,431,432,435,436],{},"标着 ",[29,433,434],{},"Prerelease"," 或 ",[29,437,438],{},"alpha",[60,440,441],{},"除非你要试某个新特性，否则不用",[15,443,444,447,448],{},[18,445,446],{},"不必追新。"," 代理内核不是版本越新越好——除非你遇到了具体问题（协议不支持、订阅解析失败、已知漏洞），否则一个能正常工作的版本可以一直用下去。",[18,449,450],{},"频繁更新反而增加了从错误渠道下到文件的机会。",[15,452,453,454,456],{},"🛑 更新时同样只从官方 Releases 页面下载。理由和第一次安装完全一样，见 ",[135,455,138],{"href":137}," 第三节。",[148,458],{},[11,460,462],{"id":461},"五一个容易混的点客户端名字-内核名字","五、一个容易混的点：客户端名字 ≠ 内核名字",[33,464,465,478],{},[36,466,467],{},[39,468,469,472,475],{},[42,470,471],{},"你看到的名字",[42,473,474],{},"它是",[42,476,477],{},"内核是",[55,479,480,491,501,511,522,535],{},[39,481,482,485,488],{},[60,483,484],{},"Clash Verge Rev",[60,486,487],{},"客户端（Win\u002FmacOS\u002FLinux）",[60,489,490],{},"内置 mihomo",[39,492,493,496,499],{},[60,494,495],{},"ClashX Meta",[60,497,498],{},"客户端（macOS）",[60,500,490],{},[39,502,503,506,509],{},[60,504,505],{},"ClashMetaForAndroid",[60,507,508],{},"客户端（Android）",[60,510,490],{},[39,512,513,516,519],{},[60,514,515],{},"OpenClash",[60,517,518],{},"OpenWrt 插件",[60,520,521],{},"调用 mihomo",[39,523,524,526,532],{},[60,525,100],{},[60,527,528,531],{},[18,529,530],{},"内核本身","，没有界面",[60,533,534],{},"它就是内核",[39,536,537,539,544],{},[60,538,119],{},[60,540,541,543],{},[18,542,530],{},"（也有官方 GUI）",[60,545,534],{},[15,547,548,549,552],{},"带 \"Meta\" 字样的客户端名字（ClashX Meta、ClashMetaForAndroid）是",[18,550,551],{},"改名前留下的","——它们内置的其实已经是 mihomo。名字没跟着改，是因为改客户端名字会让老用户找不到。",[148,554],{},[11,556,557],{"id":557},"常见问题",[15,559,560,563],{},[18,561,562],{},"Q：我要不要把 mihomo 和 sing-box 都装上？","\n不用。它们解决同一个问题，装两个只会让你在配置上重复劳动。先用订阅方默认给的格式对应的那个。",[15,565,566,569,570,139],{},[18,567,568],{},"Q：教程里让我\"手动替换内核文件\"，要照做吗？","\n先判断是不是旧文。2023 年前的教程常有这一步，因为当时要把原版内核换成 Meta。现在的客户端内置的已经是 mihomo，通常不需要替换。如果你确实要换，",[18,571,572,573,575],{},"只从 ",[29,574,196],{}," 的 Releases 页下载",[15,577,578,581],{},[18,579,580],{},"Q：Clash Premium 是什么？","\n原核心的闭源增强版，提供过 TUN 等特性。随原项目一起停更，现在这些能力在 mihomo 里已是开源实现。看到教程提\"Premium 内核\"，属于旧文。",[15,583,584,587,588,591],{},[18,585,586],{},"Q：这些内核本身安全吗？","\n它们是开源项目，代码可查。",[18,589,590],{},"但\"开源\"保证的是可审计，不是\"已经有人替你审计过\"","——本站没有能力做代码审计，也不对此作担保。真正的风险点在下载渠道，不在项目本身。",[148,593],{},[15,595,596],{},[597,598,599],"em",{},"本文整理的是各项目的公开演化关系与仓库归属，不含本站实测数据，不对内核性能作比较。项目状态与版本随时变化，请以你访问时仓库的实际情况为准。",{"title":31,"searchDepth":601,"depth":601,"links":602},2,[603,604,605,606,612,613,614],{"id":13,"depth":601,"text":13},{"id":152,"depth":601,"text":153},{"id":225,"depth":601,"text":226},{"id":329,"depth":601,"text":330,"children":607},[608,610,611],{"id":337,"depth":609,"text":338},3,{"id":364,"depth":609,"text":365},{"id":375,"depth":609,"text":376},{"id":384,"depth":601,"text":385},{"id":461,"depth":601,"text":462},{"id":557,"depth":601,"text":557},"客户端","2026-08-04","mihomo（github.com\u002FMetaCubeX\u002Fmihomo）就是 Clash.Meta 改名后的现名，两者是同一个内核；原 Clash 核心仓库已于 2023 年底移除；sing-box 不是 Clash 分支而是独立重写的项目，配置用 JSON 而非 YAML。机场订阅默认给的基本都是 Clash（YAML）格式，用 mihomo 系客户端无需转换。图形客户端已内置内核，多数人不需要单独下载。2026-08-04 核对。","md","\u002Fimages\u002Fblog\u002Fdefault.jpg",{},true,"\u002Fblog\u002Fclash-neihe-qubie-2026",{"title":5,"description":617},"blog\u002Fclash-neihe-qubie-2026",[100,626,119,627,628],"Clash Meta","内核","Clash 下载","IOPVoU6AmzmahKmf54a96_p6LJRKi_aflVexGQv4qAk",1790440510035]