[wp-trac] [WordPress Trac] #64411: Media Library - Large Image Size Uploads
WordPress Trac
noreply at wordpress.org
Mon Dec 15 15:14:36 UTC 2025
#64411: Media Library - Large Image Size Uploads
-------------------------+------------------------------
Reporter: irgordon | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Media | Version: 6.9
Severity: normal | Resolution:
Keywords: | Focuses: performance
-------------------------+------------------------------
Comment (by adamsilverstein):
Hi @irgordon - thanks for the ticket... left some questions and comments
below:
> By enforcing a chunk_size (e.g., 1024KB) within the plupload parameters
filter, we can segment the upload into smaller HTTP requests.
Interesting idea. What are the pros and cons of this approach? does it
work for all servers/clients? (I wonder why we chose the current approach
originally, was the chunked approach suggested/discussed?).
> We should consider handling these exceptions more gracefully or allowing
the threshold to be bypassed programmatically via big_image_size_threshold
when memory is detected to be insufficient, preventing the "hanging"
upload experience.
You can bypass the resizing behavior already, try this filter:
`add_filter( 'big_image_size_threshold', '__return_false' );`
> Finally, we should look at the prioritization of WP_Image_Editor
implementations. GD struggles with large pixel buffers compared to
ImageMagick; preferring Imagick where available would mitigate memory
exhaustion during resizing operations.
We already prefer Imagick when both GD and Imagick are available to handle
a given upload format. So I'm not sure what change you are suggesting
here.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/64411#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list