diff --git a/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx b/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
index 64d59a2ae9013..ee94a816e83c2 100644
--- a/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
+++ b/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx
@@ -182,50 +182,6 @@ Note: Enabling this option can lead to longer build times.
-
-
-Automatically instrument Next.js data fetching methods and Next.js API routes with error and performance monitoring.
-
-
-
-
-
-Automatically instrument Next.js middleware with error and performance monitoring.
-
-
-
-
-
-Automatically instrument components in the `app` directory with error monitoring.
-
-
-
-
-Exclude specific server-side API routes or pages from automatic Sentry instrumentation during build time.
-This option takes an array of strings or regular expressions and affects pages in the `pages` and `app` directories.
-
-When defining routes, note the following:
-
-- Specify pages as routes and not as file system paths. For example, write `/animals` instead of `pages/animals/index.js`.
-- Make sure that any provided string matches the route exactly, has a leading slash, and doesn't have a trailing slash.
-
-```javascript
-excludeServerRoutes: [
- "/some/excluded/route",
- "/excluded/route/with/[parameter]",
- /^\/route\/beginning\/with\/some\/prefix/,
- /\/routeContainingASpecificPathSegment\/?/,
-];
-```
-
-
- If you're building your Next.js application with Turbopack, this option will
- have no effect. The Sentry SDK will no longer apply build-time instrumentation
- and will rely purely on Next.js telemetry features.
-
-
-
-
This feature requires **Next.js version 11+** and doesn't currently work with self-hosted Sentry instances.
@@ -251,9 +207,18 @@ Learn more about tunneling in the
+
-Automatically create cron monitors in Sentry for your Vercel Cron Jobs if configured via `vercel.json`.
+
+ You can use this option with Next.js version 15.4.1 and later.
+
+
+Enables the use of the [`runAfterProductionCompile` hook from Next.js](https://nextjs.org/docs/architecture/nextjs-compiler#runafterproductioncompile) to upload sourcemaps after the build is completed.
+
+- This option is set to `true` by default for Turbopack as there are no alternative ways to upload sourcemaps here.
+- This option is set to `false` for Webpack as the default behavior is to upload sourcemaps during the build process using the [Sentry Webpack Plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins).
+
+**Important:** Enabling this option will mutate your Next.js build output by injecting [Debug IDs](/platforms/javascript/guides/nextjs/sourcemaps/troubleshooting_js/debug-ids/) via the Sentry CLI. If you are relying on any sort of integrity hashes for your build artifacts, you will need to disable this option.
@@ -272,37 +237,59 @@ The route manifest is a build-time generated mapping of your Next.js App Router
-
+## Next.js Webpack Options
-Enables React component name tracking. When enabled, it annotates React components with data attributes that allow Sentry to track which components users interacted with in features like Session Replay and breadcrumbs.
+
+ These options only take effect if you're using Webpack. If you're using
+ Turbopack, these options will have no effect.
+
+
+
+
+Automatically instrument Next.js data fetching methods and Next.js API routes with error and performance monitoring.
-
+
-A list of React component names to exclude from component annotation.
+Automatically instrument Next.js middleware with error and performance monitoring.
-
+
-
- You can use this option with Next.js version 15.4.1 and later.
-
+Automatically instrument components in the `app` directory with error monitoring.
-Enables the use of the [`runAfterProductionCompile` hook from Next.js](https://nextjs.org/docs/architecture/nextjs-compiler#runafterproductioncompile) to upload sourcemaps after the build is completed.
+
-- This option is set to `true` by default for Turbopack as there are no alternative ways to upload sourcemaps here.
-- This option is set to `false` for Webpack as the default behavior is to upload sourcemaps during the build process using the [Sentry Webpack Plugin](https://github.com/getsentry/sentry-javascript-bundler-plugins).
+
+Exclude specific server-side API routes or pages from automatic Sentry instrumentation during build time.
+This option takes an array of strings or regular expressions and affects pages in the `pages` and `app` directories.
-**Important:** Enabling this option will mutate your Next.js build output by injecting [Debug IDs](/platforms/javascript/guides/nextjs/sourcemaps/troubleshooting_js/debug-ids/) via the Sentry CLI. If you are relying on any sort of integrity hashes for your build artifacts, you will need to disable this option.
+When defining routes, note the following:
+
+- Specify pages as routes and not as file system paths. For example, write `/animals` instead of `pages/animals/index.js`.
+- Make sure that any provided string matches the route exactly, has a leading slash, and doesn't have a trailing slash.
+
+```javascript
+webpack.excludeServerRoutes: [
+ "/some/excluded/route",
+ "/excluded/route/with/[parameter]",
+ /^\/route\/beginning\/with\/some\/prefix/,
+ /\/routeContainingASpecificPathSegment\/?/,
+];
+```
+
+
-
+Automatically create cron monitors in Sentry for your Vercel Cron Jobs if configured via `vercel.json`.
+
+
Pass configuration options directly to the [Sentry Webpack
@@ -315,3 +302,15 @@ Enables the use of the [`runAfterProductionCompile` hook from Next.js](https://n
in any release.
+
+
+
+Enables React component name tracking. When enabled, it annotates React components with data attributes that allow Sentry to track which components users interacted with in features like Session Replay and breadcrumbs.
+
+
+
+
+
+A list of React component names to exclude from component annotation.
+
+