Release Notes Generator

Your data never leaves your browser

Generate formatted Markdown release notes from a list of conventional commits grouped by category.

Brie — Bug Reporting Tool

Found a bug while testing?

Brie captures screenshots, console logs, network data, and session replays in one click — so developers get the full context without the back-and-forth.

Install Brie — It's FreeLearn more →

About Release Notes Generator

Turn a raw list of changes into polished, structured release notes in seconds. Enter your changes in conventional commit format ("type: description"), set the version number and date, and the tool groups entries into Features, Bug Fixes, Improvements, and Documentation sections. The output is formatted Markdown ready to paste into GitHub releases, changelogs, or product announcements.

How to use

  1. Enter one change per line using the format "type: description" (e.g. "feat: Add dark mode", "fix: Login timeout").
  2. Set the version number and release date in the options.
  3. Click Convert to generate formatted Markdown release notes grouped by category.

More Product Owner Tools

User Story Formatter

Format user stories in the standard "As a… I want… so that…" structure with auto-generated acceptance criteria.

MoSCoW Prioritizer

Organise features into Must Have, Should Have, Could Have, and Won't Have categories with counts and percentages.

RICE Score Calculator

Calculate and rank features by RICE score (Reach × Impact × Confidence / Effort).

Frequently Asked Questions

FAQs about Release Notes Generator

What are conventional commits?

Conventional commits are a lightweight convention for commit messages. Each message has a type prefix (feat, fix, refactor, docs, chore, etc.) followed by a colon and a short description. This makes it easy to auto-generate changelogs.

What commit types are supported?

The tool recognises feat (Features), fix (Bug Fixes), refactor (Improvements), perf (Improvements), chore (Improvements), and docs (Documentation). Unrecognised types are listed under a general Changes section.

Can I use this for GitHub releases?

Yes. The output is formatted as Markdown, which renders correctly in GitHub release notes, CHANGELOG.md files, and most product documentation platforms.

What version format should I use?

Any format works, but semantic versioning (MAJOR.MINOR.PATCH, e.g. 2.1.0) is the most widely used convention. Stick to whatever format your project already uses.

Does this tool store my data?

No. All formatting happens in your browser. Nothing is sent to any server.