Skip to main content
100% Local Processing (Local Browser Memory) — Files Never Leave Your Browser
Engine: text-counter

Character Counter

Measure exact character counts, Unicode grapheme clusters, UTF-8 byte size, and platform limit progress bars locally.

Local Workspace (text-counter)

How to Use Character Counter

  1. 1Paste or type your social post, SEO meta description, or database string into the input workspace.
  2. 2Compare visible Grapheme Clusters against UTF-16 code units, space-excluded characters, and exact UTF-8 byte payload size.
  3. 3Monitor the live progress bars for X/Twitter (280), Meta Description (160), YouTube Title (100), Instagram Bio (150), and SMS (160).

Technical Specifications & Guardrails

  • Distinguishes visible grapheme clusters (Intl.Segmenter) from UTF-16 code units and UTF-8 byte length
  • Live capacity progress bars for X/Twitter (280), Meta Description (160), YouTube Title (100), Instagram Bio (150), and SMS (160)
  • Automatic background Web Worker offload when pasted text exceeds 100 KB
  • One-click plain-text copy and sanitized .txt file download

Practical Example: Verifying Multi-Byte Unicode Copy Against Database and Social Caps

Sample Input
A 155-grapheme promotional bio containing multi-codepoint emoji sequences and accented characters.
Verified Local Output
Flags Instagram Bio (150 limit) as 5 characters over limit while confirming Meta Description (160 limit) has 5 characters remaining and reporting exact UTF-8 byte size.

Operational Limits & Browser Guardrails

Supports inputs up to 10 MB locally (offloading payloads above 100 KB to a Web Worker). Platform limit bars evaluate user-perceived Unicode grapheme clusters; note that SMS carriers switch from 160-character GSM-7 encoding to 70-character UCS-2 segments when non-GSM Unicode characters are present.

Frequently Asked Questions

Why do Character Count, Grapheme Count, and UTF-8 Byte Length sometimes differ?

JavaScript string length counts 16-bit UTF-16 code units, whereas Intl.Segmenter counts user-perceived characters (grapheme clusters such as combined emoji sequences) and TextEncoder measures the 1-to-4-byte UTF-8 representation stored in databases and HTTP payloads.

Which platform character limits are tracked in real time?

The progress bars track X/Twitter posts (280 chars), SEO Meta Descriptions (160 chars), YouTube video titles (100 chars), Instagram profile bios (150 chars), and standard GSM-7 SMS messages (160 chars).

Is any of my pasted text logged or sent to an external server?

Never. Grapheme segmentation and UTF-8 byte encoding run strictly inside your browser's local JavaScript and Web Worker runtime.