Free tool · Last reviewed
App release notes generator
Pick a release type, paste a few changes, choose a tone — get a polished "What's New" draft for App Store and Google Play in seconds. Better than "Bug fixes and performance improvements" — and done in 30 seconds.
Pure client-side template engine. No LLM, no signup, no upload.
Generator
Tone
Release type
Draft release notes181 chars
Small but useful additions in this release. • improvement 1 • improvement 2 • A few quality-of-life tweaks based on your feedback Hope it makes the app feel a little nicer to use.
Apple App Store accepts up to 4,000 characters. The first ~170 chars are what users see on the listing card before tapping in.
Best practices
Release notes that actually drive updates
Lead with the user benefit, not the change. "Faster sync, calmer dashboard" beats "Updated CoreData migration and refactored sync queue." The first is human; the second is a commit message. Save the technical version for your changelog page.
Avoid "bug fixes and performance improvements." Apple's own data shows specific notes lift update adoption by 30-50% over the generic default. Even a single specific bullet — "Fixed the sync issue some of you flagged" — beats vague boilerplate.
Use the first 170 characters wisely. That's the truncation point on the listing card. Lead line + first bullet should land within that budget. Anything past it requires the user to tap "more."
Don't include version numbers in the body. Apple shows the version above the release notes automatically. "Version 2.4 introduces…" wastes characters. Lead with what changed, not what version is shipping.
End with an invitation, not a sign-off. "Reply at hello@ if anything else feels off" or "Tell us what to build next" creates a feedback loop. "Thanks for your continued support" is forgettable. Indie apps benefit most from this — every email becomes a product conversation.
FAQ
Quick answers
- How long should App Store release notes be?
- Apple App Store accepts up to 4,000 characters in 'What's New' but the truncation point on the listing card is around 170 characters. Aim for 80-200 characters in the lead — that's the part most users actually read. Longer changelogs go below.
- Should release notes be marketing copy or a changelog?
- Both. Lead with one human sentence about the user benefit ('Faster sync, calmer dashboard') then list the specific changes as bullets. Pure changelogs feel impersonal; pure marketing copy feels evasive. The blend is what users trust.
- Do I have to update release notes every version?
- Yes — Apple requires updated release notes for every binary submission, even if the change is internal. 'Bug fixes and performance improvements' is the legal-minimum default, but it doesn't help retention; users skip the update prompt. Specific notes lift update adoption by 30-50% in our testing.
- Can I include emojis in release notes?
- Yes, both Apple App Store and Google Play accept emojis. Use them sparingly — 1-2 in the lead line, occasional accents in bullets. Lifestyle/consumer apps benefit most; productivity/finance apps usually do better with clean text.
- Should I mention the new version number?
- No. Apple shows the version number above the release notes automatically. Including 'Version 2.4 brings…' in the body wastes characters. Lead with what changed, not what version is shipping.
- Does this generator save my notes anywhere?
- No. The whole template engine runs locally in your browser. Your inputs (release type, change keywords, app name) never leave the page — refresh the tab and they're gone.
Ship the release with screenshots that match
Ryplix Studio creates App Store-ready iPhone and iPad screenshot sets from raw app screens, with AI-written headlines tuned for App Store search. Free to start — 5 credits on signup, no card.
More free tools: character counter, listing preview, rejection checker.