PocketHost runs the latest patch of each PocketBase minor release from 0.23 on (for example 0.41.*), and you can change your instance’s version to stay current. When changing PocketBase versions, whether upgrading or downgrading, it’s important to take precautions to ensure the stability of your instance and the integrity of your data.
PocketBase 0.22 and older can’t be picked for new instances or version changes. Instances already on them keep running until February 6, 2027. On that date, any instance still on 0.22 or older stops working, and its owner gets a download link by email. Archives are deleted after 180 days. While you own an instance on 0.22 or older, a warning at the top of the dashboard lists it. See the announcement for details, including upgrade help on Discord.
Moving from 0.22 or older to 0.23 or later is a bigger step than other upgrades. PocketBase migrates your data on its own, but 0.23 rewrote the JavaScript hooks API, so custom pb_hooks need updating. Follow PocketBase’s 0.23 upgrade guide and test on a second instance first, as described below.
Upgrading your instance to the latest version of PocketBase is straightforward but requires careful planning to avoid data loss or unexpected behavior. Here’s the recommended approach:


For most cases, automatic upgrades are possible by simply switching to the latest version:

0.41.*).
If the automatic upgrade results in an unresponsive instance due to database schema issues, a manual upgrade is required:
Be cautious when downgrading – PocketBase does not officially support downgrades. While downgrades may work in some cases, there is no guarantee they will succeed without causing issues. If you attempt to downgrade and run into problems, there is no official resolution path.
To avoid potential disruptions, always create a second instance, restore your backup to it, and test the upgrade there first. This practice ensures you can catch any issues before applying changes to your live instance.
When you upgrade to a new version, PocketBase may perform automatic migrations on system tables. These migrations are typically non-destructive, but you should proceed with caution and ensure you have a backup before applying any updates.