Seen from the server side, there is absolutely no technical difference between "transferring for viewing in a browser window" and "downloading for storage".
Maybe a server will provide a (smaller) preview and the (larger) real image for download, and can distinguish which one has been accessed. But it can register (and log) only the access to these files, the IP address the request came from, a generic "id string" of the browser software - not the intent of a client.
But file access does not always result from human interaction with a client computer. On the one hand, browsers store images and other website data on your system even if you don't even use "save image as...". On the other hand, many browsers even "follow links" (that is: download things!) in advance, to speed up navigation. The browser cache even might get into your local backup that way, even if you never willfully accessed these files!
Finally, using "save as" and cancelling (not selecting a destination filename) may or may not initiate a download, depending on the implementation of the browser you are using.
4Registered as such by whom? Many log analysis software (ie awstats, goaccess) considers a download any file with a particular suffixes (.zip, .pdf...). The list of extensions is usually configurable. Other software may use different approaches. – jjmontes – 2019-01-14T15:06:00.387