Special characters copy and paste means transferring a Unicode character as text, using its code point to identify the exact character placed on the clipboard for pasting.
Copying and pasting a symbol can look simple because the result often resembles the original at a glance. The exact identity is instead carried by a Unicode code point, while the visible shape is a glyph that can change with fonts and platforms. The Special Characters Copy and Paste reference makes that distinction visible with exactly 48 practical entries covering punctuation, currency, mathematics, arrows, geometric shapes, general symbols, typography, and selected Greek or technical letters.
Each entry displays a formal Unicode name, a U+ code point, a product category, and a Copy button. The reference does one focused job: it helps you identify and copy one exact character without transforming an entire string into decorative or lookalike text.
The character-to-glyph-to-clipboard path
A reliable copy-and-paste process separates four things: the character’s identity, its name, the shape shown on screen, and the text placed on the clipboard. Confusing those layers can lead to a result that looks correct but represents a different character.
| Layer | What it tells you | Example |
|---|---|---|
| Unicode scalar value | The exact numeric identity stored for a character | U+20AC |
| Unicode name | The formal label used to distinguish the character | EURO SIGN |
| Glyph | The shape drawn on screen, which can vary by font and platform | A visible euro sign |
| Clipboard content | The single text character written by the Copy action | One exact character |
| Target rendering | How the destination application and active font display it | The intended glyph or a fallback shape |
Internally, the reference stores each entry as a numeric Unicode scalar value and derives the visible character with String.fromCodePoint. When you select Copy, the canonical entry is resolved by its code point. This reduces the chance that a displayed glyph and its U+ label could drift apart because two independent character mappings were typed manually.
The clipboard receives only that one derived character. The action does not add a variation selector, zero-width joiner, HTML entity syntax, CSS escape, surrounding spaces, or a trailing newline. Invisible spacing entries use bracketed grid labels such as [NBSP], [THIN], and [ZWSP] so they remain understandable, but Copy still writes the actual single character.
Why an exact U+ label matters
A code point gives you a stable identifier, while a formal name provides a readable label for the same identity. The tool supports several search routes, so you can start with whatever you already know:
- Formal name or familiar word: search for a Unicode name or a practical term such as euro, arrow, dash, check, square, alpha, or space.
- Product category: search within a navigation category or optionally filter the results by one.
- Rendered character: enter the visible symbol when you can reproduce it reliably.
- U+ notation: enter a value such as U+20AC; leading zeroes are accepted.
- Bare hexadecimal: enter 20AC without the U+ prefix to reach the same entry.
Confirm both the displayed name and code point before copying. For example, U+00B5 is MICRO SIGN, while Greek small letter mu is a different character. NO-BREAK SPACE is also distinct from an ordinary space even though both can appear blank. BLACK HEART SUIT is a named Unicode symbol, not a promise that every application will render it as a color emoji. These distinctions affect searching, normalization, accessibility readings, identifiers, and security, so appearance alone is not a dependable identity check.
Code point labels use uppercase hexadecimal with at least four digits. A font can still make two different code points look nearly identical, and it can also make a valid character appear as a hollow or missing box. That box normally indicates a missing glyph in the current font, not necessarily an incorrect code point.
Find, copy, and paste one verified character
- Open the reference and enter a search. Use the formal name, product category, rendered character, U+ notation, or bare hexadecimal value. Add the category filter when it helps narrow a broad term.
- Confirm the entry’s identity. Read the formal Unicode name and U+ code point shown on the result instead of choosing solely by the glyph’s appearance. For an invisible space, use its bracketed label to distinguish it from a blank cell.
- Select Copy on one entry. The browser writes exactly one character to the clipboard. If clipboard access is denied by the browser or operating system, the tool reports the failed write rather than presenting it as a successful copy.
- Paste at the intended location. Use the destination application’s paste command, then check that the character appears in the intended field, document, message, or source file.
- Verify the final rendering. Inspect the pasted character in the destination’s active font and application. If it looks different or missing, investigate font support and fallback behavior before replacing it with a lookalike.
Filtering and copying happen entirely in the current browser; neither a search nor a copied character is sent to Lizely. If the clipboard write fails, grant clipboard permission through the browser or operating system and repeat the Copy action. Privacy during copying does not change the fact that the destination application receives the clipboard content when you paste.
Paste for the destination’s rules
The correct copy-and-paste method depends on where the character will be used. The reference supplies the character itself, not application-specific escaping, encoding, or editorial approval.
| Destination | How to use the copied character | What to verify |
|---|---|---|
| HTML | A literal Unicode character is often valid in a UTF-8 document, although a named or numeric reference may better match a particular codebase. | The document encoding and the project’s entity convention |
| Programming source | Paste only when the project permits that literal character; use the language’s normal escaping rules when required. | Source encoding, parser behavior, and style rules |
| Documents and messages | Paste the single character into the intended position and inspect it in the editor or conversation view. | The final font, platform, and application behavior |
| Print or design work | Check that the chosen font supports the character before finalizing the layout. | Glyph availability, fallback behavior, and intended presentation |
For HTML, the tool does not generate entity syntax such as an &-style reference. Consult the WHATWG named character references and the codebase’s conventions when a reference is preferable to a literal character. For programming languages, source encodings and style rules vary, so the same visible character can be accepted in one project and rejected or rewritten in another.
What the curated table covers
“Special characters” is a practical label rather than a formal Unicode category. The tool contains exactly 48 unique Unicode scalar values selected for routine writing, documents, interfaces, code comments, labels, and design work. Its eight category names are navigation labels created for the tool; they are not Unicode General_Category values. For example, COPYRIGHT SIGN appears under Punctuation because writers often look for it alongside publication marks, even though Unicode metadata may classify it differently.
The collection is intentionally smaller than Unicode. It does not provide exhaustive coverage of scripts, combining marks, controls, emoji sequences, historic writing systems, technical symbols, private-use positions, or unassigned code points. A character’s absence from these 48 entries does not mean it is absent from Unicode. For authoritative naming records, consult the Unicode Character Database NamesList; for exhaustive browsing, use the Unicode Character Database or a specialist character map. Search in this tool always operates on its selected table and product labels rather than an online Unicode service.
Final checks before publishing or using identifiers
The copied code point remains the listed value even when two systems draw it differently. Fonts, browsers, operating systems, and fallback fonts all affect appearance. Some symbols may receive emoji-style presentation in certain environments, but this table stores no variation selectors and makes no promise about color emoji rendering. Verify the result before publishing, engraving, printing, or using it in source code.
Similar-looking characters can differ in meaning, search behavior, accessibility readings, identifiers, normalization behavior, and security consequences. Never substitute a lookalike in a domain name, account identifier, command, password, or security-sensitive token without confirming the exact code point. The tool also does not judge whether a character is legally, financially, mathematically, linguistically, or accessibly appropriate for a particular use.
This is not a fancy-text generator. It does not convert ordinary letters into mathematical alphabets, decorate usernames, compose combining-mark effects, create invisible messages, or transform a whole string. Every Copy action writes one exact character from the curated table, which makes verification and deliberate reuse straightforward.
Related reading: Special Characters Remover for Bulk Unicode Cleanup.
Related reading: How to Document Black Star Symbol Copy Paste Steps.