mrkeyoor.comAsk

sxyazi/yazitested 09 Oct 2026commit be8dc1b

yazi review

Yazi is worth a trial for terminal users who need cross-directory selection and previews and accept configuration maintenance during public beta.

  • Build failed
  • Tests failed
13 sto install
  • 566 packages
Dev Toolsevaluationupdated 01 Nov 2026
+126stars / 7d

Try Yazi if you want terminal file browsing with cross-directory selection and previews, and can maintain your configuration through breaking changes. Yazi is a Rust terminal file manager. Our run on October 9, 2026, at commit be8dc1b stopped at a compiler compatibility error, so it does not establish whether browsing, file operations or previews work.

Verdict

Yazi is worth a trial for terminal users who need cross-directory selection and previews and accept configuration maintenance during public beta. Our October 9, 2026 run at be8dc1b did not produce a working source build: rustc 1.98.0 was unsupported by packages requiring 1.99.0. Evaluate a documented binary installation with your own files before committing to it; this review supplies no runtime performance or preview-reliability result.

We ran it

Lab card: what happened when we ran yazi
Lab card from our sandbox run
Screenshot of yazi (yazi-rs.github.io)
yazi-rs.github.io
Install✓ · 13s566 packages
Build✗ · 1s
Tests✗ · 1sran, no count parsed
Repo1487 files~80,304 lines of source · 3.2 MB · 10 CI workflows

Answers from our run

Does yazi build from source?

Dependencies installed in 13 seconds (566 packages), and the build failed. We cloned commit be8dc1b into a clean Debian container with 3 CPUs and no project-specific setup.

Do yazi's tests pass?

No. The project's own test command exited unsuccessfully after 1 seconds, and its output did not expose an individual test count.

Who should not use yazi?

Users who require configuration stability through upgrades: the project explicitly warns of breaking changes.

What are the alternatives to yazi?

lf, ranger. Yazi is worth a trial for terminal users who need cross-directory selection and previews and accept configuration maintenance during public beta.

Setup2/5Major blocker in the recorded source path: dependencies completed, but build and test commands stopped at the compiler requirement.
Docs5/5Comprehensive supplied setup documentation covers prerequisites, optional preview tools, platform installation routes and shell integration; execution did not validate all instructions.
Community5/5Assessed for documented participation routes: English Discord, Chinese Telegram, plugin extension and contributor recognition. Adoption, responsiveness and support quality are unmeasured.
Maturity3/5The README documents broad file-management capabilities but identifies public beta and warns of breaking changes; our source run provides no runtime validation.

Discussed on

  1. hnYazi: Fast terminal file manager based on async I/O157 points
  2. hnYazi – fast terminal file manager written in Rust, based on async I/O4 points

Who it’s for

Terminal users who want to collect a selection across directories and keep other locations in tabs.
People willing to install preview helpers for the file types they use.
Users comfortable maintaining Lua plugins and configuration while Yazi remains in public beta.

Who it’s NOT for

Users who require configuration stability through upgrades: the project explicitly warns of breaking changes.
People who need verified browsing performance or preview reliability from this review: our sandbox did not reach those checks.
Source builders restricted to rustc 1.98.0: the recorded checkout required rustc 1.99.0.

Setup reality

Our October 9, 2026 sandbox run at commit be8dc1b recorded a successful 13-second dependency step and 566 dependencies. The build and test commands each returned exit code 101, with each duration stored as 1 second. Both log tails identify rustc 1.98.0 as unsupported and list Yazi 26.9.1 packages requiring rustc 1.99.0.

The installation guide requires file for file-type detection. Optional tools include FFmpeg for video thumbnails, Poppler for PDF previews and non-standalone 7-Zip for archive extraction and preview. These are complements to Yazi, not alternative file managers. Their presence and operation were not established by our dependency count.

Official binaries provide a documented alternative to compiling from source. We did not test that route. The quick-start guide also supplies a shell wrapper for changing the parent shell's working directory when leaving Yazi.

Should you try Yazi?

Yazi makes sense if selecting files across folders and inspecting previews would simplify work you already do in a terminal. Its README documents tabs, cross-directory selection and scrollable previews. Treat those as documented capabilities: our sandbox could not build the recorded checkout, so this review cannot confirm their behavior.

The project describes Yazi as public beta and warns of breaking changes. That matters if you intend to customize it. Lua plugins can change previews and much of the interface, but a setup you depend on also needs an upgrade plan. If maintaining that configuration is unwelcome, choose another file manager.

Our run stopped at the compiler requirement

Our run took place on October 9, 2026, at commit be8dc1b158b610254a67ee421900e8d3e6f2903b. The matching stored sandbox record specifies 3 CPUs, 12 GB of memory and the lab-rust:1 image. It records a successful dependency step in 13 seconds, with 566 dependencies, followed by build and test command failures. Each command returned exit code 101 and has a stored duration of 1 second.

Both recorded command tails identify rustc 1.98.0 as unsupported and list Yazi packages requiring rustc 1.99.0. This is a toolchain compatibility blocker for that checkout in our sandbox. It is not evidence of a failed file-copy operation or a failed test assertion.

The harness stores a success flag, exit code, elapsed time, timeout flag and log tail for each step. Here, the successful dependency step establishes only that the step completed. The test command failed before providing a test result summary; the stored test counts are null. We have no passing-test total to report.

We did not test interactive browsing, copying, image rendering, runtime speed or installation from an official binary. No audit result is attached, and scan coverage is unknown. The MrKeyoor testing-methodology page explains how command outcomes are reported and their limits. It provides provenance context, not evidence that this October run used today's procedure or that we executed it again.

Set up previews for the files you actually use

The installation guide requires file for file-type detection. It lists FFmpeg for video thumbnails, Poppler for PDF previews and non-standalone 7-Zip for archive extraction and preview as optional extensions. Install the helpers your workflow needs rather than assuming the Yazi executable supplies every preview.

Image support also depends on the terminal. The README lists built-in protocol support for terminals including Kitty and Ghostty, with Überzug++ and Chafa as other rendering paths. Our failed source run did not verify any of these paths. Check your own terminal with representative files before making previews part of a daily workflow.

The installation guide documents official binaries and an official Debian and Ubuntu APT repository. A packaged release is a reasonable next trial if you want to evaluate the application without first resolving this source-build mismatch. That recommendation is a setup choice, not a measured success for the binary route.

For shell navigation, the quick-start guide supplies a wrapper that lets the shell change directory when Yazi exits. Use its instructions for your shell if you want navigation inside Yazi to carry back into the command prompt.

When lf or ranger fits better

lf supports customization through shell commands and deliberately leaves tabs or windows to a window manager or terminal multiplexer. Choose lf if that division fits how you already work. It is an alternative file manager, not a preview helper for Yazi. We did not run it for this comparison.

ranger provides file previews, tabs and a directory hierarchy view, and requires Python with curses. Choose ranger if those features and its Python environment fit your setup. Its README also lists external tools for enhanced previews, so switching does not remove the need to check preview dependencies. We did not benchmark ranger against Yazi.

How to read the scores

These are editorial assessments, not comparative benchmarks. On the five-point scale, 1 means substantial obstacles, 2 means a major blocker in the recorded path, 3 means useful capability with material maintenance limits, 4 means strong support with identifiable gaps, and 5 means the stated dimension is comprehensively documented in the supplied evidence. Each dimension has a narrower basis below.

Setup ease is 2 because our source-build path stopped after dependency installation. Documentation is 5 for the supplied installation prerequisites, platform routes and shell instructions; it does not certify every instruction by execution. Community is 5 on a rubric of documented participation and support routes: the README names English Discord and Chinese Telegram channels, describes a plugin system and credits active code contributors. That score does not measure adoption, response time or support quality. Maturity is 3 because the project documents a broad file-management feature set while explicitly warning of breaking changes in public beta.

Before adopting Yazi, try a packaged release with a selection spanning folders and the preview types you depend on. Keep the compiler failure in its proper scope: it blocks our recorded source run, while application behavior remains untested here.

Alternatives

ProjectWhat it isPick it when
lfA Go terminal file manager configurable through shell commands.Choose it when shell-command customization suits you and you want your window manager or terminal multiplexer to handle tabs and windows.
rangerA console file manager with previews, tabs and a Python-with-curses dependency.Choose it when its directory hierarchy view and Python environment fit your setup, while checking the external tools needed for your previews.

Sources

  1. Yazi README and repository
  2. Yazi installation guide
  3. Yazi quick start and shell wrapper
  4. Yazi image-preview compatibility
  5. Yazi v26.9.1 release
  6. Native archive-folder browsing request, issue 4420
  7. Windows High Contrast readability report, issue 4419
  8. Yazi current issue activity

More dev tools reviews

Related reading