Frequently Asked Questions
Common questions about using the Character Counter — privacy, behavior, and tips.
No — all text processing happens locally in your browser by default. Nothing is sent to our servers unless you explicitly use a "Verify with server" feature.
We prefer grapheme-cluster counts (user-perceived characters) where supported. This counts emoji sequences and combined accents as a single character. We also expose byte and code-unit counts for advanced needs.
By default spaces are included in the raw character count, but the homepage counter can show counts excluding spaces — check the UI for the "exclude spaces" option.
Yes — use the Copy button to copy text to your clipboard or Clear to reset the editor. Everything happens locally for privacy.
The counter works with any Unicode text: Latin, CJK, Arabic, emoji, and combined scripts. Grapheme support varies by browser but falls back to a safe heuristic.
Bytes measure storage size (UTF-8 encoding) and vary for non-ASCII characters. Character counts measure visible characters or code units depending on the metric.
We use Intl.Segmenter when available for accurate grapheme segmentation; when unavailable we use a conservative fallback — accurate for most common cases.
Yes — enabling the option to ignore zero-width characters will strip them before counting to give an accurate visible-character count.
Yes — the Character Counter is free and doesn’t require sign-up. It is built with privacy in mind.