Changelog Generator
Build a Keep-a-Changelog-style CHANGELOG.md by adding entries to Added / Changed / Fixed / Removed / Security buckets.
Quick answer: Changelog Generator: build a Keep-a-Changelog-style CHANGELOG.md by adding entries to Added / Changed / Fixed / Removed / Security buckets. Runs entirely in your browser, free, no signup.
Last updated
Good to know
A changelog is the human-facing history of a project — the answer to "what changed and should I care?" that a raw Git log can never give, because commit messages are written for developers mid-work, not for users deciding whether to upgrade. This generator follows the Keep a Changelog convention, which groups every release's notes into five clear buckets: Added, Changed, Deprecated/Removed, Fixed and Security. That last one is not decoration — flagging security fixes explicitly helps users prioritize urgent upgrades.
Order and structure are the whole value. Entries are written for people, so "Fixed crash when importing empty CSV files" beats "fix null ref in parser," and releases are listed newest-first so the current version is always at the top. Each version gets a heading with its number and release date, which pairs naturally with Semantic Versioning — MAJOR.MINOR.PATCH — where the bucket an entry lands in often signals which number to bump: a breaking change means a major, a new feature a minor, a bug fix a patch.
A good habit is to keep an Unreleased section at the top and jot entries as you merge them, so writing the changelog is not a scramble at release time. Because everything renders in your browser as standard CHANGELOG.md Markdown, it drops straight into your repo root next to the README. Generate the surrounding project files with the .gitignore generator and the license generator.
Frequently asked questions
- Is the changelog generator free?
- Yes — free, no signup.
- Which format does it follow?
- Keep a Changelog 1.1 (Added / Changed / Fixed / Removed / Security) — the most widely-used format.
- Are my entries uploaded?
- No — every change happens in your browser.
- Should I write a changelog?
- Yes — for any project users depend on, a clear changelog dramatically reduces upgrade pain.
- How do I version?
- Semantic Versioning (semver) is the de-facto convention: MAJOR.MINOR.PATCH.