Docs Reference

Tips and best practices

Watch the videoWhen something does not work1:22
Open on YouTube

Naming abbreviations

Pick one prefix and stay with it: z (zem, zsig, ztodo), ; (;em, ;sig) or jj. Three to five characters. Avoid anything you would type by accident.

Organizing

Collections for broad buckets (Personal, Work, Developer). Tags for things that cut across them (email, meeting, code). Favorites for the handful you use every day.

Clipboard token in scripts

Always quote it:

echo "{{clipboard}}" | tr '[:lower:]' '[:upper:]'

Unquoted, any clipboard content with a space or a special character breaks the script.

Cursor positioning

{{cursor}} is reliable in native apps. In web apps it is approximate, because keystrokes are processed asynchronously. For web-app snippets, put the part you want to edit at the end of the body.

Rich text fidelity

Bold, italic, lists and alignment survive into TextEdit, Mail, Notes, Google Docs and Slack. Some advanced formatting renders differently per app; that is macOS converting HTML to RTF, not a TypeFire bug.

Getting the most out of Clips

  • Pin the handful of things you paste constantly. Pinned clips ignore every retention rule.
  • Name anything you want to find later. Names are searchable; "[Image 454×229]" is not.
  • Use tags for projects. A client-acme tag turns three weeks of scattered copies into one list.
  • Turn on screenshot auto-import if you work in design tools. Every screenshot becomes searchable by the text inside it, thanks to on-device OCR.

TypeFire runs entirely on your Mac. Snippets are plain Markdown files you own and can read with any editor. Questions or bugs: Settings → Feedback.

Documentation for TypeFire 5.1.0. Updated 2026-09-15.