Bug Reports

When I apply the Gaussian Blur effect and create multiple masks, the blur is applied only to the first mask. The other masks do not show any blur effect.Steps to reproduce: Add a clip to the timeline. Apply the Gaussian Blur effect. Create a mask under the Gaussian Blur effect. Create one or more additional masks under the same effect. Adjust the blur amount. Expected result:Gaussian Blur should be applied to every mask created under the effect.Actual result:Gaussian Blur is applied only to the first mask. The additional masks have no blur applied.Premiere version: 27.0(Beta)Operating system: MacOS Tahoe

I have been editing in premiere for 10+ years and this might be the worst update ive seen. Keyframes for the  mask tool dont work at all. The AI mask tool doesnt work at all and it broke the whole tool. I cant even do a simple hand animated mask. Adobe is way too big of a company for there to be problems like this with essential tools that we've had for decades. These are the things that make me want to abandon these programs. It is my fault I started this project in the beta version though i guess. Cant even revert to another version.

In Premiere 2026 you can copy / paste clips into AE comps. This copy /paste feature isnt working in beta. 

Scale keeps on resetting. With or without key frame it snaps back to 100% every time making it impossible to re frame clips or keep scale keyframes! 

When I adjust the scale on an image, it's not holding and reverts back to 100%

Quando vou para a tela de exportação do premiere, em qualquer projeto, a minha tela simplesmente carrega pra sempre, já cheguei a deixar horas parada pra ver se mudava algo mas não mudaPreciso de ajuda com urgência, isso pausou 100% da minha produtividade

Mask positioned outside adjustments. When try to move or paste to adjusment premiere broke.

When Premiere Beta runs on a second monitor both in clip LUT and sequence LUT the options are greyed out and I can not select anything. I have to move the premiere window to the main macbook monitor to be able to see the selection of LUTs

Premiere 26.5 Beta contains a regression that affects any third-party plug-ins based on the AE SDK. If a plug-in attempts to extract frames during event processing (a common task to perform frame-by-frame video analysis) Premiere Beta will display errors for all frames requested by the plugin. Thankfully the host app still returns the correct PF_LayerDef to the plugin, but the user is presented with a long stream of errors. Steps to reproduce:Install any recent version of FxFactory from https://fxfactory.com/download/  Launch the FxFactory app and install a product that performs frame-by-frame video analysis, such as Face Blur Launch Premiere Beta and apply the Video Effects > Face Blur > Object Blur plugin to an existing video clip on your timeline: Apply the Object Blur under the Face Blur categoryBring up the effect parameters in the inspector and click the track forward button to begin analysis, under Object Tracking section:   Notice that as the plug-in starts requesting a

I was trying to enlarge my video to 200% scale, but accidentally typed 200% into the Opacity field and hit enter. Seeing as there is no such thing as 200% opacity, Premiere apparently decided the only reasonable response was to crash. Version 27.0.0 BETA StaticLib (Build 18)MackBook Pro 16-inch, 202364GB MemoryApple M2 MaxTahoe 26.5.2

It is slow. the menu is slow. I cant use this program. Its annoying and costing me money and my reputation

The program monitor freezes completely on a single frame during playback when encountering sections with subtitles, shapes, gradients, or custom effect presets. Audio continues to play normally, but the video preview remains stuck. This issue arose immediately after updating to Premiere Pro Beta 27.0.0.20.System specifications:CPU: AMD Ryzen 9 9950XGPU: NVIDIA GeForce RTX 5070 Ti 16 GBRAM: 64 GB DDR5OS: Windows 11Here you can watch a video that shows the error.https://drive.google.com/file/d/1NrTozF6I3BnzEYklB7KkatWbtg-nK9ar/view?usp=drive_link

Export freezes while "Preparing Content Credentials”Exporting as usual and the first loading screen while exporting says “Preparing Content Credentials” and is stuck at 100%. I’ve tried toggling Content Credentials on and off. I’ve cleared my cache. I’ve tried moving on and out points, I’ve tried rebooting, I’ve tried exporting different codecs.  If I export with Credentials on, it says "Applying Content Credentials” and also freezes at 100%. I’ve verified my identity and credentials.  I’ve tried media encoder with things toggled on/off and multiple codecs. I’ve also tried other project files.  I must export. 

Title: Audio Plug-In Manager scan hangs and returns no plugins (VST3 + AU) — 27.0.0.17 and 26.0 beta, macOS 26.5.2. Release Premiere scans the same folders correctly.Environment: Premiere Pro (Beta) 27.0.0.17 and the prior 26.0 beta build. macOS 26.5.2 (25F84), Mac17,6, Apple Silicon, 64 GB. Audition (Beta) exhibits the same. Premiere Pro 2026 release and Audition release on the same machine are unaffected.Symptom: Preferences > Audio > Audio Plug-In Manager, folder list contains only /Library/Audio/Plug-Ins/VST3 (VST2 paths removed). Click Scan for Plug-Ins with Rescan existing plug-ins checked. Beach ball, then the Available Plug-Ins list is empty — no VST3, no AU. Effects > Audio Effects shows only Adobe built-ins. ~/Library/Preferences/Adobe/DVAAudioFilterScan is never created after the scan.Control: On the same machine, Premiere Pro 2026 release launched after DVAAudioFilterScan was deleted, rebuilt it on its own, and loads every third-party plugin (iZotope Ozone/Neutron/

Steps to reproduce:1. Fresh install of Premiere (Beta) v27.0.0.16 on macOS 26.5.22. Open Effects > Audio Plug-In Manager3. Confirm /Library/Audio/Plug-Ins/VST is in the VST folder list4. Click Scan for Plug-InsResult: Scan completes with 0 third-party plugins found. Opening a.prproj referencing iZotope Ozone (VST) and Insight 2 (VST) throws"Audio Filter missing" for both.Expected: Scan detects installed VST2/VST3 plugins. Release & Beta Auditionon the same machine scans the identical folders successfully andopens the same project with both effects intact.Audio Filter missing: 3:5653545a 6e4f5a4f 7a6f6e65 2050726fAudio Filter missing: 3:56535449 4e533049 6e736967 68742032

When I create a new project and drag my first clip into the timeline to create the timeline it does in as it should. however any other clips do not. please fix.

when I stop the play head over one of my clips, I can see the clip, but when I play the video the clip is not showing.  Chatting with the AI assistant - this error appears to be with Film Impacts Bokeh effect on the clip.  It seems it can't render the frames in real time so they are being dropped

I appreciate Adobe providing complimentary AI Assistant usage during the Premiere beta. However, the current usage limits are so restrictive that they are preventing me from meaningfully testing the product.In my case, I exhausted the available Assistant capacity within essentially one day of working on a relatively simple project: a roughly 108-second sequence made up of 433 still images. This was not a heavy post-production project involving multicam footage, complex audio, large amounts of video analysis or sophisticated compositing. Much of the work was repetitive timeline editing and applying straightforward effect settings.During that single project I encountered a per-response tool-call limit, a daily limit and ultimately a weekly processing limit. Once the weekly limit was reached, I could no longer continue testing the Assistant at all.I understand why Adobe needs limits during a public beta and I appreciate that the usage is complimentary. But a limit this low undermines the

I’ve recorded a Loom video to show the issue. Essentially, when I’m editing using a transcript - every clip starts too late and often in the middle of a word. So I have to go into every clip and start it earlier so you can hear the full word. 

  If you go to view → add guide​​​​​​ In the add guide menu, only thing that actually reflects the change you made is color. Anything else is changing visually but don’t really effect the guide. You also can’t create a horizontal guide it only creates vertical even if you choose horizontal And if you right click on a guide and open edit guide menu. It’s the same thing.   except it’s even worse than add guide menu. Nothing except color makes an actual change.System info    Application: Premiere Pro (Beta) v26.5.0.27    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24

This build of the Beta (it happened even on the previous one) has Control Surface completely broken. An ‘unexpected error’ prevents Premiere to initialize any Productions and Projects, resulting in a warning window telling me the error - I attached the warning window.The issue doesn't present itself in the regular release - altough I'm some version behind as the latest stable build has a known issue with RTX 50 series cards when it comes to graphics properties, which funny enough was fixed in the Beta builds.My PC is as follows:Windows 11 Pro Intel Ultra 9 285K NVIDIA 5070Ti 16GB (latest Studio Drivers) 64GB DDR5I use the Logi MX Creative Pad. 

Premiere Pro 26.3 and Premiere Pro (Beta) 26.5 both crash in MacOS Golden Gate Beta 3 (MacOS 27). M4 Pro Mac Mini, 64 GB RAM. The Beta won’t even launch fully and always quits, while 26.3 will let you open it, but basically the moment you do anything in it, it crashes. Both are basically unusable at the moment. 

I had no problems Friday- now today on Monday I can hardly use any command in Premiere Pro Beta without it is crashing. All my Adobe apps is up to date. Hope you can fix this issue, what ever is causing it.

In all past premiere pro versions a user can simply undock a folder, (by double clicking on a folder in the project window), and place that folder into any other window they’d like. With beta mode, this folder option is not available and is very frustrating to click between footage or assets when you constantly have to keep double clicking to either go forward or back

Hey guys,Just wanted to drop some quick feedback on timeline performance. I work on pretty huge projects and things get super laggy. Here are a few things I noticed:Open Timelines: Having multiple timelines open kills the performance of the main one. It feels like the background ones are constantly rendering the timeline UI. As soon as I close them and only keep one opened, everything becomes faster. Solution for that could be that the timelines are simply not taken into consideration as long as they’re not opened. VST Plugins: If I use a bunch of VSTs in a sequence, it lags (totally fair). But the lag stays even if I close the sequence or open a completely different project. It's like the VSTs never actually turn off and are still listening for a signal in the background, even when you left the sequence or project where they are used. Only a full app restart fixes it. Audio Waveforms: Hiding waveforms gives a solid speed boost when scrolling on the timeline. It feels like the app cons