Bug Reports

System: Premiere Pro 26.3.0, Build 93 macOS 26.5.2 MacBook Pro with Apple M4 Max and 48 GB memory Approximately 283 GiB of available internal storage Steps to reproduce: Open my approximately four-minute sequence containing video clips with Lumetri Color, plus Premiere-generated titles, lower thirds, and a logo overlay. Export the complete sequence using either H.264 or QuickTime Apple ProRes 422 with Match Source settings. Review the exported file. Expected result:The exported video should match the Program Monitor and rendered timeline.Actual result:Random video clips export with severe black-and-gold posterization, inverted/negative colors, or colored pixel/grain artifacts. The affected clips change between exports. Premiere-generated titles, lower thirds, and the logo remain completely normal over the corrupted footage.The same affected clip may export correctly when I export only a short range around it. For example, the first half exported correctly as H.264, but export

I updated to Premiere 26.3 on July 27th, 2026. For a 30 minute video with two stereo audio tracks, the transcription recognizes both media sources (and will allow me to select both for transcription) but after processing/loading, it only transcribes the first audio track. I tried getting around this by exporting the audio file and importing it into the project, but Premiere omitted the second audio track. I tried opening the project with Audition, and though it showed both audio tracks with the appropriate editing cuts, there was no waveform for the second track.  

The program crashes when using two effects at the same time: luminance embedding and film impact dashboard shake.

Hi all, I’m running into a really persistent issue with Premiere Pro: whenever I hit play, it just hangs on “Preparing audio” for a long time and won’t start playback.Here’s what I’ve already tried (with no success):Reinstalled Premiere ProUpdated GPU (NVIDIA Studio driver)Set Audio Hardware > Default Input = None (helped once, but the problem came back next day and now wont work again)Cleared Media Cache (both in Preferences and manually from AppData)Moved Media Cache to a fast SSDDisabled/uninstalled extra audio devices (Dolby APO, NVIDIA/AMD HDMI drivers) so only Realtek(R) Audio is activeReset Preferences and Plugin Cache (Alt + Shift launch)Renamed Documents\Adobe\Premiere Pro\[version] folder to force a new profile It does it track by track and takes about 20 minutes each, the video is 1 hour 30 with multiple audio tracks, the footage is Proxy.  Really not sure if its a Premiere issue, or a Windows Issue. Everything is up to da

Environment macOS Tahoe 26.5.2 | M1 Max MacBook Pro (64 GB RAM) Premiere Pro 26.3.0 (Build 93) No available updates in Creative Cloud at time of testing Workflow / contextI’m using the Source Sequence in Source Monitor / Open Sequence in Timeline / pancake timelines workflow: Load a sequence into the Source Monitor. Use Open Sequence in Timeline to open that source sequence in its own timeline above my working Program sequence. Now I have: Source sequence visible in the Source Monitor and its source timeline. Program sequence visible in the Program Monitor and its program timeline. I’ve recorded a short video demonstrating the behavior here:https://f.io/9T-wih53 Issue 1 – Source timeline playheads ganged even when Gang is OFFSteps to reproduce Load a sequence into the Source Monitor. From the Source Monitor, Open Sequence in Timeline  Ensure Gang Source and Program is OFF  Scrub the playhead in: Source Monitor → playheads behave independently (as expected).

I took an image showing multiple characters in that image, duplicated the image applied making on the top layer selecting the person of interest. Applied Black & White effect on the lower layer. Next, I took an adjustments layer and applied an effect called Posterize time effect and as soon as I applied it the masking behaves unpredictive.With Posterize time activated.Posterize Time Activated Posterize Time De-activatedTroubleshoot: 1. I tried to put this posterize effect on nested sequence of the two layers.2. Without Nested sequence adding and adjustment layer on the top.​​​​​​Nothing works.

Wenn man in Premiere 26.2 N-RAW, oder RED-RAW, oder ProRes RAW importiert geht das Abspielen in Premiere, aber wenn man das Exportiert, gibt es weisse Pünktlein an den dunklen Stellen, es ist nicht bei jedem Player gleich stark zu sehen, aber es macht RAW in Premiere unbrauchbar, das Davinci Resolve hat das Problehm nicht.Nehmen Sie mal eine Kamera und lassen den Obijektivdeckel darauf und machen eine Aufnahme, das ist am besten zum testen: Mein Video:  

I’m so often encountering this bug in Premiere after having the project opened for a little while. I create or edit text whether it’s just a line or a text box and user interface box around the text does not appear. I can’t see what text I’m editing, can’t see what I’m highlighting or deleting or anything. When I click on the text to drag it around, I can’t see the box at all. This is a seriously annoying bug, please fix.(I’ve made my clicks highlighted yellow so you can see what I’m clicking)

Premiere Pro reads two different creation timestamps from the same Meta Smart Glasses MOV file.In the Media Import screen, Premiere correctly shows the original recording time. However, after the clip is imported, the Project panel’s Creation Date column shows a later timestamp associated with when the Meta app processed, transferred, or exported the file.For example, one clip shows:Correct capture time in Finder and Media Import: July 23, 2026 at 4:40:17 PM Creation Date in the Project panel: July 23, 2026 at 9:08:20 PMBecause Meta Smart Glasses clips are not always processed in the same order they were recorded, sorting the Project panel by Creation Date places clips in the wrong chronological order.The correct capture timestamp is already present in the file and Premiere’s Media Import screen can read it. The Project panel should either use that same timestamp or expose the original capture-date field as a sortable metadata column.Import Tool:Project Media Browser: 

 I tried all the suggestions from the internet and nothing happens. So I then started a new project in an oldest version and and the same thing is happening.  It worked just fine last month but now its notEdit As I said, PP Is not showing the waveform. I traid everything, unstaill the app, delete cache, change colors, etc. Nothing works. It ju st stop working from one day to another

Captions panel is not working properly. It's not letting me edit captions. Only on the Program screen. Please FIX THIS. My videos ALWAYS require me to edit my captions. THIS IS SO INCONVENIENT AND IT'S SLOWING MY EDITING TIME DOWN.

Using Warp Stabilizer short or long video after the analyz the whole systme crashes. The pc just switches of itself.

Documentary files so lots of them.  Files have had proxies created but timeline does not always show them as being used.  Watermark appears after reboot of Premier, then disappears and playback sticks throughout.  I can’t even show the client progress and he along with myself are extremely frustrated.  Show worked wonderfully until 2026 came around.Support phone number has language barrier and I can’t understand most of what they are saying….why Adobe, why?  I decided to go from Avid to this?  I am dead in the water right now waiting for a 24-48 hour “elevated” phone call 

Cannot add media to project in MacOS 27 Dev Beta 3. Crashes consistently. Pr 26.0.2 is fine:Adding media to new or existing projects crashes every time. Can work with projects already created in earlier beta OS with 26.3. Uninstalled 26.3 and eventually found that 26.0.2 works as expected.

This is one thing that bugs me for many versions of premiere now.There are multiple possible situations that will change, close or even open random sequences:closing and opening a project resetting or changing workspacesSource sequences are not saved at all when closing a project.The problem with that is when working between multiple sequences, every time I reopen the project, I need to go through the process of opening all that sequences.Premiere should save them, their state (source sequence) and their order when closed.Moving panels is saved when I close the program, so why are sequences not in a reliable way?

IssueI noticed for some time now that compared to normal sequences, the audio toggles in source sequences won’t work or in a buggy way. Same with the audio meter and the mixing console.It’s especially problematic when working with source sequences often (pancake editing)Steps to reproduceOpen a source sequence (in timeline). Use the audio toggles (mute/solo) during playback and when paused.Expected vs actual resultThe video compares this expected behavior in a normal sequence and the actual behavior in the source sequence.This are the results. Expected behavior would be that both work the same (as they share the same UI):  Normal Sequence Source Sequence Mute Toggle works during playback and after pause Toggle does not work during playback (only after pausing it)  Solo Toggle works during playback and after pause Toggle does not work at all Audio Meter Works as expected Shows no level at all (interestingly, when the source monitor is selected, then the audio le

Situation is following:I have a sequence open and another one in the source monitor as source sequence.The nesting of sequences is toggled off and normal insert inserts the selected video/audio tracks instead of the nest.I want to replace a clip with part of the source sequence:I highlight the clip I want to replace in the sequence I set in/out in the source sequence I hit the key combination for "Replace with Clip.. from source monitor (Match frame)"What I expect to happen:the clip gets replaced with the patched video trackWhat happens:the clip gets replaced as nest (with all video tracks) it seems like the button for nested sequence import isn’t working with that command. 

The transcription function does not recognize any dialogue. I have clips with an isolated voice as an mp4 and as an audio mp3 file. Premiere cannot find any dialogue in either file formats. Premiere was working fine with the last project but can no longer transcribe.

Adobe Version: 26.30 build 93 Product: Adobe Premiere ProIssue Summary:When using a proxy workflow, Premiere Pro no longer automatically relinks the original full-resolution media after a project has been edited on another system and returned to the original editor.Steps to Reproduce:Import full-resolution media into a Premiere Pro project. Create and attach proxy files. Save the project and send it (along with the proxies) to another editor. The second editor opens the project, edits using the proxies, saves the project, and sends it back. Open the returned project on the original system where the full-resolution media still exists in its original location.Expected Result:Premiere Pro should automatically reconnect the original full-resolution media since the project is being opened on the original machine where the source media is still available. The proxies should remain attached, and no manual relinking should be required.Actual Result:The full-resolution media is reported as offl

Since upgrading to 2025.3, long format recordings (1 hour plus) take a really long time to import.  It'll sit on the 'importing' diaglog for 5-10 mintues per file.  And it still has to do the indexing processing after.Rolled back to 25.2.3 and the files import quickly again.   Also tried beta 25.6 and the issue still exists. Occuring with many different types of source foorage of compessed formats (pro-res imports quickly, seems to be an issue with more compressed codecs). Mac studio M2 Max 2023OSX 15.5PP 25.3.3Files on internal storageIdentical issue on another similarily equipped system.

The “Delete All Pauses” feature in Adobe Premiere Pro is straight up broken for me now.It used to work perfectly before, but now it doesn't after the update.I set the pause length to 0.01sec but when I press Delete / Extract / Delete All, it removes some parts but leaves a lot of gaps behindI’m doing the exact same thing I used to do before, but now it’s not WORKING!!!!Feels like something changed after the update because this was not an issue at all before.Is anyone else having this problem ? Can you please help me resolve it?

Hi Adobe team,I’m reporting what appears to be a regression in Text-Based Editing, specifically in how Premiere Pro detects short pauses in the Transcript panel.The version that works correctly for me is:Premiere Pro 26.0.2, build 2The version where I am facing the issue is:Premiere Pro 26.3In Premiere Pro 26.0.2 build 2, I could use the Pauses filter in the Transcript panel and adjust the Set pause length / Minimum pause length setting to detect very short pauses in spoken dialogue. This was extremely useful for dialogue-heavy editing, because Premiere would correctly identify even small pauses, including pauses around 0.1–0.11 seconds.However, in Premiere Pro 26.3, the same workflow no longer behaves correctly. The pause-length slider still allows the minimum pause length to be set very low, but Premiere now appears to ignore many short pauses that were previously detected in version 26.0.2.For example, on the exact same video clip: Premiere Pro 26.0.2 build 2: approximately 200 paus

IssueMercury Transmit fails to initialize at project startup unless the Lumetri Color panel exists in the startup workspace. Key finding (reproducible):Mercury Transmit fails to initialize at startup only if the startup workspace does not contain the Lumetri Color panel.The Lumetri Color panel does not need to be visible or active.Its mere presence as a background tab is sufficient to initialize Mercury Transmit correctly.Once Mercury Transmit has initialized, the user can switch to any other workspace and the external output continues working normally.The behaviour is reproducible with different projects, including newly created empty projects.EnvironmentPremiere Pro 26.3.0 Windows NVIDIA GTX 1070 Mobile NVIDIA Studio Driver 581.57 Clevo P775TM1 Secondary HDMI monitor (Extended Desktop) Mercury Transmit enabled Adobe Monitor 2 selected for external playbackIssueMercury Transmit does not start automatically when opening a project if the startup workspace does not contain the Lumetri Co