A Clipboard With Folders and Tags on Mac

A Clipboard With Folders and Tags on Mac

A flat list of everything you've ever copied is useful as a safety net but useless as a library. Once you start reusing certain clips — boilerplate, addresses, command snippets, canned replies — you want structure: a way to group related items so you can find them in a second instead of scrolling. On macOS, ClipHistory provides that structure through boards, snippets, and pins.

Two jobs, two tools

A clipboard manager really does two things:

1. Catch what you just copied — the rolling history. ClipHistory keeps your last 150 unpinned clips, newest-first. This is your short-term safety net.
2. Organize what you reuse — the structured layer. This is where boards and snippets come in.

Confusing the two leads to frustration. The history isn't meant to be a permanent filing cabinet; the structured layer is.

Boards: the "folders" for your clips

A board groups related clips and snippets together. Think of a board the way you'd think of a folder:

• A board for work boilerplate — signatures, status templates, standard replies.
• A board for dev — license headers, common commands, config blocks.
• A board for personal — addresses, account numbers, frequently pasted info.

Instead of one endless scroll, you open the relevant board and the items you need are right there, grouped by context.

Snippets: items that don't expire

Anything you save as a snippet persists beyond the rolling 150-clip history. That's the key difference from an ordinary clip: a snippet stays put. Save the text you reuse for weeks or months — boilerplate, templates, commands — as snippets, and organize them onto boards.

Naming matters. A snippet called "MIT header" or "weekly status template" is findable; an unnamed blob is not. Give snippets clear names so search in the Cmd+Shift+V panel surfaces them instantly.

Pins: keep the daily items on top

Pinning is the lightweight way to keep a clip around. Pinned clips don't expire out of the 150-clip window, and you can pin as many as you like — pins are unlimited. Use pins for the handful of things you reach for every single day, and reserve boards for fuller, organized collections.

A simple mental model:

• History = recent, automatic, temporary.
• Pins = a few daily-use items kept from expiring.
• Snippets on boards = your organized, permanent library.

Finding things fast

Structure only pays off if retrieval is quick. Open the history panel with the global shortcut Cmd+Shift+V from any app, then:

• Type to search across your clips and snippets by content or name.
• Browse a board when you want everything in one context.
• Grab a pinned item from the top.

The whole flow is keyboard-first, so organizing doesn't slow you down.

Transform organized clips on the way out

Because your library is structured, you can keep a single canonical version of a template and adapt it at paste time with AI transforms:

• Translate a standard message into another language.
• Rewrite a canned reply for a different tone.
• Clean formatting before pasting into a plain-text field.
• Summarize a long template down to essentials.

Transforms run through your own API key — Anthropic, OpenAI, DeepSeek, Google, or a custom endpoint — and everything stays local. No cloud, no account.

Keeping the library tidy

A few habits keep boards useful:

• Promote a clip to a snippet the second time you reuse it.
• Put it on the right board immediately, while you remember the context.
• Prune snippets you've stopped using.
• Pin sparingly — pins are for daily items, not everything.

Privacy by default

Your organized clips often hold sensitive things: account info, internal templates, credentials in commands. ClipHistory keeps it all local — no cloud, no account — and is signed and notarized by Apple, runs as a universal binary on Apple Silicon and Intel, and supports macOS 12+.

A worked example: organizing a dev board

Suppose you set up a dev board. Onto it you save: an MIT license header, a Dockerfile skeleton, your standard .gitignore, the psql connection string for staging, and a commit-message template. Each is a named snippet, so a quick search for "docker" or "psql" surfaces the right one. The three you touch every day — the connection string, the license header, the commit template — you also pin so they sit at the top of the panel. Now scaffolding a new repo is a sequence of searches-and-pastes instead of hunting through old files. The board is the folder; the snippets are the documents; the pins are the shortcuts to the ones you use most.

When to use which

A simple decision guide:

• Just copied it, need it again in a minute? Leave it in the history; grab it with Cmd+Shift+V.
• Reuse it every day? Pin it.
• Reuse it for weeks and want it grouped with related items? Save it as a snippet on a board.

Following that, the rolling history stays clean for genuinely recent items, while your reusable material lives in a structure you can navigate.

Structure scales

A flat history works at ten clips and breaks down at a hundred. Boards and snippets are what let the system grow with you: instead of one ever-longer list, you have a handful of focused contexts plus a few pinned essentials. Retrieval stays fast because you're searching within meaning, not scrolling through chronology.

Structure turns a clipboard from a place things disappear into a place you actually keep them.

Ready to stop losing what you copied? Get ClipHistory for macOS — $19.99, one-time payment, 12-month license, no auto-renewal. Signed & notarized by Apple, universal binary, everything stays on your Mac.