clear characters, honest references ♡
Editorial Policy
Our references should help you choose and copy the right heart without confusing a visual impression with a technical fact. This policy explains the sources, checks and limits behind the collection.
Use primary sources for technical facts
Unicode data is the primary reference for character names, code points, defined emoji sequences and presentation selectors. Input instructions use the documentation of the relevant operating system or application.
A friendly collection label such as “winged heart” is not presented as an official Unicode name for the complete decoration.
Preserve the actual copied sequence
The character, its code points and its copy value should agree. Where a copy includes a selector, joiner, space or several symbols, the complete sequence is retained. We do not silently turn one heart into another because their pictures look alike.
Generated decorations preserve the input letters. The between-letters style separates grapheme clusters so that a joined emoji or combining accent is not intentionally broken apart.
Write examples and meanings in context
Messages, name frames and decorative combinations are examples written for this collection. They are not copied as a set of statements from a competitor or represented as quotations from a real conversation.
A heart color does not establish a person’s intentions, health or relationship status. Cultural associations require context and a source; one example is not treated as a rule for every sender.
Separate a source check from a device test
A successful build or a browser check does not prove that an input shortcut works on a different operating system. We describe keyboard, font and application dependencies instead of promising universal compatibility.
A claim of physical-device testing should identify the relevant environment and a reproducible result. When a behavior has only been checked against documentation, it is not labeled as a completed device test.
Use assistance without treating it as evidence
AI tools may assist with drafting, implementation and organization. Generated wording is not itself a source for Unicode properties, platform behavior or a person’s intentions. Technical facts still need source checks, and the resulting pages still need review.
Correct affected content and keep dates meaningful
When an error is confirmed, we aim to correct the affected reference and related examples or links. A substantive content change should be reflected in the page’s update date; dates should not be advanced merely to imply freshness.
Information can still become outdated or contain mistakes. A documented correction is more useful than a blanket claim that every device and application has been tested.
Report an error with enough detail to reproduce it
Send the page URL, the relevant character or code point, what you expected and what actually happened. A public source link is helpful. For display or input problems, include the device, operating system, application and version if you know them.
Share only the text needed to demonstrate the issue. You do not need to send your full copy history or unrelated private messages.