10 / Payload CommentsOPEN UPTHE CONVERSATION.
Comments & moderation for Payload
A plugin for discussions beneath content and tools for the people moderating them.
Payload Comments adds comments, threaded replies and reactions to Payload CMS 3. The admin interface supports publication and moderation, with abuse prevention options and runtime settings.
Opening a discussion also changes a publication’s operations: who can post, who reviews contributions and when should a conversation close? The public interface and administration tools are two parts of the same service.
Reviewed project · facts and limits
What does Payload Comments provide?
Payload Comments is an open plugin for Payload CMS 3 that adds anonymous comments, threaded replies, reactions and optional moderation. Navanem designs both sides of the service: a public experience that needs to remain readable and an administration interface used to approve, close or follow discussions.
Activation settings, abuse prevention and thread depth need to match the editorial context and the team available to moderate it. The public repository lets teams inspect the TypeScript code, MIT licence, API and integration choices before adoption. This page describes documented project features; it does not replace the security, privacy, load and moderation assessment required for each deployment and host publication.
Source reviewed on
- Status
- Active public repository
- Role
- Design, development and documentation
- Technology
- Payload CMS 3 and TypeScript
- Licence
- MIT
Documentary screenshotDATED PUBLIC EVIDENCE.

These skills for your business
Open-source applicationsBeyond the visual · Payload CommentsTHE IDEA. THE USE. THE DETAIL.
Readable conversations
A clear hierarchy between comments and replies helps readers follow an exchange. Reactions complement discussion without replacing an argument. Thread depth needs to remain manageable.
Make moderation part of the design
Approval before publication and activation settings allow teams to adapt how they host conversations. Decisions depend on the audience, available staff and editorial context.
Fit the host publication
A comment feature should fit the publication it belongs to. Access to code and APIs allows teams to assess integration options, paying particular attention to submitted data and how it is displayed.