Contact Support
Have a question or running into an issue? We'll get back to you as soon as possible.
Prefer email? info@creativeapplications.net
Common questions
Typexp isn't expanding anything. What's wrong?
Almost always an Accessibility permission issue. Open System Settings → Privacy & Security → Accessibility, find Typexp in the list, and make sure the toggle is on. If it's already on, try toggling it off and back on — macOS sometimes loses the grant after an update. Then quit and relaunch Typexp.
I granted Accessibility access but it still doesn't work.
If you moved or reinstalled the app after granting permission, macOS treats it as a different app and revokes access. Remove the existing entry from the Accessibility list, then add it again by relaunching Typexp — it will prompt you automatically. If not, drag the app into the list manually.
Does it work in every app?
It works in the vast majority of apps — Mail, Notes, Safari, Chrome, Slack, VS Code, Terminal, and more. A small number of apps with fully custom text engines (some games, certain Electron apps) may not support the standard macOS text injection API. In those cases Typexp falls back to a clipboard paste method, which works in most situations.
Is my data private? Does Typexp send anything online?
No data ever leaves your Mac. Typexp monitors keystrokes locally using the macOS Accessibility API — nothing is logged or transmitted. If you enable iCloud sync, your snippets are stored in your personal iCloud account only. See the full Privacy Policy.
How do I back up or transfer my snippets?
Your snippets are stored at ~/Library/Application Support/TextExp/snippets.json. You can copy this file to any Mac and place it in the same location. Typexp also supports automatic weekly backups — enable them in Settings. For seamless multi-Mac sync, turn on iCloud sync in Settings instead.
Which macOS versions are supported?
Typexp requires macOS 14 Sonoma or later. The full Liquid Glass design is available on macOS 26 Tahoe; earlier versions get a clean alternative appearance.
Why build another text expander?
We looked around and couldn't find one that was simple, native, and didn't ask for a monthly fee. Most options were either bloated with features we'd never use, required a subscription just to save a few snippets, or hadn't been updated in years. We wanted something that lived quietly in the menu bar, did exactly one thing well, and was yours to keep for a one-time price. So we built it.