Telemetry
Next.js collects completely anonymous telemetry data about general usage. Participation in this anonymous program is optional, and you may opt-out if you'd not like to share any information.
Why is telemetry collected?
Next.js has grown considerably since its release, becoming the de-facto React Framework for developers. Prior to telemetry collection, making decisions about how to improve Next.js was a very manual process.
For example, Vercel dogfoods many large React applications (including the Next.js website). Additionally, we actively engage with the community to gather feedback.
However, this approach only allows us to collect feedback from a subset of users. This subset may have different needs and use cases than you. Telemetry allows us to accurately gauge Next.js feature usage, pain points, and customization.
This data will let us better tailor Next.js to the masses, ensuring its continued growth, relevance, and best-in-class developer experience. Furthermore, this will allow us to verify if improvements made to the framework are improving the baseline of all applications.
What is being collected?
We track general usage information, such as Next.js plugins and build performance. Specifically, we track the following anonymously:
- Command invoked (
next build,next dev, ornext export) - Version of Next.js
- General machine information (e.g. number of CPUs, macOS/Windows/Linux, whether or not the command was run within CI)
- What Next.js plugins are present in your project
- Duration of
next buildand size of application (total number of pages)
Note: This list is regularly audited to ensure its accuracy.
You can view exactly what is being collected by setting the following environment variable: NEXT_TELEMETRY_DEBUG=1.
When this environment variable is set, data will not be sent to us.
The data will only be printed out to the stderr stream, prefixed with [telemetry].
An example telemetry event looks like this:
{
"eventName": "NEXT_VERSION",
"payload": {
"version": "9.0.5-canary.2",
"isDevelopment": false
}
}What about sensitive data (e.g. secrets)?
We do not collect any metrics which may contain sensitive data.
This includes, but is not limited to: environment variables, file paths, contents of files, logs, or serialized JavaScript errors.
We take privacy and our security very seriously. Next.js telemetry falls under the security disclosure policy.
Will this data be shared?
The data we collect is completely anonymous, not traceable to the source, and only meaningful in aggregate form.
No data we collect is personally identifiable.
How do I opt-out?
You may opt out-by running next telemetry disable in the root of your project directory:
npx next telemetry disableyarn next telemetry disablepnpm exec next telemetry disablebun next telemetry disableYou may check the status of telemetry collection at any time by running next telemetry status in the root of your project directory:
npx next telemetry statusyarn next telemetry statuspnpm exec next telemetry statusbun next telemetry statusYou may re-enable telemetry if you'd like to re-join the program by running the following in the root of your project directory:
npx next telemetry enableyarn next telemetry enablepnpm exec next telemetry enablebun next telemetry enableYou may also opt-out by setting an environment variable: NEXT_TELEMETRY_DISABLED=1.