One thing to consider is ImageFlow (server). You can install it in DNN and then use it with querystrings doing transforms and filters and more. The docs are really nice, good examples. Processing is only done once and cached, so subsequent requests are fast.

Here is a simple example. The original image is 8 megapixels (40 MBs, not optimized).

Here it is at 1200 pixels wide
https://rrma2025.accuraty.us/Portals/0/siteContent/projects/french-country-modern/french-country-modern-backyard-pool-landscape-NY7633.jpg?w=1200

Here is the same image manipulated to cropped in to just the chimney.
https://rrma2025.accuraty.us/Portals/0/siteContent/projects/french-country-modern/french-country-modern-backyard-pool-landscape-NY7633.jpg?w=288&h=466&mode=crop&crop=48,30,60,60&cropxunits=100&cropyunits=100

Once its installed in your project and setup in your web.config, it just works. Optionally, you could also have the .NET version (uinsg .NET Standard 2.0) which would also give you a very nice C# API, but for most of our needs, using it embedded in DNN via the URL options gets us 99% of what we need.

Hé Jeremy,

Thanks for this image processing tip!

How does this Imageflow perform, compared with the already existing DNN Imagehandler? Is it easier, faster or more reliable? I find the steps to install the Imageflow (server) not so easy (or I'm overlooking it).

Also: why would you choose the server edition and not one of the other Imageflow editions?

Thanks,
Keston

Thanks Jeremy!!

How do you install it in your project? 

I don't have a custom module I want to use it in DNN and Open Content.

I believe when you install 2sxc it is included:
https://docs.2sxc.org/bas...e-resizer/index.html

It is true that 2sxc installs and configures ImageFlow for you so it can easily be used throughout your DNN instance. However, 2sxc is not necessary, using the server version it should be a straight forward install (files to /bin/folder) and config (manually modify web.config).

The reason for the server version is because it enabled DNN instance wide use of the URL parameters to rework any image (JPG, PNG, etc).

Performance should be better than the DNN built-in image handler and the available features are a very significant improvement. See my post above for a link to the docs; its a really well thought out system. 

I greatly prefer the server edition and URL parameters because it means I can use the tech anywhere in my DNN instance and get the full benefits of both the processing AND caching.

 @willem and  @Keston Pollard - its a manual install. If it seems hard, the only thing I can recommend is spinning up an extra local DNN instance (maybe using nvQuickSite) and installing 2sxc and use the web.config changes and files added to /bin/ImageFlow/ as reference for getting your instance setup.

If there is a stand-alone installer for DNN, I am just not aware of it. It would be nice if it existed.

Hi Jeremy,

Is this the stand-alone installer you were not aware of?
https://github.com/2sic/dnn-imageflow

Ciao,
Keston