Photoshop (Beta)

Use crop tool to expand the canvas, click on Generative Expand in the Contextual Task Bar…..I get an error message that says To Use This Feature, First Drag the Canvas to Expand, which, of course, I have already done.

For the last week or two, basically every time I am in a project and I try to bring a layer to the front using the bracket shortcuts, Photoshop will crash immediately. Photoshop also is not recognizing that it is crashing - it is terminating immediately and providing me with no recovery file - and I do have that toggled on. Very frustrating as this is something I do often out of muscle memory, so I can easily lose lots of progress. 

Photoshop Beta 27.9 - When invoking the Sky Replacement module (Edit > Sky Replacement) the brightness slider is not functional, although it moves freely, there is no visible change in the preview, nor is any brightness to the sky visible when applied.  All other slider functions within the Sky Replacement panel function normally. The same feature (sky replacement brightness slider) works normally in non-beta version of Photoshop v 27.8.

I can only get Generate Image to work with the latest Firefly Fill model. Not with any of the partner models (Win 11 desktop and laptop - the former running only the most current Ps production rel. 27.6 and the latter running only the latest Ps beta - not both on the same machine). Also, after trying to use reference image with a partner model it’s impossible to delete or remove the downloaded reference image. The trash can icon in the ref image dialog box doesn’t delete or eliminate the downloaded ref image. I’ve tried with multiple different base and reference images. And, I’ve tried by writing a prompt 1st (then the Generate button grays out) or making the selection and trying to establish object only and place in the selected area then choose the partner model. Neither approach works. It only works with the latest Firefly model - no partner models and I prefer working with Gemini and having the flexibility to use prompts.

All of my paid plug-ins have disappeared.  I installed Vivion and all the rest of my plug-ins disappeared.  How do I get them back?

Photoshop crashing

In AI Assisted, all of the other platforms work except for Googles. I have not run out of generative credits. I have logged out and back in again, and updated Photoshop, but it’s still not working. It was working fine earlier today.  

Rotate object not working. When click rotate object, that new layer is completely transparent, then when rotate changes accepted, always receive an error.Beta = 27.7 m.3511. Error = Could not update smart object files because of a program error (e2266e.571).

Photoshop Beta 27.11 — GPU-accelerated canvas rendering shows incorrect color (warm/red color cast) that does not match Camera Raw, Print Preview, exported files, or any external viewer.System:Photoshop Beta 27.11 Camera Raw 18.5 Windows 11 pro for workstation CPU: AMD Threadripper 3960X, 128GB DDR4 GPU: NVIDIA RTX A5000, driver 610.88 (NVIDIA Studio driver) Monitor: BenQ SW2700PT (wide-gamut), custom ICC profile generated via Palette Master Elements, recalibrated every 15 days NVIDIA Control Panel color settings: Output color depth 10bpc 64 bit, Output dynamic range Full/Maximum, "Precise" color precision mode enabled (reference mode not excluded) Photoshop Preferences > Performance > Advanced: "Use Graphics Processor" enabled, "30-bit Display" enabled, OpenCL enabledIssue:With GPU acceleration enabled, Photoshop's main canvas displays a visible warm/red color cast on an image that does not match: (a) the same image previewed in Camera Raw, (b) Photoshop's own Print Preview wind

Issue has not been resolved.  I just tested the latest beta 207.11 and the problem still persist where the image in PS has much more contrast that the LR original.  See sample included:  I turned off Usse Graphic Processor and it appears to have fixed the issue.  The problem I would have with that is I have an NVIDIA GForce RTX 3090 and I want to use the power of that card for effciency.  Now we know the workaround, how do we fix it? 

EDIT: Problem is solved. I’ve never encountered this before. For some reason, I needed to disable all of my monitors, except one, launch PS Beta, and then it worked (even when the other monitors were renabled). No idea why this was happening and why it didn’t affect regular PS (with the same HDR box checked) nor other programs with HDR support.  I don’t know how to close this report.________________________________Hello, I just updated Photoshop Beta to 27.5.0 (260305.m.3446). I have been using Photoshop on an HDR display for at least two years. OS is Windows 11 with HDR turned on for this display.“Precise color management for HDR display is checked.” ALL images now appear very dark on the screen. I have tested more than 30 photos. Most are NOT HDR photos. This includes JPG’s, tiff, PSD and both 8-but and 16-bit images. The same images look normal in non-Beta Photoshop. They also look normal if I move the photoshop window from an HDR to a non-HDR display.If i disable the “Precise color

 PROBLEM :  Images have Washed colours when opening any image in Photoshop after updating to 27.9.0 (Beta) Mac release.SEVERITY : URGENT.Ps Preferences > Performance > Use Graphics Processor is Checked. Ps Preferences > Technology Previews > Precise colour management for HDR display is Unchecked. View > Proof colours Unchecked.DETAILS :Opening any image or duplicating any image with an embedded icc profile (jpg, psd png etc.), it appears the embedded icc profile is not read.Updating seemed to have reset all Custom Color settings.After update I found Color Management Policies off, Profile Mismatches Ask When Opening UNchecked, and Missing Profiles Ask When Opening Unchecked.My custom Color Settings were not preserved through the update.My Saved Custom Color Settings are not found under the pop-up Settings.Reseting Working space to RGB: Adobe RGB(1998) and Color management Policies to Preserve Embedded Profiles and checking all “Ask When Opening” does not seem to have an a

Adobe Photoshop Version: 27.12.0 20260916.m.3679 with the new update  brush pen pressure not work with or without PSUserConfig.txt 

in camera raw funktioniert der Befehl “ Vorherige einstellungen anwenden” nicht mehr

Toolbar icons not rendering/showing blank after latest Beta update. Steps to reproduce:1. Updated Photoshop Beta via Creative Cloud last week2. Since then, all toolbar icons show blank/empty (left toolbar panel)3. Tried: uninstall + reinstall, Creative Cloud reset, Windows Essential reset — issue persists4. Photoshop Stable version works fine, only Beta affectedSystem: Windows, GPU set to Basic mode — still broken

In the creative cloud app the photoshop beta has disappeared and when I select app from left tool bar, there is nothing in there.

Using File > Package won’t cover external dependencies, e.g. textures for filters.Sample steps to reproduce: Create a file with content or open any image, convert one of the layers for Smart Filters, apply, Filter Gallery > Distort > Glass, load an external texture from another PSD, apply, save. If you try to use Package — you’ll get “Could not complete the Package command because there are no external links” warning. If you have another linked image, you’ll get no warning, but as you remove the external texture from its original location and try to edit the smart object with the preapplied filter — it will be reset back to one of the built-in textures.Also won’t attach any of non-Adobe Fonts Fonts. So basically most of the collects created with Package in Photoshop won’t provide reproducible and editable file to work on another machine

.tif file appears washed out only in Photoshop Beta with GPU enabled. The same file displays correctly in regular Photoshop. Turning off Use Graphics Processor fixes the appearance. 

Bad. Just like the last update it’s laggy and just bad. I guess with a 4080, amazing CPU, and 64gb of ram your software just doesn’t work… ridiculous. I’m about to switch to a free program at this point :\

Photoshop (Beta) — Remove Tool Performance RegressionI'm reporting a specific, reproducible regression in the Remove tool in the current Beta build (27.10.0) that I've diagnosed as thoroughly as I can from the user side.SummaryThe Remove tool, which previously worked quickly and well in this Beta build, has stopped functioning correctly. It now takes several minutes to remove even a tiny selected area, regardless of settings. The same operation completes instantly in the standard (non-Beta) release of Photoshop on the same machine, same file, same hardware.TimelineThe tool was working correctly. At some point it stopped — without any update on my part (no Photoshop version change, no graphics driver update, no known Windows update). I cannot pin down exactly when it broke, only that no deliberate change preceded the failure.SystemNVIDIA GeForce RTX 5070 Ti, correctly detected in Photoshop's Graphics Processor Settings, "Use Graphics Processor" enabled, GPU used normally elsewhere in th

Photoshop Beta 27.11.0 20260902.m.3662 8045dad x64Windows 11 64-bitThe new Light adjustment layer does not always render correctly in a linked PSD when Layer Comps are being used.I have a PSD placed as a Linked Smart Object inside a master Photoshop document. The linked PSD contains a Light adjustment layer using Exposure and Shadows.The Light adjustment looks correct when I open the linked PSD itself. When I save that PSD, the master document correctly detects the change and refreshes the Linked Smart Object. Other changes from the linked PSD update correctly, but the Light adjustment does not appear.I can force it to update with this workaround: Turn the Light layer off. Update the Layer Comp. Save the linked PSD. Turn the Light layer back on. Update the Layer Comp again. Save again. After doing this, the Light adjustment appears correctly in the master document.Expected behavior: the Light adjustment should render correctly in the master document whenever the linked PSD an

Dark Grey Interface creates screen flickering and makes the screen darker both in Beta and PS StableSetting the UI back to normal light grey seems to fix the issue, but I prefer working in dark grey.  Windows 11, PC, Dell Laptop.   

My workspace does not persist across exiting and relaunching the app. Palettes that were opened or arranged a specific way in my custom workspace upon exiting the app will appear closed or rearranged the next time the app is launched. I constantly have to go to “Workspace > Reset” in order to bring my custom space back to its appropriate order.