Included with Slideshow many products I have from DMX is the DMX image resizer. This is a great boon in many situations. Normally I import whole folders and keep the original files in a folder not included in the site files. This is because the DMX resizer puts the resized image and thumbnails in folders within the site. Personally I always switch off the feature for sharpening thumbnails, but that is a matter of taste. At first the DMX resizer seems great as it will cut down huge files to fit a specified pixel width and height. It is very much a great time saver. However, I see that although the resized files are smaller with regard to pixel width and height, the files are still very big with regard to kb size. I can take an image that has been resized in DMX resizer and run it through Photoshop save-to- web (which is not acknowledged as being the most efficient when it comes to optimizing files) and make a file which is 1/3 the size (in kb) of the resized image and still with the same pixel width and height. So I made an experiment. I first optimized a whole of load of images using PS save-to-web and made them the final pixel width and height I wanted. I then ran all these files though DMX resizer in such a way so as not to change the pixel width and height, but supposedly only to generate the thumbnails. Unfortunately what I found was that DMX resizer had made not only thumbnails, but also "resized" the main images in such a way that their pixels width and bredth were unchaged BUT the kb sizes were increased by a factor of up to 3 after the optimized images had gone though the resizer. My question is, therefore, how can I adjust the settings of DMX resizer so that it makes smaller files in terms of kb size and not just pixel width and breadth? It seems somewhat pointless to run folders of files through DMX resizer only to have to manually optimize the outputted files quite considerably. Any suggestions for a more appropriate work flow would also be appreciated.

Hello Ian,

The resizer outputs the most optimal Images Size in px/ Size in kb. You cannot change the kb size properties.

That is a shame. Pictures that have gone through DMX resizer are consuming more bandwidth than is necessary and bandwidth has again become important now we are focussing on responsive designs that also work well over the mobile network.

Also wondering about the quality settings that the Image Resizer outputs.
Are there different quality (compression) settings for large, normal & thumbnail sizes?
How do they compare to Fireworks or Photoshop (Save to Web) optimization settings?
Cheers
Dave

This reply was removed on 9/24/2015 7:17:46 AM.
See the changelog

For clients who want the stunning visuals of fireworks but are working within a limited budget or a temporary event setup, Bright-Star Fireworks offers fireworks rental options. This service is particularly helpful for one-time events, such as festivals, temporary exhibitions, or charity fundraisers, where the event organizers may not want to invest in the full cost of fireworks for future displays where to buy fireworks tasmania. By renting fireworks, you get access to high-quality pyrotechnics without the commitment of a full purchase.

It sounds like you've got a solid workflow already, but I completely understand your frustration with the DMX Resizer inflating file sizes unnecessarily. I've had similar issues in the past, and here’s what worked for me:

The resizer is great for batch resizing, but for better control over file size (in KB), I’d recommend a two-step approach. First, resize your images to the desired dimensions using Photoshop’s Save for Web or even tools like TinyPNG for compression. Then, use the DMX Resizer only for generating thumbnails, ensuring it doesn’t reprocess the main images. Sometimes, tweaking the output settings in DMX can help minimize size bloat, but it's not always enough.

By the way, if you're working with high-quality images, especially scientific or detailed illustrations, you might find some useful tips and resources at https://scientific-illustrations.com/. We’ve dealt with similar challenges and found ways to optimize without sacrificing clarity.