Paste your raw list of changes and get a clean, formatted changelog entry — three styles, Keep a Changelog convention. No signup, no cost.
What makes a changelog good?
A good changelog tells users what changed in language they care about — not commit hashes or internal refactors. Group entries under Added, Changed, Fixed, and Removed. Lead each line with what the user can now do or what stopped breaking.
Keep a Changelog vs. release notes — what's the difference?
A changelog is the cumulative, reverse-chronological record inside your repo (CHANGELOG.md). Release notes are what you post on GitHub Releases, your blog, or email for a single version. Good release notes are usually a trimmed, friendlier version of the changelog entry.
Should I write entries for internal refactors?
Only if they affect users — performance, behavior, or compatibility. "Refactored auth module" means nothing to a reader. "Login is 2x faster" does. Translate engineering work into user-facing impact.
How do version numbers work?
Semantic versioning: MAJOR.MINOR.PATCH. Bump PATCH for fixes (1.4.0 → 1.4.1), MINOR for new backwards-compatible features (1.4.1 → 1.5.0), and MAJOR for breaking changes (1.5.0 → 2.0.0).
Is this tool free?
Yes — no signup, no account, no cost. The generated text is yours to use in any project.
Free developer tools. No tracking, no signup.