--- title: WordPress images resize differently in Chrome and Firefox description: WordPress 7.2 runs resizing in the browser on Chrome but not on Firefox. A Settings toggle to restore the uniform server-side pipeline in all browsers. source: https://steem.dev/blog/wordpress-force-server-side-image-upload published: 2026-11-21 updated: 2026-11-21 site: Steem — AI WordPress plugin generator --- # WordPress images resize differently in Chrome and Firefox Upload a photo from Chrome 137 on a WordPress 7.2 site and the browser resizes it locally before anything reaches the server. Upload the same photo from Firefox or Safari and the server handles all the resizing. Both paths produce valid thumbnails. They are not the same thumbnail, because the browser uses wasm-vips and the server uses whatever image library the host installed, GD or Imagick, with its own quality defaults. For most sites that difference does not matter. For anyone who manages print-ready proofs, feeds gallery thumbnails into a pixel-precise grid, or needs to tell clients that every upload goes through the same process, it does. WordPress 7.2 added a filter to turn off client-side processing entirely and restore the uniform server path, and a Settings checkbox that controls it is a one-job plugin. ## What one build covers - Settings > Media checkbox to disable client-side processing site-wide - Reverts the Media Library grid, Add New Media File screen, and media modal to server-side processing - Works across all WordPress 7.2 upload contexts, including the block editor - No effect on non-image files or already-uploaded images ## What it does not cover - Per-user control: the setting applies to all users on the site - Non-image files (audio, video, PDF, SVG), which always used the server path - Already-uploaded images, which are not reprocessed when the setting changes - HEIC or AVIF support on the server, which depends on the host's image libraries - Any fixing of inconsistent thumbnails already on the site before the setting was enabled ## The prompt ```text Build a WordPress plugin that adds a checkbox to Settings > Media labelled Force server-side upload processing. When checked, the plugin returns false from the wp_client_side_media_processing_enabled filter, disabling client-side processing across all upload screens. When unchecked, the filter has no effect and WordPress defaults apply. Store the setting in an option. Add a short description under the checkbox explaining that WordPress 7.2 resizes images in the browser on Chrome but not Firefox, and that this option restores the server-side path for both. ``` ## Why Chrome handles the resize and Firefox sends it to the server Client-side processing depends on a Document-Isolation-Policy header that WordPress 7.2 now sends to upload screens. That header unlocks the shared-memory access that wasm-vips requires to run in the browser. Chrome 137 and Edge 137 honour it. Firefox and Safari do not yet implement Document-Isolation-Policy, so they receive it, ignore it, and fall back to the classic async-upload.php route where the server handles everything. The browser-side path applies to JPEG, PNG, GIF, WebP, AVIF, and HEIC when the platform codec supports it. Audio, video, PDF, SVG, and archives always go through the server. There is an older escape hatch too: JPEG and PNG files skip client-side processing when Scale images to fit within is enabled in Settings > Media, because that uses the plupload resize path which predates the new pipeline entirely. ## Where the vips-versus-GD gap becomes a real problem The clearest case is a team that checks image output before anything goes live. If the photographer uploads the hero image from Chrome and the developer reviews it on Firefox, they are looking at thumbnails from two different codecs. The crops will align because WordPress registered sub-sizes drive both paths, but the compression, sharpening, and colour handling come from different libraries with different defaults. A gallery layout that expects consistent thumbnail byte sizes or dimensions for a grid calculation is the second case. Both wasm-vips and GD respect the image_max_bit_depth and image_strip_meta filters, but they interpret image data differently, and a site whose grid was designed around GD output may not hold after a client starts uploading from Chrome. The third is simpler: some hosting environments with strict Content-Security-Policy rules reject the cross-origin isolation headers that enable client-side processing. On those hosts the feature will never fire even on Chrome, but WordPress still attempts it and logs the failure. Disabling the feature through the filter stops that noise. ## The filter, what it turns off, and what it leaves alone The filter is wp_client_side_media_processing_enabled. Returning false from it reverts every upload surface to its pre-7.2 path: the Media Library grid, the Add New Media File screen, the media modal, and the block editor all send images to the server for sub-size generation rather than processing them in the browser. What the filter does not change: non-image files have always gone through the server, so turning off client-side processing has no effect on audio, video, PDF, or SVG. Already-uploaded images are not reprocessed. HEIC files on browsers that cannot decode the format also stay on the server regardless of the filter, since the browser cannot read the file to begin with. A Settings > Media checkbox is the right surface for this control rather than a hardcoded filter in a theme functions file. That way the toggle survives theme changes and the person managing uploads does not need to open any file to switch it. ## Questions ### Does this affect HEIC uploads? HEIC files the browser cannot decode already go through the server, so turning off client-side processing makes no difference for those. HEIC files a Chromium browser can decode currently go through the client-side path; with the setting on they fall back to the server, which may not support HEIC without an additional extension or library installed. --- Source: https://steem.dev/blog/wordpress-force-server-side-image-upload Build this plugin: https://steem.dev/app