Payload CMS has shared an early look at what’s coming in version 4.0, and it’s shaping up to be the most significant release since Payload 3.0 brought the CMS natively into Next.js. With over 1,300 PRs merged, 600 issues closed, and weekly downloads growing from 100k to over 400k, the team is moving fast and 4.0 is where that momentum lands.
A Completely Redesigned Admin UI
The headline feature of Payload 4.0 is a full redesign of the admin panel. Built around a stronger design system with more semantic styling tokens, the new UI aims to be cleaner, more consistent, and easier to extend. Key improvements include:
- Updated list and edit views
- Better table cells and bulk actions
- Richer upload views
- Improved modals and drawers
- A redesigned user menu
- Cleaner Lexical / rich text controls
- Enhanced contrast mode and better focus states
- Removal of Sass in favor of improved Tailwind compatibility
The redesign is also tied to a deeper integration with Figma, making the experience of moving between design and CMS feel more cohesive.
Hierarchies Become a Core Primitive
Payload 4.0 is bringing hierarchies into the core framework, replacing the nested docs plugin. This means folders, tags, taxonomies, nested content structures, and tree-based organization will all be built on the same underlying primitive, giving teams managing large content or asset libraries a much more powerful navigation experience.
Better Digital Asset Management
Building on the new hierarchy system, Payload 4.0 is investing heavily in digital asset management (DAM). Planned improvements include larger file previews, PDF, video, and audio support, localized files and file versioning, on-demand resizing, expiring share links, and usage references for files and images.
TanStack Support: Beyond Next.js
One of the most exciting architectural changes in 4.0 is a new framework adapter pattern that separates Payload’s framework-specific pieces from the core. The first major proof point is TanStack support, meaning Payload users will eventually be able to choose the framework that best fits their project, not just Next.js.
MCP Out of the Box
Payload’s MCP (Model Context Protocol) plugin is getting a major simplification. The goal for 4.0: add the plugin, configure MCP JSON, and go. Tools will be opt-out by default, local development setup will be improved, and complex schemas will be handled more reliably.
Payload Skills for AI Agents
The team is also shipping Payload skills, installable instructions for agentic workflows that give LLMs Payload-specific guidance to produce correct code consistently.
Timeline
The Payload team is targeting a 4.0 beta within the next quarter, with a goal of a shorter path from beta to stable than the 3.0 release cycle. Many of the admin redesign features are already visible on the main branch.
Key Takeaway: Payload 4.0 is shaping up to be a landmark release, more polished, more flexible, and more powerful. If you’re building with Payload today, now is a great time to follow the RFCs and provide feedback to shape what ships.
Hashtags: #PayloadCMS #NextJS #WebDevelopment #HeadlessCMS #TypeScript #ReactJS #OpenSource #WebDev
Resources: