Text expansion in Obsidian with Espanso

Text expansion in plain-text, cross-app shortcuts is the practical upgrade that makes heavy typing feel manageable—especially inside Obsidian workflows. Espanso, a free open source tool, lets frequent phrases, links, templates, and even conditional text be triggered by short keystrokes anywhere on a computer (not just inside Obsidian). The biggest differentiator is how it’s configured: all settings live in editable plain text files, which can be version-controlled with GitHub and shared across machines.

That plain-text setup matters because it turns personal “typing automation” into something portable and maintainable. Espanso supports Linux, Windows, and macOS, and its configuration can be located via a command that prints the local configuration path. From there, users can open the configuration directory and edit files directly—no proprietary UI required. The configuration is split into a general config area and a match area. The match folder holds the actual expansion rules, and the speaker uses Git ignore patterns to avoid pushing private configuration (like contact details or other sensitive entries) to a remote repository.

At the core of Espanso are “matches,” which pair a trigger with an output. A basic match replaces what the user types (often a short token such as a word or keystroke sequence) with a longer phrase. The speaker’s style uses a semicolon prefix as a deliberate trigger so normal typing won’t accidentally expand. Examples include contact blocks (typing “;NVDH” expands to a full name), social links (e.g., “;me.gh” for a GitHub URL), and affiliate links (typing “;aff.Napkin” inserts a specific affiliate URL). Emojis and Obsidian-specific snippets also get treated as expansions, so the same shortcut works in any app—flags, theme links, and formatted “Obsidian” references.

Beyond simple replacements, Espanso supports richer match types. “Extensions” can pull in dynamic content such as dates, reuse clipboard text, offer multiple choices, randomize outputs, or run scripts. The speaker uses a date trigger that inserts today’s date using configurable formatting, including an Obsidian-friendly variant that wraps the date in brackets. For more controlled messaging, “regex triggers” let expansions depend on patterns rather than fixed text. That’s used to refuse sponsorships with a templated response: the typed product name is captured and injected into a prewritten explanation. A similar regex-based approach handles tool inquiries for PKM apps by inserting a response that asks vendors to confirm which requirements are met.

The speaker also addresses why not to rely on Obsidian-only solutions. Obsidian plugins for text snippets exist, but they don’t help in email, chat, YouTube comments, or other apps. Espanso’s value is that it works system-wide, so the same shortcuts apply everywhere. Compared with Text Expander, Espanso’s open source, free model and file-based configuration are presented as key advantages.

Overall, the workflow is about reducing friction: automate the repetitive parts of communication and writing so attention stays on the meaningful work—while keeping everything organized, shareable, and easy to evolve through version-controlled plain text.