--- title: "Quick Start (Cloudflare)" description: "Learn how to set up Sentry in your Next.js application deployed on Cloudflare Workers and capture your first errors." url: https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare/ --- # Next.js on Cloudflare Runtime * [Node.js](https://docs.sentry.io/platforms/javascript/guides/nextjs.md) * [Cloudflare](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md) ## [Prerequisites](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#prerequisites) You need: * A Sentry [account](https://sentry.io/signup/) and [project](https://docs.sentry.io/product/projects.md) * A Next.js application that runs on Cloudflare Workers with the [OpenNext Cloudflare adapter](https://opennext.js.org/cloudflare) or [vinext](https://github.com/cloudflare/vinext) If you haven't deployed a Next.js app to Cloudflare Workers before, follow Cloudflare's [Next.js deployment guide](https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/) first. ## [Install](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#install) ### [Run the Installation Wizard](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#run-the-installation-wizard) Run the Sentry wizard to automatically install the SDK and configure Sentry in your Next.js application: ```bash npx @sentry/wizard@latest -i nextjs ``` The wizard asks whether you want to enable **Tracing** and **Session Replay**, route browser requests through your server to avoid ad blockers, and create an example page. To match the configuration in this guide, answer **Yes** to each. Prefer to set things up yourself? Check out the [Manual Setup](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup.md) guide. ## [Configure](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#configure) **Error Monitoring** starts working as soon as you call `Sentry.init()`. **Logs** and **Application Metrics** need no extra configuration, and you'll learn how to send them in steps [#3](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#send-logs) and [#4](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#send-application-metrics-). This guide also enables **Tracing**, **Session Replay**, and **User Feedback**. Want to learn more about these features? * [**Issues**](https://docs.sentry.io/product/issues.md) (always enabled): Sentry's core error monitoring product that automatically reports errors, uncaught exceptions, and crashes. If you have something that looks like an exception, Sentry can capture it. * [**Tracing**](https://docs.sentry.io/product/tracing.md): Track software performance while seeing the impact of errors across multiple systems. For example, distributed tracing allows you to follow a request from the frontend to the backend and back. * [**Session Replay**](https://docs.sentry.io/product/session-replay.md): Get to the root cause of an issue faster by viewing a video-like reproduction of what users saw in your app before, during, and after the problem. * [**Logs**](https://docs.sentry.io/product/logs.md): Centralize and analyze your application logs to correlate them with errors and performance issues. Search, filter, and visualize log data to understand what's happening in your applications. * [**Application Metrics**](https://docs.sentry.io/product/metrics.md) (always enabled): Track and analyze custom application metrics, such as response times and database query durations, to understand trends and patterns in your application's performance and behavior over time. * [**User Feedback**](https://docs.sentry.io/product/user-feedback.md): Collect feedback directly from users when they encounter errors, allowing them to describe what happened and provide context that helps you understand and resolve issues faster. The wizard creates the files below. On Cloudflare Workers, you set the server options in the Worker entry instead, as the [Wrap the Worker Entry](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#wrap-the-worker-entry) step shows. ### [Initialize the SDK](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#initialize-the-sdk) Next.js runs code in different environments, so the wizard creates a separate initialization file for each in your project's root directory (or `src` folder): * `instrumentation-client.ts`: runs in the browser * `sentry.server.config.ts`: runs in the Node.js runtime * `sentry.edge.config.ts`: runs in the Edge runtime Use the tabs in the code box below to view each file. The snippets also turn on: * Tracing: via [`tracesSampleRate`](https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options.md#tracesSampleRate) in all three files * Session Replay: via `replayIntegration()`, sampled with [`replaysSessionSampleRate`](https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options.md#replaysSessionSampleRate) and [`replaysOnErrorSampleRate`](https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options.md#replaysOnErrorSampleRate) * User Feedback: via [`feedbackIntegration()`](https://docs.sentry.io/platforms/javascript/guides/nextjs/user-feedback/configuration.md). The wizard doesn't add this integration, so add it to `instrumentation-client.ts` yourself. Don't need a feature? Remove its integration and options from the snippets. **\[Client] instrumentation-client.ts** ```typescript import * as Sentry from "@sentry/nextjs"; Sentry.init({ dsn: "https://@o.ingest.sentry.io/", integrations: [ // enables Session Replay Sentry.replayIntegration(), // enables User Feedback Sentry.feedbackIntegration({ // Additional integration configuration goes in here colorScheme: "system", }), ], // Enables Tracing. // Set to 1.0 to capture 100% of spans for tracing. // We recommend reducing this value in production. tracesSampleRate: 1.0, // Capture replays for 10% of all sessions, // plus for 100% of sessions with an error // Requires Sentry.replayIntegration() replaysSessionSampleRate: 0.1, replaysOnErrorSampleRate: 1.0, }); // Instruments client-side navigations export const onRouterTransitionStart = Sentry.captureRouterTransitionStart; ``` **\[Server] sentry.server.config.ts** ```typescript import * as Sentry from "@sentry/nextjs"; Sentry.init({ dsn: "https://@o.ingest.sentry.io/", // Enables Tracing. // Set to 1.0 to capture 100% of spans for tracing. // We recommend reducing this value in production. tracesSampleRate: 1.0, }); ``` **\[Edge] sentry.edge.config.ts** ```typescript import * as Sentry from "@sentry/nextjs"; Sentry.init({ dsn: "https://@o.ingest.sentry.io/", // Enables Tracing. // Set to 1.0 to capture 100% of spans for tracing. // We recommend reducing this value in production. tracesSampleRate: 1.0, }); ``` ### [Register the Server-Side Configuration](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#register-the-server-side-configuration) The wizard creates a [Next.js instrumentation file](https://nextjs.org/docs/app/guides/instrumentation) named `instrumentation.ts`. It loads your server and edge configurations, and exports `onRequestError` to capture errors from Server Components, route handlers, and middleware. ```typescript import * as Sentry from "@sentry/nextjs"; export async function register() { if (process.env.NEXT_RUNTIME === "nodejs") { await import("./sentry.server.config"); } if (process.env.NEXT_RUNTIME === "edge") { await import("./sentry.edge.config"); } } export const onRequestError = Sentry.captureRequestError; ``` ### [Capture React Render Errors](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#capture-react-render-errors) If you use the App Router, the wizard adds Sentry to `app/global-error.tsx` to capture React rendering errors. If you use the Pages Router, it adds Sentry to `pages/_error.tsx` instead. ```tsx "use client"; import * as Sentry from "@sentry/nextjs"; import NextError from "next/error"; import { useEffect } from "react"; export default function GlobalError({ error, }: { error: Error & { digest?: string }; }) { useEffect(() => { Sentry.captureException(error); }, [error]); return ( {/* `NextError` is the default Next.js error page component. Its type definition requires a `statusCode` prop. However, since the App Router does not expose status codes for errors, we simply pass 0 to render a generic error message. */} ); } ``` *Other available variations of the above snippet: jsx* ### [Apply Instrumentation to Your App](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#apply-instrumentation-to-your-app) The wizard wraps your Next.js configuration with `withSentryConfig`. This instruments your app at build time, uploads source maps, and, if you said yes in the wizard, routes browser requests to Sentry through your server to avoid ad blockers. To forward only the request body to Sentry, add a tunnel route handler (SDK version `10.77.1` and later on v10, `11.9.0` and later on v11). Use the handler if Vercel Deployment Protection or another login protects your app. Learn more about the [`tunnelRoute` option](https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/build.md#tunnelRoute). ```typescript import type { NextConfig } from "next"; import { withSentryConfig } from "@sentry/nextjs/config"; const nextConfig: NextConfig = { // Your existing Next.js configuration }; export default withSentryConfig(nextConfig, { org: "", project: "", // Only print logs for uploading source maps in CI silent: !process.env.CI, // Upload a larger set of source maps for prettier stack traces (increases build time) widenClientFileUpload: true, // Route browser requests to Sentry through a Next.js rewrite to avoid ad blockers. // This can increase your server load as well as your hosting bill. tunnelRoute: "/monitoring", }); ``` ### [Add Readable Stack Traces With Source Maps](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#add-readable-stack-traces-with-source-maps) The wizard stores your auth token in `.env.sentry-build-plugin` and adds the file to `.gitignore`. The Sentry build plugin uses this token to upload source maps when you build your app locally. For CI/CD builds, set the `SENTRY_AUTH_TOKEN` environment variable in your build system instead. ```bash SENTRY_AUTH_TOKEN= ``` ### [Configure Wrangler](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#configure-wrangler) The SDK uses Node.js APIs that the Workers runtime only provides with the `nodejs_compat` [compatibility flag](https://developers.cloudflare.com/workers/runtime-apis/nodejs/). Set the [compatibility date](https://developers.cloudflare.com/workers/configuration/compatibility-dates/) to `2025-08-16` or later, which adds the `https.request` API that the SDK uses to send data: ```jsonc { "compatibility_flags": ["nodejs_compat"], "compatibility_date": "2025-08-16", } ``` *Other available variations of the above snippet: Toml* ### [Wrap the Worker Entry](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#wrap-the-worker-entry) Available since: `v11.6.0` If you build your app with vinext, skip to [Wrap the Worker Entry With vinext](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#wrap-the-worker-entry-with-vinext). On Cloudflare Workers, your Next.js app runs inside the Worker entry that OpenNext generates (`.open-next/worker.js`). Wrap this entry with `withSentry` from `@sentry/nextjs/cloudflare` to get the same Next.js spans as on Node.js, plus Cloudflare data such as spans for D1 queries. Each request gets one `http.server` span with the name of the Next.js route, and the Next.js spans become its children. `@sentry/nextjs` depends on `@sentry/cloudflare`, so you don't need to install another package. First, create a [custom Worker](https://opennext.js.org/cloudflare/howtos/custom-worker) that imports the handler of OpenNext and wraps it with `withSentry`. Pass your Sentry options to `withSentry`: ```typescript import * as Sentry from "@sentry/nextjs/cloudflare"; // @ts-ignore `.open-next/worker.js` is generated at build time import handler from "./.open-next/worker.js"; // Re-export the Durable Objects your app uses, for example for the DO Queue and DO Tag Cache of OpenNext // @ts-ignore `.open-next/worker.js` is generated at build time export { DOQueueHandler, DOShardedTagCache } from "./.open-next/worker.js"; export default Sentry.withSentry( () => ({ dsn: "https://@o.ingest.sentry.io/", // Set tracesSampleRate to 1.0 to capture 100% of spans for tracing. // Learn more at // https://docs.sentry.io/platforms/javascript/guides/cloudflare/configuration/options/#tracesSampleRate tracesSampleRate: 1.0, }), handler, ); ``` Then, point `main` in your Wrangler configuration to this file: ```jsonc { "main": "./worker.ts", } ``` *Other available variations of the above snippet: Toml* #### [Wrap the Worker Entry With vinext](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#wrap-the-worker-entry-with-vinext) With [vinext](https://github.com/cloudflare/vinext), you don't need a custom Worker. Add the [Sentry Vite plugin](https://docs.sentry.io/platforms/javascript/guides/cloudflare/install/vite-plugin.md) to your Vite config, and it wraps your Worker entry with `withSentry` from `@sentry/nextjs/cloudflare` automatically. #### [Server and Edge Configuration in the Worker](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#server-and-edge-configuration-in-the-worker) In the Worker, `withSentry` creates the Sentry client. `Sentry.init()` in `sentry.server.config.ts` and `sentry.edge.config.ts` still runs, but it creates no client and only applies the `release` option. Set all other options in `withSentry`. On Workers, these two files are optional. Keep them if you use `next dev`, which runs on Node.js and doesn't use the Worker entry. They also pass on the release that `withSentryConfig` sets at build time. Keep `instrumentation.ts`, because Next.js reports server errors, for example from Server Components and route handlers, through its `onRequestError` hook. The SDK takes the release from the first of these sources that has a value: 1. The `release` option of `withSentry` 2. The `SENTRY_RELEASE` environment variable 3. The ID of the `CF_VERSION_METADATA` binding 4. The `release` option of `Sentry.init()` in `sentry.server.config.ts` or `sentry.edge.config.ts`, or else the release that `withSentryConfig` sets at build time On Node.js, the build release comes before `SENTRY_RELEASE`. ### [Control the Data You Send to Sentry](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#control-the-data-you-send-to-sentry) By default, the SDK sends user identity data (IP address, ID, and similar) and other data like HTTP bodies and URL query parameters. This will give you rich debugging context. The SDK always filters sensitive values whose keys match a built-in denylist, such as `auth` or `password`, and sends `[Filtered]` instead. To send less data, turn off the categories you don't need in the `dataCollection` option. For the full list of categories and their defaults, [see the `dataCollection` options](https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/options.md#dataCollection). ```javascript Sentry.init({ dsn: "https://@o.ingest.sentry.io/", dataCollection: { userInfo: false, // other categories }, }); ``` ## [Send Logs](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#send-logs) Use `Sentry.logger` to send logs at different levels, such as `info`, `warn`, or `error`. You can pass any attributes you want and search or filter by them later. See [Set Up Logs](https://docs.sentry.io/platforms/javascript/guides/nextjs/logs.md) for all available logging methods and the syntax for formatting messages. ```javascript Sentry.logger.info("User example action completed"); Sentry.logger.warn("Slow operation detected", { operation: "data_fetch", duration: 3500, }); Sentry.logger.error("Validation failed", { form_field: "email", reason: "Invalid email", }); ``` If you're already logging with `console` or Consola, use an integration to capture those logs as Sentry Logs automatically: * [`consoleLoggingIntegration`](https://docs.sentry.io/platforms/javascript/guides/nextjs/logs.md#console) for `console` calls * [Consola](https://docs.sentry.io/platforms/javascript/guides/nextjs/logs.md#consola) ## [Send Application Metrics NEW](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#send-application-metrics-) Use `Sentry.metrics` to send counters, gauges, and distributions from your app to Sentry. You can pass any attributes you want and search or filter by them later. See [Set Up Metrics](https://docs.sentry.io/platforms/javascript/guides/nextjs/metrics.md) for all available metric types and configuration options. ```javascript Sentry.metrics.count("checkout.failed", 1); Sentry.metrics.gauge("time_since_refresh", 4, { unit: "hour" }); Sentry.metrics.distribution("api_latency", 187, { unit: "millisecond", attributes: { endpoint: "/api/orders" }, }); ``` ## [Verify Your Setup](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#verify-your-setup) Let's test your setup and confirm that Sentry is working correctly and sending data to your Sentry project. The wizard created an example page that sends a test error from both your frontend and your backend: 1. Build your app and run it in the Workers runtime on your machine: ```bash npx opennextjs-cloudflare build && npx opennextjs-cloudflare preview ``` 2. Open `/sentry-example-page` on the URL that the preview command prints. 3. Click **Throw Sample Error**. If you skipped the example page, add a test button to one of your pages instead. Clicking it will trigger an error for Sentry to capture. ```tsx "use client"; export default function Page() { return ( ); } ``` ##### Important Errors triggered from within your browser's developer tools (like the browser console) are sandboxed, so they will not trigger Sentry's error monitoring. ### [View Captured Data in Sentry](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#view-captured-data-in-sentry) Now, head over to your project on [Sentry.io](https://sentry.io/) to view the collected data (it takes a couple of moments for the data to appear). Need help locating captured data in your Sentry project? * Open the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page and select an error from the issues list to view the full details and context of this error. For more details, see the [Issue Details documentation](https://docs.sentry.io/product/issues/issue-details.md). * Open the [**Traces**](https://sentry.io/orgredirect/organizations/:orgslug/explore/traces/) page and select a trace to reveal more information about each span, its duration, and any errors. For an interactive UI walkthrough, click [here](https://docs.sentry.io/product/sentry-basics/getting-started-tutorial/generate-first-error.md#ui-walkthrough). * Open the [**Replays**](https://sentry.io/orgredirect/organizations/:orgslug/replays/) page and select an entry from the list to get a detailed view where you can replay the interaction and get more information to help you troubleshoot. * Open the [**Logs**](https://sentry.io/orgredirect/organizations/:orgslug/explore/logs/) page and filter by service, environment, or search keywords to view log entries from your application. For an interactive UI walkthrough, click [here](https://docs.sentry.io/product/logs.md#overview). * Open the [**Application Metrics**](https://sentry.io/orgredirect/organizations/:orgslug/explore/metrics) page to view and analyze your metrics. For more details, see this [interactive walkthrough](https://docs.sentry.io/product/metrics.md#overview). * Open the [**User Feedback**](https://sentry.io/orgredirect/organizations/:orgslug/feedback/) page and click on individual feedback to see more details all in one view. For more information, click [here](https://docs.sentry.io/product/user-feedback.md). ## [Next Steps](https://docs.sentry.io/platforms/javascript/guides/nextjs/cloudflare.md#next-steps) At this point, you should have integrated Sentry into your Next.js application on Cloudflare Workers. Here's what to explore next: * Explore [practical guides](https://docs.sentry.io/get-started/guides.md) on what to monitor, log, track, and investigate after setup * [Distributed Tracing](https://docs.sentry.io/platforms/javascript/guides/nextjs/tracing/distributed-tracing.md) to trace requests across services * [Set up tunneling](https://docs.sentry.io/platforms/javascript/guides/nextjs/troubleshooting.md#dealing-with-ad-blockers) to avoid ad blockers blocking Sentry events, if you didn't enable it in the wizard Are you having problems setting up the SDK? * If you encountered issues with our installation wizard, try [setting up Sentry manually](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup.md) * Find various topics in [Troubleshooting](https://docs.sentry.io/platforms/javascript/guides/nextjs/troubleshooting.md) * [Get support](https://www.sentry.help/en/)