--- title: error.js description: API reference for the error.js special file. related: title: Learn more about error handling links: - app/getting-started/error-handling --- An **error** file allows you to handle unexpected runtime errors and display fallback UI. error.js special file ```tsx filename="app/dashboard/error.tsx" switcher 'use client' // Error boundaries must be Client Components import { useEffect } from 'react' export default function Error({ error, reset, }: { error: Error & { digest?: string } reset: () => void }) { useEffect(() => { // Log the error to an error reporting service console.error(error) }, [error]) return (

Something went wrong!

) } ``` ```jsx filename="app/dashboard/error.js" switcher 'use client' // Error boundaries must be Client Components import { useEffect } from 'react' export default function Error({ error, reset }) { useEffect(() => { // Log the error to an error reporting service console.error(error) }, [error]) return (

Something went wrong!

) } ``` `error.js` wraps a route segment and its nested children in a [React Error Boundary](https://react.dev/reference/react/Component#catching-rendering-errors-with-an-error-boundary). When an error throws within the boundary, the `error` component shows as the fallback UI. How error.js works > **Good to know**: > > - The [React DevTools](https://react.dev/learn/react-developer-tools) allow you to toggle error boundaries to test error states. > - If you want errors to bubble up to the parent error boundary, you can `throw` when rendering the `error` component. ## Reference ### Props #### `error` An instance of an [`Error`](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Error) object forwarded to the `error.js` Client Component. > **Good to know:** During development, the `Error` object forwarded to the client will be serialized and include the `message` of the original error for easier debugging. However, **this behavior is different in production** to avoid leaking potentially sensitive details included in the error to the client. #### `error.message` - Errors forwarded from Client Components show the original `Error` message. - Errors forwarded from Server Components show a generic message with an identifier. This is to prevent leaking sensitive details. You can use the identifier, under `errors.digest`, to match the corresponding server-side logs. #### `error.digest` An automatically generated hash of the error thrown. It can be used to match the corresponding error in server-side logs. #### `reset` The cause of an error can sometimes be temporary. In these cases, trying again might resolve the issue. An error component can use the `reset()` function to prompt the user to attempt to recover from the error. When executed, the function will try to re-render the error boundary's contents. If successful, the fallback error component is replaced with the result of the re-render. ```tsx filename="app/dashboard/error.tsx" switcher 'use client' // Error boundaries must be Client Components export default function Error({ error, reset, }: { error: Error & { digest?: string } reset: () => void }) { return (

Something went wrong!

) } ``` ```jsx filename="app/dashboard/error.js" switcher 'use client' // Error boundaries must be Client Components export default function Error({ error, reset }) { return (

Something went wrong!

) } ``` ## Examples ### Global Error While less common, you can handle errors in the root layout or template using `global-error.js`, located in the root app directory, even when leveraging [internationalization](/docs/app/guides/internationalization). Global error UI must define its own `` and `` tags. This file replaces the root layout or template when active. ```tsx filename="app/global-error.tsx" switcher 'use client' // Error boundaries must be Client Components export default function GlobalError({ error, reset, }: { error: Error & { digest?: string } reset: () => void }) { return ( // global-error must include html and body tags

Something went wrong!

) } ``` ```jsx filename="app/global-error.js" switcher 'use client' // Error boundaries must be Client Components export default function GlobalError({ error, reset }) { return ( // global-error must include html and body tags

Something went wrong!

) } ``` ### Graceful error recovery with a custom error boundary When rendering fails on the client, it can be useful to show the last known server rendered UI for a better user experience. The `GracefullyDegradingErrorBoundary` is an example of a custom error boundary that captures and preserves the current HTML before an error occurs. If a rendering error happens, it re-renders the captured HTML and displays a persistent notification bar to inform the user. ```tsx filename="app/dashboard/error.tsx" switcher 'use client' import React, { Component, ErrorInfo, ReactNode } from 'react' interface ErrorBoundaryProps { children: ReactNode onError?: (error: Error, errorInfo: ErrorInfo) => void } interface ErrorBoundaryState { hasError: boolean } export class GracefullyDegradingErrorBoundary extends Component< ErrorBoundaryProps, ErrorBoundaryState > { private contentRef: React.RefObject constructor(props: ErrorBoundaryProps) { super(props) this.state = { hasError: false } this.contentRef = React.createRef() } static getDerivedStateFromError(_: Error): ErrorBoundaryState { return { hasError: true } } componentDidCatch(error: Error, errorInfo: ErrorInfo) { if (this.props.onError) { this.props.onError(error, errorInfo) } } render() { if (this.state.hasError) { // Render the current HTML content without hydration return ( <>

An error occurred during page rendering

) } return
{this.props.children}
} } export default GracefullyDegradingErrorBoundary ``` ```jsx filename="app/dashboard/error.js" switcher 'use client' import React, { Component, createRef } from 'react' class GracefullyDegradingErrorBoundary extends Component { constructor(props) { super(props) this.state = { hasError: false } this.contentRef = createRef() } static getDerivedStateFromError(_) { return { hasError: true } } componentDidCatch(error, errorInfo) { if (this.props.onError) { this.props.onError(error, errorInfo) } } render() { if (this.state.hasError) { // Render the current HTML content without hydration return ( <>

An error occurred during page rendering

) } return
{this.props.children}
} } export default GracefullyDegradingErrorBoundary ``` ## Version History | Version | Changes | | --------- | ------------------------------------------- | | `v15.2.0` | Also display `global-error` in development. | | `v13.1.0` | `global-error` introduced. | | `v13.0.0` | `error` introduced. |