Quickstart
Install the SDK and show your first branded error page in five minutes.
error.page catches errors on your site and, instead of showing your users a broken screen, renders a calm, on-brand page while you get notified. This guide gets you live in about five minutes.
1. Create a project
A project represents one website or app. From your dashboard, click Create Project, give it a name (e.g. my-store), and you're done. Each project gets its own API key, slug, and branded page.
2. Add the SDK
Paste this snippet just before the closing </body> tag on your site. It's about 4KB gzipped and loads asynchronously, so it never blocks your page.
<script src="https://error.page/js/errorpage.js"></script>
<script>
ErrorPage.init({
projectId: 'YOUR_API_KEY',
slug: 'your-project-slug'
});
</script>
You'll find your exact snippet, pre-filled with your keys, on the dashboard under Quick Setup.
Zero-install alternative
Prefer not to hand-write the config? Drop a single meta tag in your <head> and load our loader โ it discovers the rest:
<meta name="error-page-key" content="YOUR_API_KEY">
<script src="https://error.page/sdk.js" async></script>
3. Test it
Trigger an error on your site (or throw one from the console):
throw new Error('Hello from error.page');
Within a second or two the error appears in your Incident feed, and your branded page is ready to show on the next real failure.
What happens next
- Errors are grouped into incidents so a thousand occurrences of the same bug are one line, not a thousand. See Incident feed.
- Design what your users see in the Branded pages editor.
- On paid plans you can capture leads, route alerts to Slack, classify errors with AI, and serve pages from your own domain.