Bug Reports

issue: selecting Browse or Custom in the Creative section of the Lumetri panel is broken.   how to replicate the issue: open Lumetri panel, navigate to Creative section, next to Look open the drop down menu and click Browse. For me, this doesn't open up the file explorer window to find my LUT file, it simply loads the SL NOIR TRI-X lut for some reason. Manually selecting other LUTs from the drop down menu, and selecting None all work fine. It's only when selecting Browse or Custom that this happens.   version: 25.2.1 build 2 (also happened with the version immediately before this one)   OS: windows 10 home Build 19045.5608

Hello.Fit to frame not working properly. Yes, FIT TO FRAME is selected BEFORE importing the clips.When I select an in and out from the source window and drag the clip without sound, the fit to frame feature works and the clip stays at 50% (FHD sequence with 4K clips), if I drag the clip together with the audio the clip doesn't fit to frame ands stays at 100%.This is ridiculous everytime a new CC comes out something is broken that wasn't before.CC2025Macbook pro m3 max

I updated to PP 2026 and upgraded my previous 2025 project to the new year version. Now PP is basically unusable it's awful. Constant rainbow wheel and frozen every other click. I literally can not use anything and now I cannot access my project file in the old 2025 version which works perfectly since I already upgraded the project file and their not backwards compatible and Adobe has no tool for this and the 3rd party tools that do exist are not working to convert the 26 file to 25. I need help on this ASAP I have the fully maxed out M4 Max laptop and editing the best SSD's you can buy so its not a hardware issue, its once again as always an Adobe issue, If this does not get resolved I am canceling my years of membership tomorrow and switching to DaVinci for good. Thank you

Issue – When using Grow FX or Shrink FX (and possibly some other FilmImpact FX) with a white image over a white matte, you can see an outline of the image’s edge. This is likely present with other combinations of images and colors as well, but it is more visible with white on white. Steps to reproduce –  Create white matte on timeline. Place an image over the matte on the timeline. Apply Grow/Shrink FX effect. Expected result – The image should grow or shrink without a visible outline. Actual result – The image grows or shrinks with an undesired, visible outline. Screen recording – Recording attached. Adobe Premiere Pro version – 26.0.0 (and tested on a prior 25 build) Operating system –macOS 26.2 (25C56) GPU driver version (Windows only) – n/a Video format – H.264. Sample attached.  Comparative information helps us understand more about when the issue occurs:  Does it affect all projects or only some projects? All. Does it affect new projects? Yes. When did the problem begin? Ove

Premiere 2026.Transmit doesn't launch at startup. You need to open and close the prefs panel to activate it.Reset preferences doesn’t do anything.It is a bug that I reported back to v2025, but the topic doesn’t exist anymore…Thanks.Macbook Pro M1 MaxSequoia 15.7.3

When "Show Audio Time Units" is enabled in the timeline, the Control+K shortcut does not cut at the sample level. Instead, the cut snaps to frame boundaries. However, using the Razor (Blade) Tool allows accurate sample-level cuts as expected.Steps to Reproduce:1. Open a sequence in Premiere Pro.2. Enable Show Audio Time Units in the timeline.3. Zoom into the waveform to confirm sample-level visibility.4. Place the playhead between frames (not on a frame boundary).5. Press Control+K to add an edit.Expected Result:Control+K should create a cut exactly at the playhead position on the sample level when audio time units are enabled.Actual Result:The cut snaps to the nearest frame instead of cutting at the precise sample location.Additional Notes:The Razor (Blade) Tool cuts correctly at the sample level under the same conditions.Audio and video tracks are unlinked.Snapping is disabled.Attachments:1. Screenshot showing Control+K cutting on frame boundaries.2. Screenshot showing the Razor Tool

IssueClicking the "fx" toggle button on a clip causes the Effect Controls panel to turn black and reopen in a new tab.Steps to reproduce Open a Premiere Pro project with clips containing applied effects Select a clip on the timeline with effects applied Verify that the "Effect Controls" panel is open and visible Click the small "fx" toggle button on the clip (to disable/enable effects) The Effect Controls panel turns black/becomes unresponsive The panel closes and reappears in a new tab instead of returning to its original position Expected resultClicking the "fx" toggle button should only disable/enable the effects on the clip. The Effect Controls panel should remain visible and functional in its original position.Actual resultClicking the "fx" button causes the Effect Controls panel to turn black, close, and reopen as a new tab. The panel becomes unusable until it's manually closed and reopened.Screen recordingAdobe Premiere Pro version26.0 build 72Operating systemmacOS 26.

Cannot See the Red Selection outline with new “Object Mask Tool” Like this Reddithttps://www.reddit.com/r/premiere/comments/1qnvhvr/cant_see_the_mask_selection_on_premiere_pro_2026/Pls do something

I tried using premiere 2026 and it won’t open without closing or crashing. I’m not even trying to open a specific project but it closes on the home page. I’ve updated my graphics driver and even tried re-installing the app but neither of those worked. Any suggestions?Running on a windows with a Intel Core Ultra 9 and GeForce RTX 5080 and a z890 Aorus Pro Ice Motherboard. I’ve included a video in case it provides clarity.

Since I cannot find my previous bugreport after the redesign of Adobe community, not even in my profile > recent posts I have to start another one. This time it concerns the fresh 26.0 version of Premiere Pro.Render and Replace feature is glitchy in v. 26.0. It fails with timeremapping. Steps to reproduce:start an empty project, import media, cut it on your timeline take one clip and timeremap it. Try to render and replace. Result: Render and replace fails in vertical sequences. Steps to reproduce:from the previously created horizontal sequence copy and paste a clip in a newly created vertical sequence.  Fill the screen with it using the context command. Render and replace. Sometimes you get an error like above, sometimes you get this one: Render and replace fails with the new object mask. Steps to reproduce:in the horizontal sequence select a non-timeremapped clip, select it with an object mask, track it, place the unassigned mask on the opacity Render and replace the masked clip.

Audio Previews folder keeps appearing in the same sirectory as project even though in my project setings the location for them is Documents (the default one). Also in my media chache prefences I have "Save .cfa and .pek media cache files next to original media files when possible unchecked." This buggy Adobe Premiere Pro Audio Previews folder contains another folder with theprojectname.PRV format but it is empty. At the same time the real Audio Previews folder with the peak files is created in the Documents location.This is a ver annoying bug, please fix this before launching new features.Using Premiere Pro 25.1 / Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz / Windows 11 ProVersion 24H2 OS build 26100.2605

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.  

As the title says. I have a multi-monitor setup and whenever I export my second window just vanishes. I can't figure out how to get it back without relaunching the program. I can't afford to waste anymore time on this so I'm just downgrading to the last stable version for me (23.3).Version 23.5Windows 10 64-bit

We have an UXP plugin that creates a connection with a remote server. In doing so, we need to open a web page for login. Premiere opens an Permission Dialog to request permission to open that page...but the displayed dialog has a faulty rendering of :the explanation text the action buttons (Allow | Block)These are unreadable because of color (dark gray over a black background) and placement (no border for the buttons, incorrect spacing).The dialog is therefore unusable. Even worse, if the user clicks by mistake on the Block button it will be hard to recover.This is the dialogDialog with arrows showing the hard to read text and buttons After some photoshop on this image, the button are easier to read… This is currently a blocker for our plugin

HelloI’ve been getting these Frame substitution and error retrieving messages on my Premiere Pro. My Premiere Pro version is 25.6.2,. The footage is the A roll which I cannot remove and which has never before troubled me. I’ve tried deleting cache, creating a separate sequence, restarting Premiere Pro but nothing works.Is there a way to solve this problem? Updated it to 26.0, still doesn’t work.Attaching a screenshot 

I edit with split timelines (Top timeline holding a number of source sequences and bottom timeline holding program sequences) and have been doing so for years in Premiere. Update 2026 is freezing some of the source sequences intermittently when clicking between them and I have to close and re-open them to access them again. Not a major issue but a noticeable bug since the new update.  

Issue: Ripple Trim (Q/W) shortcuts are not functioning on the Subtitle/Caption track. Steps to reproduce: Create a separate Subtitle track in the timeline. Position the Playhead over a caption clip. Press 'Q' or 'W'. Expected result: The caption clip should be trimmed, and the timeline should ripple accordingly. Actual result: No action occurs on the Subtitle track unless a workaround is applied. Workaround found: The Ripple Trim tool only functions on the Subtitle track if an Adjustment Layer of equal length is created and perfectly aligned with the caption clip on a different track. Adobe Premiere Pro version: 26.0. Operating system: macOS Tahoe Version 26.2. System Specs: MacBook Pro 16-inch (2023), Apple M2 Pro, 16 GB RAM. Video format: Issue is isolated to the separate Subtitle/Caption track. Comparative information: The tool requires a parallel Adjustment Layer to trigger the ripple effect on captions. This behavior is consistent across all

For a little while now on the v25.4 beta I've been experiencing an issue when rendering sequences. Usually to prores (with alpha), but have also encountered it less frequently attempting to render to h264/5.I'll try to render out a sequence and it will do seemingly nothing for anywhere from 10-30s then pop up with an error similar to the one I've attached below. The error below was generated by a sequence that contained nothing but a text element with the sapphire ultraglow effect appliedThis issue does not occur if I hold shift during boot and set software only rendering, nor does it occur on v25.01. v25.4 (build 38)2. Windows 11 | 10.0.22631 build 22631 - rtx 4080 (latest studio drivers), amd 7900x, 96gb ram, working off an ssd3. I haven't completely locked down the pattern yet, but I seem to be running into it with sapphire's UltraGlow (latest version) a lot, but as noted previous versions of premiere do not encounter the issue with the exact same sequence, and disabling gpu renderi

Seit letzter Woche kann ich mein Premiere Pro nicht mehr starten. Der Loading Screen öffnet sich und dann erscheint plötzlich das Fenster bezüglich unerwarteter Fehler und Dump File anzeigen usw. Verschiedene Dinge habe ich bereits probiert:alles deinstalliert, komplette CC deinstalliert, Premiere Pro neu installiert mit ALt Tast beim Start in die Optionen und alle Profile und Daten gelöscht eine ältere Version installiert (25.3, 25.6) sämtliche Grafikkartentreiber geupdatedIch habe keine Ideen mehr und benötige dringend mein Adobe Premiere um mein Projekt zu beenden. 

Speed / Duration - unable to change by entering speed % or by using the slip tool. The speed % dialog box accepts the new value, when I click ok or enter it returns to 100%. The slip tool doesn't maker any adjustments whatsoever, either trying to stretch or shrink the clip. I have restarted, checked all updates and problem persists.

Issue Description:While editing a video, if I mute an audio track (using the Mute button on the track), and later unmute it, the audio plays briefly but then gets muted again automatically without any user action.Even after manually unmuting the track, it continues to mute itself again during playback.Steps to Reproduce: Open a project in Adobe Premiere Pro Add a video/audio clip to the timeline Mute an audio track using the track mute button Unmute the audio track Press play The audio becomes muted again automatically without any interaction Expected Behavior:After unmuting an audio track, it should remain unmuted and play normally unless manually muted again.Actual Behavior:The audio track automatically mutes itself again after unmuting, without any action from the user.Additional Notes: This happens repeatedly The issue occurs even when no automation or keyframes are applied It significantly disrupts the editing workflow Please let me know if you need any additional de

Hi - I've been plagued by this across many different projects now. At first I thought it was potentially tied to the Production environment, which I've been kicking the tires in the last few weeks, across 3 different Productions. But today I can confirm that is not the case as I'm in a regular project, outside of Production, and I am experiencing the problem... Enter Export menu with your sequence (via CTRL+E hotkey in my case)Grab Adobe's PR4444 presetExport via AMEInspect your clip in another player or re-import in Premiere: video is black, audio is ok.Export via Premiere Pro: your exported clip is fine. Sequence resolution is UHD, 30 fps. Fairly straightforward edit made of one main video track (sources are UHD.mp4), 1 layer of a black slug acting as a mask for one 1 layer of mogrts. I tried enabling/disabling the Max bit depth and Max quality settings thinking that was the issue initially, no change. Switch to other ProRes or H264.mp4 codecs, no issue, all is well.The "fi

Is it just me that pays attention to such things or is this problem simply ignored - has been for years, a decade probably?This is just a layer (clip\mogrt) - it’s reversed and time-remapped. This is what happens when you adjust the remapping curves to slow the part further: Can anyone tell me where is logic in that? Why is slowing down the end of a reversed clip makes it longer but when you do the same with the beginning, the whole clip shortens to the extend that it can sometimes not be seen at all? There’s nothing in front of the clip. I sow this in Pr 10 years ago and this still isn’t fixed...   

Even though you've stated that a fix has been released and optimized to work with the Blackwell architecture, something is wrong. Nothing is working as it should: slow export performance, the program crashes, and various other bugs. These problems aren't just affecting me, who has mid-range 5060 Ti and RTX 5070 cards, but are also affecting users who have RTX 5080 and 5090. Before, I edited with an RTX 3060; I even edited up to version 24 of Premiere on it. When I switched to the RTX 5000 series, I was already using the new versions 25 and 26 of Adobe Premiere. I, like most editors and cinematographers in the mid-range, use cameras that have AVCHD H.264, MP4, MOV, MXF, AVC, and H.265 codecs. I hope that you at Adobe will strive to correct these deficiencies. I have a huge regret in having migrated my system to RTX 5000 cards with a lot of features, but for my editing use they don't work well in Adobe Premiere, a program I've been editing with since CS6.