SaaS Changelog Generator
Free SaaS Changelog Generator
Paste conventional commits or a plain bullet list. Get a Keep-a-Changelog-formatted release note in Markdown or HTML — ready for your release page.
Enter a version and at least one commit or bullet to generate a changelog.
Why creators use this tool
Keep-a-Changelog compliant
Auto-sorts entries into Added / Changed / Fixed / Removed / Security — the standard everyone reads.
Conventional commits detected
feat:, fix:, chore:, refactor: prefixes are recognised and sorted automatically.
Markdown or HTML
One click to copy in either format — Markdown for GitHub/Notion, HTML for your marketing site.
Nothing leaves your browser
Your commit history is never sent to a server. Everything runs locally.
How to use it
- 1. Enter the version number (e.g.
2.4.0). - 2. Pick a release date.
- 3. Paste raw
git log --pretty=format:'%s'output or a bullet list. - 4. Copy the Markdown or HTML output and publish.
SaaS Changelog Generator — best practices in 2026
Write for humans, not compilers
Users don't care that you bumped a dependency. They care that ‘the app now loads 40% faster' or ‘export to PDF is finally here'. Translate every entry into user-visible impact.
Use active voice and past tense
‘Added dark mode' beats ‘Dark mode has been added'. It's shorter, punchier, and matches how most changelogs read.
Group by category, not by team
Users don't care which team shipped what. Group by Added / Changed / Fixed / Removed — that's what they scan for.
Lead with the biggest change
Within each section, put the change most users will notice first. If dark mode is 90% of what people asked for, it goes at the top.
Ship changelogs on a predictable cadence
Weekly, biweekly, or per-release — but consistent. Silence between releases quietly signals ‘this product is dying'.
Cross-post to your community
Discord, Slack community, in-app widget, email. Every channel that reaches an active user is a channel that needs the changelog.
Frequently asked questions
What format does this changelog use? ⌄
Keep a Changelog convention — Added, Changed, Fixed, Removed, Security. It's the format most SaaS teams and GitHub projects have standardised on.
Can I paste raw git commit messages? ⌄
Yes — conventional commit prefixes (feat:, fix:, chore:) are auto-detected and sorted into the right sections.
Does it support plain bullet lists? ⌄
Yes. Any line starting with ‘-', ‘*', or ‘•' is treated as an entry and classified by its keywords (add, fix, remove, update, etc.).
Should I ship a changelog for every release? ⌄
Yes — even tiny ones. A visible changelog builds trust with users and journalists, and doubles as marketing copy.
Is this generator free? ⌄
Yes, unlimited, no signup, no AI.
Can I copy as Markdown or HTML? ⌄
Both. Markdown for GitHub/Notion, HTML for your marketing site or in-app changelog widget.
Where should I publish it? ⌄
A dedicated /changelog page on your site plus release notes on GitHub. Optional: an in-app widget that pings users on new versions.
Does the tool store my input? ⌄
No — everything happens in your browser. Your commits never leave the page.
Need the full engine?
WriterGPT turns any keyword into a fully-optimized, ready-to-publish article with outlines, images, internal links and one-click publishing.
Try WriterGPT free →