Every collection on SoShareIT Emojis goes through the same four steps: source, filter, verify, and re-check. This page describes that process exactly as it runs, so you can judge how much to trust a page here.
1. Where the characters come from
A collection page is assembled from two pools:
- A central character pool. SoShareIT maintains a shared pool of emoji, symbol and kaomoji combinations across its tools. A collection page pulls from several related topics in that pool rather than one, which is why a coquette set also contains bow, ribbon and sparkle material.
- Visitor submissions. Some collections accept characters submitted by visitors, which is where the freshest combos come from — trends move on TikTok faster than any editor can track.
We do not scrape competitor pages, and we do not invent characters. A combination that we cannot show you in a live grid does not go on the page.
2. What gets filtered out — and what deliberately does not
Only three things are removed:
- Duplicates. The same combination, byte for byte, more than once.
- Fully invisible items. Entries made only of spaces or lone combining marks. Pasting one shows nothing, so it wastes a tile.
- Items that breach the content policy — hate, slurs, sexual content, harassment.
Just as important is what we keep. A combo that looks broken in a desktop editor very often renders perfectly on a phone, because phones ship far wider font coverage than a code editor does. Stripping “odd-looking” characters would quietly delete exactly the aesthetic combos people came for, so a combo stays unless it is a duplicate, invisible or against policy. We also never normalise a combo: variation selectors and combining marks are left byte-for-byte as sourced.
3. Verification before a collection is published
For the characters that carry meaning on a page — the ones we name and explain, rather than the long tail of the grid — we check:
- Code point and block. Confirmed against the official Unicode charts at unicode.org. If we print U+2661, that is the character you are copying.
- What it actually is. Many “emoji” in aesthetic combos are not emoji at all. ฅ is a Thai letter used as a cat paw; ᓚᘏᗢ is three Canadian Aboriginal syllabics. We say so, because it explains why they behave differently from 🐱.
- Render support. We paste the character into current iOS, Android and Windows and record what appears, including when the answer is “an empty box on this build”.
4. The honesty rules we hold ourselves to
- A “verified” or “blue tick” character is a decorative symbol. It does not verify any account, and no site can give you a real badge.
- Flag characters are text, not statements. They are listed because people search for them.
- We never claim a character is “safe everywhere”. Name filters differ per platform and change without notice — most shooters strip colour emoji from name fields, and TikTok usernames accept only letters, numbers, dots and underscores, even though the display name accepts almost anything.
- We do not fabricate counts. Copy counters reflect real copies.
5. Re-checking, and the “last checked” stamp
Unicode adds characters, platforms change font coverage, and name filters tighten. A collection is therefore not finished when it is published: pages are revisited on a rolling cycle, and facts that can go stale — render support, platform rules, counts — are re-tested rather than copied forward. Where a page shows a “last checked” date, that date is when a person actually re-tested it.
Report a glyph that does not render
If a character on this site shows as an empty box, a question mark, or the wrong shape on your device, tell us. Send the character itself (pasted, not a screenshot), where you pasted it, and your device and OS version, to [email protected] or through the contact page. That report is worth more than any amount of desk research, because it is a real device we do not own.
Who “we” are is set out on the about page.