●Change8

Migrating to Next.js v16.2.0

Version v16.2.0 introduces 2 breaking changes. This guide details how to update your code.

Released: 3/18/2026

2
Breaking Changes
2
Migration Steps
10
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

url.parserevalidateTagsharpsetImmediateRedirectTypenext-env.d.tsconfig.api.bodyParser.sizeLimitinteropDefaultRenderOptsPartialrevalidatePath

Breaking Changes

●Issue #1

feat(next/image)!: add `images.maximumResponseBody` config: This introduces a new configuration option `images.maximumResponseBody` which might affect image optimization behavior if you were relying on the previous default size limit.

●Issue #2

fetch(next/image): reduce maximumResponseBody from 300MB to 50MB: The default maximum response body size for image fetching has been reduced from 300MB to 50MB. If you fetch large images, you may need to update your configuration using the new `images.maximumResponseBody` setting.

Migration Steps

  1. 1
    If you rely on image response sizes exceeding 50MB, configure `images.maximumResponseBody`.
  2. 2
    If you were using `url.parse`, update your code to use alternatives.

Release Summary

This release focuses heavily on improving type safety within the App Router via the new `experimental.strictRouteTypes` configuration, alongside numerous stability fixes and performance improvements in Turbopack. It also introduces new developer tooling like CPU profiling and an agents-md command.

Need More Details?

View the full release notes and all changes for Next.js v16.2.0.

View Full Changelog