You can now customize error pages for platform errors on Vercel, replacing generic error pages with your own branded experiences. Custom error pages display when Vercel encounters uncaught errors like function invocation timeouts or other platform errors . Link to heading How it works You can implement custom error pages using your framework’s conventions and Vercel will automatically locate them, for example with Next.js you can simply place a 500/page.tsx or static 500.html page in the public directory. To enrich error pages with request-specific context, you can use the following metadata tokens: ::vercel:REQUEST_ID:: - Contains the Vercel request ID ::vercel:ERROR_CODE:: - The specific error code e.g.…