5 release notes templates you can copy and use today

A good template removes the blank-page problem and keeps your updates consistent. Below are five release notes templates you can copy and adapt for different kinds of products. Each one is built around the same principle: lead with the value to the reader.

1. The standard SaaS template

## [Release name or version] — [date]

**The short version:** [one-sentence summary of the release].

### New
- [Feature]: [what it lets the customer do].

### Improved
- [Area]: [what got better and why it matters].

### Fixed
- [What was broken]: [now resolved].

2. The single-feature announcement

Best when one feature is the whole story:

# [Feature name] is here

[One paragraph on the problem it solves.]

**How to use it:** [one or two steps].
**Available on:** [plans or platforms].

3. The mobile app store template

Short, friendly, and scannable for app store listings:

What's new in [version]:
- [Headline improvement].
- [Second improvement].
- Bug fixes and performance improvements.

4. The API or developer changelog

For technical audiences who need precision:

## [version] — [date]

### Added
- `[endpoint or field]`: [description].

### Changed
- `[endpoint]`: [what changed and migration notes].

### Deprecated
- `[feature]`: [removal timeline].

5. The email digest template

For pulling users back into the product:

Subject: New this month in [product]

Hi [name],

Here's what we shipped this month:

- **[Feature]** — [benefit].
- **[Improvement]** — [benefit].

[Call to action: try it now.]

Make the template fill itself

Templates solve the structure problem, but you still have to fill them in every release. Changelog Generator drafts the content from your merged pull requests so the template is filled in for you — you just review and publish.