Abbreviation Glossary Builder

Build a glossary from supplied definitions and review abbreviation uses and unexplained uppercase tokens in a document.

On-device No sign-up Free to use

Build glossary controls

Showing an example. Edit to see your own.

?

Up to 200,000 characters. The text stays in your browser.

?

One entry per line as abbreviation | definition. Up to 200 entries. Use ASCII letters and digits, with optional interior periods.

?

The same policy drives the usage counts, the duplicate check and the candidate list.

Processed in your browser. Your inputs stay on this device.

Result

Showing an example.

Check API and UI against your glossary, then find CSV as an unexplained token.

Checked 2 glossary entries against 23 characters. 2 entries appear in the text. 1 uppercase token in the text is not in the glossary.
Abbreviation glossary report
Document characters: 23
Glossary entries: 2 (2 found in the text, 0 not found)
Case policy: case-insensitive

ABBREVIATION | USES | DEFINITION
API | 1 | Application Programming Interface
UI | 1 | User Interface

Unexplained uppercase tokens (review suggestions, not an error list)
CSV | 1

Matching is exact whole-token matching only. This report does not infer expansions and cannot list every abbreviation in a document.

API | Application Programming Interface | 1
UI | User Interface | 1

Loading the tool. Your result will appear here.

https://usefreetools.net/abbreviation-glossary-builder · 20 November 2026

Was this helpful?

How to use Abbreviation Glossary Builder

  1. Enter abbreviations and definitions in the row editor, or use advanced abbreviation | definition lines.
  2. Paste the document and choose whether abbreviation matching is case sensitive.
  3. To load definitions already written as Expansion (ABBR), choose Use definitions supplied in the text. Review the loaded definitions before checking the document.
  4. Read the use counts and unexplained tokens, then copy or download the glossary and findings.

Example: Abbreviation Glossary Builder

Check API and UI against your glossary, then find CSV as an unexplained token.

You add
Text to check: API uses UI. Check CSV. Glossary: API | Application Programming Interface UI | User Interface Matching case: insensitive
You get
Checked 2 glossary entries against 23 characters. 2 entries appear in the text. 1 uppercase token in the text is not in the glossary. Abbreviation glossary report Document characters: 23 Glossary entries: 2 (2 found in the text, 0 not found) Case policy: case-insensitive ABBREVIATION | USES | DEFINITION API | 1 | Application Programming Interface UI | 1 | User Interface Unexplained uppercase tokens (review suggestions, not an error list) CSV | 1 Matching is exact whole-token matching only. This report does not infer expansions and cannot list every abbreviation in a document. API | Application Programming Interface | 1 UI | User Interface | 1

Options

Supplied glossary
Fill each abbreviation and definition row, or edit the advanced lines. The page uses your supplied definitions and never guesses expansions.
Case policy
Insensitive mode compares case variants; sensitive mode requires the exact spelling. Keep the selected policy with a reported count.

Supported inputs and limits

  • Up to 200 unique glossary entries and 200,000 document characters.
  • Abbreviations use the supported ASCII token form; matching follows the selected case policy.
  • Uppercase candidates are suggestions, so names, headings and missed variants need review.
  • Expansions are never guessed.
  • Glossary text is capped at 100,000 characters, with 40-character keys and 300-character definitions.
More details

Candidate totals are counted, while the report lists the 50 most frequent unexplained tokens.

Where your input is processed

This tool does not upload your inputs. See the limits for anything saved on your device.

An uppercase candidate is a prompt for review

The candidate list can include a name or heading that is not an abbreviation. It can also miss abbreviations outside the supported token form. Use the report to revisit the original passage and add only definitions you can verify, rather than expanding every uppercase token automatically.

Questions about Abbreviation Glossary Builder

Does this tool invent acronym definitions?

No. Enter definitions yourself or load explicit Expansion (ABBR) definitions already present in your text. An unexplained token in the report is a prompt for you to check it.

Why can a heading appear in the unexplained list?

The check looks for uppercase token patterns. It cannot tell whether a token is an abbreviation, a name or an emphasized word.

How are periods and letter case handled?

Use the spelling you want checked in the glossary. Select the case policy explicitly; punctuation variants are not inferred as equivalent.

Page updated · Project managed by Tony Hines · Report a problem with Abbreviation Glossary Builder

Related reading

All guides