What is a changelog? A complete guide for software teams
A changelog is a record of notable changes to your product. Learn what a changelog is, why it matters, and how to keep one that customers value.
If you ship software, you have probably been told you should keep a changelog. But what is a changelog, exactly, and why does it matter? This guide explains what a changelog is, what goes in one, and how to maintain it without it becoming a chore.
What is a changelog?
A changelog is a curated, chronological list of the notable changes made to a product, ordered with the most recent changes first. Each entry describes what changed in language a customer can understand — not a copy of your commit history.
What goes in a changelog?
A good changelog captures the changes that affect the people using your product:
- New — features and capabilities that didn't exist before.
- Improved — existing things that got better, faster, or clearer.
- Fixed — bugs and issues that were resolved.
It deliberately leaves out internal refactors, dependency bumps, and anything a customer would never notice.
Why keep a changelog?
A changelog earns its keep in several ways:
- Trust and momentum. A steady stream of updates shows your product is alive and improving.
- Adoption. Customers can't use features they never hear about.
- Support deflection. "Was this fixed?" becomes a link instead of a ticket.
- SEO and discovery. A public changelog is indexable content that ranks for your product's feature names.
What makes a changelog good?
The best changelogs share a few traits:
- Entries lead with the customer outcome.
- Changes are grouped and labeled.
- Updates are published consistently, not in rare bursts.
- The language is plain, with no internal jargon.
A changelog is only useful if it is both readable and kept up to date.
The maintenance problem
Most changelogs die from neglect — not because teams don't care, but because writing them competes with shipping the next thing. Changelog Generator solves this by reading your merged pull requests and drafting changelog entries automatically, so your changelog stays current without the manual upkeep.