Should I update?
All apps

Should I update Photoshop?

to 28.0.0 · out 3 daysWindows and macOS

Check known issues

Look through the issues below first: if you rely on one of those features, wait for the next update.

Your update:46 fixes · 6 new issues, 2 affect the verdictDetails

Not updating?

Three things that help while you wait.

  • So the app doesn’t update on its own.
  • If you have already updated.
  • Why there isn’t one answer, and what comes closest.

Go back to an earlier Photoshop version

In the Creative Cloud desktop app, on macOS and Windows.

  1. To keep your settings: first uninstall the current Photoshop (⋯ › Uninstall) and choose Keep when asked about your preferences.
  2. Open the Creative Cloud desktop app and find Photoshop in your apps.
  3. Select ⋯ (More actions) next to Photoshop, then Other versions.
  4. Choose the version you want and select Install.

So it doesn’t update again: Apps tab › ⋯ (More actions) › Manage auto-updates, and turn off Auto-update for Photoshop.

Adobe lists previous major versions there, so not every release may be offered. With a school or work account, your organisation may have hidden some of these options.

Adobe’s instructions

Which version should I install?

There isn’t one answer, and here is why.

There is no one version that is safe for everyone: which of the open issues affect you depends on how you work. A bug on Windows says nothing to a Mac, and a bug in a tool you never open says nothing to you. Naming one version for everyone would mean pretending that difference away.

So read the issues behind the verdict and see whether they touch your work. Each one says how bad it is, how many people it affects, which system it happens on, and whether there is a workaround.

If the current release doesn’t work for you: .

Turn off automatic updates for Photoshop

In the Creative Cloud desktop app, on macOS and Windows.

  1. Open the Creative Cloud desktop app.
  2. In the Apps tab, select ⋯ (More actions) in the Installed apps panel, then Manage auto-updates. If it says Enable auto-updates instead, they are already off.
  3. Turn off Auto-update for all apps, or leave it on and turn off only the switch next to Photoshop.
  4. Select Done.

To update later: check the verdict here, then in the Home tab select Updates and Update next to Photoshop.

Keeping auto-update on for other apps? Under Advanced options, leave Remove older versions unchecked, so you can still go back.

If the Auto-update switch is locked or missing, your organisation manages updates for you.

Adobe’s instructions

Why this verdict

Check known issues

MajorCommon workflowWindows onlyNot tracked by Adobe yet
Workaround: Shift-click each layer in the Layers panel to build a multi-layer selection.
Reported November 11, 2026DetailsRead the report

MajorCommon workflowmacOS onlyAdobe: Investigating
Workaround: Click the layer in the Layers panel, even though it is already selected, or use Layer > Align Layers to Selection.
Reported November 8, 2026DetailsRead the report

Other known issues: 2 tracked by Adobe, 2 not yet. They don’t change the verdict.

Tracked by Adobe

MinorCommon workflowAdobe: Investigating
Reported November 10, 2026DetailsRead the report

MinorCommon workflowmacOS onlyAdobe: Investigating
Workaround: Type the value into the numeric field next to the slider instead of dragging.
Reported November 8, 2026DetailsRead the report
Not tracked yet

MajorCommon workflowNot tracked by Adobe yet
Reported November 11, 2026DetailsRead the report

MajorCommon workflowReported on 28.0.0Not tracked by Adobe yet
Workaround: Run the action via a Droplet instead of File > Automate > Batch so remaining files keep processing after you dismiss each error.
Reported November 12, 2026DetailsRead the report

Fixes · 46

From Adobe’s release notes.

Customer-reported fixes

  • Photoshop 27.10: "Edit in Photoshop" from Lightroom Classic & Lightroom Desktop does not load image with Denoise
  • Show on-disk file size of smart objects and layers in Layers panel
  • Single corrupt channel aborts entire MT read instead of degrading gracefully like the canonical reader
  • Loading image sequence ignore exif/tiff orientation tag
  • [Win] Script "Load Files into Stack" failed with a "Cannot convert" error on non-English system locales.
  • [Mac] Raw images edited in Camera Raw via Bridge with Denoise adjustments could not be opened.

Crash fixes

  • Photoshop crashed when adding swatches from the Swatches panel while an Adjustment dialog was open.
  • Photoshop crashed when double-clicking gradient layer color stops in the Properties panel, causing multiple color pickers to open.
  • Photoshop crashed when clicking legacy Brushes in the flyout menu from the Brush panel on Windows.
  • Photoshop crashed when using Dynamic text on the Vertical Type Mask tool.
  • Photoshop crashed in the Curves view controller when updating tool buttons.
  • Photoshop crashed in the Hue/Saturation properties view.
  • Photoshop crashed when opening the Format menu in certain text workflows.
  • Photoshop crashed during Generative Upscale when using face enhancement via the Agent API.
  • Photoshop crashed when soloing the Rotate Object layer while editing.

Generative AI fixes

  • Generative recompose completed, but the result document could not be determined, producing an error.
  • Generative credit icon was missing on localized locales for the Generative recompose panel.
  • Generative recompose dialog fields were misaligned in localized builds.
  • Output Size in the Generative recompose dialog was misaligned by a few pixels.
  • Deprecated Gemini model error did not appear when using Prompt to edit or Generate image.
  • Soft inpainting produced garbage pixels on partial layers after using Remove tool.

UI, dialogs, and panels

  • "Something went wrong" error appeared when selecting Open from the home screen.
  • Artboards could not be created when multiple Photoshop documents were open.
  • Color panel needed a manual refresh to display correct colors in some workflows.
  • OCIO color management was broken when OS dark mode was off.
  • The Switcher ToolTip card persisted on screen even after Photoshop was minimized in Freemium mode.
  • The new Color Panel and Swatches were not disabled by the modern UI preference setting.
  • Properties panel did not show file sizes for images more than 32,000 pixels wide.
  • Place Linked with long file names expanded the Properties panel beyond its bounds.
  • Blank canvas appeared when drawing a new frame in Flow Canvas.
  • Legacy swatches only appeared after rebooting Photoshop.
  • Color Picker hue-cube sweep generated hundreds of recently used swatches.

Other notable fixes

  • Show on-disk file size of smart objects and layers in the Layers panel.
  • Edit the file name of embedded Smart Objects.
  • Junk characters appeared when renaming a Count tool folder.

Localization fixes

  • Truncated text with ellipsis in dialog strings on certain locales.
  • "Show Tool Groups on Hover in the Toolbar" string was not localized.
  • Junk characters appeared when renaming a Count Group.
  • [ES] Lightshop 8-bit warning string showed code bleeding.
  • "Enhanced edge" layer name was not localized.
  • [CN] Generative recompose showed a "cannot complete request" dialog instead of the localized error.
  • [KO] Adjustment panel strings and tooltips displayed in English instead of Korean.
  • "Start free trial" string translation was inconsistent between the Home Screen and Editor.
  • "Removing area..." loading string was not localized for Remove tool.
  • Adjustment Brush tool Contextual Task Bar strings were not localized.
  • Generative restyle strings were not localized in the release build.

New issues · 6

First reported after 27.11. 2 affect the verdict. See them with the known issues.

Fixes are Adobe’s own list; issues are what users reported, listed under the version the report names.

MajorAffects most userssince 27.10Adobe: Investigating
Workaround: Disable Use Graphics Processor under Preferences > Performance, or uncheck Foreground Composite Cache and Use GPU Compositing in Advanced settings.
Reported August 31, 2026DetailsRead the report

MajorSpecific featuremacOS onlysince 27.9Reported on 27.9.1Adobe: Investigating
Reported August 12, 2026DetailsRead the report

MinorSpecific featuremacOS onlysince 27.7Adobe: Investigating
Workaround: Disable Enable Modern User Interface under Technology Previews, or right-click to paste in the file name field.
Reported June 2, 2026DetailsRead the report

MajorSpecific featuresince 27.7Adobe: Investigating
Workaround: Export each slice format separately.
Reported May 29, 2026DetailsRead the report

Known issues in Photoshop 28.0Earlier releases: 27.11, 27.10, 27.9, 27.8, 27.7, 27.6, 27.5, all of 2027, all of 2026

How we decide

Based on public bug reports, not Adobe statements. Small numbers, read as a trend.

Every night we read the Photoshop bug reports on the Adobe Community board. An issue is listed once Adobe tracks it (sets a status such as “Investigating” or “Acknowledged”), or once it has 3 votes. Tracked doesn’t mean Adobe has reproduced it, only that someone at Adobe has taken it up. Issues Adobe isn’t tracking yet only count toward the verdict from 10 votes, so a handful of reports can’t swing it.

The verdict covers the whole 28.0 release, including its updates: an issue reported on an earlier build still counts until Adobe marks it fixed, since an update only fixes what it says it fixes.

Each issue is rated for how bad it is and how many people it affects, with AI assistance following a published rubric and checked by hand where it matters. The worst open issue decides the verdict: a problem practically everyone runs into means “Don’t update”, a problem in a common workflow means “Check known issues”.

Windows and macOS get their own verdict: the same rule over the issues that happen on that system. They are shown side by side when they differ, and as one box when they agree. Which system an issue affects is counted from its thread: an AI reads every reply that names Windows or macOS and decides whether it is a report of the bug. Instructions, questions and “works fine on my Mac” don’t count. If the reports come from Windows users and at most one person reports it on macOS, it counts as a Windows issue.

“Not marked fixed from earlier versions” lists issues from the previous 5 releases with 3 or more votes that Adobe tracks and hasn’t marked fixed: they are most likely in the current release too. Issues Adobe marks as released are fixed in a later update.

The line under the verdict is about your own update. It starts from the release before the current one, which is also the view the verdict takes, and you can pick the version you have. The fixes it counts are Adobe’s own list from its release notes; the new issues are the reports first made after your version that are worth a check.

What we don’t do is name one version to install instead. There is no one version that is safe for everyone: which of the open issues affect you depends on how you work. A bug on Windows says nothing to a Mac, and a bug in a tool you never open says nothing to you. That is why every issue is listed with who it affects, and why the verdict is a starting point rather than an instruction.

Something look wrong, or missing? Write to shouldiupdate@pixelsucht.net.