Bug Reports

I tried using premiere 2026 and it won’t open without closing or crashing. I’m not even trying to open a specific project but it closes on the home page. I’ve updated my graphics driver and even tried re-installing the app but neither of those worked. Any suggestions?Running on a windows with a Intel Core Ultra 9 and GeForce RTX 5080 and a z890 Aorus Pro Ice Motherboard. I’ve included a video in case it provides clarity.

My transcript tool is not working, I updated premiere like 2 weeks ago and this just happened today. Needless to say, this is not what the audio is saying, it’s the reading of a script. I tried both the Text Based Editing Transcript and the Static Transcript, none of them works 

Bug: Premiere Pro 26.3 playback issue with DJI HEVC D-Log M.Mac: MacBook Pro 14" M5 Pro, 24 GB RAM.OS: macOS Tahoe 26.4.Camera: DJI Mini 5 Pro.Media: 4K 60fps HEVC (H.265) D-Log M.Problem: Files play perfectly in QuickTime, but in Premiere Pro 26.3 the playhead moves while the image updates only every few seconds. Playback is extremely choppy.Test performed: The exact same files play perfectly in Premiere Pro 25.6.6 on the same Mac.

Hello Adobe Support,I am experiencing a persistent and severe crashing issue with Adobe Premiere Pro on my MacBook Pro M4 Pro with 24 GB RAM and macOS 26.5.2.Premiere Pro repeatedly crashes shortly after opening or working inside a project. The issue has occurred across multiple projects, different clients, and footage from different cameras and sources. At different points, Premiere has also crashed with brand-new projects and with little or no active editing.I have already completed extensive troubleshooting:- Cleared the Media Cache.- Reset/trash Premiere preferences on startup.- Launched Premiere with third-party plugins disabled.- Disabled hardware-accelerated decoding.- Tested different import methods, including File > Import instead of Media Browser.- Closed the Media Browser panel.- Tested multiple projects.- Tested footage from different cameras, clients, and sources.- Created completely new Premiere projects.- Completely uninstalled and reinstalled Premiere Pro.- Tested Pr

Premiere Pro v26.2.2 no me transcribe nada, literalmente nada. Se queda cargando para luego quedarse ahí quieto. Mi única solución después de perder horas fue volver a reeditar todo en la versión 2024 ya que ahí la transcripción me funciona PERFECTO. Enserio, tengo todo descargado en la v26.2.2, el paquete de idioma, el enhance speech, pero aun así nada de nada. Y no es un tema de archivo ni nada de eso ya que, como menciono, la versión del 2024 me funciona mucho mejor.

I can no longer drag layers, change numerical values, or trim a layer.It's becoming impossible to edit.It freezes up constantly, and the audio also cuts in and out. It might randomly start working again, but only for 1 click, then it won’t allow you to move or change anything. Version: Premiere Pro version: 26.3Chip: MacBook M5 MaxmacOS: Tahoe Version 26.4Memory: 128GB Becoming more and more concerned with Adobe. This has been reported several times with 0 help.Many others are experiencing the same thing.    

after opening premiere create a sequence and upload a media then premiere crashes, does it every-time 

Hi,I'm experiencing a strange issue in Premiere Pro.In my timeline, I intentionally left a gap of about 3 seconds between two clips to create a hard cut to black before the video continues.Inside Premiere, everything works as expected. During playback, the screen goes black for the duration of the gap and then the next clip starts normally.However, after exporting the video, the last frame of the previous clip stays frozen during the entire gap instead of showing black. Once the gap is over, the next clip plays normally.I've already tried several things: Leaving the gap empty. Replacing the gap with a black video layer. Adding a fade transition. Deleting and recreating the cuts. Clearing render files and exporting again. The issue only appears in the exported file, not inside Premiere.Has anyone encountered this bug before or found a solution?Thanks!

After updating to Adobe Premiere Pro 26.3 on Windows 11, several projects that had previously opened without any issues began displaying an “outdated or damaged” error and would not open properly.At the same time, my Logitech MX Creative Console also stopped functioning correctly with Premiere Pro.I initially thought the issue might be related to Windows, so I completed an in-place reinstall of Windows 11 and reinstalled the affected applications. However, the Premiere project errors and MX Creative Console issue continued.I then reverted to Premiere Pro 26.2 through the Creative Cloud application. Immediately after installing version 26.2:• All of my Premiere projects opened normally.• The “outdated or damaged” project errors disappeared.• My Logitech MX Creative Console began working correctly again.Since both issues occur in Premiere Pro 26.3 and are resolved by reverting to 26.2, this appears to be a bug or compatibility issue introduced in version 26.3.System: Windows 11Problem ve

Premiere Pro version: v26.3OS: Windows 11Summary:The Limiter within the Dynamics effect (and the standalone Hard Limiter) does not correctly enforce the threshold I set. When I set the limiter threshold to -6 dB, the output does not limit to -6 dB as expected — the metered level shows around -10 to -15 dB instead, and the limiter appears to either over-attenuate the entire signal or not respond to the threshold value correctly.Steps to reproduce:Create a new project and import an audio/video clip with dialogue. Apply the Dynamics effect (or Hard Limiter) to the clip. Enable the Limiter section and set the threshold to -6 dB. Play back the timeline and observe the audio meters.Expected result:Audio peaks should be limited to the set threshold (-6 dB) and not exceed it, while the rest of the signal remains unaffected.Actual result:The output level does not correspond to the threshold. Peaks read significantly lower than expected (around -10 to -15 dB), as if the entire signal is being at

As seen above, the video has audio, but no dialogue can be found so no captions can be made. I’ve tried to do this with three separate videos of people speaking and putting them into new sequences as well, but they all say that the audio has no dialogue. I’ve tried logging in and logging out, and clearing my media cache. My Premiere Pro is up to date.

Issue – Some of my vídeo clips present the “saw pattern” on the image lines across Program/Preview and export Adobe Premiere Pro version – 26.0.1 Operating system – Windows 11 Enterprise 25H2 GPU driver version (Windows only) – Nvidia Studio Driver 591.74 Video format – 1920x1080, 59.94i fps, SpeedHQ Codec + ProRes Proxy Coded Comparative information helps us understand more about when the issue occurs:  First project that it’s happening. Worked fine so far, same worklflow for each one. It’s only showing specifically on the SpeedHQ Codec - files from a Vzrt Tricaster TC2. The ProRes Proxy Previews just fine. VLC and other players play the video files just fine. When they are imported to Premiere or Media encoder they start having this issues. Link for the vídeo after transcoding in Encoder - Same wobbly effect and “saw pattern” I get when on Program/preview or exporting in/from Premiere.  

Text styles don’t save all the TEXT properties which leads to them being useless unless you use them for simple things that could be done by hand. Here’s a test layer nearly every property of which has been changed:Here’s the copy of the original text layer to which I applied a saved text style from the first one:The Align and transform properties are not changed accordingly. You could say, why should they, they change the layer transform properties, but see, they are not - the layer transform properties are here: Furthermore. If I make a transcribation of someone’s speech, make subtitles and upgrade them to graphics and then apply the same text layer style to every piece of text, this happens:So the properties are not inherited and changed every time and in every scenario. The same happens when you have a text style imported into the project bin. It especially happens with subtitles - I always end up moving and scaling them manually, but guess what you cannot change settings in a grou

On May 19th, Google added a new model, Omni Flash, to their Video AI generator, Flow. The latest versions of Premiere Pro (26.2.2 Build 3) and After Effects (26.2.1 Build 2) as of 05/22/26 are not properly decoding the codec used for the video outputs from this latest model. Obvious but randomly placed video artifacting is being displayed in both the preview and outputs from Premiere Pro and After Effects that are not being displayed in other applications or programs such as VLC Player, DaVinci Resolve, etc. I tried both the latest Game Ready as well as a clean install of the latest Studio Driver from NVidia for my 4080S but had the same results.

I was on vacation, didn't work for 10 days. Today I decided to continue working but I can't open any of the projects. Even if I start a new one, the project still doesn't open. As soon as I click "Create" (see screenshot), the program just freezes and all the space on the screen from other windows also doesn't work. I wait 2-3 minutes but the program doesn't open. I tried uninstalling Premiere while saving my settings, rebooting my MacBook, reinstalling the program but that didn't solve the problem. I don't remember what version of the software was before the vacation, maybe it was updated from 26.2, I can't confirm that. Currently it's 26.3. AE works fine.

Desde hace 1 mes me estaba pasando en la laptop cuando trabajaba en premiere, y es que pongo a reproducir la linea de tiempo y al segundo la pantalla del pc falla y se pone negra, pero sigue reproduciendo, y no deja de estar en negro hasta que pause el video y la pantalla vuelve a “conectarse”, pensé que solo pasaria en la laptop, como un simple problema de demandarle mucho a un core i3 de 10ma generacion, pero ahora me empezó a pasar en mi ordenador de mesa (Ryzen 5 5600g y RX 6600) y esta pasando justo cuando tengo el premiere abierto y pongo a reproducir la linea de tiempo.A alguien más le ha pasado?, me podrian recomendar como solucionarlo?, porque tengo todos los drivers al día. Muchas gracias :)

I have uncovered a critical issue/artificial limitation in the current build of Premiere Pro and Media Encoder regarding hardware decoding on the new NVIDIA RTX 50-series (Blackwell architecture) GPUs, specifically the RTX 5070 Ti.System Specs: CPU: Intel Core i9-13900K GPU: NVIDIA GeForce RTX 5070 Ti (Blackwell) Driver: NVIDIA Studio Driver 610.62 OS: Windows 11 Premiere Version 26.3.0 (Build93) Media Encoder 26.3.1 ( Build 1 )   The Bug: The new NVDEC block in NVIDIA Blackwell GPUs natively supports hardware decoding for H.264 / AVC High 4:2:2 10-bit files. However, Adobe's software seems to have a hardcoded resolution cap that breaks this functionality for 4K media. When playing a 1080p H.264 4:2:2 10-bit file on the timeline, Premiere Pro successfully engages the GPU. The Task Manager clearly shows active GPU Video Decode utilization, and playback is perfectly smooth. When playing a 4K (3840x2160) file with the exact same codec parameters (Sony XAVC S 4K 50fps, H.264 4:

As you can see from the screenshots, I’ve set the target bitrate for 15Mbps.  When I actually render/export the video, the resulting file is 30Mbps.  I’m on version 26.2.2 (Build 3).  I got a new computer a few days ago.  On my old computer, I was using an older version which did not have this problem. When I set it by hand for 14Mbps, the resulting file is 25Mbps. What gives? 

Issue:Adobe Premiere Pro and Adobe Media Encoder stall at 0% when “Copy Media” has been selected in the “import settings” within the “import” tab.Steps to reproduce:Insert SD Card - Sony FX6 Camera Acquisition Launch Premiere/Create a New Project - Project settings are set to an external SanDisk USB-C Drive formatted as APFS. Within “Import” Browse to Untitled/private/XDRoot/ and select clip(s) Under “Import Settings” toggle on “Copy Media” and select the “Copy With MD5 Verification” preset and “Same as project” copied files destination. Select “Import” Observe that Adobe Media Encoder launches and the selected clips are populated into the “Queue” as expected. Observe that the status bar never moves. Observe that “Stop Queue” is available indicating that the Queue is running. Observe that Adobe Premiere Pro “Ingest Job Status” remains at 0% in the “Progress Dashboard” window. Observe that “Queue Started” is the only entry in the Adobe Media Encoder Log Expected result:Adobe Media Encod

Product/Version: Adobe Premiere Pro 26.3 (regression; works in 26.2)OS: Windows (please fill in exact version/build: e.g., Windows 11 23H2 build ____ )GPU: NVIDIA RTX 6000 Ada GenerationNVIDIA Driver: 581.80Renderer: Mercury Playback Engine GPU Acceleration (CUDA)Steps to reproduce:Launch Premiere Pro 26.3 No windows open initially; open a project via File → Open Recent Click Export (top bar)Expected result: Export panel/window opens and export workflow is usable.Actual result: Nothing opens when clicking Export. After clicking Export once, Import/Edit tabs cannot be clicked (UI becomes partially locked). Requires restart to recover.Workaround: Installing/running Premiere Pro 26.2 allows Export to work normally on the same machine/project.

Cuando abro premier y realizo alguna acción el programa se congela por unos segundos y cuando vuelve a funcionar la pantalla de previsualización no funciona. la pantalla queda en negro! sigue reproduciendo el sonido pero no la imagen. cierro premier y lo vuelvo abrir y aveces funciona bien por 30 segundos, aveces 5 segundos, aveces 1 minuto y vuelve y hace la misma acción. actualice todos los controladores tanto del procesador como de la tarjeta de video integrada ( radeon ) y los drivers de la RTX 3060 pero tampoco funciona!no puedo realizar ninguna edición por que eso no me lo permite!

Sehr häufig friert der Mauszeiger ein er bewegt sich zwar noch, aber ich kann nichts mehr markieren oder Clips bewegen im Sinne von: sie lang ziehen, oder kürzer ziehen. Ich bitte um dringende Behebung

Running an M3 Max Macbook Pro running Sequoia 15.5 with an external monitor as well as a Blackmagic Ultrastudio Extreme playing out to a monitor. After updating to Premiere 25.4 now all thumbnails in the markers panel as well as the search panel are glitched/distorted. Was working fine prior to update. When scrubbing over shots in the search panel hover scrub works fine but then goes back to the glitched image when moving off of it. Have tried wiping cache, made new markers. When viewing a bin in icon or freeform view the thumbnails are fine. This is limited to the markers and search panels.

DescriptionSystemMacBook Pro 14” (Apple M1 Pro, 16 GB RAM) macOS Tahoe 26.x Adobe Premiere Pro 2026 Adobe Media Encoder 2026WorkflowI exported approximately 30 H.264 videos from a single Premiere Pro sequence by sending them to Adobe Media Encoder. This is my normal workflow for exporting multiple clips from one timeline.The queue contained a mixture of:Completed exports Failed exports Manually stopped exports Skipped exports (to pause the remaining queue)Observed behaviourDuring the export process, Adobe Media Encoder/Premiere created temporary folders under:/private/var/folders/.../T/Adobe Premiere Pro Audio Previews/This folder eventually grew to approximately 110 GB and contained many folders such as:Luna Sol_20.PRV Luna Sol_21.PRV Luna Sol_22.PRV … Luna Sol_34.PRVEach folder was approximately 7.9 GB.After the queue was no longer running and both Premiere Pro and Media Encoder were completely closed, these temporary folders remained on disk instead of being automatically removed.Th

Since a couple of versions ago, I found my Premiere Pro to be really slow and I did not understand why. But I just discovered that when showing the index panel in the UI, Premiere starts to be much MUCH slower, like I can’t type text without delays or can’t use the motion properties.Get rid of the index panel and the issue’s gone.I’m using Premiere 26.2.2 on MacOS 15.7.7 right now, might be a good idea to check the 26.3 version and see if it’s still an issue.Cheers.Max