Bug Reports

Were still having a lot of issues when exporting h.265 footage from DJI drones. First saw this issue in 2018, and I am still experiencing it in 2025. Often in an exported video, the h.265 drone shots will appear as a frozen still while the rest of the video is normal. This issue is fixed termporarily if I clear all my cache (Full clear with reset) and export again. This issue is still present since I first saw it in 2018, Its a bit ridiculous that we're still seeing this issue. I switched to h.264 on my drones in order to circumvent it, but 7 years later this bug still is not fixed. Premiere should be able to handle h.265 footage flawlessly by now. Adobe please fix this issue it has been going on for too too long. You cannot expect us to do a full wipe of our media cache at the start of every single session in order to circumvent this issue. 7 years, it has been 7 years, please do not let it go on to 8 years that we have to live with this.  Many forum posts offer home made fi

Since upgrading to PP2026 any export, even a light H264 video is throttling my GPU and overloading the thermals causing my computer to shut down within seconds of clicking export. Completely unusable. Have tried all sorts of workarounds including software rendering and media encoder, nothing helps. Will start my next project in PP2025 until this is fixed.System:iMac Pro 2017 2.3ghz 18-core, Radeon Pro Vegas 64 16GB, 128GB Memory, running Sequoia 15.7.9

Say i have 2 timeline tabs open, and i click form Edit to Selects - Often, but not always, premiere will act as if i have the mouse button pressed down and draw a huge marquee rectangle as i move my mouse, and it will keep acting like this until i click the mouse a couple of times to sort of unstick it.  This has happened on and off for at least the past 3 years. Im not sure if it happens to anyone else, but i have  experience it on numerous different machines/premiere versions  so its not a specific version of issues with my specific mac.  

Premiere 2026 is freezing each time I make changes: an effect, the size, add text - everything! The Play button is freezing too. The changes are not visible after rendering. And not I'm not able to use an earlier version to finish the project.

I have a suspected bug that is making the Audio Track Mixer default to Touch mode, instead of Read.This is troublesome because if a track is temporarily muted, a mute keyframe is added to the timeline. This requires navigating through the keyframe dropdown on each audio track, finding the track keyframe option, and finding and deleting all the mute keyframes.If I have the mixer pabel open in my workspace, I can watch it switch back to Touch any time I click anywhere outside of Premiere, then back into the mixer panel. The default should be Read, but no matter how many times I reset it, save my project, and save my workspace, I encounter the problem.Premiere Pro v. 23.2.0 (Build 69)Apple M1 2020 Mac Mini, 16gb RAMMacOS Monterey, 12.3.1External USB-C SSD drives

As the title states, when Live Streaming my edit with the Mercury Playback going to the Black Magic Streaming Encoder 4k, the image tears on the the live stream. Locally evrything is fine, but there is a weird handshake issue with the BMD Streaming Encoder and Premiere Pro.I tested the same setup with Davinci Resolve and everything worked flawlessly. I then tested the BMD Streaming Encoder 4k with my laptop and Premiere and the image tearing issue still persisted. The only quasi resolution was to force VSync in the nvidia control panel for premiere pro, but that caused other issues like screen blips on the live stream during scene changes.My timeline was at 23.98 for one project and 24 for another. I had issues with both. The BMD Streaming Encoder did match the timeline timebase of 23.98 or 24. When changing the BMD Streaming Encoder to 60hz, the horizontal image tering went away, but then playback juddered on the live stream because of the mismatch of timebase. I do not have this issu

Issue: Premiere Pro crashes when opening the Graphics tab of the Text panel (Window > Text > Graphics) if a graphic/text layer contains 3 or more nested subgroups, each with its own "Transform" effect applied and enabled. The crash is deterministic and tied specifically to the number of simultaneously enabled Transform effects within nested groups on the same layer — not to the project file itself.Steps to Reproduce:Create a graphic/text layer with 3 nested subgroups, each containing one text element with a "Transform" effect applied to the group. With all 3 Transform effects disabled, open the Text panel > Graphics tab — no crash. Enable 1 of the 3 Transform effects — no crash. Enable a 2nd Transform effect (2 of 3 active) — no crash. Enable the 3rd Transform effect (3 of 3 active) — Premiere Pro crashes immediately.Expected Result: The Graphics tab should open normally regardless of how many Transform effects are enabled within nested groups.This is a workflow I've used exte

Just something that could catch people out. I was working on a project and was setting up my hardware for Protools which I was going to open once exporting a reference copy from Premiere.I plugged in (device is off) a USB external mixer which is used for Protools. Initially there was no signs of a issue until I hit the spacebar, interestingly the play-stop icon was toggling but the actual video and timeline wasn't playing.No errors or issues were displayed, and I could manually scroll through the timeline including using the arrow keys, but actual playback wasn't playing.When I disconnected the USB cable from the mixer it started to play normally again.An error code or some sort of user prompt should display to alert user of the potential conflict in play back engines/hardware.

 I get this error as in the title...what is happening with this latest version 26.3 when the same project was opened by previous versions without any problems.....and why does relinking take so long in the last version 26.3...I lose the will to work in Pp because of relinking...I can easily cook lunch during that time ;-) … My files are in this format and opened quite normally in previous versions.… Video ID                                       : 1 Format                                   : HEVC Format/Info                              : High Efficiency Video Coding Format profile                           : Main 10@L5.2@High Codec ID                                 : hvc1 Codec ID/Info                            : High Efficiency Video Coding Duration                                 : 5 min 15 s Bit rate                                 : 192 Mb/s Width                                    : 3 840 pixels Height                                   : 2 160 pixels Display aspect ratio       

SummaryPremiere Pro (26.0.1.3, Windows 11 24H2, build 10.0.26100.8655) intermittently freezes completely ("Not Responding") when opening any Open/Save/Browse dialog — including Save As, Import, and the Scratch Disks "Browse" folder picker. The freeze is a genuine hard hang (Windows logs it as an Application Hang, "Top level window is idle"), not a cosmetic or offscreen-window issue. Two independent crash dumps show the identical stuck call stack. EnvironmentPremiere Pro version: 26.0.1.3 (Premiere Pro 2026) OS: Windows 11, version 24H2, build 10.0.26100.8655 RAM: 64 GB GPU driver: NVIDIA (nvwgf2umx/nvcuda64 present in dumps)SymptomPremiere becomes fully unresponsive. Clicking anywhere produces the Windows system "ding" (rejected input on a blocked modal). Occurs after a variable amount of session activity — anywhere from ~30 minutes to ~3 hours. Not tied to a fixed elapsed time. Only ever triggered by opening a common file/folder dialog: File > Save As File > Import Project Set

I recently started to use one of Premiere's newest features which allows you to upload to TikTok from the Adobe application. I love using this to upload, but it doesn't seem to work when I want to export a video as a draft. I don't know why. I tried uploading a MP4 and MOV version but neither appeared in my TikTok drafts. Is there a feature I have to enable to allow TikTok to accept these drafts or for Adobe Premiere to have access to my drafts?

i have tried fixing this by 1-re-transcribing, the same irrelevent result.2-uninstalling and installing premiere pro, which fixed the issue for a few days, but again this issue came back. please fix this ASAP, as i have my deadlines, and paying for adobe and getting this doesnt seem to be worth it. i have also tried transcribing my video in adobe podcast, just to check if there is any issue with my video file, and it transcribed perfectly, proving that my video is completely fine and there is problem in adobe text to speech or something in premiere pro.

Service is scummy, and pays off schools to force children to use their service. borderline predatory. barely functions, runs like garbage, glitches constantly, has random pop ups. Plz Fix

Hey guys, need some help. I'm editing a podcast in Premiere Pro and running into a weird export issue.Everything looks and sounds fine in the preview, but after I export, the intro comes out glitchy. Sometimes the voice just doesn't come through properly, and the background music becomes way too loud like it wasn't mixed that way at all. This has happened 3 times now on different exports.Tried clearing my media cache and rendering audio before export, but still facing it. Anyone else dealt with this? Would really appreciate any pointers.

It shows not responding every 3,4 minutes or if u go to workspace pr any settings like project memory Or any of these settings 

This workflow has been broken for a long time and I would really love to fix this one. I know this used to be on uservoice but I can't find the old bug.  Steps: 1. Set sequence preview file to "Apple ProRes 422HQ" or whatever your favorite is. 2. Render Sequence to full green.3. Go to Export, Select an H.264 preset, check "use previews"4. Watch as PrPro doesn't acess a single preview on disk and instead renders the whole timeline from scratch.  From my current example I have a .png sequence from blender than I've rendered to green in the timeline. Export->H.264, use previews checked... Look at windows resource monitor, why is premiere chewing up PNGs when it should just be referencing the preview files I JUST RENDERED. .aecache files being acessed for no reason. .png sequence being read. WHY.     

Summary:Home / start screen panel minimum height collapses to a ~1–2 pt “sliver” when the main project window is reduced to a thin title-bar strip.  Product Adobe Premiere Pro (macOS), recent 26.x builds.Steps to reproduce:Open a project so the main edit / project window is visible. Manually resize the main project window height as small as Premiere allows (title-bar / thin strip). Open Home (Home button / start screen) so the Home panel appears as a floating window. Observe Home’s height.Expected:Home’s minimum height should be at least the height of Home’s own top icon / header chrome, regardless of how short the main project window is.Actual:Home often opens as an extremely thin strip (~1–2 pt), effectively unusable, until the main window is made taller.Why this matters macOS Accessibility clients (and power users) can resize Premiere windows shorter than typical AppKit minimums because Premiere allows near-zero content height. That is excellent for workspace management.Home’s min-h

After updating to Premiere Pro 26.3, existing sequences no longer read previous resize settings correctly. Any resize made through the main Scale parameter is broken because the second scale value, Scale Width, is always shown as 100% on previously resized clips. As a result, old framing and resize adjustments are not preserved and have to be fixed manually.

Whenever I try to send anything to media encoder without doing it through the export menue it exports the entire timeline. If I use the shortcut ALT+SHIFT+M or FILE>EXPORT>SEND TO ADOBE MEDIA ENCODER my in and out points will be ignored. The Export Range is set to SOURCE IN/OUT. I've had this issue a couple of times in the last year and can't figure out the cause of it. 

Description:In previous versions of Premiere Pro (such as 2024), using a custom shortcut assigned to the “Send to Adobe Media Encoder” command respected the In and Out points set on the timeline. However, in Premiere Pro 2025, this behavior has changed.Now, when I use that shortcut, Premiere sends the entire work area to Media Encoder — even if the work area is disabled — and completely ignores the In and Out points. This breaks a key part of my workflow, where I quickly mark In/Out and send just that range to export.Currently, I’m forced to use the manual export dialog (Ctrl+M) to ensure the In/Out range is respected, which adds unnecessary steps.Steps to reproduce:Mark In (I) and Out (O) points on a sequence.Use a custom shortcut assigned to “Send to Adobe Media Encoder.”Media Encoder opens with the work area range, ignoring the In/Out points.Expected behavior:The export should respect the In/Out points marked in the sequence — as it did in Premiere Pro 2024.System info:Premiere Pro

I'm having a persistent issue with audio waveforms not generating in Premiere Pro when working with Canon C70 MXF footage.The video itself loads and plays normally, and the audio plays correctly, but the audio clips in the timeline remain completely blank with no waveforms.A few details:Canon C70 footage 4K 10-bit MXF files Original media is stored on an external Seagate HDD Premiere's Media Cache Files are stored on my Mac's internal SSD Automatic audio waveform generation is enabled "Show Audio Waveform" is enabled in the timeline There is plenty of available space for the media cache Premiere shows no background activity for "Generating Peak Files" or "Conforming Audio" I've deleted all media cache files and allowed Premiere to rebuild them, but the same issue continues I've restarted Premiere and reopened the project multiple times Video thumbnails/playback load normally; it's specifically the audio waveforms that won't generateAt first I thought the external HDD might simply be ma

Just like it says, doesn't matter what I do or how many times I re-transcribe or convert to static transcript or whatever it will transcribe everything perfectly just ignoring filler words so they cannot be selected despite clearly being in the audio just not the transcription. I feel like the algorithm being used is already ignoring then when transcribing but then is leaving them out in the script. Premiere Pro 26.2.2 (Build 3)

Once you select an element that has enough parameters to scroll, scrollbar stays always in the same position and is always visible even when there is nothing to scroll. The behaviour also exists even if nothing is selected. When nothing’s selected. When an adjustment layes’s selected and it doesn’t have enough parameters to scroll.Scrollbar is always visible but it starts small and not that noticable if you don’t select a layer that has enough parameters to scroll down. But once that layer is selected, it’s more noticable. Also this is not a simple visual bug, it block last keyframe’s curve handle to dissappear because of that extra space. (Even though it shouldn’t happen with scrollbar anyways but i guess that’s an another bug.)26.0.2 & 26.3.2 side by side.System info    Application: Premiere Pro v26.3.2    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24     GPU: Rtx 3060 Ti  Nvidia Studio Driver ver. 610.88

I had to reinstall Windows due to a freak power outage that messed up my computer from booting. Luckily Windows made a backup of my old files, so after reinstalling Premiere Pro I copy-pasted my old MOGRTs into my new Adobe’s “Motion Graphics” folder. But some of the MOGRTs don’t show up in the “Graphics Templates” window in Premiere.If I use the “Install Motion Graphics template” button to re-add the mogrt, Premiere says it’s a duplicate of a mogrt they already have. But if I delete it from the Template folder, then try to add it back through the same install button, I get a different error saying the mogrt is incompatible with Premiere and I need to update Premiere to it’s latest version. Just one problem: I’m already on the latest version of Premiere. And I originally made these templates years ago on older versions of Premiere so it doesn’t make sense that my current 2026 version isn’t current enough to import them.I followed old forum posts advice and tried installing older versio

Double-clicking on video itself on Program Monitor both selects the video on the timeline and enables Direct Manipulation for it. However, In all 2026 versions (Including 26.0) it ignores the linked audio for it and behaves as if ‘Linked Selection’ is disabled. This is a regression going from Pr 2025 (25.6) to Pr 2026 (26.0) also includes 27.0 Beta.Premiere Pro 2025 (25.6.6)Premiere 2026 (26.3.2)This is not a workflow breaking bug by any means, but will cause annoyance if user wants adjust their position and trim the same clip. (Will require extra clicks everytime.) System info    Application: Premiere Pro v26.3.2    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24     GPU: Rtx 3060 Ti  Nvidia Studio Driver ver. 610.88