Not working with WordPress 4.9.2

Indeed, it could hook into the process later, but it doesn’t. I implemented the same code in the EWWW Image Optimizer, and what I found out, was that if you resize the image later, it uses a lot more memory.
I don’t know exactly why it does that, although I have my theories, but it does.

There are a lot of other plugins that resize images during upload, and I’m not sure what other plugins are doing, but I know Imsanity and EWWW IO both use the wp_handle_upload filter.

Ninja Forms could just replicate the apply_filters() call for wp_handle_upload here: https://developer.www.ads-software.com/reference/functions/_wp_handle_upload/

Ok, sorry I’m way out of my league here.

So if you hook the process here: wp_update_attachment_metadata(), like the ninja guy said, it’ll use a lot more memory?

Which is something I definitely do not want. This is exactly why I downloaded your plugin because yours replaces the original one with the resized one.

I’m going to reach out Ninja Forms again with your suggestion.

THANK YOU FOR YOUR TIME!

Oh yeah, I didn’t mean for you to do anything with that, other than pass along the information to Ninja Forms.

To answer your other question though: yes, it uses more memory if deferred until the wp_update_attachment_metadata filter.

The main reason, I think, is that the original image is larger still when the thumbnails are generated, so it uses more memory loading the original for the resize generation. It’s usually most problematic when someone uploads images 5MB or larger. A JPG of that size can use up 10x more memory than it’s filesize. Please note, this is “working memory” (RAM), not “storage memory” (disk space). In other words, it’s the “temporary” memory that programs use when they are actively working on something, and it is much more limited than the available storage.