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 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 or static page in the directory. 500/page.tsx500.htmlpublic To enrich error pages with request-specific context, you can use the following metadata tokens: This feature is available for Enterprise teams and enabled automatically across all projects.

No additional configuration required. See the to get started or reference the following implementations: or .documentationCustom error pages with App RouterCustom error pages with public directory Read more How it works Contains the Vercel request ID::vercel:REQUEST_ID:: The specific error code e.g. ::vercel:ERROR_CODE::FUNCTION_INVOCATION_TIMEOUT