How we test our tools

Last updated: 12 October 2026

We test our tools with automated checks that run before every update goes live. This page describes exactly what is tested, and what is not tested yet.

1. Conversion tests: 4,158 checks

Every one of our 594 styles is run on 7 sample texts, including capitals, small letters, digits, punctuation, tabs and new lines, accented letters, emoji, Hindi text and empty text. That is 4,158 conversions. The test compares the result from the converter in your browser with the result from the converter on our server, character by character. Both must be identical for the update to go live. This catches mistakes in either copy of the rules.

The style table itself is checked when it is built: the build stops with an error if any alphabet has the wrong number of characters. We have also confirmed that every character in it is an assigned code point in the Unicode Character Database.

2. Browser tests: 39 checks of the interactive tools

A test suite opens the real pages in a browser, uses them like a visitor would and compares the results with known answers:

ToolWhat is checkedExample of an expected result
Fancy text generatorTyped text is converted in the browser exactly as on the serverTest 42 in bold gives ๐“๐ž๐ฌ๐ญ ๐Ÿ’๐Ÿ
Text symbolsTapping collects symbols; search shows only matching sectionsSearching "heart" leaves only the heart symbols
Character counterCharacters, app count, words, lines, bytes and limit warningsHi ๐Ÿ˜€ ๐“— + new line + ok: 9 characters, app count 11, 15 bytes
Case converterAll 10 case modes, and "Remove fancy fonts" on 16 style familiesthe QUICK brown fox. in Title Case gives The Quick Brown Fox.
Text repeaterRepeats, separators and numberinghi ร— 3 gives hi hi hi
Invisible textThe right character is repeated the right number of times10 ร— U+3164 HANGUL FILLER

3. Site checks on every page

Before each update we also check every page on the site for:

  • a working page (HTTP 200), exactly one main heading, a unique title and description, and a correct canonical link;
  • valid structured data, with every internal reference resolving and required properties present;
  • every internal link working (no broken links);
  • every style named on a page existing in the style table, so examples can never show the wrong characters;
  • tools that have not been reviewed in the last 6 months.

What we have not tested yet

  • Physical devices. Our browser tests run in a desktop browser. We have not yet tested every style on a wide range of real phones, so compatibility ratings are based on Unicode block support rather than device testing.
  • Every app. Apps and games can change which characters they accept at any time. When you find a style that no longer works somewhere, please tell us.

Read more about how the tools work in our methodology, or see every reference on the sources page.