De Facto Standard
A product, format or convention that becomes the standard because nearly everyone uses it, not because a standards body approved it.
Also known as: De Facto Standards, Industry Standard, Dominant Design, De Jure Standard
Category: Business & Economics
Tags: standards, technology, network-effects, economics, interoperability, markets
Explanation
De facto is Latin for "in fact". A de facto standard wins through adoption. Nobody voted for it. It's simply what everyone uses, so everyone else has to support it. The opposite is a de jure standard: one that a recognized body such as ISO, the IETF or the W3C formally published.
**Examples**:
- **QWERTY**: The keyboard layout that stayed long after the mechanical reason for it disappeared
- **PDF**: Adobe's format was the de facto standard for documents years before it became an ISO standard in 2008
- **Microsoft Office formats**: `.doc` and `.xls` were what everyone exchanged, so every competitor had to read them
- **Markdown**: It spread for years with no formal specification at all
- **Git**: Nobody mandated it. It just won
- **The S3 API**: Amazon's storage API is now implemented by many competing storage products
**How one emerges**:
- **Network effects**: Every new user makes the format more useful for the next one
- **Being early and good enough**: The first workable solution collects the ecosystem (see Worse Is Better)
- **Switching costs**: Once files, tools and skills depend on it, leaving is expensive
- **Dominant implementations**: What the most popular product does becomes what everybody has to do, bugs included
**Why it matters**:
- Adopting a de facto standard gives you compatibility with a whole ecosystem for free
- It can be owned by one company, which can change it or restrict it. That's a lock-in risk
- Often there's no complete specification. The real standard is "whatever the dominant implementation does"
**Link with the robustness principle**:
Liberal receivers create de facto standards by accident. When popular software accepts sloppy input, the sloppiness spreads, and every other implementation has to accept it too. Browsers and broken HTML are the textbook case.
**From de facto to de jure**:
Many formal standards started this way. Standards bodies often do their best work when they write down and clean up what already works, instead of inventing from nothing.
Related Concepts
← Back to all concepts