Postel’s Law
Accept safe, unambiguous input variation where useful and produce predictable output, while rejecting ambiguity that threatens security or interoperability.
Direct explanation
What it means
The original protocol maxim favored liberal acceptance and conservative sending. In interfaces, helpful normalization can reduce trivial errors, but silent guessing can corrupt meaning and permissive protocols can ossify mistakes.
Users benefit when harmless formatting differences work, yet systems must not reinterpret identity, money, commands, or consent without confirmation.
Research anchor: Robert Braden, editor, 1989
Research and interpretation
What the research found
RFC 1122 codified the robustness principle for internet hosts: be conservative in sending and liberal in accepting.
RFC 9413 explains that broad acceptance can reduce security and interoperability by creating divergent implementations and entrenched invalid behavior.
Popular advice versus careful use
Common shorthand: Accept every input and silently repair it.
Be forgiving only about safe surface variation; be explicit and strict where multiple meanings or adversarial input matter.
How designers apply it
- 01
Normalize spaces and punctuation in a phone-number field while preserving the submitted value.
- 02
Offer spelling-tolerant search with a visible query correction.
- 03
Parse pasted dates only when locale meaning is unambiguous.
Original UI examples
responsive finance form
Invoice amount
The form accepts localized grouping separators after confirming currency and decimal interpretation.
Harmless format variation works without silently changing monetary meaning.
desktop search
Documentation search
A typo returns likely results and displays the corrected query with an Undo link.
The system is forgiving while keeping the transformation inspectable.
Account identifier
Less effective
Silently strip characters and submit a different identifier when two interpretations exist.
Better fit
Explain the expected format, validate precisely, and ask the user to resolve ambiguity.
Security and identity boundaries favor explicitness over liberal guessing.
Limits and failure modes
Protocol design and human-facing input are different domains; any analogy must account for meaning, risk, and user confirmation.
Common mistakes
- Applying a protocol maxim as unconditional UX advice.
- Hiding normalization so users cannot verify the stored value.
When it should not dominate
- For commands, consent, identity, or money with ambiguous meaning.
- Where permissive parsing harms interoperability or security.
Responsible use
Accessibility
Accept common input methods, pasted text, speech punctuation, and Unicode responsibly; pair validation with specific programmatic error messages and correction help.
On mobile: Anticipate autocorrect, locale keyboards, pasted text, and intermittent submission without discarding input.
Ethics and context
Do not convert an ambiguous answer into the business-preferred meaning; obtain explicit confirmation when interpretation changes consequence.
On desktop: Support bulk paste and keyboard entry while exposing normalized results before commitment.
Designer checklist
- Classify safe variation versus semantic ambiguity.
- Show transformations before consequential submission.
- Threat-model permissive parsing and retain original input where appropriate.
Check your understanding
Which statement applies Postel’s Law most carefully?
Practice and continue learning
See ideas in real interfaces
These external interfaces are editorial references, not examples created to demonstrate this principle.
Sources and further reading
- 01Open source
Requirements for Internet Hosts — Communication Layers
Robert Braden, editor · 1989 · IETF
Standard · primary or original source
- 02Open source
Maintaining Robust Protocols
Martin Thomson · 2023 · IETF
Standard
Continue the graph
Related principles
principle
Constraints Principle
Well-designed constraints limit invalid actions or make their boundaries clear while preserving valid choice and recovery.
usability heuristic
Feedback Principle
Every meaningful action should produce timely, perceivable feedback that accurately communicates the resulting system state.
usability heuristic
Recognition Rather Than Recall
Make relevant objects, actions, and options visible or readily retrievable so people do not have to recall them unaided.