Skip to main content
.random..
Inspiring
June 14, 2026
Open for Voting

Additional Feedback on Action Buttons & Shortcuts

  • June 14, 2026
  • 3 replies
  • 33 views

First, I really like this feature. Having actions available as buttons with assigned shortcuts can significantly speed up repetitive workflows.

A few suggestions:

  • Shortcut conflicts: If a shortcut is already in use, Photoshop should show which command or action is using it and allow users to reassign that shortcut directly from the conflict dialog instead of simply blocking the assignment.
  • Editable save settings: For save-related actions (PNG, JPEG, TIFF, PSD, etc.), it should be possible to open and edit the associated save settings directly from this panel, including compression, transparency, ICC profiles, metadata, layers, and other format-specific options.
  • Better keyboard navigation: Pressing Enter should save changes immediately. Pressing Esc should return to the previous screen. The entire interface should be fully keyboard-accessible. Basic UX.
  • Save button placement: The Save button sits at the bottom of the panel. Consider moving it higher, duplicating it at the top, or relying on Enter as the primary confirmation method.
  • Larger icons: The icons are quite small and the icon library is limited. Larger icons and a broader icon selection (or custom icons) would improve visual recognition.
  • More modifier keys: Please support additional modifiers such as Control and Option/Alt. This would greatly increase the number of available shortcut combinations and reduce conflicts.

Overall, this feature has huge potential for power users. A few UX improvements could make it much faster and more intuitive to configure and use.

    3 replies

    .random..
    .random..Author
    Inspiring
    June 15, 2026

    -

    Trevor.Dennis
    Community Expert
    Community Expert
    June 15, 2026

    It already warns you what shortcut is being overwritten. 

    The way to keep things under control is to save custom shortcuts with custom workspaces. That way you simply swap workspaces when you need to use the default shortcuts

    Are you using a laptop, or do you have limited screen space?

    These are the defaults for the unmodified Function keys.  Some of them might useful if you have limited screen space, but IMO those keys are far to useful to waste on functions that already have shortcuts like copy, paste, cut etc.  

     

    You can use the F keys directly in Edit Shortcuts, but when selecting a workspace you need to set it and reset it to tidy it back to its as set state.  So, I use tiny actions triggered by the function key.

     

    Sometimes you need to hit Escape twice, and sometimes you need to make sure Photoshop has focus when hitting Escape.

    PLEASE don’t move the Save key Adobe.  That is the worst idea I ever heard.  Every app in this and every alternate universe has Save in the same place.

    Yes please to being able to increase icon size.  I’m old and that 1440P workspace in my screen shot breaks my heart as it is applied to a 4K Pro Art Display that I have to down-res in order to use Photoshop. :-(

    More modifier keys

    Get a gaming keyboard with programable keys.  There’s an Adobe co-ab with Logitech somewhere in these forums. Go there and have your say.  Use different shortcuts with your different workspaces.  I do both of these.  I’ve gone through a lot of keyboards, and it’s the Corsair keyboards that keep on working.

    .random..
    .random..Author
    Inspiring
    June 15, 2026

    I think we’re talking about two different things.

    I’m not saying I don’t know how to do it.

    I’m saying I know how to do it, but I think the UX of the process is unnecessarily clumsy.

     

    Photoshop already knows when a shortcut is in conflict. It already knows exactly which command or action is using it. At that point, wouldn’t it be nice to let us resolve the conflict right there instead of forcing us to leave the dialog, remember where the shortcut is assigned, change it elsewhere, and then come back?

     

    And while we’re talking about UX: just look at this panel. Why is the Save button placed as far away as possible from where all the editing happens? If going back doesn’t discard changes anyway, who exactly is benefiting from having Save all the way down there?

     

     

    D Fosse
    Community Expert
    Community Expert
    June 14, 2026

    You can still edit save settings directly from the panel, just as you can edit any action step. However, the edit function is too cryptic and hidden as it is now. Top of my wish list is two main buttons, one Play and one Edit, clearly visible and up front. I’ve suggested a layout for this before (can’t find it now) - no functional changes, just a clearer UI.

     

    As for a pop-up dialog to immediately resolve shortcut conflicts, that has AFAIK always been there.

     

    Yes, more available shortcuts would be good.

    .random..
    .random..Author
    Inspiring
    June 15, 2026

    I agree that editing action steps directly from the Actions panel is the right approach and generally works well.

     

    However, in the specific case I reported, I may be seeing different behavior.

     

    When I try to edit a recorded “Save As” step, I don’t get any dialog allowing me to modify the save options. Because of that, I’m not sure whether this is a bug, a limitation of that particular action step, or something specific to my setup.

     

    Could you verify this on your side?

     

    If you try to modify a “Save As” action, does clicking the Settings button open the full Save dialog and allow you to modify all save options?

     

    I’d be interested to know whether this is expected behavior or something that isn’t working correctly.

    D Fosse
    Community Expert
    Community Expert
    June 15, 2026

    What file format are you saving to? If it’s an old action, it may be trying to save a document with properties that aren’t supported in the target file format. Then Save won’t open.

     

    A few years ago you could get away with that because it would branch out a compliant (dumbed down) copy automatically, but MacOS changes stopped that, and now that has to explicitly call Save A Copy.

     

    Can’t test anything until this is clarified.

     

    (If this is the case, the smart option is to take advantage of the fact that it’s an action, and include steps to make the document compliant first).