# Flow Launcher: a plugin-driven search bar for Windows > Flow Launcher is an MIT-licensed C# launcher for Windows 10 and later that searches apps, files and file contents, and extends through community plugins. The README documents installation and features but leaves plugin authoring and rollback to the docs and repository. **Flow-Launcher/Flow.Launcher** — :mag: Quick file search & app launcher for Windows with community-made plugins - Repository: https://github.com/Flow-Launcher/Flow.Launcher - Website: https://flowlauncher.com - Stars: 15,685 · Forks: 655 - Language: C# - License: MIT - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/flow-launcher-flow-launcher ## What Flow Launcher replaces on a Windows desktop Windows has no single, fast, keyboard-first way to reach everything. The Start menu covers installed applications, Windows Search covers files when the index cooperates, and the Run dialog covers a handful of commands. Flow Launcher puts one input box in front of all of it. The README describes the scope as searching "everything from applications, files, bookmarks, YouTube, Twitter and more", and the feature list backs that up with sections for applications and files, web searches and URLs, browser bookmarks, system commands, a calculator, shell commands, Explorer locations, Windows and Control Panel settings, and Drag & Drop. The intended user is someone who keeps their hands on the keyboard and resents switching between the Start menu, File Explorer and a browser address bar. That is a Windows-only audience by construction: the project targets Windows 10 and later, and the installation methods are all Windows package managers. If your work spans macOS and Linux, this is not the tool, and the README does not pretend otherwise. The plugin angle matters more than the built-in features. Flow Launcher ships an extension surface, and the description calls the plugins community-made. That means the ceiling of what the launcher can do is set by people outside the core repository, which is both the appeal and the risk. ## How the launcher is put together The repository layout is the clearest statement of the architecture. Flow.Launcher/ holds the application, Flow.Launcher.Core/ and Flow.Launcher.Infrastructure/ hold shared logic, Flow.Launcher.Plugin/ is the contract that extensions compile against, and Plugins/ holds the bundled ones. Flow.Launcher.Test/ sits alongside them. The solution file Flow.Launcher.sln ties it together, and the default branch is dev rather than main, so the integration branch is the reference point for the source. That split tells you how a query flows. The application collects keystrokes, the core dispatches the query to registered providers, and each provider returns results that the UI ranks and renders. Built-in features such as the calculator and system commands are providers in the same sense that a community plugin is; the difference is only who ships them. The README lists file-content search as a capability and says the launcher "Supports Everything and Windows Index", which means file results are not produced by a private index that Flow Launcher maintains. It delegates to one of two backends on the machine. That delegation is the most consequential design decision in the project. It keeps Flow Launcher small and avoids a background crawler competing for disk I/O, but it also means file search quality is inherited. If Windows Index has not indexed a directory, or if Everything is not running, the launcher has nothing to show for that path. The README does not describe a fallback crawler, so treat the two backends as a hard dependency rather than a convenience. ## Installing Flow Launcher with winget, scoop or choco The README points at two direct downloads, a Windows 10+ installer and a portable zip, and lists three package managers. The package manager route is the least error-prone because it handles the update path later. The README gives this exact command for winget: ```bash winget install "Flow Launcher" ``` The quoted name matters: winget matches on the display name, and the quotes keep the space intact. Scoop and Chocolatey get their own one-liners in the same section: ```bash scoop install Flow-Launcher ``` ```bash choco install Flow-Launcher ``` After installation the launcher runs in the background and waits for its global hotkey. The README notes one first-run detail worth expecting: "When installing for the first time Windows may raise an issue about security due to code not being signed". That is a SmartScreen prompt, not a failure, and the README says continuing is fine if the download came from the repository. It also warns to trust only the official channels for downloads, which is a reasonable caution given how many similarly named launchers exist. For a first real use, open the launcher and type a fragment of an application name. If file search returns nothing useful, the next step is the backend: the README states support for Everything and Windows Index, and the search questions people ask about this project cluster around wiring Everything up. The README itself does not walk through that configuration, so the docs site it links to is where that step lives. ## Where Flow Launcher stops being the right tool The clearest limitation is the platform. There is no macOS or Linux build in the README, and every install path is a Windows package manager. Anyone who wants one launcher across a mixed fleet should not start here. The second is the indexing dependency. Because file results come from Everything or Windows Index rather than an index Flow Launcher builds, the launcher cannot fix a machine whose index is broken, and it cannot search a network share that neither backend covers. File-content search is listed as a feature, but the README does not say which backend provides it or what file types are covered, so the honest position is that content search is only as good as the backend behind it. The third is plugin quality. Community-made plugins are the point of the project, and the repository cannot guarantee that any individual plugin is maintained, safe, or compatible with the current release. The README does not describe a review process or a compatibility guarantee for third-party plugins. If your workflow depends on one plugin, that plugin is your real dependency, not Flow Launcher. Finally, the release cadence is uneven. The three most recent releases are v2.1.4 on 2026-09-20, v2.1.3 on 2026-06-08 and v2.1.2 on 2026-05-10. Two releases three months apart followed by a gap of roughly three months is not a red flag, but it does mean a plugin broken by a core change may wait a while for a fix. ## Flow Launcher compared with PowerToys Run The comparison people actually search for is Flow Launcher against PowerToys. The difference is architectural, not cosmetic. PowerToys is a suite: Run is one module inside a larger collection of Windows utilities, distributed and versioned by Microsoft as a single package. Flow Launcher is a single-purpose launcher whose extension model is the product. That has concrete consequences. With PowerToys, adding a capability usually means waiting for the suite to add it, or writing a plugin against PowerToys' own interface and tracking the suite's release cycle. With Flow Launcher, the plugin surface is the primary interface, the repository ships a dedicated Flow.Launcher.Plugin/ project for it, and the README describes the plugins as community-made. You get more third-party variety and you take on the maintenance risk that comes with it. A second difference is the file-search backend. Flow Launcher explicitly supports Everything and Windows Index, and Everything is a separate, long-established search tool that many Windows users already run. The README does not document an equivalent choice for PowerToys Run, so if you already rely on Everything, Flow Launcher slots into that setup rather than replacing it. If you want one vendor to own the whole experience, the suite approach is simpler. ## Licence, updates and what a fork costs you Flow Launcher is MIT-licensed, with the LICENSE file at the repository root. For most users that is invisible: you install a binary and use it. For anyone embedding the launcher, shipping a modified build, or bundling it into a corporate image, MIT is permissive and the practical obligation is preserving the copyright notice and licence text. This is a description of the licence terms, not legal advice; if you are redistributing, read LICENSE yourself. The upgrade story depends on how you installed it. If you used winget, scoop or choco, the package manager owns the version and you upgrade through it. If you used the installer or the portable zip, you are responsible for tracking releases yourself. The README does not document a rollback procedure for any of these paths, and it does not describe an in-app update mechanism, so plan on keeping the previous installer or zip if you need to step back after a bad release. The maintenance cost that is easy to underestimate is plugins. Each plugin is a separate artifact with its own distribution and its own compatibility with the current core. The README does not describe how plugin updates are delivered or how a plugin declares which launcher versions it supports. If you standardize on Flow Launcher across a team, the plugin set is the part you will actually be supporting. ## Conclusion Adopt Flow Launcher if you want a keyboard-first launcher on Windows 10 or 11 that you can extend with community plugins, and you are willing to install it from the official channels the README lists. Skip it if you need a cross-platform launcher, or if you will not accept unsigned first-run installers or a plugin ecosystem whose quality varies. Before committing, verify whether your Windows Search or Everything setup returns file contents at the speed you expect, and check how the plugin you depend on is distributed. The README's portable zip is the fastest way to test that without touching your installed setup. ## FAQ ### What does Flow Launcher do? It is a quick file search and app launcher for Windows with community-made plugins. The README lists searching applications, files and file contents, plus web searches, browser bookmarks, system commands, a calculator and shell commands. ### Is Flow Launcher free? The repository is MIT-licensed, with the LICENSE file at the top level. That covers the source; the README does not describe any paid tier or paid plugin. ### How do I install Flow Launcher? The README lists a Windows 10+ installer, a portable zip, and three package managers: winget install "Flow Launcher", scoop install Flow-Launcher and choco install Flow-Launcher. It notes Windows may raise a security prompt on first install because the code is not signed. ### How do I use Flow Launcher with Everything? The README states the launcher supports Everything and Windows Index for file search, but it does not document the configuration steps. The project's docs site, linked from the README, is where that setup would be described. ### Is Flow Launcher better than PowerToys? They differ in structure rather than quality. PowerToys is a suite with Run as one module; Flow Launcher is a single-purpose launcher whose primary extension surface is community plugins, and it can delegate file search to Everything or Windows Index. ## Sources - [Flow-Launcher/Flow.Launcher on GitHub](https://github.com/Flow-Launcher/Flow.Launcher) - [License: MIT](https://github.com/Flow-Launcher/Flow.Launcher/blob/dev/LICENSE) - [Project website](https://flowlauncher.com) - [README](https://github.com/Flow-Launcher/Flow.Launcher/blob/dev/README.md) - [Releases](https://github.com/Flow-Launcher/Flow.Launcher/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/flow-launcher-flow-launcher