Design Character Limits and Counters

Forms & Inputs · forms, validation, microcopy

Updated 2026-07-28

Question the limit first. Many caps exist because of an old column width rather than because of anything the user should care about.
Say the limit before the user starts typing when it is short and meaningful, such as a display name or a headline.
Show the counter only when it becomes relevant. A counter sitting at zero from the beginning is pressure, and one that appears near the limit is help.
Count down rather than up as the user approaches the end. What matters at that point is how much room is left, not how much has been used.
Never silently truncate pasted text. Accept it, show that it is over, and let the user decide what to cut.
Prefer soft limits where the system allows it. Blocking the keystroke means a user who pasted a paragraph now has to edit inside a cramped field with no way to see the whole thing.
Count what the user sees. Emoji, accented characters, and other scripts do not map one to one onto bytes, so a technical count will disagree with the visible one.
Make the state accessible. The remaining count needs to be associated with the field and announced at the point it starts to matter, not on every keystroke.
Explain the consequence when a limit is about display rather than storage, such as where a title will be cut off in a list.

A character limit is a constraint you are imposing on someone's writing, so it should be visible, justified, and forgiving.