Bug Reports

Premiere 26.3MacOS 14.8.4 Intel RED footage now displays incorrectly on the source monitor, if that footage is part of a Multicam sequence. The base video file displays correctly, and the Multicam sequence displays correctly on the program monitor. A sample of the distorted video is attached. 

I've spent an hour searching through forums regarding this issue. It appears as though Adobe has decided that duplicate media isn't a big enough problem for their software engineers to solve. Instead, Adobe would rather spend time implementing AI and other features that lends themselves more towards marketing bylines than to fix long standing issues. I have tried every solution I have come across, and Premiere continues to import duplicate media when importing XML files. This is insanely frustrating and a massive waste of time. Plus, there's no way to consolidate the duplicates. The "Consolodate Duplicates" command does nothing. In all the advancements made to Premiere Pro, it somehow can't tell that two clips sourced from the exact same file in the exact same directory are, in fact, THE SAME. Davinci Resolve can do this. There are literally HUNDREDS of posts across many forums - both Adobe sponsored and not - asking for a solution to this issue. This post go back well over 1

I’m trying to use the frame.io window to upload my sequence to the frame.io website.I can click export and then select my export settings, but then nothing happens.  The window just goes back to the export sequence button, and nothing is uploaded.   

After updating to version 2026, the option to remove pauses after transcription is malfunctioning. I'm having to use third-party programs, even though it worked fine in version 2025. 

Premiere Pro 25.6-26.3 CUDA/R3D Issue (RTX 3090)Up to Premiere Pro 25.5 (version that introduced film impact plugins), RED Komodo and RED V-Raptor footage worked flawlessly on my system.Starting with Premiere Pro 25.6, projects containing RED R3D footage frequently crash or fail to open properly when Mercury Playback Engine is set to CUDA GPU Acceleration.The issue occurs consistently during project loading. The only reliable workaround is to launch Premiere using Mercury Playback Engine Software Only, open the project successfully, and then switch back to CUDA GPU Acceleration. Or open the project, experience the big, switch to Software only, the timeline loads, then use Cuda.After switching back to CUDA, Premiere usually works normally for a period of time.However, during longer editing sessions, Premiere can become unstable again. Symptoms include:Black Program Monitor.Playback becoming choppy, stuttering, or freezing.RED footage no longer displaying correctly.General GPU-related in

Subject: Timeline Clips Become Unresponsive After EditingI am facing an issue in Adobe Premiere Pro. After adding clips to the timeline and making one or two edits, the remaining clips stop responding properly. I am unable to move, select, or edit them on the timeline.At that point, I can work on only one clip at a time. To continue editing, I have to close the project/tab and reopen it again. This issue happens repeatedly and is affecting my workflow.Please help me resolve this issue. I have attached screenshots for reference.Premiere Pro Version: 26.0Operating System: Windows

The 26 version of premiere has no Mask on BLUR and it is irritating. It was a great tool and now is not there. Please put it again in the version.

I cannot open few options like film impact dashboard and even the basic options like speed duration etc

Mac Studio M2 Ultra - Premiere Pro 2026.3 .0 (build93) Tahoe 26.5.1When exporting timeline from Premiere Pro in Prores 4444 (no sound) and send it to Media Encoder the resulting file is black frames.If I export the same setup but directly from Premieres export window it turns out correct.I am exporting to local desktopMedia Encoder 26.2.2 (build3).

Hi, I'm running Premiere and Media Encoder Version 24.3.0 on Windows 11. I'm having a strange issue where if a Sequence in Premiere has been renamed at any point (for example 'Amazing_Edit_V001' to 'Amazing_Edit_V002', whenever I go to export that sequence using Media Encoder, it sets the default Output Filename to the previous sequence name,  'Amazing_Edit_V001'. Regardless of whether or not I shut down all the programs or even restart my computer after renaming the sequence. It was always inherit the original sequence name. This will also happen if then rename the sequence again to 'Amazing_Edit_V003', it will still maintain the original 'V001' filename when sent to Media Encoder. I should specify that this only applies to the 'Output File' filename. It correctly recognises the the sequence name as the source name on the left.

Premiere Pro 2026 displays a false "insufficient GPU memory" warning in the System Compatibility Report.System specifications:Premiere Pro 26.3.0 (Build 93)AMD Ryzen 9 7950XAMD Radeon RX 7900 XTX (24GB VRAM)64GB DDR5 RAMWindows 11GPU acceleration is enabled and set to Mercury Playback Engine GPU Acceleration (OpenCL).Steps to reproduce: Launch Premiere Pro 2026. Open any project. Open the System Compatibility Report. Premiere displays a warning stating that the system has less than the minimum required GPU memory. Expected result:No GPU memory warning should be displayed, as the system exceeds Premiere Pro's GPU memory requirements.Actual result:Premiere reports insufficient GPU memory despite detecting and using the RX 7900 XTX correctly. Playback, rendering, and exporting function normally, and GPU acceleration remains active.Additional information:The issue appears to be limited to the compatibility checker. No performance issues, crashes, rendering failures, or GPU detection

Ever since the last update (26.2.2 Build 3) , I get the "Transform cannot allocate a buffer larger than 30000 pixels" error, mostly when I add images of any size. Sometimes nothing happens, but usually the second I try to move or scale the image, apply any effect (or even just move the image clip in the timeline), I get the error, and the playback window just turns black permanently until I restart Premiere.

'Link media...' doesn't function the way it should when linking more than one clip at a time.  When I need to re-link the media for multiple clips in the same folder, I'll navigate to the correct folder, select the first clip and then Premiere takes over and rediscovers the rest. The problem is, Premiere starts looking for those clip names OUTSIDE the folder I've specified. The clips are IN the folder I've specified! But Premiere keeps looking elsewhere until it finds other clips on the harddrive with the same file name, albeit it in drastically different parts of the file directory, and then links them instead.   I've had similar problems in the past when bringing projects from one computer to another and allowing Premiere to discover the media. It looks outside the directory I pick the first clip from, and links to outside clips with the same file name (Sony's in-camera file-naming resets to zero after every 10,000 instances, so every year or so I end up with a new clip cal

Hi - I upgraded to 26.5.2 sometime last week and during the last few days, returning to projects that had been tweaked with it since, the project files were just not in their expected location. For years I've had this workflow :  Launch Premiere  Select the project from the recent projects panel or navigate to it if it's not within the recent projects list (which is always a "0_PremierePro_Scratch" sub-folder under the overall project's name on my drives)  Once in the project, "Save As" and tweak the suffix of the project's name to today's date  Edit away. "Save".   Rince and repeat.   The default location where the software always opens the "Save As" dialog box has always been the folder from which the project was open in step 2. above.    Always. Except since version 26.5.2 After fearing the loss of 3 or 4 of my projects edited since the update, I just found them scattered in various folders. I'm not sure what the trigger is, but it

Hello,I’m using Premiere v 26.2. I am attempting to use the Object Mask Tool to track a moving subject and alter the background behind them. The tool itself works correctly, selecting the subject cleanly and creating a single frame mask that works as expected. However, when I select any of the tracking options, it moves through frame by frame and creates keyframes, but the subject is no longer outlined in the dotted line or the green color (in this instance). After the fact, the mask appears to encompass the entire frame, not just the subject. For example, selecting “change to opacity mask” or moving the mask to the Opacity setting in Effect Controls turns the entire screen black. Adjusting opacity adjusts the visibility of the entire screen. Using the same selection when just one frame is masked, however, works as intended with the subject on a black background. Inverting the single frame version works as it should, but not when tracking has been used.  

As the title states. This morning after updating I was simply trying to cut a video file over top to stay at it’s preferred frame. Once I cut the layer at the preferred point I right clicked to Add Frame Hold, yet no matter what I did the frame would not hold. It would either create another cut and not frame hold, or it would do nothing and not frame hold. Other users in the past recommended right clicking and Clicking Ok once you click on Hold Frame Options, but that did not work as intended either. Obviously an easy work around is to just take a snapshot of the preferred layer at the preferred time and reimport it, but the frame hold saves me several clicks and is easier for project hand off.  

I applied the “Stroke” effect to some still images to add a white border. Then I added scale keyframes to make the image move. Looks great in the timeline, but when I export, the still images (and sometimes the images beneath them) are a drastically different scale, so they get knocked outside the frame.From reading similar bug reports, it’s possible this has something to do with GPU acceleration? Unfortunately I’m on a Mac Studio M1 Max, so it doesn’t look like I can disable GPU acceleration.  Edit: Gaussian Blur effect is causing the same problem. Workaround is to reset all Motion effects (Position, Scale) and recreate those effects using the Transform effect instead. This fixed the problem.

Using version 26.2.2 (Build3) - but also happened on previous version.This is a nightmare issue - I’ve opened up a project I was working on the day before and the sequence of clips cuts have reset to different time codes or to the start of the clip itself. For instances where that timecode doesn’t exist, I have clips that can’t be salvaged. I can remove the cut and bring back the right timecode in places. The attached image might explain. I found some people mention this might happen if you move your clips from a folder to somewhere else but they haven’t moved at all. The rushes file names are all named differently, in their own folders for CAM1 / 2 / 3 etc and Audio tracks are in their own folder too.I managed to fix this happening with audio by renaming ALL audio clips with a new suffix and then swapping them out individually in the project - this took ages and I don’t really want to do this with the video clips.It does seem isolated to this one project, I’ve saved an XML as a backup

I seem to be experiencing an issue rather intermittently with Premiere, where even though timeline scrolling is set to “No Scroll”, it will sometimes just… page scroll for no reason during playback. I haven’t personally been able to find a pattern or way to replicate this issue consistently but it has been driving me a little crazy for a while now. Doesn’t appear to be hardware dependent for me, happens on both my work and home machine.screen recording: https://drive.google.com/file/d/1WTC7J5QxT-6nsRas-msLIdkoQDnJea5c/view?usp=sharingSystem from recording;Premiere 26.2.2Windows 11 24h2 | 26100.8246Nvidia Driver 610.47Ryzen 9 7900x96GB RamAll ssd’s

When having my more or less complicated project with added,footage sfx,some adjustment layers etc - going to export tab is impossible it loads sometimes if i am lucky most of the time i have to export trough media encoder 99% actually.I noticed it happens when i have a fairly big, normally finished project

Hi.The new Film Impact FX and Transitions are great. But I have an issue with the Dip To Black transition.By default, it is not 100% black at the middle of the transition. In order to have a dip to full black, I need to tweak the Transition Timing “end” parameter to 97%.Can someone try and replicate this issue?Many thanks!MaxPremiere Pro 26.2.2Macbook Pro M1 Max / Sequoia 15.7.7 

In the latest (26.3) version of Premiere, when I'm editing text boxes that use key frames, when I click on one text box, it'll change the other's text settings (font, size, etc) to match the one I just clicked. I constantly have to change that initial text box's font settings every time I type, after clicking on the other. 

After transcribibng captions are not creating

We are seeing some issues with keyboard shortcuts not working in CEP panels in Premiere 25.4 (and 25.4.1) on Mac. It works on older versions e.g. 25.3.For example, the usual copy-paste shortcuts like Command-C and Command-V do not work anymore in any text field used in a CEP panel. Command-X still works for cutting, it seems. If a sequence is open, the left/right arrow keys do not work anymore in any text field in a CEP panel. They seem to be captured by the sequence window and result in frame stepping. This makes it quite difficult for regular users of CEP panels who are used to those keys.Easily reproducible by installing a CEP panel like Vimeo from the Creative Cloud app.   Version info:Premiere 25.4, Premiere 25.4.1 (Build 3)Macbook ProApple M4Sequoia 15.5 

We made the mistake of installing and using the Beta version to try out new features.  Everything was fine for a few days, then we found rendering issues and other feature missing like Auto Colour, and then we noticed that Creative Cloud screen was just white space.  To try and resolve this we elected to uninstall the beta verison and all of the Creative Cloud related Apps and the original version of premier pro.When we reinstalled premier pro we find that it installs everything else but will not install the actual Premier Pro App at all which now means we can not opne access or edit any of the Premier Pro files. Really stuck with this as we have tried multiple times with uninstall and re-install with the same result.For the cost of the Monthly Subscription for these apps this really is not good enough. Does anyone else have any experience with thsi issue or have any suggestions?  Right now Final Cut is looking really attractive 😕