Bug Reports

The auto-save feature isn't working. Premiere freezes. I've been experimenting—I set the autosave interval to 10 minutes, and after 10 minutes, Premiere freezes. I set it to 3 minutes, and after 3 minutes, it freezes. Sometimes this corrupts the project, and I have to redo some of the work. This is terrible; professional software shouldn't work like this. I use the latest versions of all updated software on Windows 11

I am using the default Light Leak transition on a clip coming out of black on my timeline to get a wash of color over the video as it fades up. I also use the same effect between subsequent clips in my timeline. Everything looks great until I try to export the clip using a loudness normalization effect as part of the export. When loudness normalization is applied as part of the export, the transition coming out of black is devoid of color and the color pops on as soon as the transition ends. The following light leak transitions following it that are between two video clips look fine in the export, only the one coming out of black is effected. It shows in any type of export reliably, even ProRes 422 HQ uncompressed. Here are two clips uploaded to my google drive showing exactly this, as well as a screenshot of the effect in question on my timeline.https://drive.google.com/file/d/1FoHCIHadZKYKSuCXFkkd0PloHCHvlNRx/view?usp=sharinghttps://drive.google.com/file/d/1T3aXgDq6RJNSwG5oy1LE2fywn4

Hello,I have now clearly isolated the issue.My iPhone HDR footage is recorded as:HEVC 10-bit 4:2:0 Rec.2100 HLG 4K at 60 fpsWhen I import this footage into Premiere Pro 26.3 on Windows 11, its colors and brightness change. The exported result also appears brighter, less saturated, and different from the original iPhone video—even after uploading it to YouTube.I then disabled “HDR Video” on my iPhone and recorded a new test clip. The new clip was:HEVC 8-bit 4:2:0 Rec.709This Rec.709 clip appeared exactly like the original inside Premiere, after export, and during playback. Therefore, the problem occurs only with iPhone Rec.2100 HLG footage.I do not want to disable HDR permanently because I want to benefit from the HDR recording quality of my iPhone.Could you please provide the precise Premiere Pro settings for either:Editing and exporting the iPhone footage as true Rec.2100 HLG HDR for YouTube, while preserving its original appearance, or Converting the iPhone HLG footage to Rec.709 SDR

I’ve never had any problems using a network attached storage with any other software except Premiere.It is ultimately the biggest pain and hinders my work when it decides to forget where all of my footage and assets were.I store all footage on my local NAS and it is always connected to my workstation via physical network connection.The project file I’m working on now has decided to forget that i have a NAS and all of my assets are offline.I tried to re-link them, but it cannot automatically relink for the 1000+ assets that it cannot find.I must add that the re-linking user-experience is the worst. It takes a minimum of 10 seconds to an average of 20 seconds for a folder load any contents when browsing using Premiere’s media browser.Selecting media with ‘Automatically re-link media’ enabled does not automatically relink the footage or assets on the NAS.This needs a proper update or rewritten function for an acceptable solution, not a band-aid or workaround.

Zusammenfassung:Preview-Wiedergabe ruckelt stark bei 50%-Zeitlupe (Frame Sampling) auf 10-bit 4:2:2 All-Intra-Material, obwohl Export und lokales Rendering einwandfrei flüssig sind. Proxys, GPU-Beschleunigung und schnelle Storage-Lösungen ändern nichts am Verhalten. Bemerkenswert, da All-Intra (jedes Frame unabhängig, kein GOP-Referenz-Overhead) decoder-technisch eigentlich einfacher zu handhaben sein sollte als Long-GOP-Codecs.Quellmaterial:Codec: H.264, 10-bit, 4:2:2, All-Intra Auflösung: 4096×2160 (C4K) Framerate: 50fps (konstant, bestätigt via Frame-Count/Dauer-Berechnung, kein VFR) Bitrate: ~600 Mbps Farbraum: Rec. 709 Sequenz: 25fps TimelineWorkflow:Clip in 25fps-Sequenz einfügen Speed/Duration auf 50% setzen (Time Interpolation: Frame Sampling, Standard) Preview abspielen → deutliches Ruckeln, wirkt wie ~12,5fps statt sauberem 25fpsBereits ausgeschlossene Ursachen:✅ Framerate-Interpretation korrekt (Interpret Footage zeigt korrekt "50,0000 fps aus Datei") ✅ Kein VFR (Variable Fr

Over the last few days I’ve been getting the following error message across all projects in Premier:“Gaussian Blur 26.3.0 error at 0:00:00:00Illegal address. (code 700)”I’ve tried uninstalling and reinstalling and it still occurs. I’m running Windows 11 version 25H, what I believe to be the latest version. This issue just occurred out of nowhere, as its been running glitch free till now.

Premiere Version26.3.0 (macOS)IssueDragging an existing sequence onto the New Item button creates a new sequence whose Composite in Linear Color Mode setting does not match the original sequence.Steps to ReproduceCreate a sequence. Disable Sequence Settings → Composite in Linear Color Mode. Add a clip. Add a Color Matte above the clip with a blend mode such as Overlay or Soft Light and adjust opacity so the effect is obvious. Drag the sequence onto the New Item button to create a parent sequence. Open Sequence Settings for the newly created sequence.Expected ResultThe new sequence should inherit Composite in Linear Color Mode = Off, matching the source sequence, so nested compositing is visually identical.Actual ResultThe newly created sequence has Composite in Linear Color Mode = On, causing blend modes to render differently (lighter in this example).WorkaroundInstead of dragging the sequence to New Item:Duplicate the original sequence. Delete all clips. Drag the original sequence int

Splash screen on startup - “requires access to the following folder(s): Desktop." This issue has only occurred in v26 updates of Premiere Pro. Insufficient workaround it to reboot in an older version of Premiere Pro. 

Hello Adobe Support Team,I am experiencing a persistent issue with the Transcript and Pause Detection features in Adobe Premiere Pro.My workflow requires removing unnecessary pauses/silences from videos. For example, a 38-minute video should normally be reduced to approximately 6 minutes after removing long pauses. However, Premiere Pro is not detecting and removing pauses correctly, and the feature is not working as expected.I have performed multiple tests to identify the cause of the problem: I tested the feature on my current updated version of Premiere Pro, but the issue continued. I also tested previous Premiere Pro versions to check whether the problem was caused by the latest update, but the issue remained. I switched between the current version and an earlier version of Premiere Pro, but there was no difference in the behavior. I tested the same workflow with a different video file to make sure the problem was not caused by a specific video, but the issue happened again.

An unspecified error occurred while performing a conform action on the following file. I want solution for this. 

I just want to synchronize clips to synchronize audio from video.But when I click right bottom not appears synchronize option. My files:1 video mp41 video movIn the past versions of the Premiere 2023 this works well My Premiere PRO 2025

PILE OF TRASH! I SQUANDER BUCKS ON YOUR FAULTY PROGRAMS! GET A SERIOUS TEAM OR YOUR COMAPNY WILL BANKRUPT! SUCH A DISEASE, STONEAGE SOFTWARE, STUPID FEATURES AND BLOATED PROGRAMS! GET OFF MY FACE! I SHOULD BE PAID TO USE SUCH RIDICULUS COMPUTER JOKES! YOU SHOULD ALL BE FIRED

I've dealt with this error before but it now seems to be on steroids - Frame Substitution Recursion attempt aborting after multiple attempts on file... Mac Mini M4 Pro64G memorySequoia 15.1Media Hard Drive - WD_BLACK 4TB SN850X NVMe SSDGen4 PCIe, M.2 2280, Up to 7,300 MB/s1.9TB available of 4TBPremiere Pro 24.?, 25.2 and 25.3 (beta) I'm editing multiple footage files that I've used consistently since 2022. They are h.264 mp4 files - basically B-Roll masterfiles for work that have never given me any issue. Some of the footage is 59.97fps, some are 29.97. None are variable framerate, all have been exported into these file formats from their original sources and used without issue for some time, including on a much less powerful machine.At the beginning of January I was using Premiere Pro (beta) - not sure which version - and every footage clip in the library started giving me the "Error retrieving frame" error. I couldn't get it to stop so I switched to the non-beta versio

So I have updated the Premiere Pro from 25.6.4 to 26.0 and it updated smoothly, then I continued the editing. When I was still in Premiere Pro and decided to move files from one bin/folder to another folder, the software was suddenly not responding then crashing. Well it’s complicated because this happens everytime I reproduce the steps until now. It won’t happen if I do cut/copy then paste, but files can’t use cut feature. Please help me with this case ASAP because this didn’t happen in previous version. Only 26.0 version that causes this issue.

Environment: Premiere Pro 26.3 (June 2026 release) and 26.0.2 / Windows 11 / UXP panel (manifest v5)SummaryWriting any Color value to an effect parameter from a UXP panel corrupts the blue component. We first confirmed this on 26.0.2 across every available write path (static createSetValueAction, keyframe batch via createSetTimeVaryingAction + createAddKeyframeAction, per-keyframe transactions, and packed 64-bit numeric writes). After updating to 26.3 we re-ran a clean minimal test: the bug is unchanged.Minimal repro (clean 3-keyframe test, 26.3)Apply Drop Shadow to any clip (exactly one instance). From UXP, on "Shadow Color", write three keyframes inside executeTransaction: t+0s → pure red (1, 0, 0, 1) t+1s → pure green (0, 1, 0, 1) t+2s → pure blue (0, 0, 1, 1) (Values built by reusing the host Color object from getStartValue() and assigning components; keyframes via param.createKeyframe() → createAddKeyframeAction.) Check the three keyframes in Effect Controls with the color pick

Use the template below to provide us with information: Issue - A short description of the problem. In Text panel settings, you can and toggle on/off the "Low-confidence words," which will underline words that the transciption is not so sure about, and makes it really easy to clean up the transcript. Right now, toggling them on/off doesn't do anything. I'm not able to see any underlines, and believe me, this audio should have a lot of low-confidence words underlined. Here is the settings panel: Steps to reproduce - A numbered list of the exact steps needed to reproduce the issue. 1. Transcribe your sequence2. Go to Text setting panel 3. Toggle "Low-confidence words" on and off4. See that it doesn't underline any words Expected result - What should happen after executing the last step.Low-confidence words should be identified by being underlined Actual result -  What actually occurred after the previous step No low-con

When opening a premiere production in 26.0.2, a convert projects dialogue comes up to convert the production to a newer version. The project was created in version 26.0.2.  No project was opened in an older version and all projects correspond to that version of premiere. Upon investigating the project XMLs, the version number on all projects in production is 45. Based on some quick research, this corresponds to the project file format used by Premiere Pro 2026 (the latest version) The result of this conversion is a folder with the same name with _Pr26_V26.0.2 twice!  Why does premeire not recognize that it was created in that version?Below is an example of the folder structure.26_PRODUCTION NAME_Pr26 (original production)26_PRODUCTION NAME_Pr26_V26.0.2 (first conversion when updating)26_PRODUCTION NAME_Pr26_V26.0.2_V26.0.2 (premiere not recognizing that IS the current version and forcing a conversion to the same thing)Am I missing something here?  Any ideas on why this happened?  

Since updating to Premiere 25.6.2 last week, I immediately noticed that shuttling (playing at 2x+ speed) causes the playback audio to cut out for a short period.   To reproduce (at least on my system), specifically while playing back at normal speed, upon pressing the shuttle right hotkey to play faster, that is when it cuts out. It will also cut out if the shuttle key is pressed again while already shuttling to further speed it up.   It does NOT happen when: Beginning normal playback at normal speed, even if the 'shuttle right' key is used to start playing (pressing the shuttle key from a stopped position just plays regular speed). It's only if transitioning into true 'shuttle' speeds. It also does not happen when "maintain pitch while shuttling" is disabled   Some notes: I do not recall this happening prior to 25.6.2, and I would have noticed it because it's quite obtrustive to my workflow where I use shuttling extensively. It also happens in the 26.0 Beta I tried it in a virtual mac

  I’m experiencing a persistent issue in Premiere Pro where the  Graphics Templates → Browse search returns “No matching search results”, even when the search term clearly exists in the filenames of visible MOGRTs. Concrete example (with screenshots available): I have multiple MOGRTs installed with “LOWER” or “Lower Third” in the filename. When I type LOWER into the Graphics Templates search bar, Premiere returns “No matching search results.”This happens regardless of which location filters are enabled (Local, Libraries, etc.).Important context: This is not a recent regression.The (Essential) Graphics Templates search has never worked for me, across 5+ years of use and multiple Premiere Pro versions.Templates appear and function normally when browsing folders; only search is affected.I've included a screenshot of the local MORGT folder with the file path (in case thats the issue) -USE MAC STUDIO apple silicon but this issue has always been there for me on previous imac pros for years.

When exporting AS-11 MXFs from Windows Premiere or Media Encoder 2026 with H264/HEVC hardware accelerated encoding turned on, the exported file is presenting with reversed / broken field order when viewed in our QC suite via Iris. The issue is not visible when viewing the exports in Prem, or VLC, or in any proxies made during our post-export workflow. However it IS visible when the files have been broadcast. It is possible to get a good export directly from Prem by turning off HW encoding, but for some reason that option is greyed out in ME 2026 so we have no way of doing batch exports. We’ve had to roll back both Prem and ME to 25.2 in order to temporarily fix the situation. However this comes with it’s own set of problems as projects are not backward-compatible.

Premiere Pro 26.2.2 is hard crashing every time I attempt to upload to Frame.io directly from Premiere. Analyzed the minidump and wanted to share what I found in case others are hitting this.System: macOS, Apple Silicon (ARM64), Premiere Pro 26.2.2Repro: Initiate an upload to Frame.io via the in-app panel. Crash occurs mid-upload while encode/upload progress is reporting.What the crash dump shows:The crash is a SIGBUS (signal 10 / bus error) originating in the UXP plugin bridge. The crashing thread is the UXP JavaScript thread running the Frame.io plugin. At the time of crash, the plugin was actively handling a SequenceEncodeProgressPayload GraphQL callback, meaning the upload was in progress and the progress update triggered the fatal error. Call stack summary:__pthread_kill (libsystem_kernel)pthread_kill (libsystem_pthread)signal handler (libsystem_c)Adobe Premiere Pro [UXP/plugin bridge]Adobe Premiere Pro [encode/media subsystem]libAdobeGrowthSDK (telemetry)The Frame.io UXP plugin a

see description above

Applying Posterize Time effect says that it will just change framerate, but all my colors get completely ruined.HDR, Rec 2020, HDR footage. Lumetri Color effects applied, look fine. Only when I apply Posterize Time, it’s like it’s ALSO applying the Posterize visual effect kinda too.

Copy and paste keyboard shortcut doesn’t work on sequences in this version of premiere. Copy only works when right-clicked with mouse, and right-clicking would not work anywhere on the timeline, Cmd+v only work occasionally on clips on the timelines. When trying to copy and paste attributes or effects, only the paste in the main premiere menu works (no right click, no CMD+V)

【Summary】When a text layer has two or more strokes and is saved via Properties > My Styles > "+", the second and subsequent strokes are not stored in the saved style. Applying that style shows only the first stroke; the second one is replaced with default values (gray, 1.0, unchecked).【Steps to reproduce】1. Create a text layer.2. In Properties > Appearance > Stroke, add two strokes (e.g. White 7.0 Outer, Red 14.0 Outer).3. Click "+" in Properties > My Styles to save it as a style.4. Apply the saved style to another text layer.【Expected】Both strokes are applied.【Actual】Only the first stroke (7.0) is applied. The second stroke appears as gray 1.0 with the checkbox off.【Environment】- Premiere Pro 26.2.2 and 26.3.0 (reproduced on both)- Windows 11 Pro- Reproduced on a separate PC with a clean Premiere installation and a brand new project, so this is not environment specific.【Additional technical detail】I inspected the saved .prtextstyle file (FlatBuffers payload in StartKeyf