Bug Reports

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.  

Premiere Pro 26.3 Regression: ComponentParam.createSetValueAction throws "The script object is no longer valid" Environment:- Premiere Pro 26.2: Works- Premiere Pro 26.3: Fails- UXP PanelMinimal Reproduction:const current = await cropTopParam.getStartValue();const kf = cropTopParam.createKeyframe(current.value.value);const action = await cropTopParam.createSetValueAction(kf, true);Expected:Action object returned.Actual:"The script object is no longer valid."Notes:- Parameter is freshly retrieved.- getStartValue() succeeds.- createKeyframe() succeeds.- createCloneTrackItemAction() also appears affected.

Hi Adobe team,I’m reporting what appears to be a regression in Text-Based Editing, specifically in how Premiere Pro detects short pauses in the Transcript panel.The version that works correctly for me is:Premiere Pro 26.0.2, build 2The version where I am facing the issue is:Premiere Pro 26.3In Premiere Pro 26.0.2 build 2, I could use the Pauses filter in the Transcript panel and adjust the Set pause length / Minimum pause length setting to detect very short pauses in spoken dialogue. This was extremely useful for dialogue-heavy editing, because Premiere would correctly identify even small pauses, including pauses around 0.1–0.11 seconds.However, in Premiere Pro 26.3, the same workflow no longer behaves correctly. The pause-length slider still allows the minimum pause length to be set very low, but Premiere now appears to ignore many short pauses that were previously detected in version 26.0.2.For example, on the exact same video clip: Premiere Pro 26.0.2 build 2: approximately 200 paus

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

In Premiere Pro on macOS, I can add a guide in Program Monitor, but using the guide for clip alignment is not working as expected. When I change Motion > Position X values (for example 960 to 420), the guide does not help with accurate placement the way I expect. I need to know whether this is a bug or intended behavior, because guide-based alignment is confusing in the current workflow.

After updating to Premiere Pro 26.3, existing sequences no longer read previous resize settings correctly. Any resize made through the main Scale parameter is broken because the second scale value, Scale Width, is always shown as 100% on previously resized clips. As a result, old framing and resize adjustments are not preserved and have to be fixed manually.

When I import a sequence from an adobe premiere project into after effects, or when I copy layers from premiere and paste into after effects, opacity keyframes come into after effects. But audio volume level keyframes do not.  According to this page they should: https://helpx.adobe.com/premiere/desktop/use-premiere-with-other-apps/working-with-o[…]e-applications/copy-clips-from-premiere-to-after-effects.html But, I am unable to get the audio level information into AE.  In the past, the audio levels would come into After Effects in the form of the Stereo Mixer effect. I am using Premiere 26.3 and After Effects 26.3, having just updated from the previous version of AE26 and PR26 to see if an update would help, but it did not.

Premiere Pro Version: 26.3Operating System: Windows 11Laptop Model: HP Victus 16-r0073clCPU: Intel Core i7-13700HXGPU: NVIDIA GeForce RTX 4060 Laptop GPU + Intel UHD GraphicsRAM: 32 GB DDR5Intel Graphics Driver: 32.0.101.6790NVIDIA Driver: Studio Driver (latest available version at the time of testing)Issue DescriptionPremiere Pro 26.3 frequently becomes unresponsive ("Not Responding") during normal use.The freezes occur even in completely empty projects and are not related to media files, effects, or timeline playback.Most commonly, the issue happens when: Opening Preferences Opening Sequence Settings Opening Project Settings Editing Effect Controls Accessing clip properties Interacting with interface panels Windows remains fully responsive while Premiere freezes.Troubleshooting PerformedI have already tested the following: Reset Premiere preferences Created a new Windows user profile Disabled Hardware Accelerated Decoding and Encoding Disabled Display Color Management

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.  

On many of my projects, as of Premiere 26.2 and now on 26.3, I’m finding that Premiere is needing to recreate audio PEK files on every time a project is reopened. Example, I was working on this project file yesterday, all day. Closed it out, reopened it this morning, project is stalled while Premiere recreated PEK files.It is creating brand new PEK files in the standard MacOS media cache directory.Happens across several different projects, happens on both my Mac Studio and my MacBook Pro.Haven’t quite had a chance to do a heavily detailed test of what could be causing it, but from chatter I hear on the forums, Facebook, and Reddit, I believe this has something to do with the relinking/slow loading bug people have been reporting.

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

Bug Report: H.264 Export Fails on All Projects (Selector 9, Error Code 3)SummaryH.264 export fails consistently and immediately (within the first 1-2 seconds of encoding) on every project tested, including a brand-new project with a single random clip and no effects. QuickTime/ProRes export from the identical source completes successfully every time. This isolates the failure to the H.264 exporter component itself rather than any project, sequence, or media content.EnvironmentMac model/chip: Apple M2 macOS version: [fill in — Apple menu > About This Mac] Premiere Pro version/build: [fill in — Help > About Premiere Pro] After Effects version/build: [fill in, if relevant] GPU acceleration setting: Video Rendering and Playback renderer selector is grayed out/locked in Project Settings > General Storage involved: Local internal SSD (issue persists even with no external/network drives involved)Steps to ReproduceOpen Premiere Pro. Create a brand-new, empty project. Import a single v

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,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!

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

The outline of the mask not showing at all when creating a mask in any situation in premiere 2026

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 😕

In recent versions, the program freezes for a few seconds when the auto-save feature is enabled. The video plays, but the program’s functions don’t work. I have to force-close the program. This issue occurs in all projects, regardless of the number of files or effects. I didn’t notice the auto-save process before, but now it’s causing me discomfort, so I’ve turned it off.  The project size is 3–10 MB. Just don't tell me that my hard drive can't save 3 MB in 10 seconds—and that's why it freezes.  Windows 11MSI PCI-Ex GeForce RTX 5070 Ti Gaming Trio OC 16GB GDDR7 (256bit) Samsung 990 Pro 2TB M.2 PCIe 4.0 x4 NVMe 2.0 V-NAND 3bit MLCIntel(R) Core(TM) i7-14700K (3.40 GHz)