Your files never leave your device. All processing happens locally in your browser.
How do I keep a searchable history of my clipboard in the browser?
Open the Clipboard History Manager and either paste into the capture box (Ctrl/Cmd+V saves the snippet instantly) or click “Capture from clipboard” to read it once with a browser permission prompt. Each saved snippet is auto-classified (URL, email, JSON, number, colour, code or plain text), timestamped and character-counted; you can search across everything, filter by type or by #tag, pin favourites to the top, edit the text and labels, mark items sensitive to hide them behind a reveal, and one-click re-copy any snippet back to your clipboard. Everything is stored only in this browser’s localStorage — nothing is uploaded — and you can export or import the whole history as JSON. Note that a web page cannot silently watch your clipboard in the background, so it only ever sees what you paste or capture, and you should never store passwords or secrets here.
Capture by pasting (Ctrl/Cmd+V) or a one-off permission-prompted clipboard read
Auto-detects type: URL, email, JSON, number, colour, code, text
Search, filter by type or #tag, pin favourites, edit, mark sensitive, re-copy
Export / import the whole history as JSON; saved in localStorage only
No background monitoring, no upload — don’t store passwords here
What is
Clipboard history manager
A clipboard history manager is a utility that keeps a running list of things you have copied so you can search them and paste an older item back, instead of only having the single most-recent copy. A browser-based, client-side manager like this one cannot silently watch the operating-system clipboard in the background — browsers forbid that because it would behave like a system-wide key-logger — so it captures snippets only when you paste into it or grant a one-time clipboard-read permission. Items are stored locally (here in the browser’s localStorage), typically with per-item metadata such as an auto-detected content type, a timestamp, a character count, user tags, a pin/favourite flag and an optional “sensitive” reveal, and can be searched, filtered, edited and re-copied. It is a convenience scratch history, not an encrypted vault.
No. A web page cannot silently monitor the OS clipboard — browsers block it. It only sees what you paste into it or capture with a one-time permission prompt.
Background clipboard monitoring is deliberately impossible on the web: it would be equivalent to a system-wide key-logger, so browsers only expose clipboard contents when the page is the active tab and you actively paste, or when you grant an explicit clipboard-read permission (Chrome/Edge prompt for it; Safari and Firefox handle the prompt differently). This tool captures a snippet when you paste into the box (Ctrl/Cmd+V) or click “Capture from clipboard.” It never runs in the background, never polls your clipboard, and never uploads anything — so it can only ever contain what you deliberately gave it.
Only in this browser’s localStorage on this device. They are not synced, not encrypted, and are erased if you clear site data.
The history is kept as plain JSON in your browser’s localStorage under a single key. That means it is per-browser and per-device: it will not appear in a different browser or on your phone, it is not backed up anywhere, and clearing site data (or a strict private-browsing mode) removes it. It is also not encrypted and is readable by any script running on this same origin. You can move your history between browsers manually with the Export JSON / Import JSON buttons, but for anything you truly need to keep, save your own copy — treat the built-in storage as a convenient scratch history rather than durable storage.
No. Don’t store passwords, keys or one-time codes. Browser storage is unencrypted and readable by same-origin scripts; use a real password manager.
A clipboard history is one of the worst places to keep secrets: the data sits unencrypted in localStorage, is readable by any script on the origin, and lingers until you delete it. The “mark sensitive” flag in this tool only hides a snippet behind a click so it isn’t shoulder-surfed on screen — it does not encrypt the value. For passwords, API keys, recovery codes or 2FA seeds use a dedicated password manager or secrets vault. If you do paste something sensitive by accident, delete that snippet (or clear the history) right away.
A pure detector inspects the text: a parsable http(s) link is a URL, valid JSON is JSON, a hex/rgb value is a colour, a numeric string is a number, and multi-signal source is code — otherwise plain text.
Each snippet is auto-classified by a small deterministic engine, in order of specificity: a single token that parses as an http(s) URL (or looks like www.…) is a URL; an address matching the email pattern is Email; a hex, rgb(), rgba(), hsl() or hsla() value is Colour; a clean numeric string (with optional sign, thousands separators, decimals or exponent) is Number; text that starts and ends with matched braces/brackets and actually JSON.parses is JSON; and text that trips at least two code signals (keywords like function/const/def, operators like =>, lines ending in ; { }, HTML tags, or indented blocks) is Code. Anything else is plain Text. The detection runs entirely in your browser and updates when you edit a snippet, and it drives the type filter chips.
Detailed Explanation
📖How It Works
What the Clipboard History Manager Does
This tool keeps a searchable, local history of things you copy, so you can paste an older item back instead of only having your single most-recent copy. You add a snippet by pasting into the capture box (Ctrl/Cmd+V saves it instantly) or by clicking “Capture from clipboard,” which performs one permission-prompted navigator.clipboard.readText() read. Each snippet is auto-classified by content type, timestamped and character-counted, and shown newest-first with pinned favourites on top. From there you can full-text search, filter by type or by #tag, pin, edit the text and labels, mark an item sensitive so it hides behind a reveal, one-click re-copy it to the system clipboard, or delete it. The entire history is saved only in this browser’s localStorage, and can be exported or imported as JSON. It is a convenience scratch history, not an encrypted vault.
Capture by paste (Ctrl/Cmd+V) or a one-time permission-prompted clipboard read
Auto-classifies each snippet: URL, email, JSON, number, colour, code, text
Search, filter by type or #tag, pin favourites, edit, mark sensitive, re-copy
Newest-first with pinned on top; timestamps and character counts
Export / import the whole history as JSON; saved in localStorage only
⚙️Methodology
How Type Auto-Detection Works
A pure, deterministic engine (clipboardManagerEngine.ts) classifies each snippet in order of specificity so unambiguous kinds win before the fuzzy code guess. A single whitespace-free token that constructs a valid http(s) URL (or matches a www.host.tld shape) is a URL; a string matching the email pattern is Email; a hex, rgb(), rgba(), hsl() or hsla() value is Colour; a clean numeric string with optional sign, thousands separators, decimals or an exponent is Number; text that begins and ends with matched braces or brackets and actually passes JSON.parse is JSON; and text that trips at least two independent code signals — language keywords (function, const, def, class, SELECT…), operators (=>, ===, &&), lines ending in ; { }, an HTML/XML tag, or an indented block — is Code. Anything unmatched is plain Text. Detection re-runs when you edit a snippet and drives the filter chips. It is heuristic by design, so it can occasionally mis-file an ambiguous value.
Ordered detection: URL → email → colour → number → JSON → code → text
JSON is confirmed with a real JSON.parse, not just a leading brace
Code needs two or more signals (keywords, operators, punctuation, indent)
Detection re-runs on edit and powers the type filter chips
Heuristic, so an ambiguous snippet can be mis-classified
🔧Technical Details
Model, Storage and Re-Copy
Each snippet is a small typed record: a crypto-random id (window.crypto.getRandomValues, never Math.random), the verbatim text, an epoch-ms timestamp, a pinned flag, a tag array, a sensitive flag and the detected type. The engine handles adding (an exact-duplicate of an existing capture is bumped to the top rather than duplicated), a 500-item cap that drops the oldest un-pinned items first, filtering/sorting (pinned first, then newest), tag helpers, and JSON export/import with validation that regenerates colliding ids and re-detects missing types. Persistence is a single localStorage key written on every change and tolerantly parsed on load. Re-copy uses navigator.clipboard.writeText(); export builds a Blob and an object URL locally; import reads the chosen file with File.text(). The React page keeps all DOM and clipboard calls; the engine stays pure and unit-testable.
Snippet = id (crypto-random) + text + timestamp + pinned + tags + sensitive + type
Exact duplicates bump to the top; 500-item cap drops oldest un-pinned first
Persistence is one localStorage key; load is tolerant of old/corrupt data
Re-copy via Clipboard API; export builds a local Blob; import reads File.text()
⚠️Limitations
Honest Limitations
The single most important honesty point: a web page CANNOT silently monitor your operating-system clipboard in the background. That would be equivalent to a system-wide key-logger, so browsers only expose clipboard contents when the page is the active tab and you actively paste, or when you grant an explicit clipboard-read permission (Chrome and Edge prompt; Safari and Firefox handle it differently). This tool therefore only ever contains what you deliberately paste or capture — it never runs in the background. Storage is local and unencrypted: snippets are plain JSON in localStorage, NOT synced across devices or browsers, NOT encrypted, readable by any script on this origin, and erased when you clear site data or use a strict private mode. Do NOT store passwords, API keys, 2FA codes or other secrets here; the “mark sensitive” flag only hides a snippet behind a click, it does not encrypt it. A 500-item cap and per-origin storage quotas apply. Treat it as a scratch history, not a secure vault or a backup — use Export JSON for anything you need to keep.
No background clipboard monitoring is possible on the web — by design
localStorage is unencrypted, same-origin-readable, per-browser, not synced
Do NOT store passwords/keys/2FA codes; “sensitive” only hides, never encrypts
500-item cap (oldest un-pinned dropped first) and storage quotas apply
A scratch history, not a vault or backup — export what you must keep
🔒Privacy & Security
Private by Design
Everything happens on your device. Capturing, searching, tagging, type-detection, editing, export and import all run in the browser with no server, no account, no CDN and no telemetry in the path, and nothing is ever uploaded. Snippets live only in this browser’s localStorage, so the tool works offline once cached and your history never leaves the machine unless you export it yourself. It reads the clipboard only when you paste or explicitly capture (a permission-prompted, one-shot read), never in the background. Ids are generated with crypto.getRandomValues rather than Math.random. Because the data is same-origin-readable and unencrypted, the design deliberately steers you away from storing secrets and makes deleting a snippet or clearing the un-pinned history one click away. The only optional network use anywhere on the site is consent-gated ads, which never see your snippets.
All capture, search, tagging and I/O run locally; nothing is uploaded
History stored only in localStorage; works offline once cached
Clipboard is read only on paste/capture, never in the background
Ids use crypto.getRandomValues, not Math.random
Only optional network use is consent-gated ads that never see your data
Ways to keep a history of what you copy
Approach
What it does
Trade-off
This tool
This local manager
Saves snippets you paste/capture in localStorage
No background capture; unencrypted; per-browser
Yes
Native OS clipboard history
System-wide, auto-captures every copy (Win+V, etc.)
OS-only; not portable; some sync to a cloud account
Outside the browser
Desktop clipboard app
Background daemon logs all copies with search
Installs software; broad access; can capture secrets
No install here
Cloud clipboard / sync service
Syncs clipboard across devices via a server
Your copied data is uploaded to a third party
No — never uploaded
A browser page cannot auto-capture in the background like an OS or desktop tool — it only sees what you paste or capture. Everything here stays in your browser and is unencrypted, so avoid storing secrets. As of July 2026.
