Hi All, totally confused after reading threads here about image resizing etc. I’ve set “client_max_body_size” to 102400 in admin->settings-files to allow uploading from cellphones. But I cannot for the life of me figure out where to set image resizing. I’ve read some thread: [image] Resize images after uploading Feature This is now done. We’ll accept images of up to 10MB and then downsize them to the maximum allowed image size leopard and [image] Unable to resize images after uploading Bug Ok, I’ve found the bug . It happens that IO.size is cached and while we were actually downsizing the image, the algorithm was always checking the same file size… Thus resulting in an error when uploading a file larger than the image size limit… but just cannot get the image to resize. Help ?

Like I said, change “max image size kb” to a lower value.

Right … so i set the Max upload in nginx. And the resized size in discourse ?

Pretty much yeah. For nginx, you’ll need to change it via the app.yaml file in order to survive container rebuilds.

as far as I know, you should resize images yourself (in your desktop), and discourse will not resize huge images for you. the setting limits the size of the image one is allowed to upload.

You’re right. Any indication I got from meta is that max image size kb is the maximum allowed uploaded image size. Over this size and the image upload will simply be rejected. It has been said that Discourse will scale down very large images in the background; how large is very large, and how much to scale down has always remained a mystery. Now, @zogstrip, does it mean that max image size kb is actually the trigger level for the scale down itself? In other words, if I have: Max upload size in app.yaml = 20MB max image size kb = 1MB My original understanding is that uploading any image above 1MB will be rejected. Now @zogstrip is saying that as long as the image is no larger than 20MB it can still be uploaded. But then in the background it will be scaled down (because >1MB), half-dimensioned three times, essentially making it 1/64 of the size?

[image] schungx: It has been said that Discourse will scale down very large images in the background; how large is very large, and how much to scale down has always remained a mystery. It’s not a mystery if it’s written in plain text :wink: Ok, so here’s what happens when a user uploads an image NGINX accepts the image up to its “client_max_body_size” setting (defaults to 10MB, can be overwritten in app.yml) Then, we’ll convert large PNG/BMPs to JPEG to keep the filesize at bay Then, we’ll halve (up to 3 times) the uploaded image until it’s lower than the “max image size kb” site setting If the image is still larger, then we’ll reject it :boom: Then, go on with the upload process (fix orientation, crop, optimize…)

Ah. Clear as mud now. :wink: So it is not a background job that resizes after-all… It gets done at the time of the upload.

I think the description of the setting needs some serious rewriting: “The maximum image upload size in kB. This must be configured in nginx (client_max_body_size) / apache or proxy as well.” I don’t think it is accurate AT ALL.

Something like: Automatically scale down uploaded images to smaller than this size. Images too large to be resized will be rejected. Note: Do not set larger than upload size limit configured in nginx (client_max_body_size) / apache or proxy.

Resizing images after upload settings

Product Support Self-hosting

codinghorror (Jeff Atwood) October 27, 2017, 10:29am 17

Sure, what text do you think would make more sense there?

Topic		Replies	Views
Image upload size/resize question Product Support	24	6336	April 4, 2021
Resizing images after user has uploaded automatically Product Support	17	1018	April 20, 2020
Image upload error when using resizer Bug	7	2290	March 25, 2020
Unable to resize images after uploading Bug	4	2137	August 17, 2015
Image upload max size and further resizing regression issue Feature	16	4676	May 3, 2018

Resizing images after upload settings

Related topics