I wrote an addon to resize uploaded images automatically. It might share some behavior with [ImageStyles](https://github.com/pauloamgomes/ImageStyles), but I wanted to replace the uploaded images with smaller ones. A client tends to upload giant images and everytime my scripts try to create thumbnails, e. g. after cleaning the cache, it takes ages to process them.
## Addon
> **[GitHub - raffaelj/cockpit\_ImageResize: Addon for Cockpit CMS to resize uploaded images...](https://github.com/raffaelj/cockpit_ImageResize)**
>
> Addon for Cockpit CMS to resize uploaded images automatically
## Related discusson
> [@How to downsize uploaded image assets to max width/height?](https://discourse.getcockpit.com/t/how-to-downsize-uploaded-image-assets-to-max-width-height/883):
>
> Is it possible to automaticaly downsize image assets while uploading to desired max. dimensions (width, height)? Limit uploads by group vars “assets.max\_upload\_size” is not solution in my case. It would be useful to have an config options, somethink like: “assets.max\_image\_width,assets.max\_image\_height”.
## Usage
A copy of the original file is stored in `/uploads/full/filename.jpg`. The default file will be replaced with the resized file. From now on, you don’t have to create thumbnails from 8MB sized files again, but you are still able to use the original file, if you want to.
If users upload very large images, it will take a while to process the files.
There is no option in the assets manager to choose the original file, but your api autput has two additional keys:
**original keys:**
```auto
"path": "/2019/07/02/filename.jpg",
"title": "DSC07504.JPG",
...
```
**extra keys:**
```auto
"sizes": {
"full": {
"path": "/full/filename.jpg",
"width": 4912,
"height": 3264,
"size": 4390912
}
},
"resized": true,
```
## Options
Use the GUI or add options to `/config/config.yaml`.
If you set `maxWidth` or `maxHeight` to `0` (zero), the value will be ignored.
```yaml
imageresize:
enabled: true # boolean, default: false
keepOriginal: true # boolean, default: true
moveOriginalTo: original # string, default: "full"
maxWidth: 1024 # int, default: 1920
maxHeight: 1024 # int, default: 0
method: bestFit # string, default: bestFit
quality: 80 # default: 100
```
---
Hi @raffaelj
I’d like to use this addon which is exactly what I need. Before I go ahead I wanted to know if you anticipate this to be compatible with the [Cloud Storage](https://github.com/agentejo/CloudStorage) addon?
Thanks!
Hang
---
Not sure if it is related but I get an error. Below is reponse of the /upload request.
Any idea?
Thanks
Hang
```
Warning: imagesx() expects parameter 1 to be resource, null given in /var/www/html/lib/vendor/claviska/simpleimage/src/claviska/SimpleImage.php on line 457
Warning: imagesy() expects parameter 1 to be resource, null given in /var/www/html/lib/vendor/claviska/simpleimage/src/claviska/SimpleImage.php on line 416
Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/lib/vendor/claviska/simpleimage/src/claviska/SimpleImage.php:457) in /var/www/html/bootstrap.php on line 256 Internal Server Error
@gnagnu I don’t think, that it is compatible with the cloud storage. I used functions like `mkdir` and `file_put_contents`, which should be replaced with something like `$app->filestorage->write()`.
I’m not experienced with external cdn, yet, so I can’t really test it.
---
@gnagnu The addon should now be compatible with the CloudStorage addon, but I wasn’t able to test it, yet.
Version 0.2.0 has new features and I rewrote a lot of the code.
>
---
tbh, my actual need was to regenerate images from the uploaded images and the size of the regenerated images being controllable via config file. better yet, if it could generate multiple set of images ( thumbnail, medium & large). Your plugin was the closest of what i needed. Something is better than nothing 😀
---
> [@Cryptospy](#):
>
> better yet, if it could generate multiple set of images ( thumbnail, medium & large)
It can. That’s why I asked about your main use case.
---
