Clipboard Viewer Online is a browser-based text inspector that reveals hidden whitespace and measures a clipboard value without submitting the inspected text to a server. It can read permitted clipboard text through the browser or accept a manual paste, then immediately reports character code units, Unicode code points, UTF-8 bytes, logical lines, word-like tokens, whitespace characters, and whether the trimmed value parses as JSON. This matters because a value can look correct on screen while containing a trailing space, a tab, mixed line endings, a hidden carriage return, or a supplementary Unicode character that occupies more than one JavaScript code unit. The Clipboard Viewer provides a controlled place to examine text before pasting it into source code, a terminal, a configuration file, a database field, or an online form. It does not repair the value, execute code, or validate the safety of its contents. Its invisible-character display is reversible and changes only the presentation, while the underlying editor value remains unchanged. Direct clipboard reading may require HTTPS, a focused page, a user gesture, and browser permission, so manual paste remains a supported route. The analysis runs locally in the current tab, and the editor can be cleared when inspection is finished.
What “Online” Means for Clipboard Inspection
The phrase “online clipboard viewer” can also describe a service that stores or relays clipboard content. Here, “online” indicates that the interface runs in a web browser; the documented purpose is inspection rather than cross-device transfer. Clipboard Viewer accepts permitted clipboard text through the browser API or a manual paste, analyzes it in the current tab, and updates its results immediately as the editor changes.
It is designed as a controlled check before text reaches another application. The supported input is plain text only. The tool does not attempt to expose clipboard images, rich HTML, files, or platform-specific formats, so an empty or non-text clipboard can produce an empty string. Its results explain the size and structure of that text; they do not automatically repair, rewrite, or execute it.
Read Each Measurement in Context
The available totals answer different questions. A character count can differ from a code-point count, while the UTF-8 byte total measures a third property: encoded size. These differences do not automatically indicate corruption.
| Result | What it measures | Why it matters |
|---|---|---|
| Characters | JavaScript string length in UTF-16 code units | Some emoji and supplementary Unicode characters count as two code units |
| Unicode code points | Each Unicode code point is treated as one item | This counts code points, not necessarily visible symbols; combining sequences and multi-code-point emoji can contain several code points for one visible symbol |
| UTF-8 bytes | The size of the text after UTF-8 encoding | This indicates space used in many files, APIs, and network protocols |
| Logical lines | Lines separated by LF, CRLF, or standalone CR endings | This counts logical lines; the separate invisible-character view makes line endings visible |
| Words | Unicode letters and numbers with common internal apostrophes, underscores, and hyphens | This is a practical token inspection aid rather than a linguistic authority |
| Whitespace | The number of whitespace characters | This helps reveal spaces, tabs, and other invisible formatting |
| JSON status | A strict JSON.parse check on the trimmed text | A valid result confirms syntax only, not field safety or correctness |
Clipboard Viewer uses the browser-native TextEncoder to calculate UTF-8 size and Array.from to count Unicode code points. It explicitly handles CRLF, CR, and LF separators for line counting. For JSON, it trims the text and then performs a strict JSON.parse check. It does not repair malformed JSON, run code, follow links, or interpret pasted HTML.
Inspect Clipboard Text in Four Steps
- Load the text. Click Read clipboard and approve the browser prompt, or paste the text directly into the editor with Command+V or Ctrl+V. Manual paste gives you exact control over what enters the page, which is useful when the clipboard contains sensitive material. If browser access is denied, the normal paste route remains available.
- Compare the results. Review the character, code-point, UTF-8 byte, line, word, whitespace, and JSON figures together. For example, a mismatch between characters and code points can reflect supplementary Unicode characters rather than lost or altered data. Treat the JSON result as a syntax classification, not a guarantee that its fields are safe.
- Expose hidden formatting when needed. Enable Show spaces, tabs, and line endings. Spaces appear as centered dots, tabs appear as arrows, and line endings become visible symbols. Carriage returns and line feeds are made explicit, so mixed separators or a stray tab become easier to identify. The mapping is display-only and reversible; it does not change the underlying editor value.
- Clear the editor after the check. Remove the working value when inspection is complete, especially if it contains passwords, tokens, personal information, or private customer data. Clearing the editor removes that working value from the component state.
What Hidden Formatting Can Reveal
Clipboard problems frequently remain invisible because the editor renders both plain spaces and formatted text in ways that can look almost identical. A trailing space at the end of a command, a tab inside an indentation sequence, a carriage return before a line feed, or a mixed set of line endings can all change how text behaves after pasting.
The invisible-character view is particularly useful when comparing copied shell commands, YAML indentation, CSV rows, or environment variables. It can also help when text has moved between Windows, macOS, and Linux, where line-ending conventions may differ. The viewer reveals the formatting but does not decide whether it is correct for the destination application. That judgment still depends on the syntax and requirements of the system receiving the text.
Line counting follows the same underlying distinction by recognizing LF, CRLF, and standalone CR separators. A mixed-ending file can therefore look like one continuous line in some editors while the viewer identifies multiple logical lines. The display helps you locate the mismatch; it does not automatically normalize the separators.
Clipboard Access Can Be Blocked
Direct clipboard reading is a protected browser capability. It generally requires HTTPS, a focused page, a user gesture, and browser permission. A browser may still deny the request because of user settings, enterprise policy, restrictions inside an embedded page, or an unsupported clipboard API. A denial is not treated as lost data: Clipboard Viewer shows a clear message, and the editor remains available for a manual paste.
For background on the browser interface, MDN’s Clipboard.readText documentation covers the read operation, while the W3C Clipboard API and events specification describes the underlying web platform. Neither changes the need to avoid sensitive content. The tool reads text only, so copied images, rich HTML, files, and platform-specific formats are outside its supported input.
Privacy and Safety Boundaries
Privacy is the main design constraint behind the local workflow. The analysis happens in the current browser tab, and no clipboard text is submitted to a Lizely server. Clearing the editor removes the working value from component state. Local processing reduces one kind of exposure, but it does not make every clipboard safe to inspect.
A clipboard can contain passwords, authentication tokens, personal data, or private customer information. Think before granting clipboard access, and prefer manual paste when you want to control exactly what enters the page. An input budget also prevents an accidental enormous paste from freezing the interface.
Clipboard Viewer is an inspection tool, not a secure secret scanner, malware detector, or compliance system. It can show that a token is present, but it cannot determine whether that token has already leaked. Likewise, it can report valid JSON syntax without proving that the data is trustworthy or suitable for a particular service.
A Practical Pre-Paste Checklist
Use the viewer when the destination is strict about text that appears visually identical:
- Shell commands: check for trailing spaces, embedded tabs, unexpected line endings, and extra blank lines before execution.
- YAML: reveal the exact indentation characters instead of estimating their width from the screen.
- CSV rows: inspect line boundaries and whitespace that might affect how a row is separated or parsed.
- Environment variables: look for a trailing newline, carriage return, or space that appears to be missing in a terminal.
- Cross-platform text: compare LF, CRLF, and standalone CR separators when content moves between operating systems.
- JSON payloads: use the JSON indicator for an initial syntax check, then confirm the fields and values separately.
The JSON status reports whether the trimmed text passes a strict JSON.parse check.JSON Validator If the JSON parses successfully but contains unexpected data, the problem is semantic rather than syntactic. In either case, the viewer should be your first controlled inspection step, followed by a second check in the tool designed for the destination format.