Disable or Remove a Flow Launcher Plugin

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

At a glance

Disable a plugin first when you want to test whether it causes a problem. Remove it through the supported plugin-management interface once you no longer need it. Back up settings before removal and review any external service credentials separately.

Steps to follow

  1. Find the exact plugin in Settings and record its author, version, action keyword, and any configuration you may want to restore.
  2. Disable it and repeat the query or startup sequence that was failing. Keep other settings unchanged.
  3. Use the plugin manager’s remove or uninstall action if you want permanent removal. Restart Flow if the interface requests it.
  4. Check that the plugin no longer contributes results. Revoke unused API tokens at the connected service when appropriate.

Check the result

The plugin is disabled or absent as intended, its keyword no longer triggers it, and your other queries still work.

Limits and common pitfalls

Deleting arbitrary directories while Flow is running can leave inconsistent state. A disabled plugin can also retain settings, so disable and delete are not equivalent privacy actions.

Make the check repeatable

Treat disabling as a diagnostic experiment. If the symptom disappears, re-enable the same plugin once to confirm the relationship when safe. Report the minimal reproduction to its maintainer instead of labeling the whole launcher broken based on one extension.

Questions and answers

Will removing a plugin uninstall Flow Launcher?

No. Plugin management and application removal are separate operations.

Sources and scope

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

Related guides

Package information and verification