Bug Reports

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

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.

Premiere Pro v26.3Apple M4 ProMacOS TahoeBBC corporate environment - This requires a fix before BBC can move en masse from v25 to v26.Legacy AE-authored MOGRTs that have worked for years on both Windows and macOS are rendering incorrectly in Premiere Pro 26.3 on macOS. The same MOGRTs continue to work correctly on Windows. This has been tested across several Macs and the same issue is found on all of them. If the generated .aegraphic is revealed in Finder and imported directly into Premiere, the graphic renders correctly (but of course the fields are not editable). MOGRT should render identically to the underlying .aegraphic but does not.MOGRT displays incorrect imagery. One template displays colour bars where background imagery should appear. Another template displays a solid colour matching a Fill-effect colour elsewhere in the composition (see screenshot below).Tested and ruled out:- Background MOV asset- File path length- Filename length- MOGRT export method (Library and local)- Lu

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.

* Issue:The Frame.io V4 panel fails to load its content and shows "Connection Error".The panel authenticates successfully and renders its shell (Sequences / Browse tabs),but the body never loads. Evidence points to the UXP network stack, not toconnectivity or the CDN.* Steps to Reproduce:1. Open Premiere Pro on macOS (Apple Silicon).2. Go to Window > Frame.io > Frame.io V4 Comments.3. The panel loads its header and tabs.4. The content area stays blank, then shows "Connection Error — Unable to load   Frame.io. Please check your internet connection and try again."5. Clicking "Reload" reproduces the same result every time.* Expected Result:The panel loads my Frame.io V4 workspaces, projects and assets.* Actual Result:"Connection Error" with:  Error: The operation couldn't be completed. (NSURLErrorDomain error -999.) (-999)  Panel version: frameio-uxp_v1.0.27Inspecting the panel (right-click > Inspect Element) shows:- Successful preconnects to https://api.frame.io/, https://pictur

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)

I am experiencing a critical issue with Adobe Premiere Pro 26.0.1 on Mac M5. The speech-to-text transcription feature produces entirely inaccurate results. Even with very clear audio, the transcript does not reflect what is said in the video. For a 2-minute video, the transcription output is completely wrong and unusable. Audio files and everything else are the right ones and there is nothing wrong with them, double checked;)

Approximately every other edit, the application becomes unresponsive for 30 seconds to a minute. During this time:The UI freezes completely Playback may continue, but I cannot stop or interact with it Menu interactions are extremely delayed or unresponsive The system becomes partially unresponsive (e.g., Alt+Tab does not work until Premiere responds again)This issue also occurs when pressing play, and when opening menus.The problem began suddenly without any known changes to my workflow or system configuration. It occurs across all projects.Troubleshooting attempts:Updated GPU drivers Cleared media cache multiple times (both “clear unused” and “clear all”) Tested editing from different drives (including internal and external storage)None of these steps resolved the issue.This behavior is severely impacting usability and makes editing extremely frustrating. Windows 11 25H2 (26200.8246)Premiere Pro v26.2.0 Build 65Gigabyte AORUS 15P XD-Intel i7-11800H-16GB DDR4-3200-GeForce RTX 3070 Mobi

If you record footage in obs that contains multiple audio tracks and then import that footage into obs, all audio channels but the first one will be offset by exactly 1 frame. This issue does not occur in other editing software and only occurs within adobe premiere pro 26.3.0 (Build 93). Audio remains synced but this causes issues when creating cuts or snapping footage together, as the 1 frame difference will cause clips to not snap together properly. Zoom in of the clip in Premiere Pro, 1 frame of audio is missing. Audio is still synced.Same clip in Davinci Resolve, no frame of audio missing, audio is still synced. 

【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

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.

[System Specs] CPU: AMD Ryzen 9 9950X3D GPU: NVIDIA RTX 5070 Ti (Latest Studio Driver) RAM: 64GB OS: Windows 11 Display Setup (3 Monitors Total): Main Monitor + Secondary Monitor (24-inch) + Tertiary Tablet Monitor (Xiaoxin Pad 12.7 via SuperDisplay app). [Symptoms] While editing in Premiere Pro, the UI overlays in the Program Monitor randomly disappear. When selecting text, the blue highlight background does not show up. When an object/text is selected, the transform bounding box (scale/rotation handles) is completely invisible. The elements are still active and clickable. I can still blindly click the corners to scale or type to edit text, but I just can't see the UI guides. Important context: The Program Monitor is ALWAYS on the Main Monitor (directly connected to the GPU). The other two secondary monitors (including the SuperDisplay tablet) are only used for panels like Effect Controls or Timeline. Restarting Premiere Pro temporarily fixes the issue, but it keeps ha