Free Online Changelog Generator
Create a Keep a Changelog style changelog from release entries.
About the Changelog Generator
A changelog is a curated record of what changed in each release. It is written for the people who use the software, not for the people who wrote the commits. A good entry explains the effect of a change: a new option, a corrected calculation, a removed endpoint, or an altered default. Keep a Changelog is a widely used convention that organizes entries under headings such as Added, Changed, Fixed, and Removed, with one section per released version and an optional Unreleased section at the top.
This generator gives every release a version, a date, and up to four category lists. Type one change per line; blank lines are ignored, and a leading dash is removed so you do not end up with doubled bullets. When you click Generate, the tool sorts releases by date descending, groups the entries under the right category headings, and writes a complete Markdown document with the standard introduction and a link to the Keep a Changelog and Semantic Versioning specifications. Releases with no entries are rejected so the output stays meaningful.
The generated file uses plain Markdown headings, so it renders correctly on GitHub, GitLab, Bitbucket, and most static site generators. Version numbers are not automatically linked to compare views, because that requires a repository URL and a consistent tag format. If you want comparison links, add them after generation or extend the workflow in your release script. The tool also does not read git history: it cannot infer which commits are new features versus fixes. That classification is a human decision, and the quality of the changelog depends on it.
Dates should be written as YYYY-MM-DD, which is what the date picker supplies. The Unreleased checkbox adds an empty section for work in progress. If you generate the same changelog twice, the output is stable for the same input, which makes diffs clean. Nothing is saved or uploaded, so download the file before closing the page if you want to keep the draft.
How to use this tool
- Add one card per release and enter its version and date.
- Type changes into Added, Changed, Fixed, or Removed, one per line.
- Click Generate changelog and review the Markdown output.
- Copy it or download it as
CHANGELOG.md.
Frequently asked questions
Does it read my git commits?
No. You decide which changes belong in each category. The tool formats the notes you provide.
Can I use a date format other than YYYY-MM-DD?
The date input supplies YYYY-MM-DD, which Keep a Changelog recommends. Other formats may render, but they sort less reliably and are not standard.
Are duplicate versions allowed?
No. Generation stops if two releases share the same version, because the resulting headings would be ambiguous.