Hey there, @emc2. Welcome, and thanks for posting. You’re certainly not alone regarding alpha-channel frustrations, so take solace in that. Lord knows I’ve banged my head against that wall plenty… Anywho, I went ahead and took a look at your image files, and I had a few questions.

Minor note to start, but just so I’m not getting your statement wrong, are you suggesting your Image 4 doesn’t have alpha-channel transparency? Looks to me like Image 4 is the only one with the proper data structure and file type, and hence why it is rendering just fine here. I just wanted to clarify.

Here is what I can download from your post:

Apple agrees, and has “Alpha Channel - YES” to indicate the detection of the “A” in the RGBA binary. Same as with your Image 4, the AV1 file type image, Image 1, also has “Alpha Channel - YES”. Take a look at your file types here:

… AV1, JPEG, JPEG, WebP, respectively to 1-4…

For less minor questions, first, are you daisy-chaining file type conversions of the original image file, reprinting with additional instructions plus the previous image as a seed, or inputting brand new prompts? Second, are we talking an API-based interface or in-app?

Lastly, if you’re looking for “alpha” anything, JPEG’s won’t cut it. PNG’s can get you there, but their focus on being lossless makes them a tricky customer to work with and get to render on live surfaces. In my opinion, WebP is likely your best bet for achieving alpha-channel transparency effects, but do note, I’m bias, have achieved successful alpha-channel transparency renderings with generated PNG’s, and @_j has demonstrated .gif working perfectly fine too. Good news though, you’re already generating WebP’s with proper RGBA! Wonky conversions or re-generations aside, that still puts you far along in the game.