Editorial Guidelines
Last updated: September 12, 2026
These are the standards content on this site is written and reviewed against, so you know what to expect from the information published here.
Accuracy and Verification
Technical details about Unicode characters — code points, character names, HTML entities, and hex entities — are checked against the Unicode Standard rather than copied from other websites. During a review of comparable sites, we found published character tables containing incorrect decimal entities and mismatched hex values, which is why we derive these values from the code point itself instead of reproducing them from third parties.
Character data on this site is generated programmatically from each character's code point, so the character you copy matches the code point, HTML entity, and hex entity displayed beside it.
Useful, User-First Content
Content is written to answer a real question or solve a real problem. We prioritise a working tool and genuinely helpful explanations over publishing large volumes of thin pages built around keyword variations. If a page would not help someone, we would rather not publish it.
Clear and Accessible Language
Explanations aim to be readable without specialist knowledge. Where technical terms are unavoidable — zero-width, whitespace, code point — we define them in plain language. Pages use semantic headings and structure so they work with screen readers and keyboard navigation.
No Overstated Claims
Blank and invisible characters behave differently across platforms, browsers, fonts, and input fields. We avoid blanket claims such as "this works everywhere," and we describe support in accurate terms — for example, "supported on some platforms" — rather than promising universal compatibility.
We also avoid unverifiable promotional claims about the site itself, such as user counts, rankings, or endorsements.
Original Content
Explanations, descriptions, and page copy are written for this site rather than copied from other sources. Where we reference a public specification such as the Unicode Standard, we describe the factual data it defines without reproducing another publisher's original wording. Unicode characters themselves are part of a public standard and are not claimed as our original work — see ourDMCA & Copyright Policy.
Keeping Information Up to Date
Platform behaviour changes over time: an app that accepts a particular character today may filter it later. When we become aware that guidance has become outdated, we aim to update or remove it. Policy pages carry a visible effective or last-updated date so you can see when they last changed.
Corrections
If something on this site is inaccurate, we want to fix it. Factual errors — particularly in the Unicode reference table — are corrected once verified. You can report an issue through ourcontact page; including the specific page and character involved helps us verify and correct it faster.
Use of AI-Assisted Tools
AI-assisted tools may be used during drafting, editing, or development. They are not treated as a source of truth: technical values are verified against the Unicode Standard, and content is reviewed against the standards on this page before publication. We do not publish unreviewed machine-generated content, and we do not publish machine-translated pages presented as original localised content.
Scope of This Guidance
This site publishes practical information about text characters and how they behave. Nothing here is legal advice. Where our pages describe legal topics — such as copyright procedures — they explain general processes only, and you should consult a qualified professional for advice about your situation.