Move from Wox to Flow Launcher: Rebuild and Verify

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

At a glance

Moving from Wox to Flow Launcher is best treated as a configuration migration rather than a blind folder copy. Record the workflows you use, install Flow separately, and recreate keywords and plugins using versions intended for Flow. Preserve the old setup until your essential queries work.

Steps to follow

Write down your activation shortcut, frequently used plugins, custom queries, and theme preferences in the existing launcher.
Install Flow and assign a different hotkey temporarily so the two applications do not compete during comparison.
Find maintained Flow-compatible versions of the plugins you need. Recreate configuration deliberately instead of copying every old binary.
Test a small set of real workflows, then disable the old launcher’s startup entry when you decide to switch.

Check the result

Your core app, file, and plugin queries work in Flow, and only the intended launcher handles the final activation shortcut.

Limits and common pitfalls

A shared project history does not guarantee that all plugin APIs, themes, or configuration formats are interchangeable.

Make the check repeatable

A migration checklist should describe outcomes, not just installed plugin names: open a project folder, search a bookmark, run a known local command, or find a document. You may be able to replace an old extension with a built-in Flow feature instead of carrying over extra dependencies.

Questions and answers

Can I copy all Wox plugins directly into Flow?

Do not assume that. Use compatible releases or follow the project’s plugin-porting guidance for code you maintain.

Sources and scope

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

Related guides

Plugins and comparisons