Free tools that run in your browser. Use any tool without an account.

Favourites Cart
Sign in
Join free

Changelog Generator

  • Free
  • Runs in your browser
  • No account needed

You paste commit lines, set the version and date, and get a Keep a Changelog style Markdown entry. For example, paste 12 commits and version v1.4.0 to produce grouped Added, Changed, Fixed and Security sections per Conventional Commits.

Changelog entry (Markdown)
## [1.4.0]

### Added

- **checkout:** Add Paystack and Flutterwave payments
- **Breaking:** Drop support for Node 16

### Changed

- Load product images lazily

### Fixed

- Cart total rounding for NGN prices
Entries
4
Runs in your browser. Your files and values are not sent to us. Report a problem
Advertisement

About the Changelog Generator

You use this tool to turn commit messages or pasted git log lines into a single release entry in Markdown. It follows Keep a Changelog and maps Conventional Commit types to sections. The tool runs in your browser, so nothing is uploaded to a server. Results update instantly as you type and you can copy the Markdown or share a link that reopens with your inputs. The generator removes git hashes and merge commits, capitalises the first letter of each subject, drops exact duplicates, and can show scopes as bold labels. It omits housekeeping types like docs and chore unless you choose to list them under Other. This tool is for draft release notes and quick CHANGELOG.md fragments that you will review before publishing. See Keep a Changelog and Conventional Commits for formatting rules.

How to use it

  1. 1Enter the version string (for example v1.4.0)
  2. 2Enter the release date (for example 2024-10-15)
  3. 3Paste commit messages or git log lines, one per line
  4. 4Toggle Show scopes and choose whether to list docs and chores, then copy or share the Markdown
Advertisement

Worked example

Inputs Version: v1.4.0 Release date: 2024-10-15 Show scopes: Yes (bold labels) docs, chore, ci, build, test, style: Leave them out Commit messages (one per line): a1b2c3d feat(api): add rate limit header feat(ui): add dark mode feat(ui): add dark mode fix(auth): correct token expiry perf: speed up query parsing refactor(parser): simplify parsing logic security: fix S3 bucket ACL exposure feat(runtime)!: drop Node 10 support chore: bump deps Merge branch 'feature-x' into main update translations Generated Markdown entry ## [v1.4.0] - 2024-10-15 ### Added - **api**: Add rate limit header - **ui**: Add dark mode - **runtime**: Drop Node 10 support. BREAKING CHANGE. ### Changed - **parser**: Simplify parsing logic - Speed up query parsing - Update translations ### Fixed - **auth**: Correct token expiry ### Security - Fix S3 bucket ACL exposure Notes: commit hashes and the merge commit were removed, duplicate lines were dropped, and scopes appear as bold labels. Docs and chore lines were omitted.

How it works

Inputs: Version; Release date; Commit messages, one per line; Show scopes [Yes, as bold labels / No]; docs, chore, ci, build, test, style [Leave them out / List them under Other]Results shown: Changelog entry (Markdown); EntriesMethod used: Follows the Keep a Changelog formatConventional Commit types are sorted into sections: feat goes to Added, fix to Fixed, perf, refactor and revert to Changed, security to Security, and anything without a type to ChangedA ! after the type or a BREAKING CHANGE note marks the line as breakingCommit hashes from git log --oneline and merge commits are removed, the first letter is capitalised and duplicates are droppedResults update instantly as the visitor types; there is no calculate buttonVisitors can copy the result and share a link that reopens with their numbers

Source: Keep a ChangelogConventional CommitsSemantic Versioning. Last checked 6 November 2026.

What it is good for

  • Produces Keep a Changelog compatible Markdown automatically
  • Runs client-side in your browser so nothing is uploaded
  • Updates instantly as you type and gives a shareable link
  • Works best with Conventional Commit style messages; messy commits need manual editing
  • This browser tool does not inspect diffs, PR metadata, or run in CI
Advertisement

Questions people ask

Can the generator detect breaking changes automatically?

Yes if commits use a ! after the type or include a BREAKING CHANGE footer. If commits do not mark breaking changes, you must review and mark them manually.

Does the tool upload my commit data to a server?

No. The generator runs in your browser and processes data client-side. Nothing is uploaded unless you explicitly share a link using the page feature.

How should I prepare commits to get the best output?

Use Conventional Commits for subjects like feat(scope): message or fix(scope): message. Export the right set of commits with git log vX..HEAD for releases and paste those lines.

What happens to housekeeping types like docs or chore?

You choose. The tool can omit docs, chore, ci, build, test and style by default, or list them under an Other section if you select that option.

Can I use this in CI to auto-generate changelogs?

No. This browser tool is for quick drafts and manual workflows. For CI automation, use repo-aware tools like conventional-changelog, release-please, or semantic-release.

Will the generator include commit hashes or merge commits?

No. Commit hashes from git log --oneline are removed and merge commits are skipped. The tool keeps human readable subjects and drops duplicates.

Help keep every tool free

FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.

Advertisement
Advertisement