• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
14

Transparent checkerboard background bug. Photoshop unable to display transparency properly.

New Here ,
Sep 27, 2023 Sep 27, 2023

Copy link to clipboard

Copied

Hey folks!  For many, many years Photoshop had no issues displaying smooth gradients over the default checkerboard transparency background, but in recent years that is no longer the case.  After scouring this community for answers I've found several others reporting this bug, only to be essentially told to "deal with it" or work around it.  This is unacceptable, and I don't believe this issue is intended behavior. Photoshop did not have this problem for some ~20 years I've been using it.

 

To highlight the problem, I've taken a series of screenshots. Please also note this bug persists on multiple PCs and Macs with a wide variety of displays, bit depths, and color profiles, etc. so I don't believe the problem stems from hardware or color settings.

 

The meat of the issue is that Photoshop can't seem to display smooth gradients over the default checkerboard transparency background. The example below shows two different gradients (linear & radial) created with the gradient tool, plus a brush stroke with 0% hardness, all of which should produce a smooth transition from black to transparent.

bad_alpha_photoshop_(white_BG).png

 

As other members of the community have pointed out, the issue is made less aparent when a solid background is enabled behind the layer with transparency. The below image is the exact same as the above, only with white bg enabled.  I also cut out a portion of the white BG so show how drastic the soft brush stroke changes over the transparent background.

bad_alpha_photoshop.png

 

Now other members have claimed that the issue disappears entirely when a solid background is enabled, but the images below prove that the problem persists (to a smaller degree) even when the background isn't checkerboard.

 

Over checkerboard:

Shadow_PS_bad_alpha.png

Over white looks better than the checkerboard, however...(see next image)

Screenshot 2023-09-27 at 11.43.50 AM.png

 

If I zoom in all the way, you can still see the faint outline of these tire-tread looking artifacts, even with the solid white background enabled.  This proves it's not just the checkerboard.

Screenshot 2023-09-27 at 11.44.28 AM.png

 

Some members have correctly pointed out that this is only a problem with displaying the transparency within Photoshop, which appears to be correct. For instance, if I take a PNG created in Photoshop (with the same jagged shadow shown above) and open it in Gimp, there are no signs of the artifacts. While it's reassuring that the exported images from Photoshop don't have the artifacts, I believe strongly that the output should match what you see within program.  I shouldn't have to open up Gimp just to see how my Photoshop shadows look with transparency.

(GIMP screenshot)

Show_Heel_Shadow_Gimp.png

 

If I open that same (24bit) PNG again in Photoshop, the artifacts persist. (Notice the tire-tread artifacts in the shadow.)  This is the exact same file as the one above (arrows added to show the different shadow with the unwanted tire-tread looking artifacts).

Heel_PS_bad_alpha_arrows.png

 

Now some may say this is a minor or non-issue, but I can tell you it is negatively affecting my professional workflow.  I often have to deliver PNG files with transparency to other artists, and it causes significant delays when they open the file in Photoshop and see these horrible looking shadows.  Since they are often PNGs, I cannot always send them a file with a solid background just to they can see the shadow properly.  It also slows my workflow down if I have to keep turning on and off a solid background just to see what a final PNG deliverable might look like.

 

To be clear, Photoshop should be displaying transparency properly over the checkerboard background.  Anyone who says this is intended behavior, or that I should just use a solid background is unfairly excusing a significant and troublesome bug which should be fixed immediately.

 

Thanks for reading. Hopefully this post helps shine some light on this long-standing bug. 

TOPICS
macOS , Windows

Views

958

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe
Community Expert ,
Sep 27, 2023 Sep 27, 2023

Copy link to clipboard

Copied

Hi @Joust not sure what different actions or answers you expect from this post.

 

While this may seem like a new issue to you, this has been an issue with rendering transitions in a grid view for decades. This isn't a bug moreso an unexpected side effect of attempting to view transitions on the gridded background. The solution is to view your subtle transitions on the light grid view or a white background.

 

You could create a simple action tied to a keyboard shortcut/F key to add a solid white backround layer at the bottom of your file to preview transparency then simply delete before saving out your final .png.

 

Not trying to trivalize your workflow, but there are means to reduce or eliminate the negative impacts.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 30, 2024 May 30, 2024

Copy link to clipboard

Copied

LATEST

Hi Kevi!

 

I'm not quite sure whether you've gotten used to this surreal behavior over said decades to the point of complacency, or just know of some underlying spaghetti code nigh impossible to get around at this point that we don't, but this is indeed a bug. Unexpected side effect is one of the definitions of bug, after all, lol.

Your suggestion, while workable, is kind of ridiculous having to be proposed, consdiering the issue is on Adobe's part.

 

To illustrate my point: the issue becomes super obvious once you set custom grid colors, both white. The transparency will stay weird, but if you add a white background layer, it will magically be fixed. Same background content, wildly different mix curves - see attachments. Even better, if you put the same checkerboard pattern in the background layer, it will still render transparency correctly, as long as it's not the native transparent background.

 

Why can't PS do this correctly right off the bat is beyond me, but it definitely isn't as mystical as you make it out to be, since the software is more than capable of handling color and alpha mixing. It just seems uwilling to in this case for some weird reason.

 

Have to agree with OP and ask Adobe why they haven't addressed this for so long. Just checked PS CS2, and couldn't believe that this is exactly the same level of jank there, unlike how I remembered. Could it be related to Windows 11 or AMD drivers in any way, I wonder? Wild thinking that this is how it's been for so long, yet I've only noticed it nowadays.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 27, 2023 Sep 27, 2023

Copy link to clipboard

Copied

Thanks for the response @Kevin Stohlmeyer.  While I agree with you that there are workarounds for this, I disagree that it should not be considered a bug.  Photoshop did not always have this problem, and other software image editors do not have this problem.  Photoshop is arguably the world leading image editing app, and I don't feel out of line expecting the transparency preview to be accurate.

 

Are you saying the bug should simply be accepted by the community?  Are you saying we should not have an accurate transparency preview?  Should the editor be showing a different image than what is to be exported on save?  Should I have to make a custom action or bind a keyboard shortcut to workaround the unexpected behavior?  Should other users have to scour these forums to understand why their gradients are all borked inside the app?  I do not believe so. 

 

Whether or not the problem has been around for decades, it's not too late to address it now. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 12, 2024 Feb 12, 2024

Copy link to clipboard

Copied

This bug has been driving me crazy for years. I totally agree… this issue needs to be addressed by Adobe.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 12, 2024 Feb 12, 2024

Copy link to clipboard

Copied

Screenshot 2024-02-12 at 6.26.52 PM.png

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines