Text Tools

Count and transform text under explicitly documented JavaScript token, code-point, code-unit, whitespace, and case-mapping rules.

Describes the algorithms actually used instead of promising universal linguistic segmentation or editorial style-guide compliance.

What This Category Covers

Word and character counting
Case conversion and text cleanup
Draft length checks for content operations
Prototype and placeholder text tasks
Local-first plain-text transformations

Common Use Cases

Word Counter splits non-empty trimmed text on runs of whitespace.
Character Counter reports JavaScript UTF-16 code units; Word Counter separately reports Unicode code points.
Case conversion uses default JavaScript Unicode mapping and still needs review for names, acronyms, and locale-sensitive text.

Quick Reference

Task	Recommended Tool	Why It Helps
Editorial length checks	Word Counter	Useful for drafts, assignments, and content briefs.
Platform field limits	Character Counter	Checks metadata, ads, usernames, and UI labels.
Title and copy cleanup	Case Converter	Standardizes casing before final human review.

Text Metrics Depend On The Declared Algorithm

Word Counter treats each run of non-whitespace text as one token after trimming. Hyphenated text without whitespace remains one token. Its character metric uses Unicode code points, while Character Counter uses JavaScript UTF-16 code units; neither promises user-perceived grapheme-cluster segmentation.

Case tools use default JavaScript Unicode case mapping. The multi-mode Case Converter applies simple programmatic rules, not AP, Chicago, APA, or locale-specific title-case policy. Acronyms, brands, names, combining marks, and locale-sensitive letters still need review.

Lorem Ipsum uses a fixed local paragraph set and a bounded paragraph count. Generated filler is for layout testing, not meaningful copy or a prediction of final editorial length.