This page explains who publishes Fancymoji, how a kaomoji gets onto the site, and what to do when something here is wrong. It describes our standing practice rather than any one article.
Who publishes this site
Fancymoji is published by the Fancymoji editorial team. Pages are written and reviewed by that team as a group and carry the team name, not an individual byline. We do not present the site as the work of a named authority on Japanese typography, because it is not one: it is a reference library kept up by people who work on it together.
You can reach the team at [email protected] or through the contact page. Both arrive in the same inbox.
What this site is for
Fancymoji collects kaomoji — Japanese text faces built from ordinary characters and read upright, like ( ͡° ͜ʖ ͡°) or ¯_(ツ)_/¯ — and says what each one carries and where it fits. That is the scope. We are not a dictionary of Japanese, we do not sell anything, and no entry has been placed here in exchange for payment.
Curated, not dumped
Most sites in this corner of the web compete on volume, listing thousands of faces with nothing attached to them. We deliberately do the opposite. A face goes into the library when we can say something true about it: what mood it reads as, where it suits and where it lands wrong. A face we cannot describe usefully stays out, because an undescribed face is something a visitor can find anywhere.
That means our lists are shorter than the biggest ones on the web. We think that is the right trade, and we would rather say so plainly than pad a page to a round number.
How we check characters
A kaomoji is not an image and not a font: it is a run of ordinary Unicode characters. Before a face is published we check that the characters in it are ones the Unicode standard actually defines, so that what we hand out is real text rather than something that will collapse when it is pasted. Where we state a code point on this site, it was read from the published code charts and not guessed. Character data on the site was checked against Unicode 16.0 in August 2026.
We keep the characters exactly as they are. We do not strip variation selectors, we do not remove combining marks, and we do not quietly swap a face for a tidier-looking one. A face edited for neatness is no longer the face people are copying.
What we do not claim
We do not claim a face will look identical on every device. It will not. Every platform ships its own fonts, so a face that is perfect on a phone can show gaps or empty boxes on a desktop, and the text is unharmed either way. Where this matters, the site says so on the page instead of pretending the problem does not exist.
We also do not track the rules of individual apps. Platforms decide their own limits on name length and on which characters they accept, and they change those rules without notice. Our advice is always the same: paste it, save it, and see whether it stuck.
Corrections
If something here is wrong — a code point, a claim about a character, a meaning attached to a face — write to [email protected] and name the page. We would rather correct a page than argue for it. Factual corrections are made on the page itself, and the page’s update date moves when the change is substantive rather than cosmetic.
Update dates
Pages show when they last changed. We move that date when the content actually changed — a section added, a fact corrected, a list revised — and we leave it alone otherwise. A date that only signals freshness tells the reader nothing.
Advertising and affiliate links
At the time of writing the site carries no sponsored content and no affiliate links, and no entry in any list has been paid for. If that changes, this page changes with it and the disclosure appears on the pages concerned.
This page is reviewed when our practice changes. Last reviewed: August 2026.