Stateful test emulator of the Payload collection REST API with seeded data
All Tools 92
Tools help you build with Payload outside its config: CLIs, API clients and SDKs, frontend renderers and workflow helpers.
Editor support for Payload component paths, with import checks and autocomplete
React hook and refresh component for Payload Live Preview in frontend apps
Type-safe client for the Payload REST API with CRUD, auth and file uploads
Scaffolds a new Payload project or adds Payload to an existing Next.js or TanStack app
Vue composable that wires a Payload Live Preview into a Vue frontend
React admin bar that puts Payload editing controls on your frontend pages
Client SDK that streams live Payload draft edits into a frontend preview
Renders Lexical rich text content from Payload in Astro sites
Governance checks and ESLint rules for Payload project structure, access code and hooks
Manifest, linter and Payload block generator for a design system's components
Automated code transforms that move a Payload project past breaking changes
Idempotent seed runner that fills a Payload database with ordered, cross-referenced content
CLI and registry that installs wired Payload blocks into Next.js projects
Live preview for server-rendered and static frontends, with in-place field updates
Migrates WordPress posts, pages, media, SEO and redirects into Payload
Agent skill that enforces generated, paired Payload database migrations and gates destructive changes
AI agent skill that guides building Payload blocks and their rendering dispatcher
Migrates WordPress sites to Payload from a WXR export file
Shared lint, test and quality configs that keep Payload projects consistent
About these packages
Work with Payload data and project code using command-line tools, API clients and frontend renderers. Other tools help with data migration, API documentation and AI assistants. Choose a category based on the task you need to complete.
Installation depends on where the tool runs. A renderer belongs in the frontend that uses it; a CLI runs in a terminal or CI job. Read the README for setup, access credentials and supported Payload versions.
Frequently asked questions
What is the difference between a tool and a plugin?
A plugin extends Payload through its configuration. A tool handles a development task, such as calling the API, rendering content or migrating data. Some tools also require configuration inside the Payload project; follow the package README.
How do I install a Payload CMS tool?
Follow the command and setup instructions on its product page or in its README. Install a library in the project that imports it. For a CLI, check whether the author recommends a local install or running it with npx.
Do tools need a specific Payload version?
Tools can depend on a particular API, generated types or rich-text data format. Check supported versions and release dependencies, especially for renderers and typed clients, before adding a tool to your project.



