Bug Reports

A friend of mine sent me this video and said when he applies Warp stabilizer of the footage Premiere plays it back with huge lags. So that means after the footage was stabilized. If he renders in and out points the lags disappear, the exported footage also has no lags. Here’s how it looks:In the video the stabilized is the upper shorter clip.I would have not posted this but for one thing - his PC does not even sweat when playing back the stabilized footage but it makes it lag. In the video below you will see the performance tab pf the windows process manager, see the loads of the components. I would not say the footage is any problematic for this PC at all. So what can be the cause of this bug?Pr 26.2.2, Win 11 25h2, 32 Gb Ram, RTX 5060Ti, SSDs, i9-9900kFootage:  MP4/MOV H.264 10 bit 4:2:2 - it’s a NV 50xx GPU-decoded format so the card should be enough to play it back flawlessly.

Been seeing this small bug for a couple of Premiere versions. When you apply Warp Stabilizer to a clip it immediately starts analyzing and applies stabilization to the clip. So the Analyze button becomes inactive. If, still having this clip clicked on you change the clip length the “Analyze again” blue banner appears but the Analyze button remains inactive untill you unclick the clip and click it again.Here’s how it looks: A colleague working on Pr 26.3.2 could reproduce this bug too

Hello, my render times are being so slow, even thought im always trying to render via GPU but it seems that my mac is always using CPU. Ive reseted the cache of everything but it seems that TAO is causing my premiere to crash.. I have no idea what TAO is  

Issue Description:In Premiere Pro 2026, using the Track Matte Key effect with a Text Layer (Graphic Layer) as the matte source causes the text layer to scale down unexpectedly.Steps to Reproduce:Create a new Premiere Pro project. Create a sequence (for example, 1920×1080). Place a video clip on the V1 track. Create a Text Layer (Graphic Text / Essential Graphics) on the V2 track. Apply the Track Matte Key effect to the V1 video clip. Set the Matte option to use the V2 Text Layer. Enable the effect and observe the Text Layer.Actual Result:After enabling Track Matte Key, the V2 Text Layer used as the matte source becomes unexpectedly smaller and its scale changes.Expected Result:The Text Layer should maintain its original size and position. It should only provide Alpha or Luma information as the matte source and should not be affected by scaling.Workaround:If I first Nest the V1 video clip and then apply the Track Matte Key effect, the issue no longer occurs.This issue can be reproduced

I created a mask around a small section of a clip using the pen mask tool found in the object mask menu. I then moved the unassigned mask into the Lumetri Color tool for the purposes of coloring the masked section. Upon moving the unassigned masked into Lumetri Color, Premiere crops the entire top section of the clip, as well as the lower left section. See attached screenshots.The first shot shows how I added the pen mask to the Lumetri Color tool. The second shows the immediate result. 

Transcription filter for filler words leaves partial uhs and ums after deleting. After transcribing in Premiere, you can click the Filter button and select “Filler Words”. When you delete those selected words, it frequently leaves pieces of filler words behind, often with UM or UH filler words. Secondary issue, or perhaps feature request, it would be great to be able to choose which filler words or phrases were counted as Filler Words, so that some things could be kept if preferred, for example laughs and sighs would be nice to keep, but ums and uhs filter out. Other words such as “like”, “you know” and such, it would be nice to have the option to filter them or not. Thank you!Alex Wolfe

When exporting a sequence that contains a nested sequence, where the nested sequence has an adjustment layer applying a Lumetri Color effect, the export will consistently fail near the end (≈95-99%). Premiere Pro either becomes unresponsive, crashes entirely, or produces a 0-byte file. Removing the adjustment layer from the nest allows the export to complete successfully.

When I select a single clip in my sequence to be offlined and linked to a higher resolution clip, it kicks the entire sequence offline. I'm on Premiere 2024.2.1. Sonoma 14.4. M2 Ultra Mac Studio. I have video demonstrating it attached. When I click on the file and offline it in the project panel, it only offlines the single clip. However, in the timeline, it affects everything. Please advise.

Nikon ZR R3D NE — Interpret Footage 59.94 → 23.976 breaks audio duration Premiere version: 26.3.2Camera: Nikon ZRCodec: R3D NE / REDCODESource frame rate: 59.94 fpsInterpreted frame rate: 23.976 fps I have a project containing Nikon ZR R3D NE footage recorded at 59.94 fps with embedded audio. I used Modify → Interpret Footage → Assume this frame rate: 23.976 to create slow motion. Initially, Premiere slowed both the video and embedded audio together as expected. The audio played at the slowed speed and remained the same duration as the interpreted video. After saving and reopening the project, Premiere still correctly interprets the video at 23.976, but the embedded audio now plays at its original speed/duration. As a result, the audio ends approximately 40% of the way through each interpreted video clip. This is happening at the master/source clip level, not just in existing sequences. If I take an affected R3D NE clip from the Project panel and place it into a brand-new sequence, the

proxy files also work normal in the same project, when straight importedattached screenshot, linked proxy file on the left, imported on the rightnewest premiere prothere is also a bug that shows every time i use proxy from this person, but it is the first time i have this audio issue 

Something that’s been around, and still not fixed, since the controversial “update” of the Export panel a few years ago:No matter how much I embiggen the Settings column in the Export tab, the file path never extends to fill the available space, but remains truncated (see screen grab). The file path should take up all the available space. Steps to reproduce:Export something to a folder location that’s not really short, then drag the Settings column so it’s a bit wider. Result:Expected: Full file path should be displayed if there’s available space. System info    Application: Premiere Pro (Beta) v27.0.0.12    OS: Windows v10.0.26200, RAM: 127.91 GB GB, CPUs (logical): 32

I have been having distorted black and white pixelation in my playback window and my source window. When I play the footage, it plays normally, but when I stop playback, it comes a black or white distorted image. I adjust the UI and it changes the distortion pattern and amount. I updated all of my OS setting, I updated my Premier Pro to the latest version and this persists. I reinstalled my OS and the issue persists. This has been happening since the last update. I have attatched my "about" settings and my premier version info.

Today I opened a project and realized the edit was completely broken, every video clip was playing the wrong moments, lots of clips also have zebra bars, as if theres no content at the timecode its referencing. Nothing about my media has changed, same storage, same video clips, no modifications to how the timecode is interpreted or anything. An older version of the project opens correctly. 

The Filter Bin Content and Find functions in the Project panel are not working. I do not get any results when I search words that appear in my files' markers, transcript, or description.

I do the following all day long: *while in multicam mode*, I make cuts and copy multicam clips from "stringout sequence A," then click on the sequence tab for "selects sequence B" to switch to sequence B, pick a place on the timeline and paste the clips into sequence B, then click on the sequence tab for sequence A to go back. And very often in v23.5, seemingly due to the lagging multicam response time and possibly interaction with the timecode ticker when choosing a spot to paste, Premiere glitches out and makes the sequence tab "sticky" w/ my click long after I've released the mouse. This usually results in the sequence panel for sequence B detaching and reattaching somewhere else (or even popping up into its own window sometimes). This never happened in previous versions. If I had the patience to wait for every delay in Premiere to fully resolve before my next mouse click, it probably wouldn't happen, but when you're trying to move quickly and frictionlessly, it's incredibly annoyin

La funcion para editar video usando texto no esta funcionando, cuando hago la primera transcripcion se genera el texto normal, en el idioma que seleccione, cuando la quiero convertir a una descripcion  para editar eliminando texto, pasan 2 cosas, o simplemente no la convierte y se borra la transcripcion, o se transcribe y cambia a ingles.

I'm experiencing problems when outputting a video that uses a “directional blur effect”. When I exporting video in the media encoder, the effect doesn't appear. But this effect working when exporting video with “export media”.   

When opening and synchronizing a large project from a full day shoot with time code and then later transcribing that time-coded sequence, it seems that something in that process triggers a memory leak within my version of Premiere Pro. 26.2.2 Regularly, my instance of Premiere Pro will begin using up to 100 GB of RAM when I only have 20 GB allocated to the system. Fixing this issue requires:Closing the project Force quitting Premiere because it freezes Quickly opening the project Copying and pasting all assets that are relevant to what I need to work on into a brand new project where the issue goes awayI have attached the project file that gave me issues and would love to help solve this problem, as it's something our team uses every single time we work on a long-form content series. It continues to be an issue. [Moved to Adobe Premiere by a moderator］

When applying the “grow” effect to an adjustment layer that has beed sped up or slowed down, it doesn't work anymore and just zooms in a lot. Does not seem to apply to video layers. Also some of the other “clip length based” effects like “spin” act weird on adjustment layers that have been changed in speed.Steps to reproduce: - Add an adjustment layer to a sequence​​​​​​​- speed it up using the rate stretch tool​​​​​​​- apply the grow effect to the adjustment layerMacBook Pro M2 Pro, macOS Tahoe 26.2Premiere 26.3.0 (Build 93)

When trying to play .MOV files shot on an Alexa Mini in ProRes 4444 23.976 fps in V26.3.2, certain files (potentially shot upside down with the intention of being rotated correctly in post) does not playback properly and will not show in the Program Monitor. Scrubbing with the cursor will ‘play’ the file, but upside down. If an export is attempted, a solid black frame is generated with no data. Reverting to the latest update of Premiere Pro 2025 resolves this playback issue and all files appear on the timeline with no issue in the correct orientation and also does not generate black frames on these files upon export. Something in the latest update appears to prevent correct decoding and encoding of certain ProRes 4444 files. (V25.6.6)

When I use a PSD file to scroll through my credits. It works OK when I Export or use a jpeg file. Premiere Pro Version 26.3.0 (build 93) 

I’m using Adobe Premiere Pro 26.3.2 (Build 2). 1 month ago. When I open Premiere, everything works normally at first. I can see the Source Monitor and import/drop my files without any issues.However, after a short time, the panel suddenly disappears and I cannot restore it.When I go to Window → Projects and click on my project, instead of reopening the Project panel/resource panel, Premiere only creates a duplicate of the project tab name without showing the actual contents or panel.I’ve already tried reopening the panel from the Window menu, but the issue persists.Also creating a new project and import the old one into it doesn't work and reseting to saved layout too. i have Mac mini m2 at home and everything works fine. :(Has anyone experienced this issue or knows how to fix it?

Premiere Pro 25.6 freezes/white-screens on repeated playback of the same timeline section — all threads blocked on single internal thread Premiere Pro repeatedly freezes (Windows "Not Responding" state, playback audio/video continues briefly in background) when rewatching the same section of a timeline more than 2-3 times. This happens across different projects, including a brand new project with fresh footage — not tied to one sequence or clip.System specs:Premiere Pro version: 26.3 CPU: Intel Core Ultra 9 285K GPU: RTX 4070 Ti Super, Nvidia Studio Driver (latest) RAM: 32GB (31GB installed), Premiere allocated 25GB OS: Windows 11 Storage: Boot NVMe (Gen 4), ~50% free, media cache on same drive Renderer: Mercury Playback Engine GPU Acceleration (CUDA)What I've already ruled out:GPU/renderer settings (confirmed CUDA active, GPU usage stays near-idle even during freeze) H264/HEVC hardware decode routing (tested Intel+Nvidia both enabled, then Nvidia-only  freeze duration shortened slight

IssueWhen using the Motion Tween transition for zooming out, the transition shows black bars, although the video as enough room.The black bars fade into the video at the end of the transition.Steps to reproduceI set the fist video to 120%, the second to 100%.Then I select both clips and add the Motion Tween transition.Result: I added the actual result and the expected result (made with keyframes on scale property) as attachments.Adobe Premiere Pro version26.3.2Operating systemWindows 11Video formatDifferent formats (mp4 h264, mov prores 422),Resolution 4K and FHD, both in FHD sequence

Have been using Premiere Pro 2025, the app updated itself to the latest version (26) and is saying all my clips (hundreds) are offiline. When I try to relink them it says there is an issue with the audio channels type. Its ridiculous because I've been working on this project for months and have never had this issue. I re dowloaded the older version of PP and now thats doing the same thing...  not sure if this is a bug or somethng Ive doneExtra info: working on a Macbook Pro 2019,Graphics: AMD Radeon Pro 5500M 8 GB, Intel UHD Graphics 630 1536 MBVarious files shot on iphone, drone, pocket 3, go pro.Working off an SSD (Samsung T7 shield)Memory: 64 GB 2667 MHz DDR4OS: TahoeProcessor: 2.4 GHz 8-Core Intel Core i9