Free Tools
TestFlight "What to Test" Notes Formatter
Write clear beta release notes that fit TestFlight's 4,000-character "What to Test" field. Start from a template, track your character count live, and copy the result straight into App Store Connect. Runs entirely in your browser.
Character count
0
/ 4,000
4,000 characters remaining
0
Words
0
Lines
Tips for good beta notes
- Lead with what changed since the last build, not a generic greeting.
- Tell testers the exact screens or flows to exercise.
- Call out anything that needs a specific device, account, or setup.
- List known issues so testers don't re-report them.
The "What to Test" field
Every TestFlight build can ship with "What to Test" notes — the text your beta testers see in the TestFlight app before they install. App Store Connect caps this field at 4,000 characters. Vague notes ("bug fixes and improvements") waste the slot; specific, scannable notes get you better feedback on exactly the flows you changed. This formatter counts your characters as you type so you never paste something that gets truncated.
What a good template covers
- What's new — the changes shipped in this build.
- What to test — the specific flows you want feedback on.
- Known issues — things already on your radar.
- How to report — where and how testers should send feedback.
Heading to the App Store next?
AcceptMyApp analyzes your metadata, permissions, and privacy setup against Apple's guidelines and surfaces rejection risks before you hit submit.