Server Error
Retry first, because a 500 is our failure and offering navigation implies the rest of the site works — which is exactly what is in doubt.
Drops straight into app/not-found.tsx, and keeps the site header and footer — on a 404 the navigation is the most useful thing on screen.
app/error-404-page.tsxnpx hoverlab add error-404-page
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
The link may be out of date, or the page may have moved. Here are a few ways forward.
The real page, rendered in your current theme — every section below is a live block, not a screenshot.
Only want one section? Open it and copy that block instead — browse Empty & Error States.
Want the whole project rather than this one screen? A template ships every route, the theme tokens and the layout.
/**
* A 404 screen.
*
* Drop this at `app/not-found.tsx` in a Next.js project and it becomes the
* app's 404 for every unmatched route.
*
* Deliberately keeps the site's own header and footer. A 404 that strips
* the chrome tells the visitor they have left the site, when in fact they
* are still on it and one click from what they wanted — the navigation is
* the most useful thing on the page.
*/
import * as React from 'react'
import { NotFound404 } from '@/components/not-found-404'
export default function Error404Page() {
return (
<div className="flex min-h-screen flex-col bg-background text-foreground">
{/* Keep the chrome — the nav is the point. */}
<header className="border-b border-border/60">
<div className="mx-auto flex h-16 max-w-7xl items-center justify-between px-6">
<a href="/" className="flex items-center gap-2 font-semibold tracking-tight">
<span
aria-hidden
className="flex h-8 w-8 items-center justify-center rounded-xl bg-primary text-primary-foreground"
>
A
</span>
Acme Inc
</a>
<nav aria-label="Main" className="flex items-center gap-5 text-sm">
<a href="/docs" className="text-muted-foreground transition-colors hover:text-foreground">
Docs
</a>
<a href="/pricing" className="text-muted-foreground transition-colors hover:text-foreground">
Pricing
</a>
<a
href="/signup"
className="rounded-xl bg-primary px-3.5 py-2 text-sm font-semibold text-primary-foreground transition-colors hover:bg-primary/90"
>
Get started
</a>
</nav>
</div>
</header>
<div className="flex flex-1 items-center justify-center">
<NotFound404 />
</div>
<footer className="border-t border-border/60">
<div className="mx-auto flex max-w-7xl items-center justify-between px-6 py-5 text-xs text-muted-foreground">
<span>© 2026 Acme Inc</span>
<span>All systems operational</span>
</div>
</footer>
</div>
)
}
components/ — each block page has its own copy button.app/error-404-page.tsx. The imports already point at @/components/…, so they resolve with no edits.The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Retry first, because a 500 is our failure and offering navigation implies the rest of the site works — which is exactly what is in doubt.
Planned downtime with an actual end time on it — "back soon" is not a time, and a maintenance page without one looks like an outage nobody has noticed.
A 403 that names who can grant what was refused, because the next question is always "then who can" and a support link is the wrong answer to it.
Written for the person refreshing it during an outage: current state above the fold, the maintenance window as a real block with an end time, and a component list that names what still works.
Terms, privacy, DPA and cookies in one frame — the docs layout, because people arrive at a legal page looking for a specific clause and a wall of text makes that a Ctrl-F expedition.
The status page read during diligence rather than during an outage: ninety days of uptime, the latency curve, and every incident carrying its post-mortem — including the bad one.
One document with a plain-language column beside each clause, for the reader who cannot name the clause they need — and the cookie control inline, because a banner is unreachable the moment it has been dismissed.