Bug Reports

v23 has brought a lot of problems so far on my Surface; first the touchscreen crashes, and now the difficulty accessing my own body of work. Why am I getting this error, and why only on my Surface?     I can download the file through the web interface as a PSD, and then open it and save it as a new Cloud Document, but that's obviouly not an ideal situation.The Cloud Docs all open on my Windows desktop without any problems. Both devices are running Windows 10 21H1, both are running Photoshop 23.0.1.Does anyone know what might cause this?

Hi, When I start to have multiple layers on a file Photoshop crashes when adding adjustment layer of making a free hand selection with lasso tool.  I tried all the workaround suggested on the help page, what can do now ? Thanks for the help. - Photoshop 23.0.0 MPB 2019 AMD Radeon Pro 5500M 8 Go, 64 RAM MacOS 11.6

After the update to Photoshop CC 2020 (now 21.1.2), there are problems with working on the Wacom tablet: elements (especially smart objects and layers grouped in group folders) jump back and forth when moving and cannot be placed precisely. This happens on several computers with different tablets. This does not happen with other programs (inkluding Photoshop 2019, Adobe Illustrator CC 2020, Indesign CC 2020, Open Office, operating system and including Photoshop 2019). The mouse is working proper.   View example: https://www.dropbox.com/s/ws1k63n9epfcxfg/wacomspringen3beispiele.mp4?dl=0   I had called the Adobe support before and was finally referred to Wacom. After writing extensively with Wacom Support and performing various tests without success, I was referred back to Adobe (because the problem is only in Photoshop) and write with the Adobe support again – but without result. Now they send me to the forum.   My Setting (s):   x Wacom Intous 4 XL (PTK-1240)  

It is so annoying. For years this bug is not fixed in the German version: Tool tips can be enlarged with #. But in some Photoshop modules they are reduced in size (in Liquefy for example). This drives me crazy...

Say I have a RGB/8bit photoshop file, with one or more spot channels in it:   I make sure the visibility of those spot channel(s) is currently OFF ( by togling off each spot channels' eye icon ), and that only the RGB channels are currently selected and visible. I then create a new layer, and add a layer mask to it. I then select the new layer's RGB channel ( result: the RGB channel and its R, G, and B component channels are all selected and visible )  If I now select the new layer's 'layer mask', again, all the spot channels are made visible, AUTOMATICALLY.   Why is this happening?  The visibility of the spot channels was previously off; why does selecting a layer mask ( any layer mask of any layer, as a matter of fact ) makes all the spot channels visible?  This is really distracting and I can't think of a reason for this behavior.  I assume this is a bug.   Note: changing the solidity percentage of the spot channels to 0% doesn't preven

This checkbox has never worked as it should, but now it's more broken than ever.   It's supposed to do two things. In addition to the obvious, embedding the profile, it should also turn on the color managed view, using the system monitor profile to display the file correctly in the chosen document color space.   At the moment it doesn't use the monitor profile. People with standard monitors may not immediately notice this, but with a wide gamut monitor it becomes very obvious (oversaturated). It behaves like Save For Web with Preview set to "Monitor Color".   In the old Save For Web, there were two separate settings - an "embed profile"-box, and a rolldown for "Preview". Setting this rolldown to "use document profile" turned on the color managed view (and this still works reliably). It actually makes perfect sense to roll these two into one, so that's fine. But it doesn't work.   One more thing: Please make the "embed color profile"-box checked by default! Or at lea

Photoshop version:  22.5.1 and earlier OS: Mac OS Steps to reproduce: Make sure the file has a profile like sRGB and Save a file as PNG Close the file and open it you get the following warning: The RGB document “name of doc” has a file format that does not support embedded color profiles. Expected result: The profile would be saved like in Save for Web and using ExportActual result: Profiles are not saved and even removed when saving a PNG in Photoshop

I always start my editing process with making a Smart filter, and apply the Camera RAW. I edit in here with multiple selective edits (brush tool, gradient, etc.). When I'm done in Camera RAW I close it down and start edit with muliple layers in the normal Photoshop view.  Whenever I come to my final stages I like to do tweaks to the crop. I do this at the end, with many layers in the layer panel, including the smart layer with camera RAW from the early stages. Whenever the crop render the selective edits from the smart object get misaligned. My work-around is to create a new merged layer before the crop, but that limits my ability to go back and edit again later if I'd want to do that.    Are there any other work-arounds or will the bug be fixed in the near future? 🙏

I upgraded to PS 2022 (v23.0.0) and it looks like an old bug has resurfaced.   Expected behavior: When I click a Shape, the Properties panel should show the Shape Properties options, with things like Fill, Stroke, corner radius, etc. (Basically the same options as what appears in the top bar.)   What's happening: Some shapes will show the Masks options in the Properties panel instead of the Shape Properties options. No Fill, Stroke, etc, just Density and Feather. (I've verified that they are shapes, with the square-with-corners icon in the Layers panel.)   To reproduce: Create text object. Right-click its layer, select "Convert to Shape". Non-converted shapes (rectangles, ellipses) seem to work correctly. I've done this thousands of times in PS 2021 and 2020, and it always worked correctly.   Is anyone else having this issue? I know this bug existed for a year or two when they first introduced the Properties panel, so it's unfortunate to see it resurface a

Issue: record action bug when setting keyframes on an object property Photoshop version: All Photoshop CC versions from 2015 to 2019 (does NOT happen in the CS6 version) OS and version: Windows 10 21H1 Steps to reproduce the behavior (most options are not mandatory, posted just for reference): - open Photoshop without creating or opening any file - start recording your actions - File / New / random resolution transparent Document - Timeline: Create Video Timeline - 3D / New Mesh From Layer / Mesh Preset / Sphere - select 3D Panel: Scene: Sphere, then its Properties: Coordinates in the appropriate panel, then Timeline: <Current Layer>: 3D Meshes: Sphere, and click the stopwatch to Enable Keyframe Animation [stopwatch turns yellow] - go to a random time in the Timeline and set, say, the Y axis angle to 90 degrees - stop recording - play your recorded actions   Expected result: the recorded actions should play without issues / errors (like in Photoshop CS6)

Just noticed this bug when resizing the Shape window in the options bar Photoshop version 23.0 Windows 10 GPU RTX2600 Super, latest studio driver installed CPU i9 11900k RAM 64GB DDR4 Tested with deactivate native canvas on and off, same result Seems to be the same in version 22.5.2  

Photoshop 23.0.0 and 23.0.1 crash on startup on mac M1, big sur, native mode. Switching to rosetta fixes this, but at a pretty hefty cost to performance. I've sent crash reports, but posting it here too because its a big one. 

Using PS 22.5, each time I try to shift+click to select multiple anchor points in a Warp transformation, Photoshop crash without any message. It just quit.PS Prerelease 23.0 is is behaving exactly the same. This is a Apple issues since this is working fine on Windows.Does this is related to the fact that my GPU is not supported anymore on my old MacBookPro? macOS 10.15.7 Catalina.

I just updated to v22.5 of Photoshop and I've noticed the new "Export As" dialog is now the default (it says v5.5.5) and I've noticed quite a few regressions in the user experience compared to the previous version.   First, the font is far too thin. I am on Windows 10, my monitor is 2560x1440 and I'm not using any scaling, so this does not look great for the most part.   Keyboard shortcuts have stopped working. Before, pressing Enter upon first opening the window would do the same thing as clicking the Export button below.   Pressing Ctrl+ to zoom in and out used to work as well. Now, zooming is only possible with the small plus and minus buttons. I was wrong about this one, but it would still be nice to be able to zoom in with keys if the image area is in focus.   When selecting multiple images, the previews appear too sharp and there's visible sharpening noise around finer details that weren't there before.   It also looks like exporting SVG isn't possible a

I'm having trouble using the Line Tool in PS 22.0.0.    How do I set the width/weight of the line? In PS 21 there was a "Weight" option along the top bar, but I don't see that anymore. Am I missing it? Or did it move?    This might be a separate issue, but the lines I'm drawing are not showing up. I have a fill color and stroke color selected, but when I make a line, I don't see it. I just see a blue outline of where it is... the same that might happen if I made a "path" instead of a "shape."    I just need to make a line with a width/weight of 20px.

When I select the text or try to edit some text in a CMYK file it doesn't show anything showing whether or not I selected that text. I can edit normally, but without this information it gets a little complicated to know what I'm selecting or not

In previous versions Ctrl + or Ctrl - were used to zoom and Ctrl+Alt + and Ctrl+Alt -  zoomed and resized a floating window. Note : Both of these were without the preference Zoom resizes window checked.In v21.1 Ctrl+Alt +  and Ctrl+Alt -  zoom but do not resize the document window.Dave

In CC2017 (first video) you were able to see a selection border for parts of your image that go beyond your canvas. So, if you crop an image (disable 'Delete cropped pixels' first), and then Ctrl+click on the layer thumb in Layers panle, you will see the whole border around the layer pixels.   Later, and now in CC2022 (second video), We don't see the whole border, but only the part of it that fits into the canvas — which is ridiculous and useless. Now we have to call Free Transform to check a layer’s extension, or use Reveal all (and revert back then).   If it's 'indended', please reconsider your intentions, because it's just harmful. If you just missed it — please fix it.

Hello. I have had a problem with PS on iPad Pro with M1 processor for some time - system 15.0.2. the program closes as soon as it is opened. I tried reinstalling PS, the entire Creative Cloud with applications. logging out and back in and nothing. no change. other applications like Illustrator or Lightroom  are working normalny. Have you got any idea what to do ?

Hi   Firstly. Do you (Adobe) read the error message submitted from Photoshop? Is it useful to submit that way too?   To the question now! Photoshop crashes when using the Polygonal Lasso tool. I don't think it's related to Feather or what layer I select on? A bit random, not every day. Please contact me if you have questions about the issue.   Kind regards, Robert    

Photoshop 2021:When I "Save as..." and then choose the image option 6, the preview shows better quality than 7. 

New Photoshop v23 Depth Blur has major problems with strength. The blur is so weak that I had to double check if the filter applied or not.   This is the old v22.5 Depth Blur render with strength @ 75.       New v23 Depth Blur with Strength 100.  It is unusable at the current state and I will have to roll back to the old Photoshop version. 

Whenever I try to send an image from Lightroom cc to Photoshop cc, Photoshop crashes and won't open the image.

I have had this problem for the last few iterations of Photoshop, but I can't remember when it started. I am surprised that I haven't seen anyone else mention it.When I move the screen (for instance, when at 100% on a large document) using flicks on my Magic Mouse (Mac OS, of course), the screen will continue scrolling for 10-15 or more seconds after my last flick. This means that it is basically impossible to scroll using flicks on the mouse. I find using the space bar + drag much less intuitive and much slower, and since I can barely see the scroll bars in the modern Mac user interface, I am spending way too much time doing things that used to be dead simple.Is there anything I can do about this?(MacOS Mojave 10.14.2, Photoshop 20.0.2, Magic Mouse 2)

There's a noticeable lag in curves since version 21.1. I am now on 21.1.2 and it's still there. Up until 21.0 they used to refresh smoothly. I am attaching a video to illustrate the problem. I'm also attaching a couple of screenshots of my performance tab in "Preferences". These are my PC specs: Operating System Windows 10 Home 64-bit CPU Intel Core i7 7700K @ 4.20GHz Kaby Lake 14nm Technology RAM 16.0GB Dual-Channel Unknown @ 1070MHz (15-15-15-36) Motherboard ASUSTeK COMPUTER INC. PRIME Z270-A (LGA1151) Graphics 4095MB NVIDIA GeForce GTX 1050 Ti (Gigabyte) NVIDIA Studio Driver 442.92 (latest one) Thanks!