AI, Development & Tech News

WordPress 7.2 scales uploads in the browser: Here's what you should check beforehand

261121 wordpress 7 2 images in the browser title image
Skip to table of contents
Contents 5 sections
  1. What happens when uploading in the browser?
  2. When does the browser compute, and when the server?
  3. Where can it go wrong?
  4. What this means for you
  5. Sources

Adam Silverstein describes in a Dev Note from November 17, 2026, how WordPress 7.2 handles images during upload: Chrome and Edge from version 137 onward scale the images themselves and generate the preview sizes in the browser, and the server receives the finished files. According to the developer documentation, this has been running in the block editor since WordPress 7.1, and 7.2 extends it to the media library, the upload page, and the media dialog.

For site operators, this shifts where the computing work occurs, and some plug-ins run into outdated assumptions. The sources give no release date; the software is free of charge.

What happens when uploading in the browser?

The browser scales and rotates the image via WebAssembly and generates the preview sizes with wasm-vips, independent of Imagick or GD on the server. JPEG, PNG, GIF, WebP, and AVIF are processed; audio, video, PDF, and SVG work as before.

According to the Dev Note, the process consists of three steps: The browser sends the original to the REST interface, then delivers each image size individually afterward, and finally reports completion. As a result, more individual requests occur per upload, in our assessment; the sources give no load figures.

The developer documentation mentions two special cases: The browser decodes HEIC photos into a JPEG, and the original is retained. Animated GIFs get animated preview sizes, which can become almost as large as the original. For static sizes, you set the filter wp_generate_animated_image_subsizes to false.

When does the browser compute, and when the server?

The browser only takes over if all conditions are met. Otherwise, the upload runs through the server without any notice to users, just as in WordPress 7.1.

Läuft dein Upload im Browser?
Bedingungen laut Dev Note vom 17. November 2026 und Entwicklerdokumentation
  • Chrome oder Edge ab Version 137
  • Gerätespeicher über 2 GB, mindestens 2 CPU-Kerne
  • Netz schneller als 2g, Datensparmodus aus
  • Sicherheitsrichtlinie erlaubt blob:-Skripte
  • Firefox: Verarbeitung auf dem Server
  • Safari: Verarbeitung auf dem Server
Die Schwellen für Speicher, Kerne und Netz lassen sich laut Dokumentation nicht einstellen.
Quellen: Make WordPress Core, WordPress Developer Resources

The documentation names Chrome and Edge from version 137; Firefox is not supported, and Safari does not use the technique. The device needs more than 2 GB of device memory and at least two CPU cores, the network must be faster than 2g, and data saver mode must be turned off. In addition, a set Content-Security-Policy must allow blob: scripts, otherwise the server remains responsible.

Where can it go wrong?

Plug-ins that detect uploads via the Ajax call miss the new uploads. As an identifying feature, the documentation states that $_POST['action'] is not upload-attachment and DOING_AJAX is not set. The Dev Note advises detecting them via the REST request.

The hook wp_generate_attachment_metadata fires twice, first with the context create and after completion with update. Custom image editors via wp_image_editors do not take effect this way; the only option there is to turn it off.

On multisite installations, the browser checks each file, including preview sizes, against the storage quota. If not all sizes fit, they are missing without any message to users; if none fit, the upload fails. According to the Dev Note, an improvement is in progress. The option upload_space_check_disabled turns off the check.

Since 7.2, the editor's cross-origin isolation no longer requires rewritten HTML or a crossorigin attribute. Embedded content from other domains loads without credentials; resources behind a login or signed cookie break. The sources contain no statement on YouTube, advertising, or payment widgets.

What this means for you

Open your test environment in Chrome or Edge from version 137 and enter window.crossOriginIsolated in the browser console. If it says true, isolation is active on this screen. Then upload a photo and check the media library, featured image, and embedded content in the editor, not on the live site.

Decide where the images should be created. If you need server-side processing, for example because of a custom image editor, set the filter wp_client_side_media_processing_enabled to __return_false. You can also tie it to conditions, for example only for users without administrator rights.

If you use a Content-Security-Policy, add blob: to worker-src. On multisite installations, test the storage quota. For plug-ins that detect uploads, ask the vendor.

Adam Silverstein published the Dev Note on November 17, 2026.

Sources

Comments

Register and comment.

Continue reading

You might also like

View all articles →