SwiftList: A .NET 10 Alternative to Everything and Listary with USN Journal Indexing
A modern, high-performance local file search and productivity tool for Windows. A sleek, customizable alternative to Everything and Listary built with C# WPF and NT Services, featuring instant NTFS MFT parsing, real-time USN monitoring, and plugin support.
At a glance
- What is it?
- SwiftList is an open-source Windows search tool that indexes NTFS drives via the USN Journal and MFT, offering a popup, a main window, and an inline Explorer bar. This review covers its architecture, setup, limitations, and where it fits against established tools.
- Who is it for?
- Adopt SwiftList if you want a modern, MIT-licensed search tool that reads the NTFS USN Journal and MFT directly, with a plugin SDK and a SYSTEM-level service for real-time indexing. Avoid it if you need a tool that works on non-NTFS drives or if you cannot run a background service; the portable build may lack some features.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 42 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What SwiftList Solves and Who It Targets
SwiftList addresses a specific pain: finding files on Windows quickly without the overhead of a full-text indexer or a slow directory walk. The README positions it as an open-source alternative to Everything and Listary, which are the two dominant tools in this space. The target user is someone who regularly searches local NTFS drives and wants results in milliseconds, not seconds. The project also targets power users who want to extend search behavior through plugins, since it ships an open plugin SDK. It is not a general-purpose desktop search tool; it focuses on filenames and paths, not file contents. The README does not mention content search, so you should not expect it to index file text. The intended audience is Windows users on Windows 10 or 11, with a preference for x64 or ARM64 hardware.
Inside the Indexing Mechanism: USN Journal and MFT
The core mechanism is direct reading of the NTFS USN Journal and the Master File Table (MFT). Instead of walking directories recursively, which is slow on large drives, SwiftList reads the on-disk structures that NTFS already maintains. The USN Journal records changes to files and directories, so the indexing service can track modifications in real time. The MFT contains metadata for every file on the volume, which allows initial enumeration without a full scan. The README calls this 'millisecond indexing' and describes a 'low-footprint background service' that keeps the index in sync. This is the same fundamental approach that Everything uses, but SwiftList implements it in C# with .NET 10 and WPF. The architecture separates a SYSTEM-level indexing service from the per-user UI, which the README calls 'process isolation'. That separation is a design choice that helps with permissions, because reading the USN Journal often requires elevated privileges. The service runs at SYSTEM level, while the UI runs as a normal user process, reducing the attack surface of the UI.
Three Search Interfaces: Popup, Main Window, and Explorer Bar
SwiftList offers three ways to invoke a search. The quick popup window is a small overlay that appears on a hotkey, designed for fast queries without leaving the current context. The full main window is a larger interface for browsing results and managing settings. The third option is an inline bar that docks directly into File Explorer or native file dialogs, which is a distinctive feature compared to Everything's standalone window. The README says this inline bar is one of the 'three ways to search', but it does not specify how it integrates with Explorer or whether it works with all dialog types. This is a potential area for verification. The inline bar is a strong productivity feature for users who live in Explorer, but it also adds complexity and potential compatibility issues with Windows updates. The README does not state whether the inline bar requires a shell extension or a separate process, so you should test it on your specific Windows build.
Search Syntax and Fuzzy Matching
Search is not plain substring matching. The README describes 'FZF-style fuzzy search', which means it uses a scoring algorithm similar to the fzf command-line tool. Users can combine multiple keywords, and the matching supports prefix, suffix, exact, and exclude operators. For example, you can search for files that start with a certain string, end with another, or exclude a pattern. The README also mentions pinyin aliasing for Chinese filenames, which is a thoughtful addition for users who type in romanized Chinese. This feature is not present in Everything or Listary by default, so it is a differentiator for Chinese-speaking users. The exact syntax is not documented in the README; it points to the User Manual for details. This is a limitation of the README, but it suggests that the search language is rich and may have a learning curve. The fuzzy matching is a step beyond Everything's simple wildcard support, but it may also produce unexpected matches if users are not familiar with fuzzy scoring.
Getting It Running: Install, Portable, and Build
The README provides clear download options. For x64 systems, there is an installer (SwiftList-Setup.exe) and a portable ZIP (SwiftList-Portable.zip). For ARM64, there are native builds: SwiftList-Setup_arm64.exe and SwiftList-Portable_arm64.zip. The installer is 'recommended' because it supports the background service, which is essential for real-time USN Journal monitoring. The portable build likely runs without installation, but the README does not confirm whether the background service works in portable mode. That is a gap to verify. Building from source requires Windows 10/11, the .NET 10 SDK, Visual Studio 2022 or JetBrains Rider, and Inno Setup if you want to build the installer. The repo provides two batch files: build_and_run.bat rebuilds and relaunches everything locally, and make.bat produces Release builds for both x64 and ARM64 in dist/. These commands are straightforward for a .NET developer, but they assume a specific toolchain. The README does not list any NuGet dependencies or third-party libraries, so the build process may be relatively self-contained.
Limitations and When It Is the Wrong Tool
The most obvious limitation is that SwiftList only indexes NTFS drives, because it reads USN Journal and MFT structures. If you have files on exFAT, FAT32, or network drives, this tool will not index them. The README does not mention any fallback for non-NTFS volumes. That is a hard boundary. Another limitation is the requirement for a background service. The installer is recommended because it supports the service, but if you run the portable build, you may lose real-time updates. The README does not explain the implications of running without the service. Also, the project targets .NET 10, which is a very new runtime. If you are on an older Windows version or cannot install .NET 10, you may have compatibility issues. The README states Windows 10/11 as a requirement, but it does not specify which minor versions are supported. Finally, the plugin SDK is open, but the README does not detail the API. That means you cannot assess the effort of writing a plugin without consulting the Developer Manual. For a user who needs a simple search tool and does not care about plugins, the extra complexity of the service and the SDK may be overkill.
Comparison with Everything and Listary
Everything is the most direct competitor. It also reads the USN Journal and MFT, and it is known for its speed and tiny footprint. SwiftList differs in three ways: it is written in C# and .NET 10, it offers a plugin SDK, and it includes an inline Explorer bar. Everything has a simpler interface and a longer track record, but it does not have a built-in plugin system in the same way. Listary is a productivity launcher that focuses on quick file access and application launching, with a different architecture that does not rely solely on MFT. SwiftList's approach is closer to Everything in terms of indexing, but it adds a launcher component and a more modern UI. The README claims 'ultra-lightweight' and 'low-resource', but it does not provide memory or CPU numbers, so you cannot compare directly. The choice between these tools may come down to the plugin ecosystem and the inline Explorer integration. If you need a specific search provider or a custom action, SwiftList's SDK is a differentiator. If you want a battle-tested tool with a large user base, Everything may be safer.
Maintenance, Upgrade Cost, and License
The project is under the MIT License, which is permissive and allows commercial use, modification, and redistribution with attribution. The README does not include a copy of the license text, but the license identifier is clear. The repository shows recent activity: the last push and the latest release v4.2.2 are both dated 2026-08-05, indicating active development. There are three releases on the same day (v4.2.0, v4.2.1, v4.2.2), which suggests a rapid release cycle, possibly fixing bugs quickly. That is a positive sign for maintenance, but it also means you may need to update frequently to get fixes. The upgrade cost depends on how you install. The installer likely supports in-place upgrades, but the README does not describe the upgrade process. The portable build requires manual replacement of files, which is a low-cost but manual process. The plugin SDK is open, but the README does not state whether plugins are version-locked to a specific SwiftList release. That is a risk: a plugin written for v4.2.0 may not work with v4.2.2 if the API changed. You should check the Developer Manual for versioning policy before building a plugin.
Editorial conclusion
Adopt SwiftList if you want a modern, MIT-licensed search tool that reads the NTFS USN Journal and MFT directly, with a plugin SDK and a SYSTEM-level service for real-time indexing. Avoid it if you need a tool that works on non-NTFS drives or if you cannot run a background service; the portable build may lack some features. Before adopting, verify that your Windows version supports .NET 10 and that the USN Journal is enabled on your target volumes. Confirm that the inline Explorer bar works with your specific Windows Explorer version and that the plugin API covers the extensions you need. Check the latest release notes for v4.2.2 to see if any known issues affect your use case.
Community notes