Photoshop

Hi Adobe,Since updating to the latest Photoshop version, Generative Fill occasionally gets stuck on “Generating…” and never returns a result.It seems to happen more frequently with larger selections, while smaller selections usually work. Restarting Photoshop temporarily helps, but the issue comes back.I’ve also tried disabling/re-enabling the Graphics Processor, but it doesn’t seem to make a difference.Is this a known issue with the current version, or is there a recommended workaround?Photoshop: 27.9.1OS: Windows 11Thanks.

In Photoshop 27.9.1 the image preview in Export As looks like a chunky mess even at 100% and when the export image isn’t being scaled, as if it’s taking a smaller image texture and scaling it back up with a fast/nearest-neighbor type algorithm... it does not match the original image. This also makes it impossible to judge the Resample mode (Bicubic, Bilinear, etc) when you ARE scaling the image on export, because the preview has no relation to the actual resulting saved image.I downgraded back to 27.8.0 and it works fine again.Windows 11 25H2, nVidia 3080 Ti on drivers 610.88 (GRD)Here is a screenshot showing the document at 100% in Photoshop with the Export As window open below it. Hopefully this image gets attached untouched/unscaled (original is 2603x1347)This may or may not have something to do with being on a high-res monitor (3840x2160) in Windows with its interface scaling active (150% in my case) as I looked at PS 27.9.1 on a different machine on a standard res monitor with no

The tab to click on and change the properties for an adjustment layer randomly disappears. Quitting and re-opening the app solves the issue, but it will happen again within minutes, usually when switching between different projects or different app on the computer.  On Photoshop v26.6 - Mac Mini M4 pro, 32gb ram, 1tb ssd.   Any help would be appreciated! ss

PS 27.8.0An error message pops immediately upon choosing the local device option for Remove Tool processing.GPU has 12 (just under 12) of ram on the card which is higher than listed requirements for this.Checked sys info and PS sees the GPU’s ram so I’m not sure where the disconnect is in the ram check sparking this error.  Attached. screenshot showing error message and portion of sys info scrolled to gpu data seen. 

Hello,I started using the new photoshop version 27.0 and noticed some really annoying problems while using the "subject select (SS)" and "remove background(RB)" features from the taskbar, in some instances it just doesn't recognize images at all, images that it had no problem working on the previous version.At first I thought this was a problem after i rasterized the image, as soon as I imported and used SS or RB on the smart object it worked as expected. But if i rasterized the same image and then tried to use the same features, photoshop would select the outer bounds of the image imported.But after trying again on both smart objects and rasterized images i realized that the same thing happened with both types of layers.I also thought this might have been a problem with images generated with firefly, but again, i had the same problem with photos and other files that were not ai generated. Here is an example of the weird selection it made on non-generated image as a smart object l

app.activeLayer.kind returns an error for Grain adjustment layers, is here anyway to return a value for them? Is it detectable with AM? Currently, just using a try catch to return undefined.activeDocument.activeLayer------------------------1) allLocked=false2) blendMode=BlendMode.NORMAL3) bounds=0 px,0 px,13754 px,7760 px4) boundsNoEffects=0 px,0 px,13754 px,7760 px5) fillOpacity=1006) filterMaskDensity=1007) filterMaskFeather=08) grouped=false9) id=700210) isBackgroundLayer=false11) itemIndex=1212) kind= Internal error13) layerMaskDensity=10014) layerMaskFeather=015) linkedLayers=16) name=Grain 117) opacity=10018) parent=[LayerSet Effects]19) pixelsLocked=false20) positionLocked=false21) textItem= Layer is not a text layer.22) transparentPixelsLocked=false23) typename=ArtLayer24) vectorMaskDensity=10025) vectorMaskFeather=026) visible=true27) xmpMetadata=[XMP Metadata] 

I have a photoshop document open. When I try to export it — whether that’s “Quick Export as PNG,” or “Export As,” I am met with an error. The text of the error is “Could not complete the Quick Export as PNG command because of a program error (854aee.3153)” and “Could not complete the Export As command because of a program error (854aee.3153)” respectively. This is a very new install. I looked for this issue and found others had it through the years. I have ensured that Photoshop has full disk access. I’ve also tried with and without the graphics processor. It’s pretty crippling to be completely unable to export my work in any usable format. Renders the program completely useless, effectively. System info:Apple M116GB memorymacOS version 26.5.2 (25F84) Photoshop version 27.9.1

The Adobe Firefly connector in Codex is repeatedly failing with:HTTP 403 Forbidden — “MCP streamable transport probe failed”Endpoint: https://photoshop-mcp-service.adobe.io/v3-creativity-b8f2a/mcpThe connector worked briefly and successfully generated images, but then began returning this error again. It occurs before Firefly receives the prompt, even when generating one image at a time. Disconnecting, reconnecting and restarting the app have not resolved it. Please investigate the connector’s authentication/transport authorization.

When I try to use the function “ Select > Subject” on v26, the software will select the object from the background on the image with out any issues.however the exact same function does not work on v27 and pop up a warning saying on subject can be found no matter using the AI function or the basic one to achieve the same goal.

I updated to Photoshop 27.10.0 and now when I click “generative fill” in the contextual taskbar, the cursor to type the prompt no longer appears automatically in the box for the prompt. So when I start typing, it cycles through the toolbar keyboard shortcuts instead. This is a glitch that did not exist in previous versions, I could always immediately start typing my prompt after clicking the generative fill button in the contextual taskbar.

Product: Adobe PhotoshopAffected Version: 27.10Last Known Working Version: 27.9.1Platform: WindowsDescription:Photoshop 27.10 appears to have introduced a regression in the way DCS files containing multiple spot-color plates are interpreted.The exact same DCS file opens correctly in Photoshop 27.9.1. In 27.10, the first custom plate is instead interpreted as Photoshop’s native Gray channel. After this happens, the spot-color metadata/tagging associated with the subsequent channels is also incorrect.This affects production files used for screen-printing color separations, where every DCS plate needs to retain its correct plate name and spot-color assignment.Steps to Reproduce:Open the attached DCS separation file in Photoshop 27.9.1. Open the Channels panel. Confirm that the first plate and all subsequent spot channels are interpreted correctly. Close the file. Open the exact same DCS file in Photoshop 27.10. Open the Channels panel. Observe that the first custom plate is now interprete

To better explain the situation, I will attach a screenshot. This is rather annoying and I don’t know how to move the small tiles out of the main workspace. There at the right side.  

Photoshop hangs (~26s, main thread unresponsive) when opening AI-generatedimages containing C2PA Content Credentials. Non-AI images open normally.Reinstalling, resetting preferences, and fixing permissions did not help. Photoshop 27.10.0 (build 20260824.r.26), macOS 26.2 (25C56),Mac15,7 / Apple M3 Pro / 36 GBCrash GUID: 6837CE11-99CB-400D-A87F-506920E5830CDunamis Session ID: 1091910b-5f18-4726-861b-30dab874293aMain thread, 11/11 samples, stuck in C2PA validation on import:  __NSFireTimer (Foundation)  ??? (Adobe Photoshop 2026 + 20931384)  adobe_context_create_ai_compliance_workflow + 60 (libadobe_c2pa.dylib)  ??? (libadobe_c2pa.dylib + 480580)  ??? (libadobe_c2pa.dylib + 489032)  ??? (libadobe_c2pa.dylib + 490712)  <- recursing ~8 levels deep  ...One sample shows libadobe_c2pa waiting in _dispatch_semaphore_wait_slow(possible network/trust-list lookup on the main thread).Secondary: the Generator thread was in vfork during the hang, brieflyblocking malloc on other threads (_xzm_fork

Please restore the "Delete Hidden Layers" command in the Layers panel menu.In recent versions of Photoshop (27.8), the Delete Hidden Layers command has disappeared from the Layers panel menu. It used to be available directly from the panel and was an essential productivity feature for many professional users.Removing this shortcut forces users to perform additional steps for a very common housekeeping task. This is a regression in usability rather than an improvement.Please restore Delete Hidden Layers to the Layers panel menu, where it was for many years. It was easy to find, consistent with professional workflows, and saved valuable time when cleaning complex PSD files.Many long-time Photoshop users rely on this command every day. Bringing it back would improve workflow efficiency at virtually no cost.Thanks a lot in advanceBest regardsCleo (senior art director and graphic designer with over 20 years of daily Photoshop use)

when I crop an image using content aware fill it comes up with an error and crashes photoshop

I am currently working on a Mac mini, Tahoe 26.7.  I have the Creative Cloud Photography plan with 1 TB on a yearly plan.The issue that I have been experiencing is the inability to use the REMOVE TOOL when taking an image from Lightroom Classic into Photoshop.  When I click on the remove tool, I get a message:  Required components are being downloaded.  Check back later to use the feature once the download is complete.  I do that, hit ok and nothing.  I will try again and hit cancel and briefly a message says that the download successfully installed.  There is still no change to the situation and the option bar for the remove tool does not appear.  The mouse just turns into a cross hair.I also noted that the PS icon appears again on my dock when I am working in photoshop in this situation.  I am not sure if this is a relevant matter. I am running Lightroom 15.5.1, camera raw 18.5.1 and Photoshop 2026, 27.10.0 release.I have spent 3 hours on 3 separate occasions with tech support at Ado

I have been using the remove tool for general clean up for months now. But since the update for PS CC 2026 it is borderline unusuable. I haven’t read much about it on here, so I though I’d ask if this is an actual but or a simple case of “ens***ification. Ever since the 2026 update I can no longer replace details in snow or sand textures for example because the resulting textures either rendered by the AI or in Photoshop itself do no longer look like the neighbouring textures but patchy, blurry and simply unusable. It doesn’t matter whether I set AI to auto, on or off. Results look like from 2010’s patch tool basically, neither texture, nor color or luminosity match the general area. On top of that for about two months now the tool has become incredibly slow for whatever reason and since I do have a 300mbit fiber conection I doubt it is the internet needed for the transfer of the image data as has been hinted at here on the forums recently.I then tried to simply mark the areas I would

Adobe photoshop versi 27.10.0

Hello, I an on-the-go type, not at my desk very often. I mostly use the PS app on my iPad whenever my needs are simple. Today suddenly the left-hand toolbar is gone. Which severely limits my usage! It looks like there has been an update. Maybe that has caused this? How can I get the toolbar back?? TY

Why is it that when I record an action,I hold Shift and click C, B, A, and Layer 1 to merge the layers into D,but when I run the action, it always gets stuck with an error at Layer 1?When I record it again, it puts my layer order into a group. What operations should I avoid?  

After moving the zero point to a different place, Photoshop continues to create a New Guide as if the zero point had not changed. Why?