Release Note Generator
Fill in the details below
Your output will appear here.
Our release notes generator turns a title and a list of shipped changes into release notes in Markdown. Tick the change types, add each change, choose a tone and a language, and AI drafts notes you can paste into GitHub, your docs or a product update email. It suits product managers, developers and support teams. Review the draft before you publish. It is free with no sign-up.
Fill in the details below
Your output will appear here.
Tick New Feature, Improvement or Bug Fix so the notes group related changes the way readers expect.
Choose from Friendly, Professional, Relaxed, Bold, Witty and more to match how your product speaks to users.
Write notes in English, Spanish, French or German from the same list of changes.
Copy the draft as Markdown and paste it into a GitHub release, a changelog file or your help center.
Three steps from a blank form to a result you can use.
Enter a Title, tick the Changes shipped types and type each change, pressing Enter after every one.
Pick a tone and one of four languages, then click Generate to draft the notes.
Check every line against what really shipped, copy the Markdown and publish it where your users look.
Release notes tell users what changed and why it matters to them. A good set is short, grouped by type and written in plain words, not copied from commit messages.
Keep a Changelog, a widely used guide for changelogs, says changelogs are for humans, not machines, and that the same types of changes should be grouped. It lists six types. The tool's three checkboxes map to three of them.
| Keep a Changelog type | Meaning | In this tool |
|---|---|---|
| Added | New features | New Feature |
| Changed | Changes in existing functionality | Improvement |
| Fixed | Bug fixes | Bug Fix |
| Deprecated | Features that will be removed soon | Add as a change line and say so |
| Removed | Features now removed | Add as a change line and say so |
| Security | Fixes for vulnerabilities | Add as a change line and say so |
The guide also puts the latest version first and shows the release date of each version. We suggest adding the date to your Title or to the published page, since the draft only knows what you type.
Example: an illustration with made up changes. Your real output will differ in wording.
Inputs: Title is "Version 2.4: Faster Reports". Changes shipped has New Feature, Improvement and Bug Fix ticked. The change lines are: "Export reports to CSV", "Reports load in about half the time" and "Fixed due dates showing a day early for users in UTC minus time zones". Choose a Tone is Professional and Language is English.
A good draft looks like this in Markdown:
## Version 2.4: Faster Reports
### New Features
- Export any report to CSV from the report menu.
### Improvements
- Reports now load in about half the time.
### Bug Fixes
- Due dates no longer show a day early for users in UTC minus time zones.Notice that each line says what the user can now do or no longer suffers. If a draft adds a benefit you did not ship, delete it.
The draft can only be as clear as your change lines. Keep a Changelog warns that using commit log diffs as changelogs is a bad idea because they are full of noise. Rewrite internal notes before you add them.
| Internal note | Better change line |
|---|---|
| Refactor report query, add index | Reports load faster on large projects |
| Fix TZ offset bug in due_date | Due dates show the correct day in every time zone |
| Bump auth lib | Security update to sign in (no action needed) |
We follow three rules: lead with the user's benefit, name the screen or feature, and say if the user must do anything. For tone, Professional or Friendly fits most software updates. Witty can work for consumer apps, but we keep security and bug fix lines plain in any tone.
Keep a Changelog recommends stating whether you follow Semantic Versioning. Under Semantic Versioning, a version has three numbers, MAJOR.MINOR.PATCH:
This lines up with the change types. A release that only has Bug Fix lines is usually a patch. New Feature lines suggest a minor version. A breaking change calls for a major version and a clear note telling users what to update. Put the version in the Title field so it lands in the heading of the draft.
If your team tracks work in Onethread, the tasks you completed for a release make a ready list of change lines to paste into the tool.
Quick answers about the Release Notes Generator.
It turns a title and a list of shipped changes into release notes in Markdown. You tick the change types, add each change, choose a tone and a language, and AI drafts grouped notes in the output panel. You copy the result and paste it into GitHub, a changelog file, your help center or an email.
Yes. It is free to use and needs no sign-up or account. Fill in the Title, tick the change types, add your changes, pick a tone and a language, and click Generate. There is no download step. You copy the Markdown and paste it wherever you publish updates.
A changelog is a running file that lists notable changes for every version, latest first. Release notes usually describe one release in more detail for users. Both should group changes by type. The tool drafts notes for one release, which you can paste into a changelog or publish on its own.
Yes. The output is Markdown, which GitHub release descriptions accept. GitHub can also generate notes automatically from merged pull requests, contributors and a changelog link. Our tool works from your own change list instead, which helps when pull request titles are too technical for users to read.
We suggest Professional for business software and Friendly for consumer apps. Witty or Bold can suit a playful brand, but keep bug fixes and security lines plain. Luxury and Adventurous rarely fit software updates. Whatever you pick, use the same tone every release so your notes sound consistent.
Yes. The Language field offers English, Spanish, French and German. You can enter your changes in English and choose another language for the draft. We suggest asking a fluent speaker to check product names, button labels and technical terms before you publish translated notes to customers.
This Numbered List Generator adds numbers to a list you paste in.
Our PHP code generator drafts PHP code from a short brief.
Our ChatGPT prompt generator writes a role prompt that tells ChatGPT who to be.
Our website typography generator suggests fonts and font sizes for your site, with a short explanation for...