CHANGELOG Entry Builder

Build clean CHANGELOG.md entries from your commits in seconds.

Last reviewed: April 2026

New to this tool? Click here for instructions

Generated CHANGELOG
Fill in the version and entries above to generate your changelog.

How to Use the CHANGELOG Generator

The CHANGELOG Generator is a free, browser-only tool that turns your commits and notes into a clean CHANGELOG.md entry. Here's how to use it:

1. Pick a format: Choose Keep a Changelog, Conventional Commits, Simple, or Append to an existing changelog.

2. Add your changes: Paste commit messages or type entries, then assign each to a category (Added, Changed, Fixed, Removed, Deprecated, Security).

3. Set the version and date: Enter the release version and date for the entry heading.

4. Copy the markdown: The generated CHANGELOG.md text updates live — copy or download it straight into your repository.

When to Use It in Real Workflows

Reach for the CHANGELOG Generator whenever you cut a release and want a consistent, readable history. It is ideal for teams that follow Keep a Changelog or Conventional Commits, and for maintainers who want release notes that users and contributors can scan quickly.

How It Works

The tool parses your input — including Conventional Commit prefixes like feat:, fix:, and breaking-change markers (!) — and groups entries under the right headings. It then renders a properly formatted Markdown section with the version, date, and grouped changes. Everything runs in your browser; nothing is uploaded.

Tips, Edge Cases, and Limitations

1. Conventional Commits: Prefixing commits with feat:, fix:, docs:, etc. lets the tool categorize them automatically.

2. Breaking changes: Mark them with a ! after the type (for example feat!:) so they are surfaced prominently.

3. Keep entries user-facing: Write changelog lines for the people reading them — describe the impact, not the implementation detail.

Frequently Asked Questions

Keep a Changelog (keepachangelog.com) is a standard format for maintaining a CHANGELOG.md file. It groups changes under version headings, each dated, and categorises entries as Added, Changed, Deprecated, Removed, Fixed, or Security. The format is human-readable and machine-parseable.
Conventional Commits is a specification for commit messages that makes them machine-readable. Messages follow the pattern type(scope): description - for example feat(auth): add OAuth login. Tools like semantic-release and standard-version use Conventional Commits to automatically determine version bumps and generate changelogs.
Switch to the 'Append' mode, paste your existing CHANGELOG.md content into the 'Existing changelog' textarea, then fill in the new version details. The tool places the new version section at the top (below the title) and preserves all older entries.
Use Semantic Versioning (SemVer): MAJOR.MINOR.PATCH, e.g. 2.1.0. MAJOR bumps for breaking changes, MINOR for new backward-compatible features, PATCH for bug fixes. Pre-release identifiers like 1.0.0-alpha.1 or build metadata like 1.0.0+build.123 are also valid SemVer.
No. This tool runs entirely in your browser. No data is transmitted, logged, or stored.

Quick reference

CHANGELOG Entry Builder Quick Reference
Entry Type Version Date Summary
Feature Addition 2.1.0 2023-10-15 Added dark mode support and accessibility improvements
Breaking Change 2.0.0 2023-09-01 Removed deprecated API endpoints; updated authentication protocol
Performance Improvement 1.9.2 2023-08-22 Optimized database queries reducing load time by 30%
Bug Fix 1.8.5 2023-07-30 Fixed memory leak in real-time data processing module
Documentation Update 1.7.0 2023-06-18 Expanded API reference with usage examples and troubleshooting guide
Security Patch 1.6.3 2023-05-12 Addressed vulnerability in session management system