Custom Not-Found

[atomic gust]

Hi everyone!

I’d like to understand the correct approach to implementing a custom 404 page in my application. Currently, Payload CMS is using the default Next.js 404 page, and it’s not clear what the best way is to override this behavior without causing conflicts with Payload’s own layout.

Has anyone dealt with this before or knows the recommended way to handle this scenario?

[analog elk]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Installation - Adding to an existing app - Related Guides
• Blocks Field - Conditional Blocks - Example - Related Guides
• Payload Concepts - Retrieving Data - Local API

Community-Help:

• Image optimization while using R2
• Best place for a studio to deploy a growing number of Payload projects?
• Next Payload boilerplate build
• Exclude field when fetching a record

[hollow sleet]

Hey @atomic gust if you want to modify the 404 page, you can just edit src/app/(frontend)/not-found.tsxas you see fit!