Photoshop

Hi, I am on Photoshop 27.10 but it’s a bug I have experienced in several previous versions, too. Yet I have used Photoshop for 20 years and didn’t notice it before the last year or so.The bug happens when I have several files opened at once and i switch between each of them (working a bit on one then clicking and working on one another, eyedropping/selecting one color from one file then using it to fill a selection in one another ect). Currently it happens when I have seven 600ppp CMYK files opened.When the files are opened, everything works fine for quite a long time, then the bug happens after 1 hour or so : when i switch from one file to another and i start working on any layer of it, suddenly I see that the file is lagging like hell : every action takes 1 second or more to be implemented (a brush stroke, a magic wand selection etc). I can’t work on the file anymore and have to shut it down.Then several things can happen : when the file is shut, i can still work normally on the othe

System: Photoshop 2026 on MacBook Pro M5 ProSteps to reproduceCreate a Timeline Frame Animation. Create three layers: Layer A, Layer B, and Layer C. Set up the frames as follows: Frame 1: Layer A visible only Frame 2: Layer B visible only Frame 3: Layer C visible only Select Frame 2 and duplicate the visible Layer B.Expected behaviorIn Photoshop 2023, 2024, and earlier versions, the duplicated Layer B is visible only on Frame 2, because that is the frame on which the source layer was visible.Actual behavior in Photoshop 2026The duplicated layer becomes visible on Frame 1 as well as Frame 2.The same problem occurs when pasting content with Cmd+V while working on Frame 2: the newly pasted layer also appears on Frame 1.This significantly disrupts frame-by-frame animation workflows because every duplicated or pasted layer then has to be manually removed from Frame 1.Possible cause: “Propagate Frame 1”This appears to be related to Propagate Frame 1.Disabling “Propagate Frame 1” does not

Issue summary: When choosing Layer > New Background from Layer after cropping part of an image on a layer without ticking the Delete Cropped Pixels checkbox, the cropped pixels end up deleted.Product and version: Photoshop desktop version 20.0.10 and 21.2.11Operating system: macOS 12.7.6Steps to reproduce:Open an existing document with some layers. Select one of these layers, crop it without ticking the Delete Cropped Pixels checkbox. Under Layer, choose New Background from Layer. Select the crop tool and drag the edge handles of the crop border. Notice that cropped pixels have been deleted (sometimes only part of them).Expected result: Cropped pixels shouldn’t be deleted according to the setting of the crop tool. If this behaviour is intended, I’d suggest a notification before applying New Background from Layer to a layer. Actual result: Cropped pixels are deleted.

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.

Eu estou tentando utilizar a versão mais recente do photoshop 27.10 porém a visualização dos arquivos, a tela fica acinzentado, por exemplo a prancheta que é branca fica cinza. Estou tendo que sempre voltar para a versão anterior por conta disso.

GPT says it’s connected to Adobe but I’m always getting the 403 - access forbidden. This is despite me being signed in to both Adobe and GPT. I’ve tried signing out and uninstalling on both but nothing works. I’m using Chrome for my Adobe, the GPT app for GPT. Is this a technical fault on Adobe’s side or is there something I’m doing incorrectly? 

as described in the title bar RegardGert Laursen

When using the “Remove” tool in Photoshop 2026 (27.8.0) on Windows laptop I receive “Tool is not responding - check internet and try again later” error.  Internet is perfectly fine however it does this about 10mins and then works for a bit.

Hi,Expanding the image while using the Crop Tool (the color in this case, about a solid gray) using Content Aware Fill - makes wrong color, in my case after expanding a lighter frame at the previous image edge borders and a lighter gray color is used for the expanded areas. Is this a known bug? I’ve downgraded to 27.8, no issues there.Thank you,Patrik

Adobe Photoshop 27.10.0 on Mac OS 14.6.1When adjusting a Color Balance (or other) Adjustment Layer by dragging the handles in the Properties Panel it incorrectly disregards the effect of a Curves Layer above that is Clipping Masked to a 0% Fill Layer. This does not happen when the Color Balance Layer is edited by entering numbers or when the Curves Layer has a Layer Mask instead of being Clipping Masked. Hiding and revealing the Color Balance Layer corrects the display.Steps to recreate: • create a Color Balance Adjustment Layer with some changes• create a Layer with pixels (plain, Solid Color, Smart Object, …) and set it to 0% Fill and uncheck »Blend Clipped Layers as Group«• create a Curves Adjustment Layer with some changes• Clipping Mask the Curves Layer to the 0%-Fill-Layer• drag one of the handles of the Color Balance Layer in the Properties PanelExpected result: The combination of adjustments should be displayed correctly. Actual result: The Curves Layer’s effect is not honored.

Hey everyone,Up until recently, I was using Photoshop 27.8 (Mac 26.5.1) and everything worked perfectly fine.The newer Generative Fill and Expand model produces textures that are way too smooth. I’d even call them blurry. And yes, I’m aware of the 1024×1024 px limitation, but this happens even with 100×100 px selection.Because of that, I’ve been using the old Firefly 1 model from 2023, which, unlike the newer model, works really well for my use case. It handles textures amazingly well. I mainly use it for removing distractions: I select the unwanted object, leave the prompt empty, hit Generate, and Firefly 1 understands perfectly well that the selected area should be removed.However, something seems to have changed starting with version 27.9.If I leave the prompt empty now, Firefly 1 starts generating completely random objects instead of simply filling/removing the selected area. For example, I had a white T-shirt with some red text on it that I wanted to remove. I selected the text, l

Where can I find Customer Care case. Adobe have closed a case without solved my isseu. In the email Adobe say that I can follow my case, but it's nowhere to find.

I tried 'Generative upscale' which is a third party feature. Firstly, it didn’t work at all. Secondly, it broke Photoshop, which now crashes on creating a new file. No choice but to uninstall, reinstall, and never use this feature again - at least, until it's been integrated as a safe Adobe feature and not this third party trash. For the record, generative upscale would be extremely useful if it worked!

For a company that charges an exorbitant premium subscription fee, their software stability is a absolute joke. A routine update completely destroyed the core Lightroom-to-Photoshop handshake workflow, rendering the standard 'Edit in Photoshop' feature entirely useless.When you try to bypass their broken code pathways, you are met with flat, washed-out color profiles that fail to render correctly even when manually assigning the proper color spaces. Adobe clearly does not test their systems properly before forcing updates onto paying users. They are using their consumer base as live guinea pigs for broken code.Instead of saving professionals time, Adobe’s lack of quality control turns simple, two-minute edits into hours of grueling tech support. It is completely incompetent, frustrating, and unacceptable for software that is supposed to be the industry standard. I am actively looking for alternatives to cancel my subscription.It is not surprising that so many people are switching away

Ever since the latest update of Photoshop (version 27.10), the content-aware fill tool has been rendered useless. When using this tool, it will bug out when i straighten an image out or will fail when cropping an image. When I go to cancel the content-aware fill load screen, it will not cancel and I have to force quit out of Photoshop. Because of this issue, my usual editing speed has been significantly slowed down. I rely on this tool heavily for my job and without it working correctly, it is causing delays for complete projects and unnecessary stress. 

27.10 is slow saving files: 1) Super slow (20 seconds to save a 4K resolution .JPG file.) 2) Erroneous warnings that the file has been updated (it's hasn't) before saving. 3) PS seemingly locking up when saving. Reverting to the prior version of PS (27.9.1) cleared up all the issues. OneDrive being enabled or disabled didn't make a difference.Open and edit any PS .PSD or JPG file. Try to save it. Wait and wait and wait.

A custom Action (created in the Actions panel) does not appear in the Action dropdown of the File > Automate > Batch dialog.Workaround to make it appear: open a document, select the Action in the Actions panel, then close the document — after that the Action shows up in Batch.However, when running Batch with this Action, Photoshop returns the error: "The command '[command name]' is not currently available" — i.e. Batch cannot find a command recorded inside the custom Action. The same Action runs without any issues when played manually from the Actions panel (Play).Steps to reproduce:Create a new Set and Action in the Actions panel, record several steps. Open File > Automate > Batch — the Action is missing from the dropdown. Open a document, select the Action in the Actions panel, close the document. Open File > Automate > Batch again — the Action is now listed. Select a Source folder, run Batch.    

Dear all, I already have a working and proven solution to my issue after 10 hour reading posts, cross-checking and ultimately finding out through trial and error. The solution I would like to share with so you’ll be spared the pain.  Issue: On the same monitor, there was a colour mismatch between pictures displayed in Photoshop and other apps in Windows 11. Photoshop was the most vibrant, closest to the desired AdobeRGB, all other apps like Camera Raw, Bridge, and third party editing tools showed something more like sRGB. This was also the case for some other non-photo-editing related apps, e.g. Windows explorer showed pictures in AdobeRGB, the photo/video preview app in sRGB. Hence, the problem pointed towards the operating system.  Background: Windows 11 25H2 has a bug concerning ACM when using hardware or software-calibrated monitors. It somehow overwrites colour profiles in certain apps, but not in others, “on the fly”.  Applicable specifications (main factors bold others for refer