Payload CMS v3.82.0 & v3.82.1 Released: TypeScript Hooks, Media Improvements & Next.js 16.2.2 Requirement

Payload CMS v3.82.0 & v3.82.1: What’s New

Payload CMS has shipped two new releases in quick succession — v3.82.0 (April 8, 2026) and v3.82.1 (April 9, 2026) — bringing meaningful developer improvements, important bug fixes, and a new minimum Next.js version requirement. Here’s a full breakdown of what changed and what you need to do.

🚀 New Features in v3.82.0

TypeScript postProcess Hook for Type Generation

One of the headline additions is a new typescript.postProcess hook that fires after Payload generates your TypeScript types. This gives developers a programmatic way to modify or extend generated types — a long-requested feature for teams with complex type customization needs.

Media File Disambiguation via Query Parameter

Payload now supports disambiguating media files by prefix via a query parameter. This resolves edge cases where files with identical names in different upload collections could conflict, improving reliability in multi-collection media setups.

Improved Default Slugify Utility

The default slugify utility now trims whitespace before processing, preventing slugs with leading or trailing hyphens — a small but impactful quality-of-life fix.

Plugin Improvements

plugin-redirects: Added Portuguese translation support
plugin-search: The beforeSync hook now receives the collection slug, enabling more targeted sync logic
UI: Drag-and-drop components are now exported from the @payloadcms/ui package

🐛 Key Bug Fixes in v3.82.0

Next.js HMR Fix — Minimum Version Bumped to 16.2.2

A critical fix addresses Hot Module Replacement (HMR) issues in the Payload admin panel. As a result, the minimum required Next.js version has been bumped to 16.2.2. If you’re running an older version of Next.js 16, you’ll need to upgrade before updating to Payload v3.82.0+.

Storage Fixes

S3: Redundant re-uploads are now avoided when a file was already uploaded by the client (with comprehensive E2E tests added)
Azure: Fixed MIME type handling for streaming uploads

UI Fixes

Fixed relationship filter showing duplicate options when switching operators
Fixed missing unpublish button for globals and incorrect version count incrementing after unpublish
Fixed radio fields not reliably triggering admin.condition re-evaluation on sibling fields
Fixed admin meta title rendering [object Object] in browser tab when using object form

Multi-Tenant Plugin

Fixed an infinite API calling loop that occurred on user switch — a significant stability fix for teams using Payload’s multi-tenant plugin.

⚡ Performance Improvements in v3.82.0

Validation is now skipped for default timezones, reducing unnecessary processing overhead on every save operation.

🐛 Bug Fixes in v3.82.1

The patch release v3.82.1 followed just one day later with targeted fixes:

Next.js config: Fixed incorrect config key used for disabling Turbo server fast refresh
plugin-nested-docs: populateBreadcrumbs is now properly awaited in resaveChildren, preventing race conditions
storage-s3: Avoids unnecessary getObject calls when the ETag matches — a meaningful S3 cost and performance improvement
Documentation: Fixed incorrect select syntax example in querying docs

What You Need to Do

If you’re upgrading to Payload v3.82.x, here’s your checklist:

Upgrade Next.js to 16.2.2 or higher — this is now a hard requirement
Run npm install @payloadcms/next@latest (or your package manager equivalent)
If you use the S3 storage adapter, review your upload logic — redundant re-upload prevention is now active
If you use the multi-tenant plugin, test your user-switch flows after upgrading
Check your TypeScript type generation pipeline if you have custom post-processing — the new typescript.postProcess hook may simplify your setup

Key Takeaway: Payload CMS continues its rapid release cadence in 2026. The v3.82.x releases are developer-focused, tightening the Next.js integration, improving TypeScript tooling, and squashing storage and UI bugs. The Next.js 16.2.2 minimum requirement is the most important breaking change to be aware of before upgrading.

Hashtags: #PayloadCMS #NextJS #WebDevelopment #TypeScript #Headless CMS #JavaScript #OpenSource

Resources: