Free changelog tool

Free Changelog Template Generator

A changelog template is a structured record of product changes grouped by release so customers and teammates can quickly understand what shipped. This free changelog generator turns release notes into Keep a Changelog-compliant Markdown or HTML in seconds.

Generate changelogOpen release notes tool

Need a public place to publish updates after each release? FeatureVote helps product teams collect feature requests, prioritize the roadmap, and share what shipped with customers.

Step 1

Set the release version

Enter a semantic version like 1.4.0 or v2.0.0-beta.1, then add an optional release date for the changelog heading.

Step 2

Add updates by category

Paste one release note per line under Added, Changed, Fixed, Deprecated, Removed, or Security.

Step 3

Copy or download the result

Switch between Markdown and HTML output, copy either format instantly, or download the Markdown file for docs or GitHub Releases.

Changelog builder

Build release notes from one form

Enter a version, optional date, and release items for each Keep a Changelog category.

Added

0 items

New features, integrations, or capabilities.

One release note per line.

Changed

0 items

Updates to workflows, UX, or product behavior.

One release note per line.

Fixed

0 items

Bug fixes and stability improvements.

One release note per line.

Deprecated

0 items

Features or endpoints scheduled for removal.

One release note per line.

Removed

0 items

Capabilities or APIs removed from the product.

One release note per line.

Security

0 items

Security fixes, patches, or policy updates.

One release note per line.

Live output

Preview and export

Toggle the output format, review the result, then copy or download it.

Release items

0

Active sections

6

Semver check

Ready

Add release notes by category to generate a polished changelog.

Markdown preview

Keep a Changelog sections are omitted only after you add real content.

406 characters
## [Unreleased]

### Added

- Describe newly shipped features or capabilities.

### Changed

- Describe behavior changes, redesigns, or improvements.

### Fixed

- Describe the issues or defects you resolved.

### Deprecated

- Call out anything users should stop relying on.

### Removed

- List any removed features, pages, or API behavior.

### Security

- Summarize security fixes or hardening changes.

Changelog writing tips

Write each bullet from the customer's perspective, not the implementation team's perspective.

Put breaking or risky updates into Deprecated or Removed sections early so customers can prepare before an upgrade.

Keep one release note per line in the form for cleaner Markdown, HTML, and GitHub release exports.

How to create a product changelog

  1. 1

    Set the release version

    Enter a semantic version like 1.4.0 or v2.0.0-beta.1, then add an optional release date for the changelog heading.

  2. 2

    Add updates by category

    Paste one release note per line under Added, Changed, Fixed, Deprecated, Removed, or Security.

  3. 3

    Copy or download the result

    Switch between Markdown and HTML output, copy either format instantly, or download the Markdown file for docs or GitHub Releases.

Related product and release tools

Pair this changelog generator with other free tools on FeatureVote when you need roadmap planning or fuller release-note formatting.

Release Notes Generator

Build fuller release notes with extra sections and publishing-friendly formatting.

Roadmap Template Generator

Turn upcoming features into a visual roadmap after you document what already shipped.

Subtle product link

When you want changelog entries tied to actual customer demand, use FeatureVote to collect requests, validate roadmap ideas, and close the feedback loop after you ship.

Visit the main FeatureVote product

Changelog generator FAQ

Common questions about changelog templates, release notes formatting, and semantic versioning.

What is a changelog template?

A changelog template is a repeatable structure for documenting what changed in each release. It helps product teams keep release notes clear, consistent, and easy for customers to scan.

What is Keep a Changelog?

Keep a Changelog is a widely used changelog format that groups updates into standard sections such as Added, Changed, Fixed, Deprecated, Removed, and Security. It gives teams a clean, predictable release-note structure.

Should changelog versions follow semantic versioning?

Yes. Semantic versioning makes release history easier to understand because the version number signals whether a release contains a patch, new functionality, or breaking changes.

What should product release notes include?

Good product release notes highlight what shipped, what changed, what was fixed, and anything customers need to know before upgrading. They should focus on customer impact rather than internal implementation details.

Can I use this changelog generator for GitHub releases or docs?

Yes. The Markdown output is useful for GitHub Releases, documentation, or internal release summaries, while the HTML output works well for changelog pages, emails, or CMS editors.

Publish better updates, then learn what customers want next

Generate a polished changelog here, then use FeatureVote to capture feature requests, prioritize feedback, and communicate what ships across your roadmap.

Explore FeatureVoteBack to all free tools