Vercel now supports customizing platform error pages
By Steven Van ·
It's limited to Enterprise teams, works automatically on every project, and can show the failing request's ID and error code.
Vercel now lets teams on its Enterprise plan replace the generic pages it shows for platform errors, such as function invocation timeouts or throttled functions, with their own branded pages.
- Add a page using your framework's own conventions, for example a static 500.html in the public directory or, with Next.js App Router, 500/page.tsx. Vercel scans the build output and configures the routing automatically.
- A single 500 page serves as the fallback for any platform error that doesn't have its own dedicated page, so one page can cover every case.
- Pages can include the tokens ::vercel:REQUEST_ID:: and ::vercel:ERROR_CODE::, which Vercel replaces with the actual request ID and error code when it serves the page.
Error pages must be static, since they handle failures that could also break server-side rendering. The feature is enabled automatically across all projects on Enterprise teams, with no extra configuration. See the documentation for implementation examples.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →