How to Update Procreate 5 Beta
StyleFrame Team8 min read
If you're testing Procreate 5 through Apple's TestFlight app, open TestFlight on your iPad, find Procreate in your list of apps, and tap Update next to the newest build. You can also turn on automatic updates for that app inside TestFlight. The App Store won't update a beta build, and the original Procreate 5 public beta is closed, so what you can update today depends on which beta you actually have installed.
Which Procreate beta are you running?
"Procreate 5 beta" can mean two different things, and the update path differs between them.
The original Procreate 5 public beta. This ran in late 2019 through limited applications (roughly 10,000 seats, which filled quickly). Testers received an email with a TestFlight link and installed the beta as a separate app next to the release version. That program is long closed, so if you still see this build in TestFlight, updating means moving to the current App Store release of Procreate.
Later 5.x betas, such as the 5.4 beta. These ship through TestFlight too, but Procreate has said the 5.4 beta is not a side-by-side build. It installs over your App Store version because the team needed to test upgrading brush files to the iCloud brush format. That changes the risk profile completely, and it's why the backup section below matters before you tap anything.
To check which one you have, open TestFlight and look at the app name, version, and build number. If you can see two Procreate icons, you're running a side-by-side beta.
How to update a Procreate beta through TestFlight
- Open TestFlight, not the App Store. Beta builds are distributed and updated only through TestFlight. The App Store's Updates tab won't show them.
- Select Procreate from the list of apps you're testing.
- Read the "What to Test" notes. Testers' notes for a build may list known issues and what the team wants feedback on. Check them before updating, since a new build might change file formats or reset settings.
- Tap Update. If the button says Open instead, you're already on the newest build available to you.
- Wait for the install to finish, then launch Procreate and open a throwaway canvas to confirm brushes, palettes, and the Gallery behave normally before you open anything important.
Turn on automatic updates (optional)
In the Procreate page inside TestFlight, you can enable automatic updates. This is convenient, but I'd leave it off on a device you use for client work. Auto-updating means a new build with new bugs can arrive without you choosing the moment.
Know the expiry rule
TestFlight builds expire after a fixed window. If the beta stops opening, it has usually expired and you need to install a newer build or move back to the App Store release. Don't wait until an expired build blocks a deadline.
Back up before you update, especially for 5.4
For a beta that overwrites your App Store build, treat the update as a risky operation. Procreate has been explicit that these betas can contain serious bugs, including crash loops, and that it doesn't store your data and can't recover lost files. A sensible routine:
- Export your artwork. Back up your canvases as
.procreatefiles to the Files app, iCloud Drive, or an external drive. Procreate's own help documentation covers the backup steps. - Export brushes and palettes separately. Custom brushes and swatches are easy to forget, and brushes are what the 5.4 beta touches directly.
- Make a full iPad backup through iCloud or Finder (macOS) or iTunes (Windows).
- Turn off automatic iCloud backup on a primary device while the beta is installed (Settings > your Apple Account > iCloud > iCloud Backup > Back Up This iPad). Otherwise a fresh backup could overwrite your last good backup, the one that still contains the stable Procreate build.
- Use a secondary iPad if you have one. This is Procreate's own recommendation, and it's the only truly safe option if you rely on the app for production.
If your iPad is the device you use to produce animatic frames, concept boards, or texture art for a live job, don't put a beta on it. Early looks at new features aren't worth the risk, as the Procreate team itself says.
How to join a Procreate beta if you aren't in one yet
Procreate has typically run beta access through a signup process on its community forum (Folio), not through the App Store. The pattern from past rounds:
- Watch the Procreate beta announcement on the Folio forum and sign up for the notification.
- Apply when applications open. Spaces are limited and have filled very quickly in the past, and the opening time was published in a single time zone (Australian), which caught plenty of people out. Convert the time to your own zone in advance.
- If accepted, you'll get an email with a TestFlight invitation. Procreate has reportedly said the TestFlight code usually arrives within 24 hours.
- Install TestFlight on your iPad, redeem the invitation, and install the build.
Check the announcement for the specific beta you're after. Procreate's rules on whether the build installs alongside or over your existing app differ from one beta to the next.
Moving from the beta back to the App Store version
When a beta ends and the final release lands (for example, Procreate 5.4 appearing on the App Store), you'll want to get back onto the standard build. This is where a lot of users hit trouble.
A common failure mode: someone joins the beta with a secondary Apple Account signed into the App Store, then switches back to the main account that purchased Procreate and finds the App Store won't update the app. Removing Procreate from TestFlight on the secondary account didn't clear it in at least one reported case.
The fix reported in that thread was:
- Export everything (artwork, brushes, palettes) to Files.
- Delete the beta copy of Procreate from the iPad.
- Sign in with the Apple Account that purchased Procreate and download the app again from the App Store.
- Import your artwork, brushes, and palettes back in.
Only do this once your exports are confirmed and readable. Some users hesitate because they worry they'll have to repurchase the app. Redownloading with the purchasing account shouldn't require that, but verify you're signed into the right account first.
Troubleshooting common update problems
No Update button in TestFlight. You may already be on the latest build, or the tester group may not have been given the new one yet. Pull to refresh in TestFlight and recheck the build number.
The App Store offers an update but TestFlight doesn't (or vice versa). These are two separate channels. If the final release is out, the App Store version may carry a higher version number than your beta, but installing it can conflict with the TestFlight copy. Back up, then remove the beta and install from the App Store.
The beta crashes on launch after an update. Don't keep relaunching it. Back up whatever you can reach, check the Procreate forum for known issues with that build, and report the crash through TestFlight's feedback option. A crash loop can leave your data inaccessible, so stop and escalate before you delete anything.
The invitation link doesn't work. Open the link on the iPad while signed in with the Apple Account you used to apply, and make sure the TestFlight app is installed first.
Beta expired. Install a newer TestFlight build if one exists. If not, install the App Store release after backing up.
Keeping beta risk out of your production pipeline
Many motion designers and animators don't use Procreate as the center of their pipeline. It's where key art, storyboard frames, style explorations, and texture passes get made before they go into After Effects, Premiere Pro, Cinema 4D, Blender, or Nuke. That makes the update decision simple: the beta can be a sandbox for new brushes and tools, but whatever feeds a comp should come from a stable install.
A practical setup:
- Keep one stable iPad build for anything headed into a delivery. Flatten or export final art as PNG or layered PSD from there.
- Run betas on a spare device or skip them until the final release.
- Keep exports organized by version. If a beta build changes how a brush renders, you want to know which frames came from which build.
Where Styleframe fits
Procreate is good at making the frame. Turning a handful of frames into moving, consistent footage is a different job, and that's where can sit in the pipeline. In practice, you keep your compositing workflow and use Procreate for the art, so the beta-versus-stable question only affects the drawing stage and not the rest of the pipeline.
Quick checklist
- Confirm which beta you're on (TestFlight app name, version, and build number).
- Back up artwork, brushes, and palettes, and make a full device backup.
- Turn off automatic iCloud backup if the beta overwrites your App Store build.
- Update from TestFlight, not the App Store.
- Test on a scratch canvas before opening real projects.
- When the beta ends, export, delete, and reinstall from the App Store with the purchasing Apple Account.
Updating a Procreate beta takes a minute. Recovering from a bad build when you skipped the backup can take much longer, so do the preparation first and the update second.