Photoshop

1. SummaryIn Photoshop 27.9.1, native Spectrum widgets (sp-textarea / sp-textfield) placed inside an ancestor container with overflow: hidden; height: 0 (a common CSS trick used to visually crop/round native widget corners) become completely non-interactive. ❌ Symptom: No cursor, no focus state, no keyboard input, and placeholder text disappears. 🔄 Regression: The exact same markup and CSS worked perfectly in Photoshop 27.8 and prior. 💡 Scope: Only native Spectrum widgets are affected; standard HTML <textarea> / <input> elements continue to work under the same CSS layout. 2. Environment Photoshop Version: 27.9.1 (Broken) vs 27.8 (Working) OS: Windows (Confirmed) Extensibility Platform: UXP Panel Affected Widgets: <sp-textarea>, <sp-textfield> 3. Root Cause AnalysisThe plugin utilizes a .crop wrapper to clip and offset native inputs: CSS .crop { position: relative; width: 100%; overflow: hidden; height: 0; }  The child (sp-textarea) is absolutely posi

I’m on Photoshop v27.8.0 and Windows 11. Expanding does not reveal the ‘l’.Screen resolution in my case is 1440p if that could be an issue.

In the Canvas Size dialog, with “Relative to current dimension” checked, the width nor height can be set to 0. This is a big problem if you only want to change one dimension.Also, I will say that it is very annoying that the up and down arrow keys no longer increase and decrease the value by a whole number.

Really annoying bug. I spend 10 minutes going through my list of fonts in Photoshop, clicking the star next to fonts I want to remember as "favorites". Many of these fonts are installed via fonts.adobe.com. But Photoshop keeps turning off the "favorite" star for many (but not all) of my font selections. I think I've figured out the cause: If I start Photoshop shortly after logging in, before the Adobe Creative Cloud magic has had time to activate all my fonts, the fonts that are not yet activated don't exist yet (as far as Photoshop is concerned), and they lose their "favorite" star. Once the star is turned off by this bug, it stays off until I go back into Photoshop (after the fonts have all been loaded) and turn the star back on again.

Photoshop Version: 27.2.0 (Windows)  (sorry not 27.2.2 as per title)Steps to reproduce:Open Photoshop. Create a new RGB 8-bit document. Select Image → Adjustments → Brightness/Contrast. Instead of opening the Brightness/Contrast adjustment, Photoshop enters an eyedropper/modal state. Menus become disabled until Esc or Enter is pressed. Repeating the command eventually leaves Photoshop locked in the modal state.Expected behaviour:Brightness/Contrast dialog (or Properties panel) opens.Actual behaviour:Eyedropper/modal state appears, preventing use of the command.

When using the Move tool to reposition/shift a Pattern Fill layer, the on-canvas result is not calculated live. The move is registered internally (the pattern's actual position does change), but the canvas does not visually redraw to reflect it. Toggling the layer's visibility off and back on (hide > unhide) forces Photoshop to redraw and show the correct, updated position.Steps to reproduce:1. Create or open a document with a Pattern Fill layer (Layer > New Fill Layer > Pattern).2. Select the Move tool (V) with the Pattern Fill layer active/targeted.3. Click and drag on the canvas to reposition the pattern.Expected result:The pattern shifts and the canvas updates live, in real time, as it did in Photoshop 2025.Actual result:The canvas does not visually update while/after dragging. The move has actually occurred (confirmed because toggling the layer's visibility off then on forces a redraw that shows the pattern in its new, correct position), but there is no live visual feedba

This is what the gradient style selector looks like when a gradient is applied to a shape layer's stroke. It appears very wide and with options overlapping each other vertically. The same selector for gradients on a shape's fill appears normal. This also appears this way when it's accessed through the control bar when the Shape tool is selected.   This is on Photoshop 26.8.0 on Windows. {Thread renamed by moderator}

When I create a droplet in Photoshop 2025, it creates a folder instead of an EXE file. What is the solution?

Steps to reproduce:1. Open Photoshop v27.x on Windows 11.2. Open any image (8-bit PNG/JPG).3. Go to Image > Adjustments > Exposure...4. Move the Exposure slider (for example, +0.5).5. Observe the Gamma Correction slider: it instantly jumps to 0.01 and the preview becomes heavily distorted.Actual result:Gamma Correction resets to 0.01 automatically after moving the Exposure slider, producing a washed-out / broken preview.Expected result:Gamma should remain stable or adjust smoothly; it should not reset to an extreme value.System info:- Photoshop version: 27- OS: Windows 11- GPU: RTX 5070 (12GB)- GPU acceleration: Enabled- Bit depth: 8 bits/channel

When running large batch jobs getting "Could not complete the command because there is not enough memory (RAM)" using Photoshop 2026 (2.8.0). Makes large batch jobs difficult in the extreme and was never, ever an issue in Photoshop 2025. 

i am getting this when i attempt to enter photoshop.any ideas why? photoshop being nlockrd  

It has been 4 days that I cannot open/upload to use photoshop web

Issue summary:Creative Cloud Libraries panel is non-functional in Photoshop 27.8.0. Library assets are visible, but all Library commands and interactions do nothing. Rolling back to Photoshop 27.7 restores full functionality.Product and version:Adobe Photoshop 27.8.0 (20260610.r.13, x64)Operating system:Windows 10 Pro 64-bit (Version 10.0.19045.6456)Steps to reproduce:Launch Photoshop 27.8.0 on Windows 10. Open Window > Libraries. Select a Creative Cloud Library containing color swatches (or other assets). Create or select a shape layer or text layer. Click or double-click a color swatch in the Libraries panel, or right-click a swatch and choose Set Color or Edit. Alternatively, drag a color swatch from the Libraries panel onto the selected object.Expected result:The selected shape or text should update to the Library color. "Set Color" and "Edit" should execute normally, and Library assets should be usable.Actual result:The Libraries panel displays all assets correctly, but all Lib

SUMMARY All Neural Filters that load a local AI model fail with "We've temporarily disabled this filter because of an error" if the Windows user profile path contains a non-ASCII character (e.g. C:\Users\Jørgen). ENVIRONMENT Photoshop 27.8.0 x64 Windows 10 22H2 (build 19045) NVIDIA RTX 5060, driver 32.0.15.9649 (also reproduced previously on an AMD Radeon card) STEPS TO REPRODUCE 1. Use a Windows account whose profile path contains a non-ASCII character,   e.g. C:\Users\Jørgen (æ ø å ä ö ü é ñ ç etc.) 2. Open any 8-bit RGB image. 3. Filter > Neural Filters > Photo Restoration. 4. Toggle the filter on, or raise any slider above 0. EXPECTED The filter processes the image. ACTUAL "We've temporarily disabled this filter because of an error." The error appears on ANY non-zero slider value. Leaving every slider at 0 (i.e. no inference) produces no error. AFFECTED FILTERS Photo Restoration, Skin Smoothing, Colorize, Depth Blur, Color Transfer - i.e. all filters that run a downloaded loc

Select the Object Selection Tool. The try to name or rename a layer with something containing an 'n' like "name". The 'n' will not appear until you deselect the Object Selection Tool. The layer will be called "ame". Have the Object Selection Tool selected. Then create a new layer and try to name it “new layer”. The ‘n; will not be able to type into the name. You will get “ew layer”. If you deselect the Object Selection Tool then the ‘n’ will work again.

Create a gradient layer Disable gradient layer check ”align with layer” Crop the image with crop toolExpected behaviour:Image cropping doesn’t affect gradient position Actual behaviour:Image cropping affects gradient position, which is anchred to layer size.  

Hey everyone, i've noticed that when I add bullet-listing styling to my paragraphs and then export them to pdf the symbols don't appear (watch image 1) , they only do when exporting to png or before exporting (see image 2) Does anyone know how to solve this? Or is it a bug? Photoshop 2025, version 26.3.0 release

Hello, I've found a possible spelling error in the Spanish version of the Photoshop app and wanted to report it so it can be fixed. This error appears in the FEATURED section and says "explore lo mejro de Photoshop" instead of "lo mejor".Al momento de abrir la aplicación en Photoshop en la parte de Destacados existe un error ortográfico, debería decir lo mejor  

Hi everyone, I would like to report this explicitly as a bug report, and I kindly ask that it not be moved to the Questions section again. The behavior is reproducible in my setup and appears to involve the interaction between Photoshop 27.6, Windows Ink, the Remove Tool, and assigned Wacom pen side switches. Short description In Photoshop 27.6, using the Remove Tool repeatedly causes a massive memory increase. Photoshop then becomes unresponsive for a while and eventually shows the error message: “The operation could not be completed because there is not enough RAM.” In my tests, this happens when using the Wacom pen, but not when performing the same Remove Tool actions with the mouse. Key findingI ran several comparison tests with the same file while monitoring Windows Task Manager. Test 1 – Remove Tool with mouse inputPhotoshop 27.6 Windows Ink enabled Remove Tool input with the mouse 46 Remove Tool strokes no freeze no RAM errorMemory usage increases somewhat, but remains controlle

 selection and deletion of objects are done on the device or in the cloud, but the device has not been working for six months, so I use the cloud version. However, now the cloud version starts the search slider, and after a couple of seconds, it displays that no objects have been found 

I have the following error message from the Photo restoration neural filter   It seems specific to this image which I think is an ideal candidate.   Adobe Photoshop Version: 26.2.0 20241127.m.2885 1797431 x64Number of Launches: 353Operating System: Mac OS 15.1.1System architecture: Intel CPU Family:6, Model:14, Stepping:12 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, AVX, AVX2Physical processor count: 6Processor speed: 3700 MHzBuilt-in memory: 40960 MBFree memory: 23011 MBMemory available to Photoshop: 36510 MBMemory used by Photoshop: 70 %Crash Handler: AdobeDCX Version: 7.24.8SAM SDK Version: 9.1.0.1-fioACP.local Status:- SDK Version: 4.0.0.5- Core Sync Status: Reachable and compatible- Core Sync Running: 7.2.0.58- Min Core Sync Required: 4.3.66.28Live Edit Client SDK Version: 4.0.6Adobe Firefly: Please use any generative AI feature to view the latest version.OpenColorIO version: 2.4.0    

v25.11 and still the same problem!

Hello Adobe Support Team,After updating to Photoshop v27.3 and v27.3.1, I encountered an issue when using the Curves adjustment.When adjusting Curves on the composite RGB channel (not individual R, G, or B channels), if I make an additional adjustment afterward, a residual or ghosted image from the previous adjustment appears. If I switch to another layer and then return to the original layer, the residual image disappears. However, if I continue adjusting the Curves, the ghosting issue reappears.I tested this behavior by downgrading to Photoshop v27.2, and the issue does not occur in that version. The Curves adjustment works as expected in v27.2 without any residual artifacts.This issue seems to be specific to v27.3 and v27.3.1 and may be related to how Curves adjustments are refreshed or rendered.Thank you for your time and support. I hope this information is helpful for identifying and resolving the issue.

Version 27.7.0 / WIndowsI oftentimes add many guides (by exact percentage) to my documents.So I use the New guide pop-up.It was always a quick and streamlined process as the number field was preselected, I just had to write in it and hit Enter. Now I have to manually click in (or Tab into) the number field to be able to write my numbers.This is clearly a regression because of the new pop-up. So I consider it a bug.I think the Canvas Size dialog box already had the same problem, so you could consider it a feature request there and in every other pop-up too: Always the first input field should be the active one, not the OK button which makes not much sense.That could be pushed by hitting Enter no matter what part of the pop-up is active.Thanks for looking into it!