Espanso Problems & Issues
Real user-reported problems, complaints, and limitations for Espanso. Based on analysis of 13 signals.
Overall score: 64/100
Issues by Category
Espanso expansions stop working until you restart it
Users report the service still showing as running while triggers no longer expand, often after sleep or resume, until `espanso restart` is run. Most reported on Linux and Wayland but also seen elsewhere.
Espanso fails to start on Fedora and other Wayland setups
Reports of 'unable to start service: timed out' and EVDEV permission errors on Fedora KDE, where only running the Wayland binary directly worked and systemd service mode did not.
Espanso not expanding in terminals and some apps
Terminals (Kitty, Windows console host), Obsidian and Electron apps are reported as trouble spots: dropped characters, wrong special characters or nothing happening. Switching backend or paste shortcut per app usually fixes it.
Espanso on Wayland is experimental and hard to set up
Wayland support is labelled experimental in the official docs. It needs a Wayland-specific build (not available as a package on every distro), a setcap step for input device access, and a keyboard layout set by hand for non-US layouts.
macOS accessibility permission confusion after install or update
Espanso needs Accessibility permission on macOS. Users report it not sticking after updates or reinstalls, and having to remove and re-add the entry, plus a security warning on first start.
Long replacements silently fail (clipboard_threshold)
Replacements over 100 characters switch to clipboard injection by default. In some setups this fails with no warning, so long snippets do nothing until clipboard_threshold or backend is changed.
YAML config is a barrier for non-technical users
Everything is configured by hand in YAML files. Indentation and quoting mistakes break matches, and there is no built-in visual editor, which is the main reason people pick TextExpander or Text Blaze instead.
No mobile apps and no built-in sync
Espanso runs on Windows, macOS and Linux only. There is no iOS or Android app and no cloud sync, so snippets travel only via git, Dropbox or similar.
Keyboard layout and new keyboards confuse Espanso
Non-US layouts on Wayland need layout set in default.yml, and a newly connected keyboard is only picked up after restarting Espanso.
Espanso stops on macOS when Secure Input is stuck
On macOS, Secure Input (turned on by password fields, and often left on by password managers or browser extensions) blocks all expansion. The official docs call it unreliable and say the auto-fix only works on older macOS versions.
App-specific configs are not supported on Wayland
Per-app configuration (filter_title, filter_exec, filter_class) does not work on Wayland, apart from a partial workaround on KDE with kdotool. This removes the usual fix for apps that misbehave.
Support is community only with a large open issue backlog
Help comes from GitHub issues, Discussions and Reddit. The repository carries around 546 open issues, and some threads end without a documented fix.
Free and open source, but expect time cost
Espanso is GPL-3.0 and free, with donations only. The cost is setup and troubleshooting time rather than money.
Regret Patterns
Common reasons users regret choosing Espanso.
Choosing it expecting a GUI
New users expect a snippet manager window and find only YAML files.
Wayland switch breaks expansion
Moving from X11 to Wayland means a different build, permissions and no app-specific configs.
Snippets work, then silently stop
Expansion quits after sleep or an update until Espanso is restarted.
Mac permission reset after update
Accessibility permission has to be re-granted after an update or reinstall.
Long snippets fail in some apps
Clipboard injection of long text breaks in terminals and some editors.
Needing sync or mobile later
No phone app or sync leaves a gap when workflow expands.
When Espanso Breaks Down
Specific scenarios where Espanso fails or underperforms.
Password fields and Secure Input on macOS
Expansion is blocked while macOS Secure Input is active, even when stuck.
Wayland sessions
Experimental, needs extra setup, no app-specific configs.
Terminals and Electron apps
Dropped or wrong characters, paste shortcut mismatch.
Replacements over 100 characters
Switch to clipboard injection which can fail silently.
Fedora KDE with systemd service
Service times out or lacks input device access.
After sleep or resume
Service looks alive but expansion stops until restart.
Large shared snippet libraries
Hand-edited YAML is hard to maintain for teams.