Templates are now standalone, regular Strapi applications
Templates have been fully rewritten in Strapi 5 and now are standalone, regular Strapi applications, making it easier to create, distribute, and reuse them.
This page is part of the breaking changes database and provides information about the breaking change and additional instructions to migrate from Strapi v4 to Strapi 5.
| 🔌 Is this breaking change affecting plugins? | No |
|---|
| 🤖 Is this breaking change automatically handled by a codemod? | No |
|---|
Breaking change description
In Strapi v4
Templates were npm packages with strict requirements (see v4 documentation).
In Strapi 5
Templates are now just regular Strapi 5 applications, which can be run on their own.
Migration
This section regroups useful notes and procedures about the introduced breaking change.
Notes
- For additional information about creating a new Strapi application based on an existing template, see the templates documentation.
- Creating a Strapi template is now as simple as creating a new Strapi 5 application and adjusting its codebase to your needs.
Manual migration
Templates in Strapi v4 were only useful if applied on top of a default Strapi application. Strapi 5 templates are now standalone Strapi 5 applications.
To convert your Strapi v4 template into a usable Strapi 5 template, ensure the template includes all files required for Strapi to work. Your folder containing the v4 template applied on top of a full-blown Strapi application should be enough to be a Strapi 5 template.