Lemke Software GmbH Forum

Hi and good day,

For the web, users are always very much focused on image optimation → to reduce image size load while retaining quality.

Recently I realized that a simple trick goes far to do just that:

An image (no1)
with 4154 * 2968 px and 1.8 MB

when I crop just one side - cut off some 20px the image load will be considerably less:

(no2) image
with 4154 * 2948 px will just have 520KB, which is 29% of the original!

Then of course scaling it down for the web will further reduce of load.

Question 1:
How to technically explain this big reduction of (in this case) 70%?
How is this possible?

If we can reduce the load so much while keeping the same quality (both had 72ppi), a cut of 20px is not a big deal (depends on the image of course).

Question 2:
How can this be used more intentionally?

/omarkn

Hi,

the reduction depends on the used save as quality.

Just use "Save as" instead of "Save". Now click onto options and enable the display of the file size.

Now you will see the new file size depending on the selection save quality.

Thorsten

The answer to my question earlier I would guess is:

The cutting off and then saving is a kind of save-as.
The process probably inherits the default settings from GC.

Question 3

Then where does the Save-for-web fit in in this process, this is then also a kind of save-as, only fewer steps?
They are alternatives?

/
with best regards, Omar KN, Stockholm, Sweden

Save for web does the same. But has fewer format options. The save for web is a bit historic.