Opt out
A privacy policy prohibits framework usage reporting.
Next.js 16+ · Command
next telemetry
next telemetry manages Next.js's optional anonymous usage-data collection. Enable, disable, or inspect it from the project root, with environment variables available for debugging or opt-out.
How it works
The next telemetry command controls Next.js's optional anonymous usage-data collection. Run it from the project root with enable, disable, or status; use NEXT_TELEMETRY_DEBUG=1 to inspect what is collected, or NEXT_TELEMETRY_DISABLED=1 to opt out through the environment.
Syntax
next telemetry [enable|disable|status]Parameters
| Name | Type | Description |
|---|---|---|
-h, --help | flag | Displays command help and available options. |
--enable | flag | Enables Next.js telemetry collection. |
--disable | flag | Disables Next.js telemetry collection. |
Returns
Changes or reports the local telemetry-collection setting; the command does not return application data.
Key points
- Next.js collects anonymous, aggregate usage information.
- The command supports help, enable, and disable options.
- Disable collection with
next telemetry disable. - Use
next telemetry statusto inspect whether collection is enabled. - Re-enable collection with
next telemetry enable. - Set
NEXT_TELEMETRY_DISABLED=1to opt out through the environment.
Common mistakes
- Telemetry participation is optional; disable it when the project or organization does not permit collection.
- Run the command from the project's root directory.
Example: Manage telemetry
npx next telemetry disable
npx next telemetry status
npx next telemetry enableDisables telemetry, checks its current status, then enables it again.
When to use it
Check status
A developer wants to inspect the current setting.
Opt in
A team chooses to participate after previously opting out.
Related
NEXT_TELEMETRY_DEBUGNEXT_TELEMETRY_DISABLEDnext telemetry enablenext telemetry disablenext telemetry status