A changelog generator creates properly formatted CHANGELOG.md files following the Keep-a-Changelog convention. Organize your releases by version with categorized entries — Added, Changed, Fixed, Removed — in the standard format that developers and open source contributors expect.
Project Settings
Used for version compare links
Versions
CHANGELOG.md Preview
Keep-a-ChangelogHow to Use the Changelog Generator
The changelog generator creates CHANGELOG.md files in the widely-adopted Keep-a-Changelog format. Every version gets a dated section with categorized changes that developers, contributors, and users can scan at a glance.
Step 1: Configure Project Settings
Enter your project name — it appears in the changelog header. If you provide a repository URL (e.g., https://github.com/user/repo), the generator automatically creates version compare links so readers can see the exact code diff between releases.
Step 2: Add Versions
Click Add Version to create a release section. Enter the version number in Semantic Versioning format: MAJOR.MINOR.PATCH. Increment PATCH for bug fixes, MINOR for new features, and MAJOR for breaking changes. Set the release date to today or the actual release date.
Step 3: Add Changelog Entries
Each version supports six entry types following Keep-a-Changelog conventions: Added for new features, Changed for updates to existing functionality, Deprecated for features being phased out, Removed for deleted features, Fixed for bug fixes, and Security for vulnerability patches. Add multiple entries per type by clicking the type button multiple times.
Step 4: Use the Unreleased Section
The Unreleased section at the top of your changelog tracks work in progress — changes that are merged but not yet released. When you cut a new release, move entries from Unreleased into a new versioned section. This keeps reviewers informed about what's coming next.
Step 5: Download and Commit
Click Download CHANGELOG.md to save the file, then commit it to the root of your repository. Or copy the Markdown and paste it into an existing changelog. The generated output follows the Keep-a-Changelog specification exactly.
FAQ
Is the changelog generator free?
Yes, completely free with no limits or signup required. Generate and download as many CHANGELOG.md files as you need. All processing happens in your browser.
Is my project data safe?
Absolutely. Everything runs locally in your browser using client-side JavaScript. Your version numbers, release notes, and project details are never sent to any server.
What is the Keep-a-Changelog format?
Keep-a-Changelog (keepachangelog.com) is a widely adopted convention for writing CHANGELOG.md files. Each version gets its own section with a date and categorized entries: Added, Changed, Deprecated, Removed, Fixed, and Security. Versions follow Semantic Versioning.
What are the changelog entry types?
Keep-a-Changelog defines six change types: Added (new features), Changed (changes to existing functionality), Deprecated (soon-to-be removed features), Removed (removed features), Fixed (bug fixes), and Security (security vulnerability fixes).
What is an Unreleased section?
The Unreleased section at the top of a changelog tracks changes that have been merged but not yet released in a version. When you cut a release, you move those entries into a new versioned section. This generator includes an Unreleased section by default.
How does Semantic Versioning work with changelogs?
Semantic Versioning uses MAJOR.MINOR.PATCH format. Increment PATCH for backward-compatible bug fixes, MINOR for new backward-compatible features, and MAJOR for breaking changes. Link your versions to compare URLs (e.g., GitHub compare links) so readers can see the exact diff for each release.
Can I add multiple versions to one changelog?
Yes. Click 'Add Version' to add as many versioned sections as you need. You can reorder them and the generator outputs them newest-first, which is the Keep-a-Changelog convention.