Bug Reports

Here are a few bugs for Beta version as well as universal bugs for all versions.Beta version bugs:The Object Mask Tool is great. But the removal of free shape draw mask tool is a mistake. That’s why I still have to use non beta version sometimes. If I want to draw a specific shape and use if further as a mask. On Beta - that is impossible. What? The Object Mask Tool highlights a suggested shape. That is a significant downgrade if I want  a strict shape easily. Stability issues. Once in a while I encounter a situation where clicking on something closes down the app. I have RTX 4090 24GB, 64GB RAM, i9 3.2GHz, 12TB, win11. Is my device too old… already?Bugs that no one cares about in ALL versions:This is surprising. I just am unable to believe that this is never noticed. It has been a bug a year ago. It is a bug now. and probably will remain a bug in the future. It’s for those who enjoy punishing themselves: Text - Captions. There is a problem when editing captions. As you know, Enter but

I installed the Premiere Pro Beta yesterday. I'm on the 7 day free trial. When using the hand tool in the program window, with the window zoomed in, scroll bars don't appear and the hand tool does not move the contents of the window around when clicking, holding and moving the cursor. The icon does change to a fist when clicked and held. The hand tool does work in the Source window. Macbook Air M1 2020 running Ventura 13.3.1 (a)Adobe Premiere Pro (Beta) 24.1.0 (Build 25)

I have created an object mask that tracks in a short sequence.  A Gaussian blur is applied to the masked area. The mask was created by drawing around the item on the first frame of the sequence, and then using imbetweening across the rest of the sequence frames.  This works perfectly - the tracking is awesome. There are 2 issues:Within Premiere, playback is corrupted (lots of flashing colours across the full canvas). When you pause playback, this settles and shows everything correctly (including the mask and blur).When exporting the sequence to a video, the object mask and blur are ignored (entirely absent).  Exporting individual frames (as BMPs) works correctly. System spec:Arm processor: Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) CPU (3.42 GHz)64GB RAMWindows 11 25H2Version 25.6.0 BETA (Build 102)

Description: I’m experiencing a bug in the current Premiere Pro Beta (version 25.6.0) related to manual masking and keyframe animation.When I draw a mask using the Pen tool or shape tools and attempt to animate it using Mask Path keyframes, the mask does not respond to changes. Even after enabling the stopwatch and adjusting the mask on different frames, the animation does not register—both keyframes remain identical, and the mask stays static.I’ve confirmed this behavior in multiple projects and tried the following workarounds:Toggling the Mask Path stopwatchManually adjusting the mask shape on different framesUsing different effects (Gaussian Blur, Lumetri Color)Resetting workspaces and preferencesNone of these resolved the issue. It seems the new masking system in the Beta is not properly linking manual mask adjustments to keyframe animation.System Info:Premiere Pro Beta v25.6.0Windows 11 Pro 64GPU: Nvidia GeForce RTX 3080 LaptopThis bug is blocking my workflow, especially for subtl

Stroke effect > pre scaling does not work as expected.W11 pro 26.2.0.41No issue in public 26.0 version 

After masking and tracking an object with the latest tool in the object (which works suprisingly good and smooth), I can not change the opacity of the mask unde this tool. The opacity slider moves but does not do anything. Help pls :')

I’m trying to run a plug-in built with the UXP framework in Premiere Pro 25.6 Beta.When I load the plug-in using the UXP Developer Tool, it runs correctly in Premiere.However, when I place the plug-in folder directly into~/Library/Application Support/Adobe/UXP/Extensions/and try to launch it via Window > UXP Extensions in Premiere, the plug-in doesn’t appear.In the UXP Extensions menu, I only see options like “Browse Plug-ins” and “Manage Plug-ins,” but not the plug-in I placed manually.How can I make the plug-in appear in the UXP Extensions menu without using the UXP Developer Tool?Also, I’m wondering: now that UXP Extensions are available, are classic extensions (CEP) no longer supported?

Editing 4K footage in a 1080p timeline.Scale set to 50% (as in Fit)100% wireframe is showing in the Program Monitor with Direct Manipulation set to OnSuppose this is more of a bug as moving the clip around makes it the clip all jumpy.Putting all the clips in a new sequence solves the issue temporary.W11 pro26.3.0.9 

Pop-up windows blocked, there's nothing you can do once this happens. 

When dragging playhead through the timeline with the mouse it gets stuck on every cut when Selection follows Playhead (SFP) is turned on.After each cut I need to grab the playhead again.When SFP is turned off there is no issue. W11 Pro26.3.0.2

Using the current Beta version in multi-camera mode, as I drag the scrubber across the timeline the scrubber stops at each segment boundary. I have to re-grab the scrubber and pull it into the next segment. Also when I start up the Beta version, there is a message saying that there is an update available. When I attempt to update the message is that the update is not yet available.

Analyze is turned off, but its Premiere is still making prin files. I don't want them. They are making a mess of the Project folder. Or please put them in their own folder.

Hi everyone,I just started using the Premiere Pro beta to test out the new object tracking feature. No matter how long I wait, it gets stuck at "Initializing" and just keeps spinning.I've confirmed with multiple other users that they are seeing the same issues. My setup: Windows 11, Premiere Pro beta 26.0, GPU 5080, CPU Ryzen 9800X3d. The footage is from an iPhone 17.Things I've already tried: clearing the media cache, converting the file to ProRes, and nesting the clip before tracking. Nothing seems to work. Does anyone have any ideas? 

I tried the direct link provide here: But that did not help with the Beta version.  

Premiere Pro (Beta) freezes after each minor editing action (selecting or moving a clip on a track, zooming the timeline, etc.). Each freezing may take from 1 to 5 minutes, so I can’t edit my videos well. This happens even in simple projects with 2-3 tracks and without complex effects. system info 

Adobe Premiere Pro Beta peeps! What up? Y’all ship so fast, it be all like Cutty Sark up in here.I originally posted in Premiere Pro by accident and the version has already updated to v26.2.0 but the issue remains. Transcribe works great for 98% of the words but I need to edit the 2% of words it got wrong. But I cant. I go to the transcript panel, double click to edit a word, change it. Click out because enter just creates a line break, and sometimes the edit doesn’t take. Thanks for looking into it, I love editing via transcript. It makes everything so much easier, especially with filler word removal. But also, it would be nice to create my own dictionary, I edit a highly technical podcast with a lot of abbreviations and jargon. I’d love to able to teach the transcription tool the words it almost never understands… but maybe it’s learning from my corrections. If only they would take... more reliably.

Steps to reproduce:When you click on any color window to open color picker dialog Premiere 26.2 (build 24) instantly crashes.System info    Application: Premiere Pro (Beta) v26.2.0.24    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24

On export:  Some object masks are offline and will be ignored. How to find these masks and reconnect? The mask folder is filled with files with ' impossible'  file names.   I went thought the entire project and could not find any offline object masks. I did make several but deleted them from the timeline before going to export. 25.6.0.92

I have done the recent updates, I tried restarting the software and the PC but it doesn't solve the problem. It will probably be fixed with the next update ?

After opening  Premier in 25.6.0 Build 31 (Beta), Mercury Transmit doesn't transmit to the monitor.I have to go into Preferences | Playback,  just click OK, and it starts working. (Didn't have to change anything because the proper monitor is still selected.) I thought it might have to do with the beta upgrade, but it fails after the app restarts, and works again after the reset.Graphics card is nVidia 5080.  On Windows 11. 

I’m experiencing the same issue others have reported. I can’t open an Adobe Premiere Beta project—the application crashes immediately upon opening the file.I’ve tried all the troubleshooting steps listed in Adobe Support, and I don’t use any third-party plugins, so that’s not the cause. At this point I’m completely stuck and unable to work.Since switching to Premiere Beta, I’ve been running into a new blocking issue almost every week. Right now, I’m literally unable to do anything but wait for a fix. This is extremely frustrating, especially on a deadline.Any guidance or workaround would be greatly appreciated.

Under “Opacity” and the others effects the Mask option is disappeared. 

When I try to open Premiere Pro Beta 26.2 I get the splash screen and then nothing opens. I've updated all my drivers, rebooted, uninstalled and reinstalled, and ran as administrator. Nothing works.ThanksWindows 10ASUS MB64GB RamNVidia Ge Force RTX 2070

I uninstalled the software but it doesn't work

This is an annoying behavior that did not happen before and is still present even in the Premiere Pro Beta. When you modify the value of an existing keyframe, its interpolation resets from Bezier to Linear.For example, if a Scale keyframe is set to 50 with a custom Bezier speed curve, and I later change that same keyframe value to 60, the keyframe immediately becomes Linear. This forces me to manually recreate the Bezier speed curve every time I need to adjust a value, which significantly slows down the workflow and breaks fine motion adjustments.The expected behavior is that modifying a keyframe’s value should preserve its interpolation type and Bezier curve unless the user explicitly changes it.