Photoshop Developers

Currently, Photoshop names Generative Fill layers using the full AI prompt, which often results in very long file names appearing in the document tabs. This makes it harder to quickly navigate between multiple open files.Proposed Solution:Instead of displaying the full prompt in the file name tab, use a short identifier such as:“AI Layer” or a simple symbol/icon indicating AI-generated contentThe full prompt can still be preserved in:Layer metadata Properties panel Tooltip on hoverExpected Outcome:Cleaner, more compact file tabs Faster file navigation in multi-document workflows Reduced visual clutter without losing prompt dataThis keeps the interface minimal while still retaining all the important information in the background.

Adobe Photoshop Version: 27.5.0 20260314.m.3457 1720e4b  x64 (beta, PublicBeta)Windows 10Steps:Select something with the marquee tool, or other selection tool click “Select Inverse” in the contextual task bar use the brush tool on the selection try to press crtl + z or other keyboard shortcuts it doesn’t work! for some reason!I wanted to type out a more detailed description with more examples but I somehow submitted this before I was done typing. This has actually been happening for a while but I just was ignoring it.I cannot figure out how to consistently get the keyboard shortcuts working again other than waiting for a while and clicking seemingly random things on the screen. 

En la sección de curvas se desconfiguran y la línea ya no la puedo mover después de un tiempo para hacer ajustes en la imagen. Solamente se mueve con las teclas de movimiento. Después de desconfigurarse  la sección de curvas todo photoshop falla 

1. When will the next version of Photoshop be released after updating to 27.5?2. Why is there no date in Settings > Installed Apps after successfully updating to 27.5?

I’m having an issue with the new Rotate Object feature in Photoshop Beta 27.6.0.The option is grayed out in the Contextual Task Bar, and I can’t click it.Here’s what I’ve already checked/tested: Photoshop Beta 27.6.0 Creative Cloud Pro account RGB 8-bit Rasterized layer & smart object Tried it in Transform mode Tried a brand new file with a transparent background Color profile set to sRGB IEC61966-2.1 Tried both PNG and JPG Tried it with my own object image Also tried it with a free Adobe Stock image, and it still did not work

After 30 years of working with photoshop, content aware fill is acting odd. It fills in the desired area with strange  mixes of the sampled content. It used to pick up one what was in the edges and intelligently fill in the blanks. I am using the same techniquest I’ve been using for DECADES. I want to emphasize again that I’ve been using this app for a VERY long time and this is not user error. You folks need to review this and fix it. I added this under “Photshop Developers” but I am talking about the

Dès que j’ouvre photoshop mes outils ne s’affiches pas. J’ai essayer de les masqué puis les affichés, j’ai éteint démarré, encore éteint encore démarré mais absolument rien n’y fait, à chaque fois c’est le même problème depuis la version 27 et c’est extrêmement pénible. J’ai désinstallé photoshop puis réinstallé mais rien y fais… Résolvez ce problème s’il vous plait. 

Photoshop バージョン: 27.4.0問題:キャンバスサイズの変更がアクションに記録されない。詳細:Photoshop 27.4.0 で新規アクションを作成し、キャンバスサイズを変更すると、ステップ自体は記録されますが、幅と高さの値が保存されません。そのため、アクションを実行してもキャンバスサイズが変更されません。テスト結果:同じ操作は Photoshop 26.11.3 では正常に動作します。26.11.3 で作成したアクションは、Photoshop 27.4.0 でキャンバスサイズを正しく記録し、正常に動作します。結論:これは Photoshop 27.4.0 のアクションレコーダーのバグであると思われます。

Photoshop version: 27.4.0 Problem:Canvas Size changes are not recorded in Actions. Details:When creating a new action in Photoshop 27.4.0 and changing the Canvas Size, the step is recorded but the width and height values are not saved. Therefore the canvas size does not change when the action is played. Test results:The same operation works correctly in Photoshop 26.11.3.Actions created in 26.11.3 record the Canvas Size correctly and run normally in Photoshop 27.4.0. Conclusion:This appears to be a bug in the Action Recorder in Photoshop 27.4.0.

Hello, I would like to use the Photoshop API for my project, but I'm not sure how to get started. Our company already has an active Adobe Creative Cloud subscription (enterprise/team plan). I'd like to know: 1. Do we need to sign up for a separate API access, or is the Photoshop API included in our existing subscription?2. Where can I obtain the API credentials (Client ID, Client Secret, etc.)?3. Are there any additional costs or usage limits associated with the Photoshop API?4. What is the correct process to set up a project on the Adobe Developer Console and enable the Photoshop API?5. Is there any official documentation or quickstart guide you would recommend? Any guidance or step-by-step instructions would be greatly appreciated. Thank you!

Hi everyone,in a Photoshop 2026 UXP plugin I want to export an artboard (or layer) as an jpeg image. Same function as right clicking an artboard or layer and selecting “Export As” choosing JPG with quality 6.I am using Photoshop 2026 27.4.0 on OSX with M1 CPU. UXP 9.2.0 and UXP Developer Tools 2.2.1I just found a method to export a whole document using document.saveAs.jpeg() method. But I do not want to export the whole document, just a few artboards inside it.I tried duplicating the document and using document.crop() method on the copy. But the crop method doesn’t do anything, the document with and height are the same after crop(). See here:/* Non working example of using document.crop()*/await core.executeAsModal(async () => { const document = app.activeDocument; console.log(`Document size before crop: ${document.width} x ${document.height}`); const res = await document.crop({top: -61, bottom: 660, left: 8753, right: 9934}); console.log(`Document size after crop: ${

Add the ability to paint brush strokes as lines, like in Fresco. When you draw a stroke in Fresco and hold at the end, a perfect line is drawn using your current brush. The only way to accomplish this now in Photoshop is to either Shift-tap (which draws a line from your starting point but with no indication like a rubber band) or to create a path then stroke the path with your brush. Both of these methods are outdated and cumbersome. The Fresco method is much easier and modern.

Product: Adobe PhotoshopVersion: 27.3.1Operating System: Windows 11 ProOS Version: 24H2Build: 26100.7705Architecture: 64-bitPrinter Model: HP OfficeJet 3833Printer Type: Inkjet(Usual Connection: USB or Wi-Fi — does not affect the result)Problem Description: Photoshop is excessively slow during the printing process.When sending any document to print, the program spends a considerable amount of time processing the job before sending it to the printer, even with simple, small files.The system functions normally, and the problem only occurs within Photoshop, not with other applications.Frequency:The problem occurs consistently and reproducibly.Expected Result:The print job should be processed and sent to the printer immediately or with minimal latency.Current result:Prolonged delays before the document is sent to the printer.I request that this be reviewed as a possible performance or compatibility issue between Photoshop 27.3.1, Windows 11 Pro 24H2, and the HP OfficeJet printer's printing

** Edit **posted in wrong senction. Reposted in photoshop beta bugs.  

No puedo expotar mis archivos jpeg en alta calidad, no me permite configurar una alta calidad antes de guardar en mi version de ps web  

Hello Adobe,I’m developing a UXP plugin that normalizes transformed text layers (similar to Free Transform → Apply behavior). The goal is to recreate the text layer cleanly with the same visual appearance — same text, font, color, and point size, but without transformation.While this works perfectly using ExtendScript (JSX), in UXP the results are inconsistent:The new text appears much smaller than the original when the source layer was a paragraph text (area text).Multiple new layers are created at random positions far from the original location.The effective visual font size calculation based on boundsNoEffects vs. a clean text layer width seems unreliable in UXP.It appears that UXP’s text creation and measurement APIs (batchPlay, bounds, textKey.textShape) handle paragraph text differently than JSX, breaking proportional scaling and position tracking.Could you please investigate or confirm if this is a known limitation of the UXP Photoshop API?We need consistent behavior between JSX

Hi everyone  ! I am trying to do an uxp plugin for photoshop, and in that project I a m trying to recreate a script I made as an extended script to automate some actions. One of them I do pretty often is to move a layer inside a group once I made some changes. Such as :  if (cameraLayer.parent !== infoATCGroup) { cameraLayer.move(infoATCGroup, ElementPlacement.INSIDE);But I do not see any of this in the documentation for uxp and when I use what I see in the plugin Alchemist while moving a layer intoy a group, it does not work and occurs an error  when I try to use the same syntax in my uxp plugin. Here is an exemple of what I see with Alchemist : const {executeAsModal} = require("photoshop").core; const {batchPlay} = require("photoshop").action; async function actionCommands() { const result = await batchPlay( [ { _obj: "move", _target: [ { _ref: "layer",

Hi everyone,I’ve been working on a custom UXP plugin called ChatGPT Bridge (v1.0.0). It loads successfully in Adobe UXP Developer Tools, but when I load it inside Photoshop (v26.7.0) the panel appears — yet it’s completely blank. No HTML content is rendered.Setup details:- Plugin name: ChatGPT Bridge- Version: 1.0.0- Photoshop version: 26.7.0- Manifest version: 5- Files included: `manifest.json`, `index.js`, `bridge-panel.html`- Folder structure is correct, and the plugin loads fine in UXP Dev Tools without errorsIssue:When I open the panel in Photoshop, the JS code runs (alert tests confirm this), but `bridge-panel.html` never displays. The panel window is visible but empty.Troubleshooting done so far:- Verified manifest structure and file paths- Confirmed HTML file exists and is referenced correctly- Replaced `.png` icon with `.ico` format per Photoshop UXP requirements- Tested with `document.body.innerHTML` to check if the HTML is being read (no visible output)- Restarted Photoshop

Here's an example using the active document name without extension:   var docName = app.activeDocument.name.replace(/\.[^\.]+$/, ""); var d = new ActionDescriptor(); d.putString(stringIDToTypeID("textData"), docName); executeAction(stringIDToTypeID("textToClipboard"), d, DialogModes.NO);    P.S.: Rather than assuming the ruler units, it's often safer to explicitly set them:   var w = app.activeDocument.width.as('px'); var h = app.activeDocument.height.as('px');   var origRulerUnits = app.preferences.rulerUnits; app.preferences.rulerUnits = Units.INCHES; // Units.PIXELS etc var w = app.activeDocument.width.value; var h = app.activeDocument.height.value; app.preferences.rulerUnits = origRulerUnits;  

Hello, everybody!My task is: a script, that copies the dimensions of an image (or other predefined text) to the system clipboard: #target Photoshop var w = Math.round(activeDocument.width); var h = Math.round(activeDocument.height); var str = "image size is : " + w + " X " + h;My question is: How to copy "str" to system clipboard? 

 Hi,I have an older native C++ plugin built using Photoshop 2022 SDK. I’m trying to communicate with a UXP plugin using PIUXPSuite.In my native plugin, inside the StartUpPlugin function, I have the following code:  if (!sUxpProcs) { LOG_TRACE((0, "🔧 [UXP-LISTENER] Acquiring PIUXPSuite for message listening")); SPErr e = sSPBasic->AcquireSuite(kPSUXPSuite, kPSUXPSuiteVersion1, (const void**)&sUxpProcs); if (e != kSPNoError) { LOG_TRACE((0, "❌ [UXP-LISTENER] Failed to acquire PIUXPSuite: %d (0x%08X)", e, e)); } else { LOG_TRACE((0, "✅ [UXP-LISTENER] PIUXPSuite acquired for listening: %p", sUxpProcs)); // Get plugin information using available SPBasicSuite methods LOG_TRACE((0, "🆔 [PLUGIN] Plugin Reference: %p", gPlugInRef)); // Add UXP message listener SPErr listenerResult = sUxpProcs->AddUXPMessageList

Bug Report:Photoshop Version: v26.11.0 and betaOperating System: Windows10 & 11Problem:Any UXP plugin, including the most minimal test case, fails to launch from the Plugins menu. It always produces the same console error: TypeError: Cannot read properties of undefined (reading 'commandId') at oe.menuItemClickHandler.Steps to Reproduce:This has been confirmed on two separate computers with fresh installations of Photoshop and the UXP Developer Tool. The error is 100% reproducible with the minimal plugin code below.When this plugin is loaded and "Run Bug Test" is clicked from the Plugins menu, it throws the commandId error instead of showing the alert. This demonstrates a critical failure in the UXP command system for this build of Photoshop.

Hello, We have developed a UXP plugin (written in plain JavaScript) for Photoshop, and we would like to have support for Windows 11 ARM. Is there a workaround available at the moment, or are there any plans to support it? All the best,Nikos

Hey everyone,I’m building a web app that needs to merge 3 bracketed RAW images (dark, normal, and bright) into a single HDR image, similar to Photoshop’s “Merge to HDR Pro” feature on desktop.Does anyone know if the Photoshop API supports this functionality, or if there’s any endpoint that can combine exposures into a 32-bit or tone-mapped HDR image?If not, is Adobe planning to add HDR merge support in a future API update?Thanks,Amin Bulaqi

Hello everyone,I'm a Photoshop plugin developer currently adapting my product for the native ARM64 version of Photoshop on Windows.I'm trying to determine the best practice for an installer to handle the architecture choice correctly. The SDK documentation doesn't seem to cover this installation strategy in detail.The Core Problem:Even on an ARM64 Windows machine, a user could have either:The native ARM64 version of Photoshop.The x64 version of Photoshop, running through emulation.This is especially relevant when installing to the common Program Files or AppData plugins directory, which might be shared.I've researched this and received a suggestion (from an AI, to be transparent) about a potential method. It claims that the solution is to install both the x64 and ARM64 versions of the plugin into a specific folder structure, and Photoshop will silently load the correct architecture version while ignoring the incompatible one.The proposed structure would lo