sxyazi/yazi

Choose this fork only if you want an almost-identical upstream base. If you want new functionality or an actively differentiated build, upstream is the better choice right now.

Choose this fork only if its older feature set plus a few concrete workflow additions match your needs. If you want the newest Yazi capabilities, active fixes, and easier upgrade path, upstream is the better default.

Prefer upstream unless you explicitly need this fork’s older API additions or packaging conveniences. This fork is best for adopters who want a frozen, experimental Yazi variant; it is not a good choice if you want current maintenance or broad feature parity.

Choose this fork only if its VFS/URL/DDS direction is the point of adoption. If you want a current, broadly supported daily-driver Yazi, upstream is the safer choice because this fork is far behind and highly divergent.

Choose this fork only if its added preview support and simplified controls match your workflow and you are willing to give up upstream freshness. For most adopters, upstream Yazi is the safer default.

Choose this fork only if its specific behavioral changes are exactly what you need and you can tolerate being far behind upstream. For most users, active upstream Yazi is the safer choice.

Choose this fork only if its added selection/UI tweaks are exactly what you want and you are willing to accept being far behind upstream. For most adopters, current upstream Yazi is the safer and more capable choice.

Prefer upstream unless you specifically need this fork's early customization work or are willing to maintain a large rebase burden. This fork is not a good choice if you want current Yazi features, active maintenance, or plugin ecosystem compatibility.

Choose upstream unless you specifically need this fork’s separate repo identity; it adds no visible functionality and is already slightly behind current Yazi.