Update Flow Launcher Plugins and Check Compatibility

Plugins and comparisons · Published October 30, 2026 · Publisher: flowlauncher.app

At a glance

Plugin updates are separate from Flow Launcher application updates. Check the app version and preserve plugin settings before updating extensions. Newer default plugins may depend on a newer Flow branch, so do not copy plugin files across versions without checking compatibility.

Steps to follow

  1. Record the Flow version and the versions of any plugins important to your workflow.
  2. Back up the active UserData folder with Flow closed, then reopen the app to inspect available plugin updates.
  3. Use the plugin-update interface and review the selected items. Where selective updates are offered, update a small set and retest.
  4. Run each updated plugin with its explicit action keyword. If one fails, capture its version and error without changing all the other plugins at once.

Check the result

The updated plugins report the intended versions and still complete their basic queries. Check the main launcher separately from each integration.

Limits and common pitfalls

The 2.0 release notes describe a framework change for default plugins. A plugin from that generation is not automatically compatible with a pre-2.0 application.

Make the check repeatable

A controlled update leaves a trail: which plugins changed, which queries were tested, and where the backup lives. If a remote service fails at the same time, compare the service directly before attributing the failure to the plugin update.

Questions and answers

Can Flow check for plugin updates automatically?

The 2.0 release notes describe an option for automatic plugin-update checks. Inspect the setting in your installed version.

Sources and scope

Documentation-based guidance, with source review on October 30, 2026. What was and was not tested.

Related guides