What this policy commits us to
- Character data is checked against the Unicode Standard, never copied from another styling site.
- A style is not published until it has been pasted into a real phone, not just previewed here.
- Characters are served byte for byte. We never normalise, tidy or substitute one.
- Where a style is fragile, the page says so instead of letting you find out after you set your username.
- No invented authors, no invented statistics, no paid placement of a style.
This page describes how SoShareIT Fancy Text decides what to publish and what has to happen before a style reaches the menu. It exists because in this niche the failure modes are invisible until they are somebody else’s problem: a style that looks perfect in our editor and arrives as a row of empty boxes in a friend’s Instagram feed.
Last updated: 30 August 2026 · Published by the SoShareIT Fancy Text editorial team
Why we do not copy character data
We do not take character mappings from other styling sites. It is the fastest way to add a style and the fastest way to inherit somebody else’s mistake.
A wrong mapping is unusually durable. One site publishes a character that is nearly right, others copy it because it is already out there, and years later everybody’s “cursive” menu contains the same wrong glyph without one person having checked it against the standard that defines it. Nobody notices, because noticing requires the exact step that was skipped.
Mappings come from the Unicode Standard itself: the code point, the formal character name, and the block it belongs to.
What has to be true before a style is published
Four checks, in this order. The order matters because the first one changes what the rest are looking at.
The Android check runs first
Not last. A device font gap is the most common failure and the cheapest to catch early, and finding it first changes what gets written rather than just whether we ship. A style that renders on Android usually stays; one that does not either gets dropped or gets a warning on its page.
The iPhone check exists to stop us generalising
Apple ships a different font stack, so identical clipboard content can be correct on Android and meaningfully different on iOS. When the two disagree the page has to describe both outcomes rather than pick the prettier one and present it as what you will get.
The paste check catches what no device test can
Platforms are stricter than operating systems and their rules are invisible until you hit them. A style can render perfectly and still be stripped from an Instagram display name or rejected by a game’s name field. That is not a font problem and choosing a better character will not fix it, so it becomes a note on the page instead.
The Unicode check is aimed at us, not the style
The first three test the characters. This one tests the editor. Names and code points are verified against the standard rather than against memory, because “I am fairly sure that is what it is called” is precisely how a wrong name enters circulation and stays there.
What we never do to a character
Characters are stored and served exactly as they are. It is the most important rule we hold ourselves to and the one with the least visible consequences when broken.
Concretely: we do not strip variation selectors, we do not remove combining marks, we do not convert a styled character back to plain ASCII, and we do not swap a decorative combination for a more common one because it looked odd in a preview. Text that appears broken in an editor very often pastes perfectly into a social app, so “it looks wrong on my screen” is never grounds for changing it.
Zalgo is the clearest case. It works precisely because it stacks combining marks that any tidy-up routine would remove. A generator that quietly normalises its own output would produce plain text and call it Zalgo.
Saying when a style is fragile
Not every style is equally safe, and pretending otherwise would make the menu look better and the site worse.
The mathematical alphanumeric styles — bold, italic, script, double-struck — are the most widely supported, because the characters have been in the standard a long time and most font stacks cover them. The more decorative ranges are patchier, and heavy combining marks are the least predictable of all: they can render, be stripped, or break a line’s spacing depending entirely on where they land.
Where we know a style is fragile, the page says so. A warning costs us a little polish and saves you discovering the problem after you have already set your username.
Corrections
When we get something wrong we change it on the page where it was wrong, and the last-updated date moves with the change. We do not fix things silently and we do not backdate, because a date that moves on every automated touch tells you nothing.
Reader reports are the most valuable input we get. Platform rules change without announcement and we cannot test every app every week, so a message saying a style stopped working in a particular place tells us something we had no other way to learn. The contact page says what to include.
Advertising and independence
This site carries Google advertising and that is what pays for it. Nobody pays for a style to be added, moved up the menu, or described favourably — there is no sponsored placement here and no affiliate arrangement. Advertisers have no input into what we publish, and we do not choose which individual ads Google serves. What advertising means for your data is set out in the privacy policy.
Authorship
Pages are published by the SoShareIT Fancy Text editorial team and attributed that way. We do not invent a named expert, a photograph or a credential to make a page look more authoritative, because a fabricated byline is a lie about the most easily checked thing on the page. Who we are is on the about page; how we work is here.