Bug Reports

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: Since Photoshop 2025 (exact version unknown, but after 25.12.4) direction-based brush strokes, when set in the brush settings (Shape Dynamics - Angle Jitter - Direction), are not working properly. The very first 'pixel' of nearly every stroke is angled about 90 degrees perpendicular, before correcting itself immediately as the stroke continues. This breaks a previously working workflow. The problem is only mitigated by using external stabilisation (I’m using Lazy Nezumi Pro with light smoothing), which suggests the issue is related to how initial pen input samples are handled at stroke start. I also ideally need to have 1% smoothing enabled in Photoshop, or the bug can lightly reoccur occasionally. Using older Photoshop versions avoids the issue, but this is not a viable long-term solution due to other compatibility and stability concerns. I have used these brushes for years with no issues until recently.Product and version: 25.12.4. (laptop) the bug does not occur in th

EnvironmentAdobe Photoshop 2026 27.10 (ARM64)Mac mini 2024, Apple M4 Pro, 24 GB RAMmacOS 27.0 Golden GateProblemImmediately after enabling Preferences > Plugins > Enable Generator, Photoshop displays the message:“There is a problem with Generator.”I checked the Node executable bundled with Photoshop:/Applications/Adobe Photoshop 2026/Adobe Photoshop 2026.app/Contents/MacOS/nodeRunning:file "/Applications/Adobe Photoshop 2026/Adobe Photoshop 2026.app/Contents/MacOS/node"returns:Mach-O 64-bit executable x86_64Therefore, Photoshop itself is ARM64, but the Node executable used by Generator is still Intel x86_64-only.Before Rosetta 2 was installed, running:"/Applications/Adobe Photoshop 2026/Adobe Photoshop 2026.app/Contents/MacOS/node" --versionreturned:zsh: bad CPU type in executableI then installed Rosetta 2 with:softwareupdate --install-rosetta --agree-to-licensemacOS reported:Install of Rosetta 2 finished successfullyAfter installing Rosetta 2, the Photoshop Generator error disap

An error occurs when using "Load Files into Stack..." in Photoshop.The issue persists even after resetting Photoshop preferences and reinstalling the application.Are there any solutions?Photoshop27.10（Japanese）、Win11 

Since version 27.4 and continuing in 27.5 I’ve been experiencing image flickering when using the Curves adjustment. In version 27.4, the issue occurs in all Curves use cases. In 27.5, it appears primarily when applying Curves as a Smart Adjustment on a Smart Object. It is slightly improved, but still noticeable when using Curves as a standard adjustment layer.I’ve attached a video demonstrating the issue: The first example shows Curves applied as a Smart Adjustment on a Smart Object (strong flickering). The second shows a direct adjustment on a non-Smart Object layer (no issue). The third shows a standard adjustment layer (minor flickering still visible). The flickering is clearly visible, especially in the first case.Please look into this issue, as it makes precise adjustments very difficult.Thank you.example video:https://youtu.be/jbe6K-ORr44 

Photoshop version:Photoshop 27.10.0Operating system:macOSSteps to reproduce:Launch Photoshop with the Home screen enabled. Open a document by clicking its thumbnail under Recent Files on the Home screen. Do not click anywhere in the document and do not press any other keys. Press the Command (⌘) key. The currently selected layer's opacity immediately changes from 100% to 50%.Expected result:Pressing the Command key by itself should not alter the document or layer opacity.Actual result:The selected layer's opacity changes from 100% to exactly 50%.Additional information / workaround:The issue only occurs when the document is opened by clicking a Recent File thumbnail on the Photoshop Home screen.I have confirmed that:File → Open does NOT reproduce the problem. File → Open Recent does NOT reproduce the problem. Pressing Esc after opening the document and before pressing Command prevents the problem. Clicking anywhere with the mouse after opening the document and before pressing Command al

I am experiencing a reproducible issue with Generative Upscale in Photoshop 27.10 on macOS.When I use Generative Upscale > Firefly Upscaler, the resulting document is created, but the image is completely black.Steps to reproduceOpen an image in Photoshop. Choose Generative Upscale. Select Firefly Upscaler. Run the upscale. The result opens as a solid black image.Expected resultThe upscaled image should be displayed normally.Actual resultThe resulting image is completely black.Important detailsPartner models such as Topaz work correctly inside Photoshop. Firefly Upscaler works correctly in the Firefly web app. The problem occurs only with Firefly Upscaler inside Photoshop. I tested with sRGB, RGB color, and 8-bit images. I reset the Photoshop preferences completely. I signed out of Creative Cloud and signed back in. None of these steps fixed the problem.The UXP log repeatedly shows errors related to the newly created document:handleNewDocument: activeDocument nullhandleNewDocument: d

Its been more than one week that im facing repetitive Firefly (Fill and expand function) error inside photoshop with this message:The service is not responding. please check your Internet connection and try again.I checked my Firewall (is off), sign out and in several times, and also made sure To disable Rosetta mode and run Photoshop natively on Apple Silicon (its Mac), but the function is very randomly working maybe 1 out of 10 tries. I still have credits and this problem didn't exist before.  

The only neural filter that works is color transfer. All the other filters are grayed out and not functional.

Here are the details to reproduce the issue:Steps to Reproduce: Create or open a CMYK document in Photoshop on macOS. Define a custom CMYK color swatch (e.g., using pure channel values like C0 M8 Y100 K0) and save it to the Swatches panel. Verify the swatch: The Info panel and the color applied to the artwork maintain the correct, original values. Trigger a break in continuity using either of the following actions: Scenario A (Restart): Close Photoshop completely and reopen the application. Scenario B (Export): Export the Swatches panel to an .ase or .aco file, and then re-import that same file back into Photoshop. Expected Behavior:The swatch should retain its exact, unaltered CMYK numerical values across application restarts and file exports/imports, exactly as it behaves on Windows.Actual Behavior: Upon Restart: The stored swatches in the panel automatically alter their values due to an unintended forced conversion to RGB. Even when viewed or forced back into CMYK dis

Since updating to Photoshop 27.3.1 shape layers have been behaving inconsistently. Running on Windows 11.I have multiple shape layers, all different colours, which I can manipulate fine individually. But, when I select multiple layers in the layers panel, all layers change to the colour of the lowest-most layer. This issue is inconsistent, sometimes layers behave as expected and other times they don’t.Also, some shape layers have text layers above them which are linked. If I move a shape layer, the text layer moves too as expected, but if I rotate the shape, the linked text doesn’t rotate.  I didn’t have either of these issues until I updated.Any help would be appreciated.

Using the latest Photoshop 27.7 with Modern User Interface enabled, in the file dialog launched from Save for Web you cannot copy/paste text into the file name. Also when you hit the escape key to cancel the file dialog and return to Save for Web screen, hitting escape a second time does not close out of Save for Web but command-period still does. If you avoid trying to copy/paste text the escape key still works correctly. Disabling Modern User Interface returns all the expected behavior. This is on a fresh machine set up a couple weeks ago.Photoshop 27.7macOS 15.7.5

Standard behavior (consistent for many years): Photoshop is open and running; I install a new font using Font Book on macOS; that font is instantly available in Photoshop. The same was also true for fonts added using Adobe Fonts. New behavior (as of recent app revision): Photoshop is open and running; I install a new font using Font Book; the font is not available in Photoshop until I close and open the app again. Adobe Fonts do sometimes become available in the running app, but it takes a long time -- on the order of 15-30 minutes. This is using Photoshop 27 on macOS Sequoia (not Tahoe).

I have several M1 Macs—from Mac mini to iMac—and they all have the same issue. Whenever I open Photoshop, Illustrator, or InDesign, even if I don’t do anything, WindowServer will jump to around 80–90% GPU usage. Once I start working with files, even just opening a single image, the whole system becomes choppy and starts dropping frames, with GPU usage almost maxed out.But : if I switch the app to full-screen with menu bar mode (press F), the window shadows disappear, GPU usage drops back to normal, and everything runs smoothly—even with large files open. This makes it pretty clear the issue is related to how window shadows are being handled in macOS 26 and how it interacts with Adobe apps.It’s been months since Adobe 26 came out, and I’ve been waiting for updates to fix this, but even the latest versions still haven’t solved it. At this point, I’m wondering if it’s even fixable.M1 Macs are not that old—most Mac minis and iMacs from around 2021–2022 are still M1, so they’re definitely n

Issue summary: Round-tripping a photo through Edit in Photoshop and saving it back with zero edits made results in a visibly brighter image in Lightroom.Product and version: Lightroom desktop (cloud), version 9.4.1 MAS arm64Operating system: macOS 26.6.2Steps to reproduce:Select a photo in Lightroom and choose Edit In > Edit in Photoshop. In Photoshop, make no changes of any kind. Save as, keeping the file as TIFF. Return to Lightroom and compare the reimported version to the original.Expected result: The image should be visually identical to the original, since no edits were made in Photoshop.Actual result: The reimported image is noticeably brighter than the original.Additional testing performed:Confirmed Edit in Photoshop settings match on both apps: TIFF, ProPhoto RGB, 16 bits/component. Photoshop Color Management Policy set to Preserve Embedded Profiles, and the file stays 16-bit throughout. Tested with resizing (various amounts and resample methods, including Preserve Details

Hello Adobe team,I am reporting an issue with Photoshop 27.7 on Windows 11 where the new Remove Tool on-device generative AI model cannot be enabled on an NVIDIA GeForce RTX 5080.The “Device” option remains greyed out, even though all documented requirements appear to be met.SYSTEM SUMMARYPhotoshop version: Adobe Photoshop 2026 / 27.7Operating system: Windows 11GPU: NVIDIA GeForce RTX 5080VRAM: approximately 16 GBDirectX: DirectX 12 / DirectX 12.2 availableNVIDIA driver: current and newer than Adobe’s stated minimum requirementPhotoshop GPU acceleration: enabledPhotoshop GPU status: GPU is detected and allowedAvailable disk space: sufficientThe GPU is usable for normal Photoshop GPU acceleration.The important detail is that Photoshop appears to detect and use the RTX 5080 for general GPU acceleration, but in the system information / GPU identification path the card is shown as:NVIDIA GeForce RTX 5080 UNKNOWNThis strongly suggests that the issue is not general GPU acceleration, but the

The system is running an up-to-date version of Windows 10 with the latest Nvidia Studio drivers. The Shadows/Highlights settings dialog has always provided a live preview while moving the sliders, provided the live preview option was enabled. Since the latest update to PS 27.8, however, the live preview no longer appears as soon as a slider is clicked or activated with the mouse. The preview remains hidden for as long as the slider is being moved or remains active; the preview only appears once the slider is released.  

IssuePhotoshop 27.10 and Photoshop Beta 27.11 have a significant performance regression when opening and saving image files on Windows 11.System- Operating system: Windows 11 Pro, build 26200- GPU: NVIDIA GeForce RTX 5060 Ti 16GB- NVIDIA driver: 616.56- Displays: two monitors, sometimes used in Extend modeSteps to reproduce1. Open the same image files in the previous Photoshop version.2. Open the same files in Photoshop 27.10 or Photoshop Beta 27.11.3. Compare opening one image, opening 10–20 images, Save, and Save As.4. Repeat the workflow with one monitor and with two monitors in Extend mode.Actual result- Opening image files is more than 50% slower in Photoshop 27.10 and Beta 27.11.- Opening 10–20 image files is also significantly slower.- Save and Save As are significantly slower.- Photoshop feels less responsive when using two monitors in Extend mode.- Rolling back to the previous Photoshop version clearly improves the opening and saving performance.Expected resultPhotoshop 27.10

When decoding Panasonic S1M2 RW2 RAW files in Adobe Camera Raw, the Camera Matching V-Log profile is severely inaccurate. So I cannot apply my Vlog LUTS on it.Additionally, after applying the Camera Matching profile in ACR, it is not possible to apply a LUT on top of it. This is a critical limitation for the RAW → V-Log → color grading workflow.（All Bug and issues above do not exist in Lumix Lab which is offical APP of Panasonic, I think you can fix these issues according to their offical APP）And I think you can improve it by learning the Color Edit Workflow in Davinci Resolve.

Hi everyone,I’m looking for help with a recurring issue when saving scanned PNG images as PDF files in Photoshop (27.3.1). Recently, the PDFs generated are partially corrupted or misread by Adobe Acrobat Reader DC and Photoshop.The Problem: When I open these PDFs in Adobe Acrobat Reader DC, I get the following error:"The dimensions of this page are out-of-range - Page content might be truncated."The page size appears as 1x1 mm, making the content cropped and pixeled.What I’ve discovered so far: Third-party viewers: If I open the same PDF with PDF-XChange, it displays perfectly with the correct dimensions. Re-opening in Photoshop: If I open the "corrupt" PDF back in Photoshop, it also shows the wrong 1x1mm size. The "Workaround": If I check the box "Preserve Photoshop Editing Capabilities" when saving, Photoshop is able to reopen the file correctly, but Acrobat still struggles with it. Has anyone encountered this "out-of-range" dimension issue recently? Is there a specific setting i

I would like to report a suspected EXIF metadata-writing issue affecting edited JPEGs from a Canon EOS R8.All affected files identify their editing software as “Elements Organizer 24.0.” The original camera JPEGs do not produce the same warning. The edited images still display and fully decode, but their EXIF directory structure is malformed.Environment- Operating system: Windows- Camera: Canon EOS R8- File format: JPEG- Embedded software/version string: Elements Organizer 24.0- Full installed Elements version/build: [add from About/System Information]- Diagnostic tools: ExifTool 13.59 and Pillow 12.3.0Actual behaviorExifTool reports this exact warning for every affected file:Wrong format (string) for IFD0 0x8769 ExifOffsetAn independent inspection of the JPEG EXIF/TIFF headers confirmed that tag 0x8769 (ExifOffset / ExifIFDPointer) is declared as TIFF type 2 (ASCII/string), rather than the expected type 4 (LONG).This field points to the EXIF subdirectory; it is not a timezone offset.

I’ve reported this already in “Bug Reports” and my post was deleted with no resolution and no communication. I’ve reposted there and now looking for help here!When “opening as layers in photoshop” the images are very slow to load in PS 27.8 vs. 27.7. This problem is confirmed by several other users I know. What used to take 11 seconds now takes 17 seconds. There’s a new behavior where each of the layers “flashes” up on screen for a split second before the loading actually starts and it takes significantly longer than it used. Downgrading to 27.7 restores correct (fast) functionality. Why would my bug report get deleted and if there’s a bug then, how are we supposed to report it so that Adobe will address it? Thanks

After updating my iPad to iPadOS 27, Photoshop 7.8.2 will not open any images. I receive “not a valid Photoshop 2.0 file.” This happens with new iPhone photos, screenshots, Camera Roll, Files, and Place Photo. I restarted the iPad and completely deleted/reinstalled Photoshop, but the problem remains. 

porque foi descontinuado as versão antigas do photoshop ?  quem não tiver pc moderno não poderá usar ? poderiam ao menos deixar uma versão antiga que possa roda em pcs mais antigos ....

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