Photoshop

Cancelei o teste gratuito no prazo e está a ser debitado cobrança em minha conta. Gostaria que fosse resolvido 

I wanted to buy Premiere Pro, but I made a mistake and instead I bought photoshop. Can I have a refund? or is it over for me :,(

Photoshop crashes. Photoshop was running fine until it said the scratch drive wasn’t big enough so I followed advice on forums and cleaned up some files in the c:drive to make more space. I also at this time opened the old gradients and followed advice to move them on my computer somewhere in the app data roaming. I have since checked the following: reset preferences, reset windows font cashe, manually deleted CT font cashe and roaming data, disabled GPU in preferences, reinstalled creative cloud and photoshop many times, ran a windows system repairs (sfc\scannow)  tried with a different local account on same laptop, used Adobe cloud cleaner tool,, checked read write access to folders (but could not do spool\drivers\colour). The problem started when I tried to fix the scratch drive and when I was at same time tried to restore the old legacy photoshop gradient tools. I have tried now to put my scratch drive on a different drive and this also doesn’t work (although I don’t know if possib

Recent PS update blocks `<textarea>`/`<input>` transparency + breaks button/input styling (UXP regression)I've been developing a plugin for 1.5 years, had it working beautifully with styled themedbackgrounds, and was waiting on Marketplace seller verification. A recent Photoshop update hasblocked `background: transparent` on native form controls in UXP, which has taken anotherwise finished, ready-to-ship plugin out of commission.Environment- Photoshop (release): `<FILL IN — Help ▸ About Photoshop>`- Photoshop (Beta): `<FILL IN>` — **reproduces identically in Beta**, so this is unfixed across the current pipeline (no staged fix)- UXP runtime: `<FILL IN — require('uxp').versions>`- macOS: `<FILL IN>`- manifestVersion: 5What broke1. `<textarea>` / `<input>` no longer honour any transparency. `background: transparent`   (and even low alpha such as `rgba(255,255,136,0.01)`) renders as a solid dark block   instead of showing the layer/paper beh

When using the default, “Soft Round Pressure Size” brush in Photoshop, I am experiencing an issue I’ve found out to be called the “shoelace” or “aglet.” You can see it in the images I’ve provided, but essentially, I have these small “aglets” at the ends of my strokes when using pen pressure as the control for the size of my brush. These “aglets” appear no matter the setting, driver, hardware, user profile, or pen-tip adjustments that I’ve tried so far. In my experience, what I’m seeing is a light “hotspot” when I put my pen down (if using opacity/flow below 100%), and when I pull up, I get the aglets. I am in a digital illustration class, and my professor uses this brush for our exercises, making it difficult for me to keep up with the class.Below I will list out, to the best of my ability, my relevant hardware/software specs as well as the diagnostic tests I’ve tried. This happens across all hardware and driver installs: Software -Windows 11: version 10.0.26200 build 26200 Driver: NVI

I'm a seasoned Photoshop/Bridge CS5 user who recently upgraded to CS6.  In Bridge I just ran my first Image Processor batch, trying to convert a set of RAW .NEF files to .PSD files with a basic editing action I created applied to them.  Photoshop CS6 opens the files from Bridge and applies the actions, but then I get the "Script alert" error message "Sorry I could not process the following files" and a list of all of the files in the batch I was trying to run the script on.  The files all remain open and are saved on my hard drive in a folder created by the Image Processor script, but do not close unless I manually close them.  I never had this problem in CS5 where the image processor would apply the desired actions to the batch of photos one at a time, then save and close.  Thoughts on how I can fix this bug?

This version has so many bugs, I don’t even want to use it any more and am switching back to 2025. Just to name a few, it crashes every time you try to print directly from the program. The last month alone, it has cleared my actions 3 times without an app update. It crashed randomly when our workflow is always the same. I have files that work just fine with older versions, but with 2026 it acts like my files are corrupt. Updates clearly aren’t helping either and I have my workspace and preferences the way I like, but even with syncing the actions continuously get cleared. If this ever gets fixed I’ll consider switching, but in the meantime until 2027 comes out, I will be sticking with 2025.

I’ve been experimenting with Photoshop for creating Roblox-style gaming thumbnails and profile graphics, especially for mobile viewers on YouTube and Discord.One issue I keep running into is that some text effects and character outlines look sharp on desktop but become blurry or overcrowded on smaller screens.I’m also testing different username styles and invisible spacing characters for cleaner gamer tags, but compatibility seems inconsistent across platforms.For creators working on gaming thumbnails or Roblox-related graphics:What canvas size works best? Do you sharpen before or after resizing? Are there recommended export settings for mobile clarity? How do you preview username formatting across platforms?Would appreciate any workflow tips from people designing gaming content in Photoshop

# Generative Remove runs on the CPU instead of the GPU since version 27.9.1**Issue summary**Since updating to Photoshop 27.9.1, the Remove tool in Generative mode loads about 6 GB of data into the graphics card memory, then performs the actual work on the processor instead of the graphics card. The graphics card stays at idle power for the whole operation. A removal that used to complete quickly now takes several minutes.**Product and version**Photoshop desktop version 27.9.1 (build 20260803.r.1 65900e1)**Last version where it worked correctly**Photoshop 27.8.0 (build 20260610.r.13 4081857). The problem started immediately after updating on 6 August 2026.**Operating system**Windows 11 Pro, version 26200**Hardware**Graphics card: NVIDIA RTX PRO 4000 Blackwell, 24 GB, driver 32.0.15.9672Processor: Intel i9-13900K (32 logical cores)Memory: 128 GB**Steps to reproduce**1. Open any photo.2. Select the Remove tool.3. In the options bar, make sure the generative mode is turned on.4. Paint over

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 

At first I thought it was due to the latest update, but after a tip to install an older version, I still couldn't open a file. I use macOS 15.7.9

it is becoming entirely too long for pictures to open up in Photoshop by way of Lightroom. I have seen others have the same issue and I have checked the space on my computer as well as updated both programs and nothing has changed. It is increasing the timeframe of me editing some of the most simplest photo shoots by adding hours. Any help with this issue? 

I use a psd file on a transparent background wor watermarking. I layer this onto the photograph - right click the psd layer and select blending options - that has always then allowed me to control not only the opacity, but the volume / depth of that watermark. I ran a batch process yesterday where it did about 800 of these without error. The next time I went to do one - manually now, blending options would not respond so far as ant of the depth commands would go. All it would do was allow the layer to be flat - it would no longer create that illusion of being embosssed. etc. Nothing has changed to the best of my knowledge and I have assures that nothing is set on 32 bit, no opacity is set to 0, I have no idea why that function has suddenly come up lame. I have reset the styles in that menu, restarted the program, restarted the computer, but cannot get blending options to - Bevel and Emboss. Any ideas or thoughts ?  Windows 10 / CS6 / everything the same so far as I know. Wored successf

Hola… desde hoy, al intentar abrir una imagen para editr en Photoshop, me sale una ventana como la de la captura ajunta. Sólo funciona con fotos en formato .WEBP (rarísimo). Intenté de todo: actualicé la tarjeta gráfica (NVIDIA GeForce GTX 1650, con 16 gigaas de Ram), deshabiliaté el uso de la GPU en Rendimiento (en Preferencias del programa), desinstalé y volvi a instalar el rpograma, etc. Alguien sabe a qué se debe este error? Gracias

I am trying to use transform/warp with split points.  I am able to add the points needed however when I try to select multiple with the shift key Photoshop exits without any error.  I see this in 27.9.1 and 28.0.  I am on a Mac mini running an M4 processor, Tahoe 26.5.1, 24GB of memory.  I have tried to disable the GPU which made no difference.

I am having trouble getting my Photoshop desktop app to work. It was working before last night but starting last night I cannot get it to stay open. It will start to open but then it will close again. I have tried all the usual work arounds and talked to tech support, who said to call today if it wasn't working and so here I am.