Bug Reports

Pr 26.2.2, Win11 26h1, RTX 4080, internal SSDs, 14700K, 64 Gb of Ram. After my project was finished a month ago I exported it via the Project Manager in Premiere and then uploaded it into a cloud. Today I needed to review something from this project, so I downloaded it back and upon opening it saw this:It’s strange because there IS a masks data folder in the archive, but if I point Premiere to this folder, it does not relink the masks saying they can’t be located:How come and how can I fix it? I’ve got quite a bunch of object masks in the project to retrack everything again. Besides, the project was made in the same exact version of Premiere - 26.2.2 so there cannot be any mask data conflicts.

Issue:The automatic Object Mask generates low-resolution, pixelated and aliased edges around the subject. The problem is visible after tracking and remains in the exported video.Steps to reproduce:1. Import a video into Adobe Premiere Pro.2. Place a graphic or text layer above the video.3. Duplicate the original video and place it above the graphic.4. Create an automatic Object Mask around the person.5. Track the mask.6. Export the sequence.Expected result:The Object Mask should preserve a clean and accurate edge around the person at the original video resolution.Actual result:The tracked mask creates visibly pixelated and blocky edges, especially around the hand and fingers. The pixelation is also present in the final export.Additional information:- Mask type: Object Mask – Smooth- Feather: 0- The problem is visible at full preview resolution and in the exported file.- Increasing Feather only blurs the defective edge and does not improve the mask accuracy.  

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

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

I’m experiencing an error in Premiere Pro that I can’t seem to resolve, despite trying all the recommended solutions I found on Google and YouTube. I believe it might be related to the new Premiere Pro 2025 update. The issue occurs when I try to create a project from the Project Manager to share with my team. I even tried rolling back to the 2024 version, but the same error persists. I also tested this project on a different device, but the error still comes up.   I've attached screenshots below from both versions.     P.S. I’ve already tried clearing the media cache, but the error keeps appearing.

I placed the Type Tool Cursor on the program monitor and the cursor disappeared, but I typed some text anyhow.  Grabbed my Select tool to click on the text and there was no Boundary Box (or whatever its called).  Figured something was wacky, so I “toured” the Premier layout, clicking this ‘n that. Finally found the culprit: The Rulers selection on the program monitor.  If Rulers are ON, the vanishing act takes place.  OFF, the Type Tool cursor and boundary box return.  I’ve attached a couple of screen captures showing before and after. Btw, that Rulers Icon looks a bit funky when OFF. 

We are aware that customers who saved projects in Premiere v25.6.0 may find that those files now open only in v26 (beta) and cannot be opened in v25 versions. We know this is disruptive, and we’re working on a fix.    What you need to know:  Projects saved in v25.6.0 save in the v26 version format.  Because of this, they can’t be opened in earlier versions, including v25.6.1 (even though it is the current generally available release)  We’re developing a tool that will let you convert affected projects back to a v25-compatible file.     Our Solution  We’re building a small app that will convert a v25.6.0-saved project back to the v25 format. We’ll share more information, including availability and instructions, as soon as the tool is ready in the coming days.     We know that there is nothing more important than the reliability of a project file, so we’re working with urgency to get this downgrade tool in your hands

MacBook Pro M1 Pro macOS 15.7.7 Premiere Pro 26.2 Mercury Metal Camera Shake native Multicam preview only Export unaffected  [Moved to Adobe Premiere by a moderator］

The timeline cursor is completely out of sync with playback - not just lagging behind, it's acting completely independently. It moves when playback is paused, it stays static when playing, basically moving at random. Making any changes causes the app to hang. Literally cannot edit. Playback is poor too, it takes about 5 seconds from pressing play to getting playback, even though everything is fully rendered. Resizing the timeline also causes severe lag.  AMD 50504070 GPU128gb RAM

Bug: Transcript.createImportTextSegmentsAction + executeTransaction melden Erfolg, committen aber nichtsUmgebungPremiere Pro Version: 26.3.0 (Manifest minVersion), UXP Manifest v5 API: @adobe/premierepro UXP-Bindings (ppro-Namespace)Erwartetes Verhaltenppro.Transcript.createImportTextSegmentsAction(textSegments, clipProjectItem) erzeugt eine Action, die per project.executeTransaction() committet wird und das Transkript am ClipProjectItem anhängt - äquivalent zu Text-Panel → Overflow-Menü → Import → Import Static Transcript.Tatsächliches VerhaltenJede einzelne Stufe der Kette meldet Erfolg, aber ppro.Transcript.hasTranscript(clipProjectItem) und die UI (Text-Panel) zeigen übereinstimmend, dass kein Transkript angekommen ist.Minimal-Reproduktionconst project = await ppro.Project.getActiveProject();const sequence = await project.getActiveSequence();const track = await sequence.getAudioTrack(0);const trackItems = await track.getTrackItems(ppro.Constants.TrackItemType.CLIP, false);const pro

SummaryPremiere Pro (26.0.1.3, Windows 11 24H2, build 10.0.26100.8655) intermittently freezes completely ("Not Responding") when opening any Open/Save/Browse dialog — including Save As, Import, and the Scratch Disks "Browse" folder picker. The freeze is a genuine hard hang (Windows logs it as an Application Hang, "Top level window is idle"), not a cosmetic or offscreen-window issue. Two independent crash dumps show the identical stuck call stack. EnvironmentPremiere Pro version: 26.0.1.3 (Premiere Pro 2026) OS: Windows 11, version 24H2, build 10.0.26100.8655 RAM: 64 GB GPU driver: NVIDIA (nvwgf2umx/nvcuda64 present in dumps)SymptomPremiere becomes fully unresponsive. Clicking anywhere produces the Windows system "ding" (rejected input on a blocked modal). Occurs after a variable amount of session activity — anywhere from ~30 minutes to ~3 hours. Not tied to a fixed elapsed time. Only ever triggered by opening a common file/folder dialog: File > Save As File > Import Project Set

I've submitted this bug several times now.  2 things: how do we know if adobe has acknowledged a bug? do they respond to let you know? 2nd thing, the bug itself:   take a nested sequence, insert it onto timeline.  Add another layer in the nested sequence, apply time remmapping.  Sequence will go black before it reaches the end of the sequence. This vid below demonstrates that it is not the normal behavior of a time remmapped clip.  Most of the time when I encounter this bug it is when the original footage is not the same res as the final sequnce.   [hyper link removed by author request]   [Typo removed from title. — Mod.]

In the latest version 26.3.2 the same problems as with version 26.3...everything new, latest drivers, fresh system and the same problems....relinking files too long... the same error appears again with the HEVC codec... which we solved in the previous post... BUT WHY DOES THE ERROR (HEVC) APPEAR AGAIN IN THE LAST ITERATION.....while the relinking is going on, the processor goes to 80% and when the dashboard shows that all the files are loaded... the timeline cannot be started for another 15 minutes because Pp is loading "something else" and during all that time the processor is at 70.80%...please solve it....here is the link with all these problems from the previous post from v26.3...all my data and configuration are there.…HEVC codec missing Pp 26.3 - WIN11 ???best regards

If I have only certain section of a text filled with a color, in previous versions that section also got the other text effects (like drop shadow), however I noticed this no longer applies. Filling color is green only for the first two words of the text. Notice how the text shadow is not present.Now that the whole text is filled with color, the shadow appears.As I stated previously, this didn't happen in previous versions because this video is already uploaded to Youtube when I edited it back in 2021. Notice how, when the first two words are selected, both the filling color and the drop shadow effect are turned on. However, the drop shadow doesn't appear.However, the moment when I enable the filling color for the very last character, it starts working how it should be. 

It shows not responding every 3,4 minutes or if u go to workspace pr any settings like project memory Or any of these settings 

Issue: Applying a mask or crop to a clip on the timeline causes the clip to turn green and snowyExpected Result: Should be a clean mask or cropActual Result: The clip turns green and snowy, and/or creates an odd screened mosaic on the clipScreen Recording: MP4 and JPEGsPremiere Version: 26.3.2 (Build 2)Operating System: iMac 27" 3.6 GHz 8-Core Intel i9, Radeon Pro Vega 48 8GB, 128 GB 2667 MHz DDR4Video Format: 5K RED RAW clip on a 4K timelineStarted occurring on a 26.2 project as soon as it was updated to 26.3 (Build 93). Just updated to 26.3.2 (Build 2), and no change. Reset all options on app startup, and the issue remains.

This bug or feature drives me nuts and it has been out there for eternity. When you Render and Replace a clip that was warp stabilized first you always get a warning banner if you choose Include Video effects: The only solution so far is to activate the Hide Warning banner checkbox in this effect's advanced menu: The guys in this topic here say that with Render and replacing the Warp Stabilizer effect does not work, but in Premiere Pro 24.6.1 I can clearly see my footage stabilized (see the attached video) and I still get this warning banner. Why? What's its purpose there? Why does it even show if the clip's length remains unchanged? So. CAN ADOBE PLEASE FIX THAT ALREADY? 

Issue: Double clicking on program monitor doesn’t switch the selection if you already have a selection. Steps to Reproduce: Try to double click on program monitor while another clip is selected. Expected Result: It should switch the selection Actual Result: It doesn’t select Premiere Version: 26.2 Build 65 Operating System: Windows 11 Pro 25H2 GPU Driver (Windows only): 597.79 Studio Driver Video Format: It happens with every layer. (Images, videos, gifs etc.)  

I’ve generated captions and now need to edit and reformat how some of them appear on screen.  Where I could click on the caption and previously select it to visually edit it in the program window - the editor is creating an error where it does not select the captions to where they can be visually edited.I can edit them in the text window, which is not visual or expedient for reframing and formatting needs. This appears to be a new bug presented in captions and caption editing

Scene edit detection has been failing lately on premiere 2026. Have to quit and come back in to fix it. error “scene edit detection encountered a failure when analyzing the clip.” premiere 2026 version 26.3.2 (build 2), mac os tahoe 26.6.1  

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: The Premiere version 26.3 is causing issues with scale and position when exporting and rendering videos, but everything looks fine when I'm in the project and timeline, so the only way I can check for errors is to export a whole video. This only happens with some file types such as images animated using Film Impact Dashboard or vertical images that I have scaled to fit the landscape frame. I have since rolled back to 26.2.2 and everything works fine. So I'll wait to see if the next version also has these issues.Steps to Reproduce: I have a feeling it is a compatibility issue with my PC.Below are the details of my system:Processor    AMD Ryzen 7 9700X 8-Core Processor (3.80 GHz)Installed RAM    32.0 GB (31.6 GB usable)Graphics card    AMD Radeon RX 7900 XT (20 GB)System type    64-bit operating system, x64-based processorI have a timeline for an 8 minute YouTube video and export in YouTube 4k. Then I watch the exported video back to see if the error has occurred.I did try renderi

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