Bug Reports

This bug started happening in one of the latest versions, possibly in the last half a year. When selecting pixels in the same layer, moving them over existing pixels and then deselecting & undoing the operation, PS deletes the bottom pixels. This also happens when adding to selection. This behavior did not happen in previous versions of the program and defiantly feels weird. 

Photoshop 21.0: Continually crashes on macOS 110.14.6 if ADOBE color picker is selected, if Appel color picker, no problem.This problem is only in Style editor wehen we change any color ????

Just installed the update to Photoshop CC 2020 but Lens Blur now fails to work. I get a total checkerboard effect and if I click OK the filter simply fails and leaves the image blank/checker-boarded. HELP !!!

So I've noticed after the 2020 update, the gradients are behaving strangely, I don't know if this is a bug or a change of how it functions. If it is the latter please change it backIf you insert a shape layer and change its fill to a radial gradient...If you then try to squash the circle, say to create a shadow under somethingThen commit the shape transform, the gradient doesn't change with the shape, instead, it reverts to the same aspect gradient in which you start.This occurs even with the Layer Style > Gradient Overlay method, it will still not function correctly. The only way around this I have found is to make the gradient as in step 1, Rasterise the shape, then transform. This is way more destructive than the old method of the gradient just transforming with the shape.let's get this either sorted or changed back 

Before PS v21 update size of paragraph box was changing correctly in properties panel, now it started distorting text inside.+ suggestion to add functionality to select multiple paragraph boxes and change sizes at once not one by one.

In PS 2019 when you create a depth map and go to Filter>lens blur, and activate the Depth Map, you can no longer click on the image to change the depth of field accurately.  Clicking does not pick up the accurate value form 0-255.  You have to move the slider to get all the values

While I understand that using STL files from Thingiverse aren't guaranteed in any way to work in Photoshop... I have an STL file that used to work flawlessly in CC 2018 and is now utterly unworkable in CC 2019. I've got the latest version as of this posting date.Model looks like this:(There's a bunch of domes).In CC 2018, opening the file immediately results in a UV map that looks like this:The round parts are the domes, and it all paints quite nicely.In CC 2019, opening the file results in a prompt to generate UVs. The generated UV looks like this:It is unusable. The result is the same with/without the preserve appearance checkbox.Additionally!!!!The exact same tool-tip appears for all 3 of these options in the Generate UVs dialog. 

When converting anything into a smart object layer, the shortcut ctrl+alt+shift+t produces inconsistent and unrelated (to what was the transformation) results. This was verified by other Photoshop users on the Adobe forum. This has been going on for quite some time now. 

Users have reported enormously bloated files where the issue appears to be spurious entries in the photoshop:DocumentAncestors XMP tag. I was provided some sample files and found tens of megabytes of data disappeared from each file when I removed that tag.The file that I was given was created in Photoshop CC 2017 for Windows.While not absolutely certain, evidence seems to suggest that the corruption is being produced in Photoshop, under conditions that I haven't been able to reproduce. As opposed, for example to it traveling around the internet on infected files (which may well be happening as well)See this thread in the Adobe user forums  https://forums.adobe.com/message/10371400  (my comment is at the bottom as I write this.) Or this thread (look near the bottom) https://forums.adobe.com/thread/2382524?start=40&tstart=0   and this blog post   http://prepression.blogspot.com.au/2017/06/metadata-bloat-photoshopdocumentance

Photoshop 20.0.6 file extension (ex .jpg) not changing during format change on macos Catalina.

Hello,using the tool Free Transform (Ctrl+T) in the new version of Photoshop CC 2019 (release 20.0.0) on a Windows 10 64 bit PC, I'm not able anymore to move the handle of a selected area (using the Ctrl button) in a free mode, now I can move it along the vertical or horizontal ax only.Which setting I have to change in order to have the same behavior of the tool as in Photoshop CC 2018 (release 19)?Many thanks!!!Luciano

Windows 10Photoshop v20.0.1___Why is nobody talking about this???After you've non-proportionally scaled a text layer, be it by accident or intentionally, that text layer is permanently ruined and you must copy the text out, convert it to plain text, then paste it back into Photoshop.The Character Panel is unaware of a text layer having been scaled, as is the toolbar in the top left where transform settings can be input during the transform process.There is no way I'm aware of to undo transform scaling to a text layer, or reset it back to normal.See my tests below:Top Row:Original, unedited/non-transformed text layer.Middle Row:Copied my original text layer twice. Transformed one and squashed it to be much narrower. Transformed the other one to be really long/wide.After doing this, when I select said text and view my Character Panel, I'm mislead to believe the text hasn't been scaled when I know it has. I'm told the horizontal scales are "100%" when in fact they are not.Bottom Row:Copie

I just recently updated to Adobe Photoshop CC 2019, and my healing brush tools and clone stamp tool lags when I use it.  I had no prior issues with CC 2018.  What gives?

ADOBE, PLEASE, FIX THAT BUGS! ADD ACCURATE PERSPECTIVE MATCH TOOL!PS calculates horizontal field of view wrong, IT'S A BUG!!! See the proof. As you see PS says us that in this canvas size we've got a horizontal FOV like 75 and vertical 30. But it's a mistake. The real Horizontal FOV must be 67.6The simple formula proves itcanvas width w = 5000 pixelscanvas height h = 2000 pixelsd = 3732,73 (distance to the center of projection)Horizontal FOV 2 tan-1 ( w / 2d ) = 67.6Vertical FOV 2 tan-1 ( h / 2d ) = 30So if you try to save an image from PS and then create the same canvas size in Adobe Dimension CC or in any other proper application and use the saved image from PS as a background, then will put camera FOV 75 degrees you will certainly see that perspective of this cube will not match. But if you put in FOV the value like we've got in the formula above (67.6 degrees) the perspective will fully match because it's correct, it's simple trigonometry.  Image is not availabl

(Maybe this has been reported previously, but I did not find it) Previously (at least in PS CC pre-2014), I was able to hold "Alt" while left clicking in the "Create new fill or adjustment layer" button at the bottom of the layers panel - this way, after choosing the desired fill/adjustment layer, I could access a dialog where I could name the layer and adjust some options before actually creating it. But with the current version, I can't, although it does work if I click with the *right* button while holding Alt . Is this the intended behavior now? I'm running Win 8.1 and PS CC 2014.2.2 (20141204.r.310 x64).

Here are just a few bugs I found to help the adobe team out.1.) Eyedropper Tool "Current and Below" not working properlyThe eyedropper tool for sampling colors on "current layer and below" doesnt always work when my layers are inside of a group folder with a cliping mask added to that folder. This bug actually has been going on for several versions of photoshop too Mac/and PC.Actually I made  a file that replicates the bug. Please take a lookhttp://coreyloving.com/TEMPSTuff/EyeDropperCurrentAndBelow.psd2.) New View> Flip Horizontal Dual Windows BugWhen using the new View>Flip Horizontal with a second window. If you keep flipping that 2nd window after awhile it seems to mess with the UI of photoshop causing UI glitches/slowdown. Like for example the layers panel and other windows start acting up and freezing. This happens to me on my Mac at work, but I dont think I got it to happen much on my windows PC at home.3.) New Color Wheel BugFor me I have my panels pinned to the side

Brand new CC install on new Windows 10 install, new hard drive. Exporting via SFW.I had copied over one custom setting file to ~\AppData\Roaming\Adobe\Adobe Photoshop CC 2019\Optimized Settings\ but it wasn't showing in the SFW Preset list.Decided to create a new preset, and Photoshop offered to save it in the CC 2018 folder instead of CC 2019. Cancelled that and copied my old preset into CC 2018 and verified that it showed up in SFW.

Photoshop CC 2015.0.1. I record action - "Save As" using JPEG2000 format (80% quality, lossy). After that I open Automate-Batch and call recorded action to folder. Unfortunately saved files are incorrect - many times larger than supposed to be. And save process is very long. My source files are 16-bit TIFFs with non-sRGB color profiles.

For this issue, the color picker has to be set to "Current & Below", or "Current & Below, No Adjustments."The problem is if you try and color pick your current layer inside a group that has any kind of layer clipped to it, it will ignore your current layer and only pick underneath it. In some areas, it sometimes picks the proper color, but typically it just ignores the current layer. The only way to resolve this is to unclip the layer from the group, turning it off doesn't help. This has been verified as a bug in CC 2015.5 and CC 2017, all versions, by both me and a colleague on separate machines, both PC. I haven't tested any other CC versions, but it is NOT an issue in CS6.Interestingly, on lower resolution files, it sometimes goes away, but it's persistent on higher res files. Also, in SOME documents, changing the sample to 3x3 rather than point, it will pick up the proper color in more areas, but is still glitchy. I wonder if the cache levels on the document might

export layers to files is merging each layer with one other layer on export. I have a bunch of text only layers and half a dozen regular image layers.  I'm exporting png24.   I've used this feature extensively and today it starts doing this.  I finally found a work around - I put a blank text layer at the bottom of all my text layers and at least now I can't see the overlay.  Also, export layers to files only seems to work right if I set my visiblity and choose Visible Layers Only.  Any other choice causes the program to terminate early with some sort of "delete isn't available" or something.

When you use Export As for an Artboard the granularity is 1%, i.e. if you enter 0.625 it is rounded up to 0.63. This is a massive limitation when it comes to exporting artboards and is an issue that was not in 19.1.6, where it worked fine.

When I try to copy and paste Japanese kanji with ruby above it into a text field, only the ruby pastes. I'm copying from a .docx document if that makes any difference. This page explains what ruby is https://en.wikipedia.org/wiki/Ruby_character.

Hello,I am a photoshop user and i desperatly need to use the overlay preview in masking. This can be done on english keyboard with the \ shortcut.But it does not work with french keyboard, photoshop tells me I should do CTRL + \ but, on a french keyboard, we have to press ALT GR to make the \, and photoshop does not recognize CTRL + ALT GR + \I know this can be done manually in the "channel" tab but I want to do it fast with a shortcut.So please, can you make this shortcut assignable ?

Hi! The following issue has been around for years. And if you are not careful you might loose your work!Here's the issue:When I am done with an image in photoshop I have created an action to save different versions of my file like: layered PSD file, flatened TIFF, Low Res JPG.The save paths lead to different folders on a network drive (Synology NAS). So far so good. Works like charm. BUTthe next time I turn my Mac and NAS back on, the action uses a random path! Sometime it even puts in a weird filename. So there is a huge chance that existing files will be overwritten.It mostly happens that one or two paths will be random and one stays as it has been set by me. If you are not super aware of this it can LEAD TO DISASTER!Why is that Adobe?Could you pleas fix that Adobe!A fix would be highly appreciated.Thank you.

Since I upgraded from Photoshop CC 2015 to CC2019 it has been a torture to work with Photoshop. Very laggy performance, polygonal lasso tool very slow when autoscroll to the left (even with Shift pressed). The properties tab doesn't close when clicking on "X" button, but it closes when you try to move the window.The redraw is very slow, with several problems of visualization. For example, if I have 2 files open and I wanna flick from one file to another (Ctrl+Tab) my screen doesn't update and I need to undock it the from tab to redraw my screen.Almost every time, if I'm working with my file docked in Tab mode, all the shortcuts stop to work and I need to undock in order to have the shortcuts working again.In summary, its impossible to work healthy.I've checked already and tried different settings on Preferences, but nothing has changed.I've tried to remove Adobe CC products from my machine and reinstall from scratch, but nothing has changed.All the drivers are updated to the lates