Quick answer: macOS has no clipboard history of its own, and most Mac clipboard managers have no one-click export either. You have three real options: pick an app that advertises export, read your manager’s local database directly, or run a small script that logs the clipboard to a file. Which one fits depends on whether you need a past archive or future logging.
It sounds like a basic feature. A clipboard manager stores everything you copy, so surely you can save that list somewhere. In practice, most of these tools are built around the opposite workflow: recall something quickly, paste it, move on. History is treated as a short-lived buffer, not an archive.
That matters if you want to search last week’s copied snippets, hand a log to a colleague, back up pinned items before a reinstall, or migrate to another tool. Here is what is realistic, what takes some effort, and what to avoid.
| Route | Best for | Output | Effort | Catch |
|---|---|---|---|---|
| 1. App with built-in export | Regular archiving, non-technical users | Varies by app (text, JSON, CSV) | Low | Few apps offer it; may mean switching tools |
| 2. Read the local database | One-off recovery of existing history | Whatever you query out with SQLite | Medium | Storage format can change between versions |
| 3. Logging script | Ongoing, searchable plain-text log | Plain text file | Medium | Text only; captures sensitive content unless you filter |
If export is a hard requirement, check the app’s documentation before installing, not after you have six months of history. Look for three things: the export format (plain text, JSON, CSV), whether images and files are included or only text, and whether export covers pinned items and metadata like timestamps and source app.
Compare candidates on those points using each app’s current documentation, since features change between releases. Paid, sync-focused managers are more likely to have structured data handling. Lightweight, local-first tools tend to skip it. We have not verified export support for specific competing apps here, so confirm each one yourself .
Maccy is a free, open-source, local-first clipboard manager for macOS. It keeps history on your Mac, with no account and no cloud sync. As far as we know it does not ship a dedicated « Export history » command . Because the data is local, though, routes 2 and 3 below work with it.
Two Maccy app settings are worth knowing before you export anything:
This is the right route when you already have history you want to recover. Newer Maccy mac versions keep history in a database inside the app’s sandbox container. A typical location is:
~/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy/Quit Maccy clipboard first, and work on a copy of the file so you never risk the original:
cp -R ~/Library/Containers/org.p0deje.Maccy/Data/Library/Application\ Support/Maccy ~/Desktop/maccy-copy sqlite3 ~/Desktop/maccy-copy/Storage.sqlite ".tables"Once you know the table and column names, you can export with SQLite’s built-in modes:
sqlite3 -header -csv ~/Desktop/maccy-copy/Storage.sqlite "SELECT * FROM <your_table>;" > history.csvExpect some cleanup. Clipboard content is often stored as binary blobs keyed by pasteboard type, so text may need decoding. If you are not comfortable with SQL, route 3 is easier. Also note that full-disk or sandbox access prompts from macOS can block Terminal from reading another app’s container. If you hit a permission error, grant Terminal access under System Settings → Privacy & Security → Full Disk Access.
If you want a future-proof, grep-able record that does not depend on any app’s storage format, log the clipboard yourself. macOS ships with pbpaste, which prints the current text contents of the clipboard. This script polls it and appends a timestamped entry whenever the content changes:
#!/bin/bash LOG="$HOME/clipboard-log.txt" last="" while true; do current="$(pbpaste)" if [ -n "$current" ] && [ "$current" != "$last" ]; then { echo "=== $(date '+%Y-%m-%d %H:%M:%S') ===" echo "$current" echo } >> "$LOG" last="$current" fi sleep 1 doneSave it as clipboard-logger.sh, run chmod +x clipboard-logger.sh, and start it with ./clipboard-logger.sh. To run it at login, wrap it in a launch agent plist in ~/Library/LaunchAgents.
pbpaste loop can still read them. Do not run this while handling secrets, or add filtering.It runs alongside Maccy without interfering, because both only read the clipboard.
Clipboard history is one of the most sensitive files you can create on your Mac. Over a week it can include passwords, API keys, one-time codes, addresses, and private messages. Before exporting:
macOS itself keeps no history, so there is nothing built in to export. Clipboard managers store their own history, and exporting it means using an app with an export feature, reading its database, or logging the clipboard with a script.
As far as we know, Maccy has no dedicated export button . Its history is local, so you can read it from disk or log the clipboard with the script above.
It depends on the app. There is no system-wide location. Sandboxed apps usually store data under ~/Library/Containers, and others under ~/Library/Application Support.
Only with care. Exports can contain passwords and tokens. Exclude sensitive apps, store the file encrypted, and delete it when finished.
If you need regular, polished exports, pick a tool that documents the feature. If you need to rescue what is already stored, read the database from a copy. If you want a durable archive you fully control, a ten-line logging script beats any proprietary format. Whichever you choose, keep the export as protected as you would a password list.
Maccy is free and open source if you want a fast, local-first manager to build these workflows on. What would you archive your clipboard for: search, backup, or migration? The answer decides which route is worth your time.
If you want to try it yourself, maccy.at is a free, open-source clipboard manager for macOS — the clipboard history guide covers the rest.
