Payload comes with a built-in Plugins infrastructure that allows developers to build their own modular and easily reusable sets of functionality.

Writing plugins is no more complex than writing regular JavaScript. If you know how spread syntax works and are up to speed with Payload concepts, writing a plugin will be a breeze.

Example use cases:

  • Automatically sync data from a specific collection to HubSpot or a similar CRM when data is added or changes
  • Add password-protection functionality to certain documents
  • Add a full e-commerce backend to any Payload app
  • Add custom reporting views to Payload's admin panel
  • Encrypt specific collections' data
  • Add a full form builder implementation
  • Integrate all upload-enabled collections with a third-party file host like S3 or Cloudinary
  • Add custom endpoints or GraphQL queries / mutations with any type of custom functionality that you can think of

How to install plugins

The base Payload config allows for a plugins property which takes an array of Plugins.

import { buildConfig } from 'payload/config'
// note: these plugins are not real (yet?)
import addLastModified from 'payload-add-last-modified'
import passwordProtect from 'payload-password-protect'
import { mongooseAdapter } from '@payloadcms/db-mongodb'
import { postgresAdapter } from '@payloadcms/db-postgres'
import { viteBundler } from '@payloadcms/bundler-vite'
import { webpackBundler } from '@payloadcms/bundler-webpack'
const config = buildConfig({
bundler: webpackBundler() // or viteBundler(),
collections: [
slug: 'pages',
fields: [
name: 'title',
type: 'text',
required: true,
name: 'content',
type: 'richText',
required: true,
db: mongooseAdapter({}) // or postgresAdapter({})
plugins: [
// Many plugins require options to be passed.
// In the following example, we call the function
// and pass it options accordingly
// This plugin takes no options and just
// needs to be passed directly
// ..
// To understand how to use the plugins you're interested in,
// consult their corresponding documentation
export default config

When Plugins are initialized

Payload Plugins are executed after the incoming config is validated, but before it is sanitized and had default options merged in.

After all plugins are executed, the full config with all plugins will be sanitized.

Simple example

Here is an example for how to automatically add a lastModifiedBy field to all Payload collections using a Plugin written in TypeScript.

import { Config, Plugin } from 'payload/config'
const addLastModified: Plugin = (incomingConfig: Config): Config => {
// Find all incoming auth-enabled collections
// so we can create a lastModifiedBy relationship field
// to all auth collections
const authEnabledCollections = incomingConfig.collections.filter((collection) =>
// Spread the existing config
const config: Config = {
collections: => {
// Spread each item that we are modifying,
// and add our new field - complete with
// hooks and proper admin UI config
return {
fields: [
name: 'lastModifiedBy',
type: 'relationship',
relationTo:{ slug }) => slug),
hooks: {
beforeChange: [
({ req }) => ({
value: req?.user?.id,
relationTo: req?.user?.collection,
admin: {
position: 'sidebar',
readOnly: true,
return config
export default addLastModified

Available Plugins

You can discover existing plugins by browsing the payload-plugin topic on GitHub.

For maintainers building plugins for others to use, please add the topic to help others find it. If you would like one to be built by the core Payload team, open a Feature Request in our GitHub Discussions board. We would be happy to review your code and maybe feature you and your plugin where appropriate.


Form Builder Plugin