# Backward Compatibility

> When a new version still works with things made for the old one.

**Field:** Software Development  
**Category:** Product & Releases  
**Also known as:** Backwards Compatibility, Backward Compatible, Backwards Compatible

## Think of it like

Think of it like a new phone charger that still fits your old phone.

## Definition

Backward compatibility means a new version still works with things made for the old one. Old files still open, old code still runs and old apps can still call the API. You get it by adding new things without removing or changing old ones. It lets users update without fear. Keeping it forever has a cost, since old ways pile up in the code.

## Example

Jack adds an optional field to his API. Old apps that never send it keep working, so the change is backward compatible.

## Why it matters

Users update more often when nothing breaks. The whole group of apps moves on together.

## Common mistake

Promising it forever. At some point old ways must go, so deprecate them with warning and remove them in a major version.

## Three principles

- **Old things still work.** Files, code, apps.
- **Add, do not change.** That is the trick.
- **It has a cost.** Old ways pile up.

## Related terms

- [Breaking Change](https://learn.benibix.com/term/development/breaking-change)
- [Semantic Versioning (SemVer)](https://learn.benibix.com/term/development/semantic-versioning)
- [Deprecation](https://learn.benibix.com/term/development/deprecation)
- [API Versioning](https://learn.benibix.com/term/development/api-versioning)

---

Source: https://learn.benibix.com/term/development/backward-compatibility
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
