Skip to main content

Filter by idea status

10000+ Ideas

PCL86
PCL86Participant

Add a “Don’t show again” option to AI Denoise and AI Sharpen confirmation dialogsOpen for Voting

I would like to request an improvement to the confirmation dialogs shown when using AI Denoise and AI Sharpen in Photoshop.Currently, every time I intentionally use AI Denoise or AI Sharpen, Photoshop displays a confirmation dialog explaining that the feature uses a Topaz partner AI model and may consume generative credits.I understand that this information is important, especially for first-time use. However, displaying the same confirmation dialog every single time interrupts the workflow unnecessarily. These features are selected and used intentionally by the user, so repeated confirmation becomes more of a disruption than a useful warning.Please add a “Don’t show again” checkbox to these dialogs, similar to other Photoshop warning dialogs. Ideally, the warning should appear only the first time, and users should be able to re-enable it later from Preferences if needed.Requested improvements:- Add a “Don’t show again” checkbox to the AI Denoise confirmation dialog- Add the same option to the AI Sharpen confirmation dialog- Show the warning only on first use once the user has acknowledged it- Provide a way to reset or re-enable these warnings from PreferencesThe information about partner AI model usage and credit consumption is understandable, but showing it every time significantly slows down the workflow. Photoshop is a professional tool, and users should be able to acknowledge this once and continue working without repeated interruptions.Thank you for considering this improvement.

Eorl999
Eorl999Participant

Restore automatic crop snapping to rotated image bounds (pre-AI behavior)Open for Voting

In recent versions of Photoshop, the Crop Tool no longer automatically snaps to the actual pixel bounds of a rotated image in the way it used to.Previously, when rotating slightly and then cropping, the crop frame would naturally align to the real edges of the image content. This made it easy to avoid leaving unintended empty/black edges in the corners.Currently, the tool instead assumes that the user may want to expand the canvas (e.g. via Generative Expand), and does not respect the true pixel boundaries in the same way. This makes precise cropping slower and increases the risk of leaving small artifacts (e.g. thin black triangles in corners).Request:Please add an option (or restore default behavior) for:Automatic snapping of the crop boundary to the actual rotated pixel edges A “strict pixel bounds” mode that ignores AI/expansion assumptionsWhy this matters:In photojournalism and other documentary contexts, it is essential that images are not altered beyond basic adjustments. AI-generated image expansion is not ethically acceptable in these workflows.Because of this, tools should clearly support a “pixel-accurate” workflow where only existing image data is used, and where boundaries are respected automatically.The previous crop behavior supported this kind of work more reliably. The current behavior increases the risk of unintentional errors and slows down a precision-focused workflow.

debunixKnown Participant

Keyword sync between Bridge and Lightroom and Lightroom and BridgeOpen for Voting

I'm trying to switchover from Adobe Bridge to Lightroom for tracking and sorting photos. I have literally hundreds of keywords, lots of species and common names, in Bridge.  I need a proper photo catalog again, and Lightroom is what's there.  But....it turns out Bridge will happily export those keywords to an .xml or .txt file, but Lightroom will not import them directly because Lightroom disallows punctuation characters in keywords.But after I worked with text edit to remove/replace all of the forbidden characters, and imported the xml file into Lightroom, it did import them, but kept all the formatting stuff...So each of these lines came out as keywords<?xml version="10" encoding="UTF 8" standalone="yes" ?><keywords version="2">    <set name="Characteristic" disclosed="false">        <item name="Geolocator screenshot" />        <item name="inset closeup" />        <item name="Landscape" />        <set name="macro" disclosed="true">            <item name="extension tubes" />        </set>        <item name="scale" />        <item name="silhouette" />        <item name="video" />So         <item name="Geolocator screenshot" />And not    Geolocator screenshotI see complaints about this going back 20 years--I presume since the introduction of one or the other of these two programs.I want my keywords written into metadata so available across ALL apps for the future.And I should not have to retype those hundreds of words and be limited to classifications Adobe selects, like 'People' or 'Other'.  Is this meant to be for working catalogs of thousands or hundreds of thousands of diverse images, or not?And we're in 2026. How hard it is to code things so Lightroom can work with ALL CHARACTERS when Bridge can already do it?I'm not the first with this complaint, nor the last.  Some come to it from Bridge, some come to it from Lightroom.What were they thinking, to set up sibling programs and NOT sync the metadata handling?  Really, really not good customer service to make your users work this hard.  I call this a BUG.  And I also REQUEST the feature of interoperability between these sibling programs.