Disclaimer

1. General disclaimer

The information and tools on this Site are provided in good faith and for general use. To the fullest extent permitted by law, they are provided without warranty of any kind as to accuracy, completeness, reliability, or fitness for a particular purpose.

We take care to be accurate — every base alphabet on this Site was checked character by character against the Unicode database, and compatibility notes come from real testing rather than assumption. Even so, information can become outdated, and the environments this text is pasted into change constantly. Use of the Site and reliance on anything you find here is at your own risk.

2. “Fonts” is a convenient word, not an accurate one

Throughout this Site we use words like “fonts”, “font generator”, and “font styles”, because that is what people search for and how the tool is understood. Strictly speaking it is not what is happening.

• No font is created, supplied, or installed. The Site does not produce .ttf, .otf, .woff, or any other font file, and nothing is downloaded to your device.
• The output is Unicode characters. Distinct code points that happen to resemble styled Latin letters — for instance Mathematical Alphanumeric Symbols (U+1D400) or Fullwidth Forms (U+FF00).
• The appearance is not ours to control. How those characters look is determined by the fonts on the viewing device. The same character can look noticeably different across an iPhone, an Android phone, and a desktop browser.

We are not affiliated with, endorsed by, or connected to the Unicode Consortium, nor with any type foundry, font designer, or the platforms named on this Site.

3. Rendering and compatibility

This is the disclaimer that matters most in practice. Whether styled text displays as intended depends on factors entirely outside our control:

• The viewer’s device and operating system, and how recently it was updated;
• The system fonts installed on that device, which determine which Unicode blocks can be drawn at all;
• The specific app displaying the text, since apps differ in font handling even on the same phone;
• The platform’s own processing, as some strip, substitute, or normalise unusual characters.

When a device cannot draw a character it shows a placeholder box, commonly called tofu. That is a gap in that device’s fonts, not a fault in the character or an error on this Site. The same text may display perfectly for one person and as boxes for another, simultaneously.

We therefore do not warrant that any style will render correctly for any given audience. Bold, script, and small caps are the most widely supported; gothic, blackletter, and heavily decorated styles fail most often on older devices.

4. Our compatibility testing and its limits

We publish compatibility tables because nobody else in this niche does, and because guessing is worse than testing. It is fair to be clear about what that testing represents.

• It reflects results on the devices, browsers, and app versions available to us at the time of testing;
• It is a snapshot, not a live status — platforms change behaviour without announcement;
• It cannot cover every combination of device, OS version, app version, and regional font package in existence.
• A mark indicating a style works is our tested finding, not a contractual guarantee.

We correct these tables when we learn something has changed, and reports from readers are a significant part of how we learn it. If a style behaves differently for you, please tell us via the contact page.

5. Platform rules and acceptance

Instagram, TikTok, Discord, Facebook, X, LinkedIn, and every other platform set their own rules about what characters are allowed in names, bios, and posts, and enforce them as they see fit. Some reject unusual characters in usernames, some silently strip them, some allow them in one field but not another.

We have no relationship with these platforms and no influence over their decisions. Nothing on this Site should be read as permission, from them or from us, to use styled text in a way that breaches their terms. If a platform rejects your text, changes it, or takes action on your account, that is a matter between you and that platform.

6. Accessibility and searchability

Styled Unicode characters carry real trade-offs that are easy to overlook and worth stating plainly.

• Screen readers handle them poorly. A screen reader may read mathematical script characters letter by letter, announce them by their formal Unicode names, or skip them entirely. Styled text can be effectively unreadable to someone using assistive technology.
• Search engines do not treat them as ordinary words. A styled word is a different string from its plain equivalent, so it may not match searches for the plain word.
• Platform search and hashtags behave the same way. A styled hashtag is a separate tag from the plain one and will not appear in the plain tag’s feed.
• Some styles consume more characters. Combining-mark styles count as multiple characters against a field’s limit even though they look like one.

Our recommendation, given freely and repeated across the Site: keep anything that must be found, indexed, or read aloud in plain text, and use styling for emphasis rather than for substance.

7. How you use the output

Text generated here can be used freely, including commercially, as set out in our Terms & Conditions. Responsibility for that use rests with you.

We are not responsible for content you create with the output, for how it is received, or for consequences arising from it — including a rejected advertisement, a bio that displays as boxes to part of your audience, a username a platform refuses, or a message misread because of an unusual character. We do not monitor what people generate, and we could not: nothing you type reaches us.

8. Style counts and descriptions

We state 285 named assets — 173 base alphabets and 112 decorations — and that figure is deliberately literal rather than promotional. Two honest qualifications:

• Some Unicode alphabets are incomplete. Certain blocks are missing individual letters, which are substituted with the closest correct legacy characters. Where a set has known gaps, the affected style page says so.
• Style names are descriptive, not official. Names such as “Classic Script” or “Flowing Italic” are our labels to make styles easy to identify. They are not formal Unicode designations, and other sites may use different names for the same characters.

9. External links and advertising

This Site links to external resources and displays advertising served by third parties, principally Google AdSense. We do not control external sites or the ads shown, do not endorse them, and are not responsible for their content, products, accuracy, or privacy practices. Any transaction with an advertiser or linked site is solely between you and them. Further detail is in our Privacy Policy.

10. No professional advice

Content on this Site is informational. Notes on accessibility, platform behaviour, or commercial use are practical observations from testing and experience — they are not legal, accessibility-compliance, or professional advice. If you have formal accessibility obligations, or a legal question about branding or content, consult a qualified professional.

11. Contact

Questions about this Disclaimer, or corrections to anything stated on the Site, are welcome at info@fontclip.com or via the contact page. Factual corrections are acted on.

Related: Terms & Conditions · Privacy Policy · Cookie Policy Cookie settings · About FontClip