Interaction & speed

Postel's Law

Also known as Robustness Principle

Be liberal in what you accept and conservative in what you send: accept messy user input gracefully, and respond in clear, consistent ways.

Retention · Friction & Flow Psychology1 research source
Share
Messy input flowing into a funnel and coming out as one clean, consistent form — an illustration of Postel's Law.

See it in action

The same screen without and with Postel's Law. Watch both sides play out, then compare the outcome.

Strict about formatPhone numberMobile(415) 555-0132Invalid format. Use 10 digits, no spaces or symbols.Continue

A perfectly understandable number is rejected; the person must guess the “right” way to type it.

Liberal in what it acceptsPhone numberMobile(415) 555-0132Mobile+1 415 555 0132Got it — we'll text you a code.Continue

Any reasonable format is accepted and normalised behind the scenes; the output is consistent.

What to watch: the same input — rejected on the left, quietly cleaned up on the right.

Do

Accept varied input (spaces, dashes, case, formats) and normalise it yourself.

Don’t

Push your system's format rules onto people, or be sloppy in what you send back.

Key takeaways

  • Accept many input formats (dates, phone numbers, spaces) and normalize them yourself.
  • Don't reject input for formatting the system could fix.
  • Keep output — messages, data, layouts — predictable and consistent.

Quick facts

Also known as
Robustness Principle
Described by
Jon Postel
Year
1980
Category
Interaction & speed

Postel's Law explained

Postel's Law, also known as the robustness principle, says: be conservative in what you do, be liberal in what you accept from others. It began as advice for network protocols and applies equally to interface design.

In UX terms, products should accept a wide range of user input (different formats, typos, partial information) and translate it into what the system needs, while providing clear, consistent output.

This shifts the burden of precision from the user to the system. People should not have to know the exact format a database expects.

Where it comes from

Formulated by internet pioneer Jon Postel as the robustness principle in the early TCP specification (RFC 761, 1980), and since adopted as a general design principle.

How it shows up in apps

Forms that reject a phone number because of spaces or a card number because of dashes create pointless errors at high-intent moments like sign-up and checkout.

Postel's Law examples

A sign-up form accepts '(415) 555 0132', '415-555-0132' and '4155550132', formats them consistently, and never shows a format error.

  • Flexible phone number fields

    Accepting phone numbers with spaces, dashes, brackets or country codes, and normalising them behind the scenes, prevents needless validation errors.

  • Natural-language dates

    Calendar and task apps that understand 'next Friday at 3pm' let users enter dates in their own words rather than a fixed format.

  • Search tolerance

    Search that corrects typos and understands synonyms returns useful results even when users do not type the exact product name.

How to apply Postel's Law

  1. Accept common variations in input formats and normalise them automatically.
  2. Correct or suggest fixes for typos instead of rejecting input.
  3. Validate only what really needs validating, and explain errors clearly.
  4. Keep your outputs consistent and predictable.
  5. Design for different devices, input methods, screen sizes and assistive technologies.

Want Postel's Law checked in your own product? Our mobile app ux audit evaluates it alongside the other principles that shape how users decide, onboard and stay.

Common mistakes

  • Rejecting valid input because of formatting such as spaces in card numbers.
  • Being so lenient that ambiguous input is silently misinterpreted.
  • Inconsistent output formats that confuse users.

How to measure it

Track validation error rates per field and the number of attempts users need to submit forms. Search logs showing zero-result queries reveal where the system is not tolerant enough.

Frequently asked questions

What is Postel's Law?

Be liberal in what you accept and conservative in what you send: accept messy user input gracefully, and respond in clear, consistent ways.

Where does Postel's Law come from?

Formulated by internet pioneer Jon Postel as the robustness principle in the early TCP specification (RFC 761, 1980), and since adopted as a general design principle.

How does Postel's Law apply to app design?

Forms that reject a phone number because of spaces or a card number because of dashes create pointless errors at high-intent moments like sign-up and checkout.

Who is Postel's Law named after?

It is named after Jon Postel, an internet pioneer who wrote the principle into early TCP specifications around 1980.

What is an example of Postel's Law in UX?

A form that accepts phone numbers in any common format and formats them consistently, instead of rejecting input that does not match a strict pattern.

How do you measure Postel's Law in a product?

Track validation error rates per field and the number of attempts users need to submit forms. Search logs showing zero-result queries reveal where the system is not tolerant enough.

Sources

  1. Postel, J. (1980). RFC 761: DoD Standard Transmission Control Protocol. Internet Engineering Task Force. Find on Google Scholar ↗

View all 60 laws of UX

Keep exploring

Postel's Law in practice

Keep exploring

Certifications that test it

Pass it on

Teach this to your team

Share it before your next design review — a shared vocabulary makes product decisions faster.

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free certification

Can you apply Postel's Law under pressure?

Test it in 18 real product scenarios in the free Product Design Science test. Score 70% and earn a founder-signed certificate anyone can verify.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy