Bug Reports

IssueAdobe Premiere Pro freezes temporarily while bookmarking fonts from the font selection dropdown menu. Steps to Reproduce1. Open Adobe Premiere Pro and create a new project.2. Select a text layer or create a new one.3. Click on the font selection dropdown menu.4. Start typing to search for a font or scroll through the font list.5. Select a font to bookmark.  Expected ResultPremiere Pro should bookmark the font without significant freezing or lag. Actual ResultPremiere Pro freezes for a noticeable amount of time while bookmarking fonts. System Details- Adobe Premiere Pro Version: 25.2.3 (build 4)- Operating System: Windows 11 (24H2)- GPU: RTX 2060- GPU Driver Version: Studio driver v576.02

The shortcut to reset to saved layout (Shift + Opt/Alt + 0) resets the layout, but pops out the project panel into a seperate window every time. I was able to temporarily resolve this issue by creating a duplicate copy of a preset layout, however, the problem affected my custom workspaces after I shut the program down and started it back again.Clicking "Reset to saved layout" from the Window menu or from the Workspace shortcut menu does not experience the same problem (hence the bug report.)

The "Hard Limiter" Audio Effect is not applying to all Audio cuts that it is pasted to, and only applies to individual unique instances of the effect (so applying a new Limiter one by one, instead of pasting to all cuts as it used to). Version: 25.2.3Windows 11 Version 24H2How to reproduce:- Place Hard Limiter Effect on Audio- In Effect Controls, set Limiter value- Copy Effect- Paste on second Audio cut- Play, and see that the Limiter does not effect the file at all- Remove the Effect- Place a NEW Hard Limiter effect on Audio, set value, then Play, and see that the Limiter only works on a unique instance of the Effect. Previously, you could set the Effect value, then paste it to your entire timeline of audio and save yourself the editing time. Now, I'm having to manually apply it to every cut and it's very inconvenient. If this is intended, it's a backstep and a downgrade. If it's a bug, I hope that it is addressed soon. The number of issues with Creative Cloud makes me want

Ever since I moved from 2023 to 2025 I've noticed a significant loss in ripple trimming perfomance after doing a fair number of cuts. For context: I work with 20-60 minute footage and I go back and forth to better improve my cuts, and doing so in the 2025 version (2025.1) has been difficult due to this issue. On the 2023 version, as you'll notice on the recording, the cutting/trimming is basically flawless and works immediately after I press the shortcut (I apologize for the very low volume on the mic).This has to be looked at, it is the most important part of video editing for me and a lot of other editors that work for youtube creators, so either I'm doing something wrong or the program is bugged. I appreciate if anybody could recommend me something that is not moving back to the 2023 version, I'm open to test other 2024 versions, even tho the new features on 2025 are sort of important to me.

Product Version: 25.2.2OS:Windows10 Pro 22H2 Bug Description:Importing an XML file containing Essential Graphics (EG) clips into Premiere Pro causes their clip markers to become incorrectly unified/synchronized. Adding a marker to one imported EG clip results in the same marker appearing on all other EG clips from that XML. This prevents independent marker usage on EG clips after an XML roundtrip, hindering workflows релиing on clip-specific markers.Key Behaviors & Observations:Alt-dragging an EG clip to copy it can also cause marker unification, even without XML export/import.Ctrl+C/Cmd+C and Ctrl+V/Cmd+V to copy/paste EG clips initially preserves marker independence.However, after an XML file (containing these initially independent EG clips) is imported, any method of copying these imported EG clips (Alt-drag or Ctrl+C/V) then results in marker unification.This issue seems to stem from the XML import process incorrectly unifying the underlying source grap

When editing videos in Premiere Pro, the program keeps crashing.Windows 1164GB DDR5 RAM4TB SSDAsus GeForce RTX 4070TI SuperAsus RTX Prime Z790 PIntel Core i9 14900KMy computer is like this. It shuts down at least 10 times while editing. I'm fed up, I'm going crazy

This eye dropper tool does not work, if I move the program panel to second monitor. How to fix this? 

I have a clip with multiple time remapping keyframes. I want to adjust a selection of keyframes at once: Specifically, I want to select all the "first" keyframes (they are all in pairs), drag them out to make an ease, then adjust the handles so they are all eased the same. The first image shows the selection, and the second image shows what I'd like the result to be, BUT right now I have to adjust each keyframe individually, I can't manipulate all at once: I can select multiple KFs, but then when I drag to separate, it deselects all but the one KF I'm manipulating. I understand that there are temporal issues, but what I want is to just have a transform on each keyframe, which I can then manually tweak. Right now, I have to click on a KF, drag it over, adjust handles, then repeat a LOT of times.   

We developped this very useful mogrt in AE-CC2024 that gave us a pretty slick workflow, but since mid 2024, it's become useless because of the randomness of the problem. I've seen many posts on the web reporting similar problems in mogrt workflows even before CC2024, with no clear fixes. It's an AE comp, exported as a mogrt, that enables the treatment of text captions in 4 languages (English, Chinese, Japanese and Korean). It also provides color highlighting controls for 5 groups of characters and with the flip of a switch, re-scales/re-positions it all to fit in tall format. It worked fine for a few 2024.xx versions until it suddenly started showing the following problems in the native wide format:Characters will randomly show as "Regular" even though the font "under the hood" is MyFont-Bold.ttfThe problem may not appear on-screen, but will be in the exported copy (via AME or PrPro exports)Quit/relaunch, you have different characters that now show the problemCC2025 shows the same issu

Hi, I'm having an issue installing the language packs for transription in Premier Pro 23.6.8. I am unable to do this through Creative Cloud as it does not recognise the version as being installed. I need to use the older program for compatability for plug-ins. I've tried signing out of CC and specifiying the install location but this has not worked. I'm using Windows 11. Thanks.  

when I move the curser through the timeline or the source panel previewing audio I hear painful audio clipping the moment I click anywhere on the audio it happens like this:1. I wanna go to second 5:002. I click on that time3. I hear a static popping/clipping/hiss sound for a period as long as a click (tenth of a second)4. audio plays normally and this happens all the time with all of my audio, and I tested the same audio files outside of premiere and in davinci resolve and the issue isn't there so it's a premiere pro issue and it's so annoying.

I have a project file I work with weekly for a client, every week I create new reels and shorts. 3 Days ago I saved the project, now every time I open it the thing crashes.  Even auto-saved files past a certain hour crash. When I open a new project and import sequences, the new project also crashes after saving and opening again.I have uninstalled and reinstalled clean versions.I have installed older versions. I have uninstalled all 3rd party plugins.I have updated all drivers, Bios, CPU, GPU,  C++I have followed every step on thiswebsite. https://helpx.adobe.com/premiere-pro/kb/fix-premiere-pro-crash-issues.htmlI have sent hundreds of crash reports and have a few saved .dmp files I could send.  1) Version 25.2.3 2) Windows 11  

 What failed: igdkmdnd64.sysSpecs: Premiere Pro 25.2.3windows 11intel i5-12400f16gb ramintel arc b580editing on SSDMy pc is crashing consistently when editing 4K 8 bit footage in Premiere. Does not crash otherwise but is extremely disturbing to my workflow, Whilst not the strongest machine, the build should be able to handle this footage in the small timeline that it is.So far i have ensured i’m updated to the newest graphics drivers, checked my GPU temp at the time of crash (47 celsius) and reinstalled Premiere, Not sure what to try next HELP PLEASE!!!Note: i’ve seen online that igdkmdnd64.sys can typically be iGPU related, though my cpu lacks integrated graphics, mabye some correlation? just speculating as i am a novice

When i do time remapping on a nested sequence and increase the speed to more than something like 300%, it introduces black screen on the nested sequence, like the rest of the footage within the nest went missing. please fix this i have to render the nested sequence and then apply time remapping

So I had a few videos split into clips, did the editing, turned them into nested sequences, saved the file, and closed it. Now 2 days later I have reopned the file to continue the work, and find that most of my nested sequences have been split again (all except for 1), and I have no idea why/how, because I am 100% sure that's not how I saved it. I opened the last auto-save and it looks the same. To further clarify, ever single video layer should only be having one nested sequence, instead it has many, but from the looks of it those clips are still all nested, so it's not like the file reverted back to before I made the nests, it looks more like the nested sequence got split again, evenly, at the same point for all video layers. Also when I originally made the nested sequence, i changed the name, and now all those clips have that name. I also looked for the nested sequences that I originally made in the project panel, but could only find one, which I then dragged int

I am working on a project in blender. I create 1000s of still frames that i use Premiere Pro to turn into videos and add effects. I have been doing this for many years without issue. Recently, Premiere Pro has started to crash with the error message and report dialogue about 50% of the time when I try to import or export any media to the disk. If I start the project and click on videos or frames to import, it might crash. If I click on the export tab, it might crash. If manage to get to the export tab and then click to change the directory to save the exported file, it might crash. I am having to restart the application dozens of times an hour to get anything done. It has generated loads of .dmp files and I must have sent adobe a report about 50 times in the last week with the amount of error messages I've been getting. Seems related to anything that interacts with external files on the disk. The disk in question is a 2TB SSD and it has plenty of space left and has no corrupt

I've just freshly reinstalled my Mac Studio M1 with Sonoma and installed Premiere along with the latest (14.5 and the previous 14.4.1) Blackmagic Drivers, and I can not get Mecury Transmit to recognise the my BM Monitor 3G device. The device is recognised in the BM Video Desktop software, but does not show up in Premiere or After Effects. I've been through and enabled security settings where needed and restarted and because the device is present in the BM software, it would indicate a problem with the current version of Premiere/After Effects. This is the first time reinstalling this machine, but it did work with this setup previously, although I did have some misc issues editing in PP which I never did get to the bottom of... hence the reinstall!   

Some of my personal presets dissapeared when I restarded premiere pro.. But i think i found the solution.. After version update 24.5 this problem seems to appear.. Version 24.5 and before are working fine with holding the presets. This problem seems to appear by alot of people when I look at the forums.. I use all 3rd party plugins from other creators and i cant update those presets.. So hopefully they come with a solution by future updates from Premiere Pro, so that all the personal presets stay after reopening Premiere Pro.  After update version 24.5 also Bevel Edges, Convolution Kernel, Blurs and Solarizes where removed from the effects panel, maybey there is a relation between that.. 

Hi, When exporting a sequence from PP to AME - when setting 'Set Start Timecode' this only accepts Drop Frame timecode and not 25 PAL. I've set it to 09:59:55:00 within the preset - however when importing the clip back in the clip has a start timecode of 09:59:54:23 Sequence is 50i and the Preset is AVC Intra 100 25 Upper Field First Premiere 25.2.3 Build 4

I'm getting weird jumps in color in the viewer window using Lumetri for color correction.  The difference happens when you look at the frame still, versus when it's playing.  The output seems to match the playback color, so the still frame is wrong. The jump is subtle and mostly the blacks are going magenta in my particular footage.  Source clips are Prores 4444XQ 4K Quicktimes. On Mac OS Sonoma 14.7.2 Apple M2 Ultra 192 Gb Mem

After updating to Premiere Pro 2025, I noticed that my saved presets still appear, and the effects inside them are there, but all the effect settings have reset to their default values. In other words, the structure of the preset is intact, but none of the custom settings I originally saved are preserved.I’ve already re-imported the presets, reset preferences, and cleared the cache, but none of that helped. Has anyone else experienced this issue? Is there a fix or workaround for this? Any help or links to relevant discussions would be appreciated

Hello,Is there a way to prevent Premiere Pro from crashing the computer? This occurs with basic text editing in Premier Pro almost daily recently...Other open applications don't run any tasking processes simultanously. Any configuration or CPU limit on the Premier Pro or Mac settings? Premiere 2025 version 25.2.1 (Build2) Mac Os Ventura Thanks.

1.  Build a suitable media data structure on a local drive2. Copy the entire contents of that drive to LucidLink cloud storage. 3. Unmount local drive4. Open project, help Premiere find all the media again on the cloud drive.  Once all media online, save project and quit.5. Reopen project.  Premiere has forgotten where all the media is and everything needs to be relinked again.  For each files location, Premiere still suggests the old local drive. Steps 4 and 5 happen every single day.   How can I get Premiere to properly remember all media is now in a new location - in the Link window, it's still asking for the original drive name, and it's been a week now of work and saving this project since that drive was even in use.   I've also seen this problem when moving just to a new local drive.

Bug: When I play my media, playhead refuses to move, when I pause the media, playhead lags to where its supposed to be. I can only really catch it moving when its impossibily zoomed in. Sometimes it will lag while moving when the project has been open long enough.It's been going on for about a year now I'm tired of putting up with it. I've tried clearing my media cache, reseting my saved layout, shift alt when launching, nothing works. After trouble shooting for months I've come to realize when the effect controls are open, the playhead ceases to move whatsoever.

Subject: Intermittent Voice-over Recording Failure in Premiere Pro (Version 24 and above)Hello,I am experiencing a critical issue with voice-over recording in Premiere Pro.The issue:The voice-over recording intermittently fails. It sometimes records audio normally, and other times, the recorded audio file has a duration of 0 seconds.This occurs regardless of the audio device used (including professional audio interfaces, webcam microphones, and USB microphones).The problem persists consistently in Premiere Pro versions higher than 24.Troubleshooting performed:Reinstalled Premiere Pro completely.Tested various audio hardware including Steinberg UR22C audio interface, webcam microphone, and USB microphones.Changed USB connection methods (direct connection, USB hubs, etc.).Verified settings including sample rate (48000Hz), buffer size (512 samples), and audio latency.Temporary solution:Downgrading Premiere Pro to version 24 completely resolves the issue, confirming it is a software-relate