Async file work and previews are the reason to choose Yazi
Yazi is a three-pane terminal file manager with Vim-like movement, visual selection, tabs, bulk rename, archive handling, trash, drag and drop, and a file chooser. Its right pane can preview code, images, video, PDFs, archives, and directories. File operations run asynchronously, CPU work can use several threads, and long tasks expose progress and cancellation. That mix is more useful than a plain directory tree when the terminal is already where you edit code and run commands.
The lab clone at commit fef23f3 contained 1,399 files and about 76,133 lines of source in a 3.1 MB checkout. That is a substantial Rust application, not a thin shell around ls. Yazi also has a concurrent Lua plugin system, a package manager for plugins and themes, custom previewers, virtual filesystem providers, and communication between running instances without a separate server process. The breadth explains both its appeal and the amount of configuration surface users inherit.
What happened when we ran it
In our fresh Debian sandbox, Yazi installed in 32 seconds and pulled 569 packages. The Rust build completed successfully in 264 seconds on 3 CPUs with 12 GB of RAM. Those results show that commit fef23f3 was buildable in the stated rust:1-bookworm container without credentials or privileged access. They do not measure interactive speed, preview latency, or file-copy throughput, so the README's speed claim remains a design claim rather than a benchmark from this run.
cargo test also exited successfully in 12 seconds, but it reported 0 passed and 0 failed out of 0. The repository had 10 CI workflow files and no tests directory in the checkout. A successful command with zero discovered tests gives little evidence about file moves, plugin compatibility, terminal probing, or platform-specific openers. The honest reading is that the build path worked, while the test command did not exercise a suite.
Rich previews require more than the core binary
The installation guide names file as a prerequisite for file-type detection. The polished preview and search setup adds separate programs: ffmpeg for video thumbnails, 7-Zip for archives, poppler for PDFs, fd and ripgrep for search, fzf and zoxide for movement, resvg for SVGs, and ImageMagick for more image formats. Yazi needs no hosted account or API key, but users still own this local dependency chain. Community packages may also trail the current release.
That distinction matters after an install which pulled 569 packages in the container. A basic browser can work before every optional tool is present, but a missing thumbnail or search action may come from the companion program rather than Yazi. Image display depends on terminal support for Kitty graphics, iTerm2 images, or Sixel; X11 and Wayland fallbacks use Überzug++, while Chafa supplies an ASCII path. Windows adds its own file.exe and MIME-detection setup.
Public beta means release notes are part of maintenance
The README calls Yazi a public beta suitable as a daily driver and warns that heavy development can bring breaking changes. Release v26.8.15 shows both sides. It added drag and drop, trash, bulk create, an official Debian and Ubuntu APT repository, and custom VFS providers. The same release renamed SFTP configuration sections, changed key syntax, removed an archive URL behavior from the core, and deprecated several Lua and action APIs. A plugin-heavy setup should be pinned and upgraded deliberately.
The 76,133-line checkout still has platform edges documented in open reports. Remote filesystem search is disabled in the VFS tracker, and fzf support for remote files is still unchecked. Another report describes APFS-to-macFUSE copy failure when a Cryptomator destination rejects extended attributes. A separate Linux report says a Sioyek AppImage opens through the shell and Nautilus but not through Yazi. Each is a good reason to test the exact remote, mount, and opener workflow you depend on.
Active maintenance outweighs the thin sandbox test signal
The repository had 41,679 stars and 66 open issues and pull requests when we fetched it. The latest release was published on August 15, 2026, code was pushed on August 25, and issues were updated that week. That combination is stronger health evidence than a release tag alone. Documentation is also unusually detailed, with separate guides for installation, configuration, image protocols, plugins, the command line, drag and drop, and inter-instance messaging.
Yazi earned a 264-second successful build in the Debian container, but the 0-test result keeps it from receiving a blank check. For terminal users who want previews and are comfortable maintaining a toolchain, the feature set is hard to match. Start with the core binary and file, add preview programs only when you need them, and keep the previous package plus configuration available during upgrades. If those habits feel normal, Yazi is an easy first trial; if they feel burdensome, nnn or ranger asks less of its owner.