Strata review: a keyboard-first GTK4 file manager for Arch and Omarchy

What Strata is, and who it is actually built for

Strata is a file manager for Linux desktops, written in Rust against GTK4. Its own description is narrow: a fast, keyboard-first file manager for Linux. The README goes further and names its audience directly, saying it is designed for Omarchy and works on compatible GTK4 Linux environments. Arch Linux and Omarchy are described as the primary supported environments.

That framing matters more than the feature list. This is not a distribution-neutral file manager with a fallback build for everything else. The interactive installer detects the architecture, the glibc version, Arch Linux and Omarchy 3 or 4, and the release binaries require glibc 2.39 or newer. If you run Debian stable or an older enterprise distribution, you are outside the tested path before you open the first window.

The navigation model is the other half of the pitch. Strata offers three browser modes: navigable Columns, an Icons grid, and a sortable List table. Columns is the Miller-column layout, where each directory level stays visible as a column beside its parent. If you have used ranger or yazi in a terminal, the spatial idea will be familiar, but Strata renders it as a GTK4 application with thumbnails, drag targets and desktop integration rather than a TUI.

How the search, preview and filesystem layers fit together

The mechanism worth understanding is search. Pressing Ctrl+K opens a recursive search that matches files and directories by name or path while the tree is still being indexed. Global search covers Home and all mounted local drives, independent of the folder you are currently in, and the README says the dialog warns when results are incomplete. Folder-scoped filtering is a separate feature from this global search, which is a distinction the documentation draws explicitly.

The limitation is stated in the same paragraph: URI-native remote shares are not yet included in global search. So an authenticated SMB share that you mounted through the location field is browsable but not part of the index. That is a real gap for anyone whose working set lives on a NAS.

Previews are handled by isolating parsers from the application. The README describes bounded previews for text, source code, images, camera RAW, PDF, audio and video, with native parser-backed formats isolated from the application process. The Cargo.toml backs this up with separate dependencies for each format family: poppler for PDF, gstreamer for media, resvg for SVG, cairo-rs with the pdf and png features, and gdk-pixbuf for images. File Properties reports media resolution, duration, bitrate, codecs and audio/video rates where those are available.

Filesystem work is described as cancellable directory loading, bounded streaming, incremental monitoring, stable selection, and virtualized large directories. The virtualized rendering is what keeps a directory with tens of thousands of entries usable, and the incremental monitoring is what keeps the view current without a full rescan. The README does not publish reindex timings or memory figures, so there is no number to quote here.

Installing Strata and making a first real change

The interactive installer is a shell script fetched from the repository and piped into bash. It detects the Linux architecture, the glibc version, whether the machine is Arch Linux, and whether it is Omarchy 3 or 4, then installs the latest verified stable release.

curl -fsSL https://raw.githubusercontent.com/lgse/strata/main/install.sh | bash

The README states that the installer shows every privileged package operation before asking to run it, and that it verifies both the published SHA-256 digest and GitHub Actions provenance before installing anything from the release archive. The binary lands per-user at ~/.local/bin/strata. During the run you are offered optional desktop-menu, default-folder-handler, Open file location, system file chooser, SMB, broader image and RAW, and Omarchy keybind integration.

For an unattended Arch or Omarchy install, the README gives this form. Each --with-* flag implies --non-interactive, and optional integrations stay disabled unless you select them.

curl -fsSL https://raw.githubusercontent.com/lgse/strata/main/install.sh \
  | bash -s -- --non-interactive \
      --with-smb \
      --with-raw \
      --with-desktop-entry \
      --with-folder-association \
      --with-omarchy-keybinds

Folder association implies the desktop entry and --with-file-manager. Use --with-file-manager alone if you only want Open file location integration. Non-interactive package installation needs passwordless sudo or cached credentials, and the full option list comes from ./install.sh --help.

Replacing the system file chooser is deliberately separate from all of the above. You opt in through Settings → General → System file chooser, through the installer, or by running the portal flag directly.

strata --install-portal

There is also a documented AI-assisted path: the README supplies a prompt to hand to a coding agent with terminal access, which is asked to confirm the glibc-based system and GTK4 environment, detect x86_64 versus aarch64, and select only the matching *-unknown-linux-gnu archive from the canonical lgse/strata GitHub release. Phone backends are not installed by the script at all.

Where Strata gets in your way

The glibc 2.39 floor is the first hard boundary. It is a requirement of the current binaries, not a preference, and it pushes older distributions out of scope entirely.

The second is remote search. Browsing GIO and GVfs locations such as authenticated SMB shares works from the location field, but those shares are not part of global search. If your mental model of a file manager includes finding a file by name across everything you can see, Strata does not do that yet for remote locations.

The third is the file chooser. Opting in means Strata answers file-open dialogs for other applications. That is a system-wide change of behaviour, and it is offered as a one-time in-app prompt. If you dismiss it, --without-file-chooser keeps your current chooser, and neither folder association nor an unattended install enables it automatically.

Finally, consider release cadence. v0.18.0 shipped on 2026-09-15, two days after v0.17.0 on 2026-09-13, with a release candidate in between. The repository is not archived and the last push was on 2026-09-16, so work is ongoing. Rapid minor releases are good for fixes and less good if you pin versions in a managed environment and dislike churn.

Strata against a terminal file manager like yazi

The nearest alternative for the keyboard-first audience is a terminal file manager such as yazi or ranger. Both give you Miller-style columns and modal keybindings, and both run anywhere a terminal runs, including over SSH and on distributions Strata does not support.

The difference is where the rendering and integration live. yazi draws text into a terminal emulator and inherits the terminal's font handling, clipboard behaviour and image protocol support. Strata is a GTK4 and Wayland application: the Cargo.toml pulls in gtk4, gdk4-wayland, gio and gio-unix, with gdk-pixbuf, gstreamer, poppler and sourceview5 for previews. That buys real thumbnails, PDF and media metadata in File Properties, drag and drop, a desktop entry, and the option to serve as the system file chooser.

It also costs you portability. A terminal file manager does not care whether your session is X11 or Wayland, and it does not need glibc 2.39. If you spend most of your day in tmux or over SSH, Strata is the wrong tool, because it is a graphical application that expects a GTK4 desktop session. If you want the file manager to be the thing your desktop opens when another app asks for a file, Strata is doing a job yazi does not attempt.

Licence, updates and the cost of staying current

Strata is MIT licensed, per both the repository metadata and the Cargo.toml. THIRD_PARTY_LICENSES.md sits at the repository root, which is where the bundled and linked components are accounted for. The dependency list is long and includes media and document parsers such as gstreamer, poppler and unrar, so if you redistribute a build rather than installing the published binary, the third-party notices are the file to read. That is a packaging question, not legal advice.

Updates are handled in the application. The README describes opt-in automatic checks, release notes, verified downloads, and in-place installation for release binaries. The same verification language appears in the installer: SHA-256 digest plus GitHub Actions provenance before anything from the release archive is installed.

Upgrade cost is mostly the platform floor. Each release is built against a glibc baseline, and the current one is 2.39 or newer. If you are on Arch or Omarchy you will track that without thinking about it. If you are not, you are maintaining a compatibility story the project does not claim to support. The repository also carries mise.toml, mise.lock, rustfmt.toml, deny.toml, typos.toml and a tests directory, so building from source is a documented development path rather than an afterthought, and Cargo.lock is committed.

Editorial conclusion

Adopt Strata if you run Arch or Omarchy on Wayland and want Miller-column navigation with a keyboard-first model, and if you are comfortable with a project whose releases move quickly. Skip it if you are on a non-glibc distribution, if you need remote shares indexed in global search, or if you want a file manager with a long track record. Before installing, check your glibc version, read install.sh before piping it to bash, and decide deliberately whether you want Strata to replace your system file chooser, because that choice is separate from the binary install.

Frequently asked questions

Official sources

1. lgse/strata on GitHub
2. License: MIT
3. Project website
4. README
5. Releases