Free release notes template (plus examples + tips to stand out)

Copy our release notes template and see it filled in for different situations. Plus, find out how some studios turn their release notes into something people read for fun.

Writing release notes is one of those jobs that's easy to put off.

The work's out there, and everyone's moved on. But someone still has to explain what changed.

And the easy way to do that is with a template. We’ve made one you can copy, with a few filled-in examples underneath.

Keep scrolling, though, and you’ll find out how to make them even more useful. Your changelog can in fact become a marketing asset; something people actually look forward to.

The release notes template

Copy everything between the lines, paste it wherever you publish your notes, and fill in the brackets.

[Product name] [version number]: [the biggest change, in a few words]

[Release date]

[One or two sentences on the change your users will care about first.]

Action needed

  • [Anything users have to do: a config change, a migration, an upgrade you'd recommend for security reasons. Delete this section if there's nothing.]

New

  • [Something users can do now that they couldn't before.] [Link to docs or to the original request, if there is one.]
  • [Add one bullet for each change, as many as you need.]

Improved

  • [Something that works better, described the way users will notice it.]
  • [Another improvement.]

Fixed

  • [Something that was broken and now isn't, described the way users ran into it.]
  • [Another fix.]
  • [More fixes, and so on.]

[Optional: a thank-you to contributors, or a link to a bigger announcement.]

How to fill in the template

Each part of the template has one job:

  • The headline names the change, not just the number. "Version 2.4.0" tells readers nothing. "Version 2.4.0: dark mode is here" tells them whether to keep reading.
  • The summary is for skimmers. If someone reads one sentence, make it this one.
  • Action needed goes first. If users host or integrate your product, anything that needs action from them can't sit under the new features. That includes security fixes: if a release patches one, say so near the top so people know to upgrade.
  • New, Improved, and Fixed list every change. Add as many bullets as you shipped, but keep each one short. Write it as what the user can now do, or what stopped going wrong. Your team might understand "Refactored the export handler". But everyone else might only clock something like "Exports no longer time out on big files". If a change needs further explanation, link to the docs or a proper announcement blog post.
  • Link the request behind the change. If a feature came from your feedback board, link the original post. The people who asked for it will want to know it's arrived.

Delete any section that's empty. A "Fixed" heading with nothing under it looks a bit pointless.

And keep your plans out of it. Release notes describe what's shipped, so "coming soon" belongs on your roadmap.

One more small thing: the date. 11/02/2026 means November 2 in the US and 11 February in much of the world. If your users are spread around the globe, write the month out, or use the 2026-11-02 format (year, month, day), which is more versatile.

Release notes examples

Here's the template filled in for three different kinds of release.

1. A weekly roundup

If you ship small changes all the time, bundle them into a weekly or fortnightly roundup so each one has something to say.

This week's updates: repeating events and faster search

October 30, 2026

Two things people have asked for a lot: events that repeat, and search that keeps up with busy calendars.

New

  • You can now set an event to repeat every day, week, or month. (This was one of the most-voted requests on our feedback board.)

Improved

  • Search results load in under a second, even on calendars with thousands of events.

Fixed

  • Shared calendars no longer show events in the wrong time zone when you're traveling.

2. A self-hosted release with upgrade steps

This is Fider's v0.36.0 release from June 2026, trimmed down to fit the template. Our original notes put security first, too, because self-hosters need to know when to upgrade.

Fider v0.36.0: public roadmap view and security fixes

June 24, 2026

This release adds a public roadmap view and includes several security fixes, so we recommend upgrading.

Action needed

  • Upgrade recommended: this release includes security fixes.
  • Run the two new database migrations as usual (‘make migrate’).

New

  • A public roadmap view, so your users can see what you're working on. (On our hosted version, it's part of the Pro plan.)
  • Board owners on multi-site instances can schedule their board for deletion, with a grace period and a cancel link.

Improved

  • Comments can now be up to 4,000 characters long.
  • Tag management has a cleaner layout, with icons.

Fixed

  • Images placed at the start of a post now display properly.
  • Notification icons in the header no longer wrap onto a second line.

3. A one-line fix

Not every release needs every section. If you've shipped a single fix, the notes can be two lines long.

Version 3.2.1: CSV export fix

November 2, 2026

Fixed

  • CSV exports were stopping at 1,000 rows. They now include everything.

An exception: release notes for developers

If you build something that developers write code against, like a library, an API, or an open-source package, you'll probably come across a different convention.

Developer projects often keep a CHANGELOG.md file. It's a running record of every release, stored alongside the code itself. Many follow the keep a Changelog format, whose first principle is that changelogs are for humans, not machines.

It uses six headings: Added, Changed, Deprecated, Removed, Fixed, and Security. Two of those matter to developers in a way they rarely do to anyone else. "Deprecated" warns that a feature is on its way out, and "Removed" confirms it's gone, so anyone building on the project can update their code before it breaks.

If developers will be reading your changelog, use those headings. They line up closely with our template: Added is New, Changed is Improved, and our Action needed section covers Deprecated, Removed, and Security. If your readers aren't developers, stick with the template above.

Make your release notes part of your brand

The template above is a shortcut. It gets clear, useful notes out the door fast. For plenty of teams that's all they need.

But if updates are a big part of how you talk to your community, release notes can do a lot more. If they’re written with creativity (or even in character), they can become something people read for fun: a useful marketing and branding asset.

Ghost Ship Games' Season 06 notes for Deep Rock Galactic are written partly in character, as briefings from "Management" to the game's dwarf miners. The new Bone Collector enemy has a "distinct blue glow and scurrying movements (no, it's not Scout)," a dig at one of the game's own player classes. Further down, in a list of ordinary bug fixes, faster-opening doors on the Space Rig base get a one-word verdict: "(huge)."

Regular Studio went another way with its Motorslice demo. Its patch notes included a section titled "Embarrassing," owning up to an enemy attack the developer had switched off and forgotten to turn back on. GamesRadar covered that, too.

Notice what both have in common: the jokes sit alongside the information, not instead of it. You can still tell exactly what changed in every entry. That's the rule to keep if you try this yourself. Personality is a bonus, but readers came to find out what's different.

Both of these come from games, but the approach works elsewhere, too. If your brand already has a fun, personality-led voice, your release notes can carry it too, whatever kind of software or digital product you make. PostHog's changelog, which we looked at in our changelog guide, is a good example from the SaaS world.

Your next release

You don't need a perfect set of notes. You need a good set that goes out every time you ship.

So copy the template, delete the sections you don't need, and fill in the rest. Then, when a big release comes along, give yourself an extra half hour and have some fun with it.