Why clipboard history still keeps plaintext after you copy a generated password

After you generate a password, the usual next move is to click Copy, then paste into a signup form, a router admin page, or a server panel. The button sounds like “send it where I am about to paste.” The order is the other way around. The page calls navigator.clipboard.writeText and hands the string to the operating system. Paste is only a later read. Between those two actions, the plaintext is no longer private to that tab.

UsePwd Password Generator follows that path. Random mode is 6–128 characters, 16 by default; anything under 8 is flagged as weaker. Characters are drawn in the current tab with Web Crypto. The page opens immediately — no sign-up. The success toast says “Copied to the clipboard.” That means the system clipboard, not “only the next input.” The string does not appear in a request body to UsePwd. Security answers whether plaintext leaves the browser toward UsePwd. This article covers the next layer: after the tab is done, can the operating system still keep the string.

That is a different layer from “why a rotated key should not go back into chat.” That piece is about you pasting an API key into a searchable, syncable, archivable channel; see After a cloud env-var leak, why the new key should not go back into chat. This one happens earlier. You may not have opened chat yet. Win+V, or another signed-in device, can already read the same string.

Windows 10 and Windows 11 both ship clipboard history. The first time, press the Windows logo key+V, then choose Turn on. After that, each ordinary copy that fits the supported formats enters the list. Microsoft’s support page states the ceiling: history holds up to 25 entries; each entry is at most 4 MB; supported formats include text, HTML, and bitmap. Older unpinned items are dropped to make room for new ones.

A restart clears unpinned history. Pinned items are the exception: they stay after a reboot, and they are not evicted to make room. To delete one entry, open Win+V, open More next to that item, and delete it. To clear unpinned items on the device and in the cloud in one step, use Settings → System → Clipboard → Clear clipboard data, or Clear all at the top of the history panel. Those steps are in Microsoft Support, Using the clipboard. You can run them on this PC.

A password is far smaller than 4 MB, so length is not the filter. Sixteen random characters, 128 random characters, or several passwords copied as one newline-joined block all enter history as text. Screenshots use the clipboard too. If you capture the password still on screen, that bitmap can occupy one of the 25 slots. Seeing text in the panel does not mean text is the only format history stores.

Windows clipboard sync is tied to a Microsoft account or a work account. The path is Settings → System → Clipboard. Turn on Clipboard history across your devices. Automatic sync uploads text you copy, then delivers it to other devices that use the same sign-in. Manual sync waits until you press Win+V and tap Sync on that item. Both modes are in the same Microsoft support article. The difference is not “does it ever reach the cloud.” It is “every copy, or only the copies you mark.”

Apple devices use a different pipe. Universal Clipboard sits on Handoff: devices on the same iCloud account, close to each other, can copy on one and paste on another. Apple’s Handoff security page states two facts you can check against the product. First, clipboard content is shared with Universal Clipboard by default unless the app developer opts out. Second, apps can read clipboard data before the user pastes; with Universal Clipboard on, that read extends to apps on the user’s other signed-in devices.

The transfer itself is encrypted. Handoff advertises over Bluetooth Low Energy, protects activity payloads in a way similar to iMessage, and moves larger data over peer-to-peer Wi-Fi with TLS. That only means a stranger on the path may not unwrap the bytes. It does not mean the shared iPad in the kitchen cannot see the string. The trust model is the account, not one computer. A household sharing one Apple Account, or a work laptop and a home PC on the same Microsoft account, widens who can read the password you just copied.

Microsoft’s Win32 documentation lists Cloud Clipboard and clipboard history formats. If an app does not want its clipboard data in history or on other devices, it can register and write these formats: ExcludeClipboardContentFromMonitorProcessing keeps every format in that write out of history and out of sync; CanIncludeInClipboardHistory with a DWORD of 0 stays out of history, and 1 asks to be included; CanUploadToCloudClipboard 0 and 1 control cloud sync only, not local history. The reference is Microsoft Learn, Clipboard Formats.

Password managers and Windows Credential Manager use that native path. A web page calling navigator.clipboard.writeText has no equivalent: it can write text, and it cannot attach those exclude formats. So a Copy click from a website is ordinary text to the system and to third-party clipboard tools. That is not a site “forgetting to encrypt.” It is the clipboard API the page is allowed to use, which stops at text.

UsePwd is not a vault and does not offer accounts. The top bar only has a language switch. The generator and the audit page both open immediately. Audit estimates strength on this device and checks a public leaked-password list shipped with the page. The test password is not uploaded, and the check is not Have I Been Pwned or a web-wide lookup. Those promises cover “did the password enter a UsePwd request.” They do not cover whether Windows wrote the same string into Win+V. Both can be true at once: the Network panel is clean, and clipboard history still shows plaintext.