Font Character Set Planner
Find the characters your font needs from real text. Inventory every unique Unicode code point in a headline, interface, article, or language sample, then compare it with practical release sets before you draw or promise coverage.
Local browser tool
Plan the characters your font actually needs.
Paste representative copy. The planner finds every unique Unicode code point, groups it by role, and compares it with a practical release preset. Your text stays in this page and is not uploaded.
Text inventory
46 unique code points
8 outside Basic Latin
Letters
29Numbers
10Punctuation
6Whitespace
1Why a character inventory belongs at the start
A font release is a promise about text it can represent. “It has the alphabet” is not enough when the intended copy also contains curly quotes, currency, fractions, accented names, mathematical symbols, or combining marks. Starting from representative text makes that promise concrete.
The planner works at Unicode code-point level. It keeps a decomposed e plus combining acute distinct from the precomposed é, because a font can map and shape those sequences differently. That distinction is easy to miss when the screen renders both as the same visible grapheme.
Use three kinds of samples
- Real product copy: navigation, labels, names, prices, dates, and error messages expose the characters a working interface actually uses.
- Language samples: prose from the languages you plan to claim catches accents, marks, and punctuation that an English pangram will not.
- Stress strings: deliberately include quotes, dashes, brackets, percentages, currency, and numerals so quiet omissions do not reach the release file.
What the presets do—and do not do
The Starter proof set is intentionally tiny: it helps test proportions before the alphabet becomes expensive to revise. Uppercase display supports short all-cap uses. Basic Latin covers printable ASCII. The Western Latin working set extends that baseline with Latin-1, Latin Extended-A, and common typographic punctuation.
These are planning recipes, not certifications. A range can include characters irrelevant to your audience and still omit language-specific behavior outside the range. Confirm the exact orthographies, shaping needs, and license expectations for the release you describe.
Scope and privacy
Frequently asked questions
Does the planner upload my text?
No. The inventory runs in the browser. Typelure does not send the text from this tool to an application server.
Does a matching preset prove that a language is supported?
No. Code-point coverage is only one layer. Language support can also depend on combining marks, shaping, localized forms, punctuation conventions, spacing, and proofing by a reader of that language.
Why count code points instead of visible letters?
A visible grapheme can contain more than one code point, such as a base letter followed by a combining mark. Font mappings and character coverage are therefore planned at the code-point level even when readers perceive one character.