Release Notes Template: Six to Copy, With Real Examples
Shayan, Founder15 min read

A release notes template is a repeatable outline for announcing software updates so your team doesn't start from a blank page every time code ships. A good template gives you a consistent place for what changed, how the product worked before, who is affected, and what the reader needs to do next.
Where teams usually get stuck is trying to force every release into one giant template. When you use a heavy major-launch document for a two-line bug fix or a renamed sidebar tab, half the headings sit empty, and someone ends up typing filler like "No new features introduced in this release" just to satisfy the form. And when a blank template isn't paired with a real example written in the same shape, those bracketed placeholders like [Feature name] and [Primary benefit] nudge writers into sounding like a press release instead of telling customers what actually changed on screen.
Different releases need different shapes. Below are six plain-text templates covering the updates software teams actually ship: a standalone feature release, a weekly agile round-up, a bug fix or hotfix, a breaking API change, a UI rename, and an App Store or Google Play update. Under each blank template is a real release note from Linear, Raycast, 1Password, Apple, Stripe, Supabase, or Bear that follows that exact structure.
You can copy any template straight from this page, or download all six in one Markdown file to paste into GitHub, Notion, Confluence, Google Docs, or Word. If you want to dig deeper into who reads product updates and how to edit rough drafts, check out our guide to writing release notes.
What goes into a release notes template
When someone sets up an internal release template in Confluence or Notion, they often build a deployment checklist by mistake. They add fields for QA sign-off, sprint numbers, database migration steps, and internal Jira ticket codes. Then that document gets copied onto the public updates page, leaving customers staring at strings like #AUTH-3584 and !41895 that mean nothing outside the engineering team.
A customer-facing release note only needs seven building blocks, and no single update needs all seven at once:
- Title. Name the biggest change in the words a customer would use, not the release number or the month.
- Date and version. Put a calendar date on every post. Add a version number if your users install builds, pin SDK versions, or check an
Aboutdialog. - Summary. One sentence at the top, used only when the entry bundles several changes together.
- What's new. One short paragraph per feature explaining what the user can do now and what it was like before.
- Improved and Fixed. One line per item naming the part of the product that changed and the symptom it resolved.
- Breaking changes and action required. Labelled right at the top whenever an update requires a user or developer to change a setting, update an SDK, or reinstall an app.
- Links to docs and the original request. Point to the help article for setup steps and link the customer feature request that prompted the work.
Each template below keeps only the fields that kind of update needs and drops the rest.
1. Feature release template
Use this template when you're shipping a standalone capability that changes how people work and deserves its own headline entry. The trap on a big launch is opening with marketing fanfare like "We're thrilled to introduce our new inbox!" and spending two paragraphs praising the feature without ever explaining what was annoying before.
# [What you can do now, in the words a user would use]
[Date]
[What you can do now, in one or two sentences.] Previously, [what it was like before].
[One concrete case where this matters.]
Available on [plans or platforms]. [How to turn it on or where to find it.]
Built from this request: [link to the feedback request, if one exists]
[Link to the docs]Look at how Linear announced its Priority inbox on September 3, 2026:
An active workspace can create a significant amount of notifications each day, and until now your inbox treated them all the same. The new Priority tab separates what needs your attention from what can wait, so something like a review blocking a release never gets buried.
Linear puts the "previously" sentence first, naming the noisy inbox that every busy team recognizes. The second sentence states what the new tab does, and the clause after "so" gives one specific situation, a review blocking a release, instead of an abstract claim about saving time. Underneath that opening write-up, the same Linear post lists 26 smaller improvements and 16 bug fixes as one-liners, stacking the round-up template below right under the feature announcement.
Notice the request link at the bottom of the template. Almost every template leaves out the customer request that sparked the feature, even though that link is the easiest way to close the feedback loop. If the feature came from a thread on your feedback board, link it there. The people who voted on that request are the readers most likely to care, and their original post already describes the "previously" problem in their own words.
2. Weekly round-up or agile release notes template
When your team ships continuously and publishes updates on a weekly or sprint schedule, writing a standalone post for every tweak isn't practical. This grouped list is what teams usually mean by an agile release notes template, with one dated entry per week or sprint sorted by the type of change.
# [Product] updates, [date or week]
[One sentence on the biggest change this period, if there is one.]
## New
- [What you can do now, one line each]
## Improved
- [Area]: [what is better, one line each]
## Fixed
- [Area]: Fixed [the symptom, as the user saw it]Raycast publishes one of these every week with New, Improvements, and Fixes as the three section headings. Their v2.10 release on October 28, 2026 opened with:
In this week's release, we've made a bunch of updates to Raycast Notes, some of which have been highly requested!
Further down the page, its Fixes section included these three lines:
AI Chat: Fixed a text scaling issue in "Ask Question" tool
AI Chat: Fixed run errors rendering above tool calls in some situations
AI Chat: Fixed failed image generations and remote tools appearing as completed
The bullet list is easy to skim because every line starts with the product area, AI Chat:, followed by the exact symptom the user saw. A reader who never opens AI Chat can skip those lines at a glance, while someone whose failed image generations kept showing up as completed knows immediately that the bug is gone. The opening sentence is the one habit to avoid when you copy this format. Saying "we've made a bunch of updates, some of which have been highly requested" tells the reader nothing that the list below doesn't say better. Use that opening sentence to name the biggest change directly, or skip the intro line altogether and go straight into New.
If you keep a CHANGELOG.md file inside a Git repository rather than a public web page for customers, swap New, Improved, and Fixed for Keep a Changelog's six standard headings: Added, Changed, Deprecated, Removed, Fixed, and Security, with an Unreleased section at the top and YYYY-MM-DD dates.
3. Bug fix release notes template
When a patch or hotfix only repairs broken behavior, you don't need a feature summary or a theme title. The rule for a bug-fix release note is that every line should describe the symptom the user experienced, not what the engineer did to the code.
GitLab's engineering changelog guide shows the difference clearly. Their example of a bad entry is "Strip out nils in the Array of Commit objects returned from find_commits_by_message_with_elastic". Their good version of the exact same fix is "Fix 500 errors caused by Elasticsearch results referencing garbage-collected commits", because a customer who ran into a 500 error will recognize the symptom, while nobody outside the codebase knows what find_commits_by_message_with_elastic is.
# [Version], [date]
Fixed: [what was broken, as the user saw it, with the screen or feature named].
[Who was affected, if not everyone.]
[What to do, or "No action is needed."]Here is how 1Password for Mac wrote its version 8.12.33 release note on August 12, 2026:
We've fixed an issue where the 1Password browser extension in Safari couldn't connect to the 1Password app.
It names the exact part of the product, the Safari browser extension, and the failure the user saw, without any internal jargon. On 1Password's site, the sentence ends with an internal merge request badge, !40819, which we left off here because customers can't click into a private code repository anyway.
When a bug only hits specific devices or a particular workflow, put both in the sentence so everyone else knows they aren't affected. Apple's iOS 27.0.1 release note does this in one line:
This update provides bug fixes for your iPhone, including fixes for the following issues: iPhone 18 Pro and iPhone 18 Pro Max may unexpectedly restart when Face ID fails to authenticate
Anyone whose iPhone 18 Pro rebooted during Face ID knows right away that this update is for them. Compare that to pasting "Bug fixes and performance improvements", which tells a frustrated user nothing about whether they can stop using their workaround.
The same three-line template covers security patches, where the final line telling the user what to do matters most. When Obsidian shipped desktop version 1.14.5 on October 22, 2026, the entire release note was two sentences:
This release updates Electron from 43.7.5 to 43.8.3, which includes several important security fixes. Download Obsidian from our website and reinstall the app.
4. Breaking change and API release notes template
For developer-facing updates like a new API version, an SDK upgrade, a changed webhook payload, or a deprecated flag, the reader is an engineer checking whether upgrading will break production. The trap in a developer release note is mixing breaking changes into a long, unlabelled list of minor patches. As one developer complained on Hacker News:
For those saying "just use commit history", I once had to sift through 200 commits because the library author was too lazy to separate the breaking changes from the patches.
# [Version or API date], [what changed]
**What's new.** [What the change does.] Previously, [what it replaced].
**Breaking:** [yes or no]. [Who is affected: which endpoint, field, SDK or setting.]
**What to do.**
1. [Upgrade step]
2. [Upgrade step]
[Rollback window or how to pin the old behaviour, if there is one.]
[Deprecation date, if the old behaviour is going away.]
[Link to the migration guide or API reference.]Stripe's API changelog follows this exact structure. In Stripe's 2026-09-30.endive release, the entry making subscription trial offers generally available opens its What's new section with:
Adds Trial Offers for subscriptions, which define reusable free or paid introductory pricing for individual Subscription Items, each with their own price and billing period. Previously, a subscription used a single trial period for the entire subscription.
Never skip that "Previously..." sentence on an API or configuration change. A developer deciding whether to upgrade needs the old behavior named right next to the new one so they can tell in five seconds if their integration touches it. Below that paragraph, Stripe labels the change Breaking or Non-breaking, lists the added and modified fields for each SDK, gives numbered upgrade steps, and notes in the upgrade instructions that "You can roll back the version for 72 hours."
If a major release includes a long list of breaking changes, don't turn the release note itself into a ten-page migration manual. Put the step-by-step upgrade instructions in a dedicated document and link to it from the note. As another engineer on Hacker News put it, "+1 on separating 'how to upgrade' due to breaking changes from 'what's new'. A dedicated BREAKING.md / MIGRATIONS.md is a really good idea." That keeps the release note readable for everyone else while giving developers upgrading their code a single checklist to follow.
5. Rename, move, or settings change template
Menu moves, renamed settings, and changed defaults are the updates teams most often forget to announce. Internally, renaming a tab in the sidebar feels like a minor cleanup. To a customer following an older help article or clicking a saved bookmark five minutes before a meeting, it looks like the feature disappeared.
# [Old name] is now [new name]
[Date]
[Old location] is now [new location]. [Old links or paths] still work. [What has not changed.]Look at how Supabase handled a dashboard rename on September 21, 2026:
Database > Replication is now Database > Pipelines. Existing Replication URLs redirect to the new location. No API or pipeline behavior has changed.
Those three sentences answer the three questions that immediately cross a user's mind when a menu item moves: what is it called now, will my old bookmarks break, and did anything change underneath? Stating what hasn't changed is just as reassuring as stating what did.
6. App Store and Google Play release notes template
If you ship a mobile app, every update requires filling out the "What's New" box in App Store Connect and Google Play Console. Because the field is required on every build after version 1.0, even massive consumer apps fall into pasting the same empty sentence for months at a time.
On the US App Store in late October 2026, Spotify's version 9.1.94 note read:
We're always making changes and improvements to Spotify. To make sure you don't miss a thing, just keep your Updates turned on.
Spotify used that identical text across five consecutive releases. Instagram's version 453.0 note from October 26, 2026 was "Performance optimizations and stability improvements for a smoother, more reliable experience." Duolingo's version 7.146.1 note from October 28, 2026 swapped the boilerplate for a mascot joke repeated across three releases: "Our mascot owl, Duo, is trading in his usual diet of mice for bugs this week. Yup, we're squashing those pesky bugs to make the experience better for all of you." None of the three tells a user a single thing that changed in the app.
If you want one mobile release note that actually informs users and passes both stores without rewriting, you have to work around two different sets of platform rules. Apple's What's New in this Version field allows up to 4,000 characters, is hidden on an app's first version, and is required on every version after that. Apple's App Store Review Guideline 2.3.12 allows "Simple bug fixes, security updates, and performance improvements" to use a generic description, but adds that "more significant changes must be listed in the notes." Google Play's field is much shorter, capped at 500 Unicode characters per language between language tags like <en-US>, and Google's Play Console documentation states:
Inform users about recent updates made in your release. Do not use release notes for promotional purposes or to solicit user actions.
So while Apple's product page guide encourages call-to-action messaging, Google forbids prompts to rate the app, upgrade a plan, or share with friends. Keeping your text under 500 characters, putting the real change on the first line, and skipping promotional asks satisfies both stores at once.
<en-US>
New: [the one change that matters, with the screen or feature named].
[Second change, if there is one.]
Bug fixes and stability improvements.
</en-US>Here is how the Markdown notes app Bear used that exact shape for version 3.0.3 on October 22, 2026:
New: A new toolbar now appears when you're entering tags or wikilinks, or searching for notes. It makes it easier to move the cursor and type special characters.
Bug fixes and stability improvements.
Bear's note comes in at 199 characters. It names the new toolbar and the exact moments it appears on screen, then uses the generic line for the minor fixes underneath, just as Apple's guideline permits.
Instead of writing your store note from scratch, trim it down from your web release note. Even Linear, whose web changelog entry for Priority inbox runs over a thousand words with 42 itemized improvements and fixes, put "Bug fixes and minor improvements" on four straight versions of its iOS app. If you already wrote a clear opening sentence for your web changelog, paste those two lines straight into App Store Connect and Play Console.
How to write release notes with these templates
Having the right template solves the blank-page problem, but the note still depends on what you feed into it. When someone sits down on Friday afternoon to fill out the template, the temptation is to open git log and copy the commit messages. As one developer on Hacker News described the end-of-sprint scramble:
the context of the fix lives in a dozen different places: the ticket, the code, the commit message. And now I need to document it a fourth time?
Instead of starting from the commit log, start from the customer requests and bug reports you marked completed during the cycle. Commit messages are written for other engineers working in the repository; release notes are written for the person using the software.
Write each change as the plain sentence a user would say to a coworker sitting next to them. Lead with "You can now..." or "Fixed:...", and add "Previously,..." whenever naming the old limit or behavior makes the improvement clearer. Make sure every line includes a concrete noun from your product, whether that's a screen name, a setting, an API endpoint, or a device model. If a sentence could appear unchanged in another company's release notes, it isn't saying anything specific enough to keep.
Finally, always state whether the reader needs to take action, even when the answer is "No action is needed" or "Existing links redirect automatically." Answering that question in the note saves your support team from answering it ten times in the inbox. For more side-by-side examples of editing rough engineering notes into clean copy, see our guide on writing changelogs people read.
Fill the template from the requests you shipped.
In UserJot's changelog editor, Juno drafts your release note from the customer requests you marked Completed and links those requests right under the post. Free to start, with unlimited users.
Where the template fits in your feedback loop
Notice that the feature template above includes a line for the customer request the update answers. When your feedback board, public roadmap, and changelog tool are connected, every request you complete during the week is already a release note half written. The title is what the customer asked for, the "previously" sentence is sitting in their original post, and the people who voted on it are the readers waiting to hear that it shipped.
In UserJot, marking a request Completed automatically sends an email to everyone who posted, voted, or commented on it. When you open the changelog editor to publish your release notes, our editor assistant Juno reads the requests you completed since your last post along with their comments, and drafts the entry with the title, date, tags, and linked requests in place. You review and edit her draft before publishing, as she never publishes on her own, and the finished post goes live on your /updates page and inside your app through the in-app widget on every plan, including Free.
Frequently asked questions
How do I use these release notes templates in Word, Google Docs, or Notion?
You can download all six templates in one Markdown file and open it in any text editor. In GitHub, Notion, or Confluence, paste the Markdown directly and the headings and bullet lists will format themselves automatically. In Microsoft Word or Google Docs, paste the plain text and apply Heading 1 and Heading 2 styles by hand; because the templates don't rely on complex tables or merge fields, nothing breaks when you paste.
What is the standard format for software release notes?
There is no formal specification for product release notes, but the standard convention puts a title naming the biggest change at the top, followed by the date, one short paragraph per new feature stating the old and new behavior, one-line bullets for improvements and fixes, any breaking changes or required actions called out clearly, and links to the documentation. For a technical CHANGELOG.md file inside a Git repository, Keep a Changelog's six headings, Added, Changed, Deprecated, Removed, Fixed, and Security, with YYYY-MM-DD dates are the standard format.
What is a good example of bug fix release notes?
1Password's Mac 8.12.33 note is a clean model: "We've fixed an issue where the 1Password browser extension in Safari couldn't connect to the 1Password app." It names the component and the exact symptom the user experienced in one plain sentence. Apple's iOS 27.0.1 note does the same for hardware bugs by naming the affected iPhone models, the unexpected restart symptom, and the Face ID trigger so users who hit that crash know immediately that the update fixes it.
Should I write separate release notes for technical and non-technical users?
Write one main release note focused on what changed for the person using the product. Maintaining two separate sets of release notes for every update doubles the writing burden and usually causes one of them to fall behind. When a release includes breaking API changes or multi-step server upgrades for developers, put the technical migration commands in a separate migration guide and link to it from the main release note.
How long should release notes be?
Make them as long as the list of user-visible changes in the release, and no longer. A menu rename takes three sentences, a standalone feature takes one short paragraph, and a weekly round-up takes as many one-line bullets as you shipped that week. For the Apple App Store and Google Play, keep your text under 500 characters so the same release note fits both stores without getting truncated on Android.
Can I generate release notes automatically from Git commits?
Tools like GitHub's "Generate release notes" button, release-please, and git-cliff can assemble a rough draft from pull request titles or Conventional Commits, which is useful as a starting checklist for open-source libraries. However, commit messages describe internal code steps for other engineers rather than workflow changes for customers. Even when you use a script or an assistant to gather what shipped, a human still needs to cut the internal refactors and rewrite the remaining items from the user's point of view.



