Manual Setup

If you can’t (or prefer not to) run the configuration step, you can follow the instructions below to configure your application.

Create Initialization Config Files

Create two files in the root directory of your project, sentry.client.config.js and sentry.server.config.js. In these files, add your initialization code for the client-side SDK and server-side SDK, respectively. We've included some examples below.

For each configuration:

import * as Sentry from "@sentry/nextjs";

const SENTRY_DSN = process.env.SENTRY_DSN || process.env.NEXT_PUBLIC_SENTRY_DSN;

  dsn: SENTRY_DSN || "",
  // We recommend adjusting this value in production, or using tracesSampler
  // for finer control
  tracesSampleRate: 1.0,
  // ...
  // Note: if you want to override the automatic release value, do not set a
  // `release` value here - use the environment variable `SENTRY_RELEASE`, so
  // that it will also get attached to your source maps

If you want to instrument Next.js API Routes, which run on serverless, you need to wrap your handler in our withSentry wrapper in order to be able to capture crashes:

import { withSentry } from "@sentry/nextjs";

const handler = async (req, res) => {
  res.status(200).json({ name: "John Doe" });

export default withSentry(handler);

You can include your DSN directly in these two files, or provide it in either of two environment variables, SENTRY_DSN or NEXT_PUBLIC_SENTRY_DSN.

Extend Next.js Configuration

Use withSentryConfig to extend the default Next.js usage of Webpack. This will do two things:

  • Automatically call the code in sentry.server.config.js and sentry.client.config.js, at server start up and client page load, respectively. Using withSentryConfig is the only way to guarantee that the SDK is initialized early enough to catch all errors and start performance monitoring.
  • Generate and upload source maps to Sentry, so that your stacktraces contain original, demangled code.

Include the following in your next.config.js:

// This file sets a custom webpack configuration to use your Next.js app
// with Sentry.

const { withSentryConfig } = require("@sentry/nextjs");

const moduleExports = {
  // your existing module.exports

const SentryWebpackPluginOptions = {
  // Additional config options for the Sentry Webpack plugin. Keep in mind that
  // the following options are set automatically, and overriding them is not
  // recommended:
  //   release, url, org, project, authToken, configFile, stripPrefix,
  //   urlPrefix, include, ignore

  silent: true, // Suppresses all logs
  // For all available options, see:

// Make sure adding Sentry options is the last code to run before exporting, to
// ensure that your source maps include changes from all other Webpack plugins
module.exports = withSentryConfig(moduleExports, SentryWebpackPluginOptions);

Make sure to add the Sentry config last; otherwise, the source maps the plugin receives may not be final.

Configure Source Maps

By default, withSentryConfig will add an instance of SentryWebpackPlugin to the webpack plugins, for both server and client builds. This means that when you run a production build (next build), sentry-cli will automatically detect and upload your source files, source maps, and bundles to Sentry, so that your stacktraces can be demangled. (This behavior is disabled when running the dev server (next dev), because otherwise the full upload process would reoccur on each file change.)

To configure the plugin, pass a SentryWebpackPluginOptions argument to withSentryConfig, as seen in the example above. All available options are documented here.

If you want or need to handle source map uploading separately, the plugin can be disabled for either the server or client build process. To do this, add a sentry object to moduleExports above, and set the relevant options there:

const moduleExports = {
  sentry: {
    disableServerWebpackPlugin: true,
    disableClientWebpackPlugin: true,

If you disable the plugin for both server and client builds, it's safe to omit the SentryWebpackPluginOptions parameter from your withSentryConfig call:

module.exports = withSentryConfig(moduleExports);

In that case you can also skip the sentry-cli configuration step below.

Configure sentry-cli

The SentryWebpackPlugin uses sentry-cli to manage releases and source maps, which can be configured in one of two ways - using configuration files, or with environment variables - both of which are discussed below. For full details, see the CLI configuration docs.

If you choose to combine the two approaches, the environment variables will take precedence over values set in the configuration files. One common approach is to set sensitive data (like tokens) in the environment and include everything else in the configuration files added to your VCS.

The URL, organization, and project properties identify your organization and project, and the auth token authenticates your user account.

Use Configuration Files

You should commit all the properties to your VCS, except the auth token. You can accomplish this by using two files: including the properties of your organization and project, and .sentryclirc including your auth token. This is the approach taken by the wizard and it allows you to commit the former while ignoring the latter in your VCS.

Here is an example:
# cli.executable=../path/to/bin/sentry-cli

Add the token to .sentryclirc:


And don't forget to ignore .sentryclirc in your VCS.

Use Environment Variables

Alternatively, the cli can be configured using environment variables.

Property nameEnvironment variable
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) to suggesting an update ("yeah, this would be better").