Blog

Release notes template (copy and paste, with examples)

A release notes template is a fixed outline you fill in for every release, so each one tells users what is new in the same place and the same order. The outline below has five parts: a headline sentence, then New, Improved, Fixed and a Heads up note. Copy it, fill in the brackets, and delete any group that has nothing in it.

Release notes are written for the people who use your product. They are not the same as a changelog, which is the complete dated record for developers; the comparison of changelog and release notes explains the difference. If you need that file, start from the Keep a Changelog template.

The release notes template

## What's new in [Product] [version] ([date])

[One sentence on the most important change, written as a benefit.]

New
- [A thing users can now do.]

Improved
- [Something that got faster, clearer or easier.]

Fixed
- [A problem users had, described by what they saw.]

Heads up
- [Anything that changes how existing users work, and what to do.]

There are also ready-made CHANGELOG.md and release notes templates for libraries, APIs, web apps and mobile apps in the changelog templates repository.

The same template, filled in

## What's new in Acme 4.2 (November 19, 2026)

Offline mode is here. Open your last 20 documents without a connection, then sync when you are back online.

New
- Offline mode for your recent documents.
- Unlock the app with Face ID or your fingerprint.

Improved
- The home screen shows your recent items first.

Fixed
- The app no longer closes when you rotate the phone during an upload.

Heads up
- Support for Android 8 ends with this release. Update your phone to keep receiving new versions.
feat: add pdf export (#142)Changelog · developers## 1.2.0 - 2026-10-12### Added- Report PDF exporter (#142)Complete, dated, terseRelease notes · usersAcme App 1.2You can now save any reportas a PDF from the toolbar.Curated, friendly, explains
One change, two audiences, two voices.

Notice what the example leaves out: no pull request numbers, no function names, no refactors. Those belong in the developer changelog. The user version keeps only what a customer can notice.

How to fill in each part

  • The headline sentence. Lead with the change most users will care about, in terms of what they can do. "Offline mode is here" says more than "Added a local cache layer".
  • New. Features and options that did not exist before. One line each, starting with the user, not the code.
  • Improved. Existing things that got faster, clearer or easier. Say what is better, and avoid claims you cannot back up.
  • Fixed. Describe the problem as the user saw it. "The app closed when you rotated the phone" is clearer than a ticket title.
  • Heads up. Anything that changes how existing users work, such as a removed feature, a moved setting or a version that is no longer supported. Say what to do about it.

When to skip a release note

Not every release needs one. A release that only bumps dependencies, refactors code or fixes a typo changes nothing a user can see, and a note for it teaches people to ignore your notes. Keep the commit in your changelog if you maintain one, and save the release notes for releases that matter.

Where to publish release notes

  • A public page on your site, so customers can find the history of the product.
  • A What's new notice inside the product, shown once per release.
  • A release page on GitHub, if your users are developers.
  • Email or an in-app message for the changes that really need attention.

The guide to public changelog pages and the guide to What's new widgets cover the first two.

Writing them faster

The slow part is turning a list of commits into these five parts. ReleaseTale reads the commits and pull requests of a release and drafts the user version as a headline with New, Improved and Fixed items, together with the developer version, and you edit before you publish. See a sample on the changelog examples page, or use the free changelog generator to sort commits by type in your browser.

Frequently asked questions

What should release notes include?

A headline sentence about the most important change, then short groups such as New, Improved and Fixed, and a Heads up note for anything that changes how existing users work. Leave out internal work that users cannot see.

How long should release notes be?

As short as possible while still telling users what changed. Most releases need a headline and a handful of lines. If a release has no change a user can notice, it may not need release notes at all.

Do I need release notes for every release?

No. A release that only updates dependencies, refactors code or fixes a typo changes nothing users can see, so it can go in the changelog without release notes. Save release notes for releases that matter to users.

Related articles