Saving overlay images from site?
Filter
Show Official Posts OnlyReplies
Hi!
Not sure why but I can no longer save overlay images from the wardrobe or item searches for CWs/ wearables anymore! They download as webp files and they are not compatible with photoshop to create previews. Was this supposed to happen? We used to be able to pull overlay files as png's to create our own HA previews
I am thinking this might be a browser thing? I just tried to saved the overlays in both the wardrobe and the shop search and was able to save as a png every time. Also when you are saving, sometimes it allows you to change to a png so have you tried that?
Dexter by ❤
hii thank you for the quick reply!
yea it seems like it's a chrome issue - I tried changing the file download option but it doesn't have png as an option on chrome. I guess I'll just have to use another browser to download for now ^^
apparently this is a new chrome thing - .webp is supposed to be a better-compressed lossless image format, but i'm not really sure i understand how it's supposed to work if it's not actually like... compatible with anything. i hadn't noticed it until someone pointed it out, but this explains why some images can't be simply dragged onto the desktop anymore. also the format isn't compatible with most mac software, even though it supposedly works with windows. really frustrating, i don't like it at all.
i found a little more information here. apparently sites can check whether someone is using a browser that is compatible with webp to determine whether to show them images in this format. i imagine this means you can code the site so that it doesn't run this check and just loads normal image formats, which would be ideal. in the meantime, you can use this chrome extension to add the option to right-click and "save as png" to all images. (i guess i'll have to be using this until someone figures out an extension to just get rid of webp altogether.)
so basically this is completely on chrome's end unless subeta decides to stop serving up webp images.
First, I recommend you guys check to make sure your browsers don't have any updates. My browser had the same problem, but as soon as I updated, it allows me to save PNG files as PNG again. I am using Opera, by the way, but Chrome should be similar since they both use Webkit.
Anyway...
<p>...so basically this is completely on chrome&;s end unless subeta decides to stop serving up webp images.
Unfortunately, this is incorrect. Subeta does not have control over this. The article was worded a bit confusingly so I'll try to clear it up.
The section you read was talking about maintaining backwards-compatibility with older browsers that do not know how to interpet the webp format. If a website serves an image, let's call it "picture.png", to this browser, the browser will happily render it. But if the website serves its image as a webp file - "picture.webp" that is - the older browser will not even display the image, because it can't read that data format.
So if your website wants to use "picture.webp", there are ways to detect if the browser is too old to support webp, and to send it your "picture.png" instead.
However, newer browsers like Chrome are moving towards supporting webp as the new standard, which means they're sort of doing the opposite. If you send them "picture.webp", they'll display "picture.webp" correctly. But if you send "picture.png", the new browser will take that data, convert it to webp, and display the picture.
To recap, older browsers fail if we send "picture.webp", and display PNG if we send "picture.png". Certain newer browsers, however, display WEBP if we send "picture.webp", and convert the file and display WEBP if we send "picture.png".
Subeta does not use WEBP images (nor do we plan to, in the foreseeable future). We serve the "traditional" image formats (.png and .gif mostly) to your browser. We can't control what your browser decides to do from there. I hope this makes things a bit clearer. I just wanted to clarify that I looked into this, and unfortunately it's not something we can control from the website, it's entirely up to the web browser what it does.
I think the browser extension is one solution. Another thing you can do, without installing anything new, is right-click the image and select "Copy Image" and then try to paste it directly into your image editing program, such as into a Photoshop layer or even MS Paint.
bug goes on minor rant
Personally, I feel like getting rid of the "Save as PNG" option in Webkit was a very poor choice, and I see it as an example of coders failing to consider the needs of people who aren't coders. For instance, artists have no use for WEBP if they can't edit the files in any of their art programs. It's fine to make WEBP the default as long as you 1) still offer the other options and 2) explain it to people and make it easy to opt out/turn off. I feel like most people who aren't developers are going to be confused and frustrated by this. This is disappointing to me because Google should know better. They should at least know better than to not provide a native solution for people who want to opt out.
I'm also experiencing some buggy images and I'm 99% sure that this is the problem. This entire thing just looks like a bad decision tbh, and I feel like I must be missing some side to the story because Google doesn't usually do that..? Time to bother some Webkit developers I suppose. :/
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
I did try the copy image but as before, it saves with a white background for individual overlays so not very helpful in terms of working with it for previews!! ^^ Thank you so much for the detailed explanation. It seems that it's either a mistake that should be corrected by Google or they're planning something bigger down the line that necessitates using the webp format. We'll just have to wait and see I suppose :3
Thank you again!