# Why do browsers re-download files when you "save image as"? **URL:** \ **Category:** Factual Questions\ **Created:** [December 20, 2007, 7:08pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741 "2007-12-20T19:08:33Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\ **Post date:** [December 20, 2007, 7:08pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/1 "2007-12-20T19:08:33Z")
Whenever you want to save an image displayed on your browser with the “save image as” option (and I find this true at least for Firefox and IE), it fetches a new copy from the server. But it’s already got a copy, the one you’re looking at. Why doesn’t it just save that one to your hard disk? I can understand in some circumstances wanting to make sure you have the latest and greatest version of a file, but IME 99.99% of the time the one I’m seeing is identical to the “fresh” one. And if it’s a large image file, waiting for the re-download can be annoyingly time consuming. So why is it done, and is there a way around it? ---
**Author:** ![ChrisBooth12](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@ChrisBooth12](https://boards.straightdope.com/u/ChrisBooth12)\ **Post date:** [December 20, 2007, 7:36pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/2 "2007-12-20T19:36:26Z")
Because it lets you choose which format you want to save it in usually. ---
**Author:** ![scr4](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@scr4](https://boards.straightdope.com/u/scr4)\ **Post date:** [December 20, 2007, 7:41pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/3 "2007-12-20T19:41:02Z")
The browser obviously has the image in memory, but it may not have the _original file_ in memory. Once the file is decoded, uncompressed and converted into plain bitmap (or some other internal data format), why keep a copy of the original file in memory? ---
**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\ **Post date:** [December 20, 2007, 7:42pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/4 "2007-12-20T19:42:48Z")
[Responding to **ChrisBooth12** : I hadn’t thought of that, but it seems not to be true in Firefox, although IE apparently allows you to save in BMP as well as the native format. But, in principle, at least, that wouldn’t seem to require fetching a new copy of the file. If the conversion routine is part of the browser, you should be able to run it on the version of the file in memory, no? ---
**Author:** ![beowulff](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/beowulff/32/542_2.png) [@beowulff](https://boards.straightdope.com/u/beowulff)\ **Post date:** [December 20, 2007, 9:25pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/5 "2007-12-20T21:25:15Z")
It doesn’t work that way on Safari on the Mac (so maybe Safari on Windows would also work the same way). When I right-click on a image and do a save as, it saves the cached copy. ---
**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\ **Post date:** [December 20, 2007, 9:36pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/6 "2007-12-20T21:36:22Z")
[QUOTE=scr4] The browser obviously has the image in memory, but it may not have the _original file_ in memory. Once the file is decoded, uncompressed and converted into plain bitmap (or some other internal data format), why keep a copy of the original file in memory? [/QUOTE] No offense, but are you guessing, or do you know that that’s how browsers operate? ---
**Author:** ![scr4](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@scr4](https://boards.straightdope.com/u/scr4)\ **Post date:** [December 20, 2007, 9:44pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/7 "2007-12-20T21:44:29Z")
[QUOTE=commasense] No offense, but are you guessing, or do you know that that’s how browsers operate? [/QUOTE] I didn’t intend to make any definitive statements about how a browser operates. I was just making an observation, i.e. that the browser doesn’t need to keep the original file in memory. ---
**Author:** ![commasense](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/commasense/32/3017_2.png) [@commasense](https://boards.straightdope.com/u/commasense)\ **Post date:** [December 20, 2007, 9:51pm UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/8 "2007-12-20T21:51:23Z")
Okay, thanks. ---
**Author:** ![tonedef](https://avatars.discourse-cdn.com/v4/letter/t/f05b48/32.png) [@tonedef](https://boards.straightdope.com/u/tonedef)\ **Post date:** [December 21, 2007, 4:10am UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/9 "2007-12-21T04:10:17Z")
When i save a picture I have opened in firefox it doesn’t redownload this picture it just saves the one I’m viewing. I know this for a fact because i can view a 500k picture which takes me ages to open seeing as I’m on dial up. And when i click on save image as it only takes 2seconds for it to me on my computer. ---
**Author:** ![Sage\_Rat](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/sage_rat/32/399_2.png) [@Sage\_Rat](https://boards.straightdope.com/u/Sage_Rat)\ **Post date:** [December 21, 2007, 5:35am UTC](https://boards.straightdope.com/t/why-do-browsers-re-download-files-when-you-save-image-as/430741/10 "2007-12-21T05:35:34Z")
For browsers that do have this issue, my guess would be that the cause is simply that different people built the different parts of the browser and it was more of a pain for the guy who was doing the Save As code to figure out a method to verify that the file was in the cache (managed by some other guy, potentially in India), than seemed worth it.