Using Strapi built-in plugins
This section is about using Strapi built-in plugins from a developer's perspective. Not what you're looking for? Read the plugins introduction and find your use case and recommended section to read from there.
Strapi comes with the following built-in plugins that are officially maintained and documented by the Strapi core team:
✍️ Content Source Map
The Content Source Map plugin, used with Vercel Visual Editing, enhances the content edition experience.
The Documentation plugin is useful to document the available endpoints once you created an API.
The Email plugin enables applications to send emails from a server or an external provider.
The GraphQL plugin adds a GraphQL endpoint to fetch and mutate your content.
🌍 Internationalization (i18n)
The i18n plugin allows creating, managing and distributing localized content in different languages.
The Sentry plugin enables you to track errors in a Strapi application using Sentry.
The Upload plugin powers the Media Library found in the admin panel and allows versatile file uploads.
👥 Users & Permissions (U&P)
The U&P plugin offers JWT-based authentication and ACL strategies for API protection and user permissions.
Automatic plugins discovery
Strapi automatically loads plugins installed with npm. Under the hood, Strapi scans every
package.json file of the project dependencies, and looks for the following declaration:
Installed plugins can also be manually enabled or disabled.
Manual enabling/disabling of plugins
To disable a plugin without uninstalling it, switch its
enabled key to
false in the