Bug Reports

I noticed recently, that when using H.265 footage, that Premiere will work fine for a while then suddenly start having memory issues, and eventually lock up and black screen my entire computer. Sometimes I catch it before It does, and close the program, but then when I try to reopen it, it just hangs in the background and never opens.  I tried using Encoder to convert the footage to H.264 for the problem persists. I reset preferences, cleaned cache, did a clean install, everything. The only (Temporary) fix, is to completely restart my rig, and this only helps for about about 10 min of editing. Currently, I have noticed the issue when I download AI footage from Higgsfield, and it doesn't matter if its just using the upscalers or the direct footage, the problem maintains, and it only started happening after the update. This issue is bad, as I use AI footage pretty regulary for mapping out the visuals of projects, upscaling, etc. Please Advise. System: Win 11 Pro v 10.0.261

Export renders all audio clips in work area / timeline when exporting between in to out which takes forever, even for an audio only export.My export was saying twenty mins - clipped out the two clips into a new sequence on their own and it was so fast it didn't give a time. Will this be fixed soon? v25.5 build 13Mac studio M2 Max 96Gb. Sonoma 14.7.3 (23H417)

Premiere ahora selecciona otra fuente cuando cliqueo en otra variante de fuente desde el panel de texto.Premiere pro v25.5 Osx Tahoe 26Después de la última actualización a la versión 25.5, si quiero seleccionar un fragmento del texto para poner una variante de fuente por ejemplo de normal a black, en lugar de cambiar la variante, cambia la fuente completa por otra (la que está inmediatamente arriba en la lista) 

Let me try to explain the issue the best way that i can, i like coloring my scenes individually (i color a clip, copy the lumetri color settings, paste on the next clip, and change whatever is necessary while mantaining the coloring style, i'm not a fan of adjustment layes for color grading since each clip can have different lighting and such)I started to notice if i color grade a clip, sometimes the lumetri color will get "stuck inside" the clip and i cannot remove it. My main work is videos for parties and weddings, I always make a first sequence just for selecting the clips that i will use on a video, then a second sequence for the actual video with the selected clips, music, effects and color grading, so if i accidentaly delete a clip i have my first sequence as a backup.Here's an example, i finished the main video on the second sequence, i got back to the first sequence (again, the first sequence is just the clips i selected to use, no color grading or anything) and it alread

Hey y'all, long time user, first time poster. I am having an issue with FI: Grow FX and FI: Shrink FX. Upon rendering a preview, Grow FX will be zoomed in unreasonably far, so far that all you can make out is a solid color. The inverse happens with Shrink FX, wherein the clip will become so small it does not even show. This issue can be corrected by changing any of the parameters in the Grow or Shrink effect controls, but it's a coin flip whether or not the issue returns when rendering previews. I've experimented several times and have not found any patterns - sometimes it works, sometimes it doesn't.  Thankfully, the issue has not persisted through to exporting, but I attribute that to the fact that I've chosen to export with software encoding. I don't appear to have a software encoding option for previews though, so this bug is a huge pain for reviewing videos before export.  Knowing that, I've tried reinstalling my nvidia drivers, to no avail. I've also trie

I continue having issues in PP2025 when using LUTs that on R3D footage. When using the Media Browser to import clips with In-and-out points, the preview is displayed in a very strange way. It takes forever to load, and is a very frustrating process to import footage. How can this be fixed? Attached is a screenshot of the issue and how it appears, along with a screenshot of the R3D file settings. 

Hi there!MAYDAY MAYDAY..Is anybody can tell me how to fix this probleme ? Thanks in advance

Match framing subclips back to master clips does not work if they are in separate projects in a production. Steps to recreate1. Import master clip to master clip project in a production 2. Create subclips and move to a subclips project in the production3. Create an edit in an edits project in the production & add the subclips made above4. Match frame from sequence X2  Expected behaviour:Sequence should first match to subclip, then to master clip. Observed behaviour:Subclip does not match frame to masterclip (like it does where everything is in one project). Added bonus:Make one of the subclips NOT be restricted to trim region - now the 2nd match frame matches to the start of this sub clip, regardless of actual match point.

Hi all, It's one of those days I wish Adobe had a hotline for pro users... grrrrr... So I've been working on a Premiere Productions for a long time. It has several projects and I normally have 5 or six of them simultaneously opened.  Most of them have media files and only one has the assembly cuts, which is where I spend most of my time. About 40 minutes ago I noticed that, out of the blue, the undo command was no longer working. As I had auto-save on and I was able to (apparently) "save all", I pushed through for more 10 minutes till I decided I had enough of it, saved all once again, quit the application and restarted.  I was able to reopen the Productions and all looked fine WITH THE EXCEPTION that the project with the assemblies simply didn't save AT ALL! None of the work I've done in it for the past 3 hours was saved! Strangely, all the other projects were saved normally. To make matters worse, that project wasn't autosaved either, while the others we

In Premiere Pro 24.3, the Warp Stabilizer effect is extremely slow when processing log footage with the "Auto Detect Log Video Color Space" option (ADVLCS) enabled in the Lumetro Color > Settings panel. I'm defining slow as 1/12 the speed observed when applying a fresh instance of Warp Stabilizer to the same clip with ADVLCS disabled. The log footage was shot on a Panasonic S5ii (4:2:2 10-bit LongGOP, 150Mbps) and I am actively using Quicktime ProRes proxy files (quarter frame size) when applying the Warp Stabilizer effect in both scenarios. A few quick computer specs in case they are relevant: Primary drive is 512GB SSDProject and source footage drive is external SSD connected through Thunderbolt 3 port (Crucial X9 Pro, 4TB)Cache files stored on secondary SATA platter HDIntel(R) Core(TM) i7-7820X CPU @ 3.60GHz 3.60 GHzRAM: 32.0 GB (I know... more would be good!)Windows 10 Pro Education, Version 22H2 (OS build 19045.4046)Experience Windows Feature Experience Pack 1000

I'm just working on a project and for no reason this error appears and I tried all the solutions exists. Audio Hardware, Media Cache. etc...... Error Code: -1609891835 (NOT) (1609891836)

I recently upgraded to Apple Silicon (on an M1 Mac Studio) thinking that most of the kinks have hopefully been worked out, but here's a new one for me. I'm testing with a flat (Log C) ProRes MXF from an Alexa. I place that in a timeline based on the source res, and export out a ProRes 4444 at max bit-depth with 16 selected. I bring it back into Premiere. I overlay it on top of the flat MXF... and there is a significant green tint visible. Lumetri scopes indicate the same. Thinking it might be the way Premiere is interpreting the MXF, I also tested taking an H264 clip, exporting out a ProRes 4444 of a section, and bringing that back in - lo and behold, a green shift. Now for the most interesting part - I brought the ProRes 4444 that premiere created, and the flat Alexa clip, into Davinci Resolve. I put them next to each other in a timeline and toggle between the two clips while looking at the scopes - and wouldn't you know it - no green shift. So, it looks like for some reason, Pre

Summary: The Extract function in text-based editing does not work when initiated from the Program Monitor transcript. When attempting to extract (') a selected range with in/out points marked, nothing happens except the playhead moves to the in point. The Lift function (;) works normally in the same workflow.Steps to Reproduce:Open a sequence in Premiere Pro 2025 with transcribed audioEnable "Show Program monitor transcript" in the Text panel Enable "automatically set in/out points"Select a range of text in the Program Monitor transcript (in/out points are marked)Ensure all video and audio tracks are targetedClick the Extract button (or use ' shortcut)Expected Behavior: The selected range should be removed from the timeline and the gap should close automatically (ripple delete), matching the standard Extract operation behavior in Premiere Pro.Actual Behavior: The playhead jumps to the in point, but no content is removed from the timeline. The Extract operation does not execute.Wor

I have run into a pretty concerning bug that causes my entire computer to crash randomly (Event ID:41(63)) while using either Premiere Pro/After Effects. I know it is not a problem with my computer as while running other highly intensive programs such as blender, and even multiple at a time, I do not get crashes. Nor does my computer seem to be overheating, as my temperatures (I dont know if it spikes before it crashes or something to be clear) seem to be normal. My drivers are also fully updated. It ONLY happens when using premiere pro/after effects. I am not sure as to which program is causing the issue or if its a mix of both. The steps to replicate it are unclear as everytime it has happened it has been different and unexpected but I believe it has something to do with the fact I use an AMD GPU over a NVIDIA GPU, and I understand support for AMD cards will be lesser, but this is an unacceptable bug. I am using Premiere Pro: 25.5After Effects: 25.5OS: Windows PC My mo

I found out that Adobe Premiere is not utilizing the Newly installed RTX 5060.CPU- AMD 5700XRAM- 64GBGPU- RTX 5060SSD- 2X 1TB1. There are times that Adobe Premiere 2025 use the GPU for preview and playback, when i start and stop, it will stop utilizing the GPU and shift to CPU which cause stuttering in playback.2. This Issue happen everytime, So my workflow slowsdown.3. I am Editing 4K 422 10 Bit footage at 100mbps from Sony A7siii and FX30https://drive.google.com/drive/folders/18107UBikIlNZKeHNaLHsHQsOk9uH17ct?usp=sharing Can someone help me with this?All my OS, Drivers are up to date. I attached here a video file for you to see it. 

I’m experiencing consistent export failures when trying to render my project in H.264 format. The export process causes my system memory usage to spike up to 52 GB, after which all applications crash simultaneously. Immediately after, I receive an error log report and a low memory warning, prompting me to save my project. The export then fails with error code 1609629690 or 2147483646. Steps to Reproduce:-Open project in Premiere Pro.-Go to File > Export > Media.-Confirm export settings:--Format: H.264--Output location and filename: Set properly-Click Export.-System memory maxes out, all apps crash, and export fails with the above error codes. System Info: Adobe Premiere Pro Version: 25.5 (installed 2 days ago)Operating System: Windows 11 Version 25H2 (OS Build 26300.6899)GPU Driver Version: NVIDIA 581.80CPU: AMD Ryzen 9 9950X3D (recently upgraded from Intel i7-12700K)GPU: NVIDIA GeForce RTX 2080RAM: 64 GB DDR5Motherboard: X870E AORUS PRO ICE Som additional Not

While building a project I periodically import new media. In this newest version of the software 25.5.0 build 13, when I use the feature immediately after adding something to the timeline, it is creating a hidden dialog box. At that point I cannot proceed and must kill the software with task manager.

Hello Premiere Pro community! I have a problem with adobe modifying the contrast of my .HEIC files when exporting.Here I will attach a screenshot of the original .HEIC file (because I can't upload HEIC files here) and its properties and then screenshost of the exported video files (H.264 and ProRes 4444 XQ) so you can see the difference in the color of my skin.    Now I will upload screenshots of the export settings of my H.264 video file and a screenshot from the resulting video.And here is the Apple ProRes 4444 XQ video looking different from the original photo and the H.264 video.      I have tried exporting with different HDR color spaces, but this only takes away even more contrast from my photo. I will also attach the original file, both screenshots and the H.264 video file below, but there will be no preview I think. Could you please let me know if I am doing something wrong here or if this is just a bug from Premi

When working on a sports video for a client, I keep getting these glitched frames throughout the project. It happens everytime a camera flash happens on the footage. All the frames leading up to the flash are fine, but as soon as the flash happens, the glitch shows and it ruins the video product. And this is only happening in Premiere Pro. When I view the footage outside of Priemere, no glitches. For reference, I am working on:2022 Mac Studio M1 Max (Sequoia 15.6.1)Premiere Pro Version 25.5 I have tried everything I could think of, from deleting cache file, to transcoding the footage to Apple Pro Res 422, changing the sequences frame rate. Still no solution. I've attached some photos and a recording to show the issue. Hope someone can help, as this is causing issues for my company.

I am experiencing serious performance issues in Premiere Pro 2025 during heavy editing sessions. The application becomes extremely slow, frequently freezes, and sometimes stops responding entirely. These performance problems occur even in standard workflows and make the software unstable for professional use.

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

When i tried to render a file to a specific path it automatically saved in another path with another name. 

Am revenit la versiunea 25.4.1 pentru că versiunea 25.5 mi-a dat probleme grave de performanță.La export un clip de 2 minute FullHD, fără editare complexă, îmi estima 1 oră timp de randare. Playbackul în timeline avea întreruperi constante la aceeași filmare FullHD. După downgrade la 25.4.1 totul funcționează normal. Sunt dezamăgit de timpul pierdut până am găsit că problema provine de la ultimul update.

I recently updated to version 25.4.1 of Premiere Pro, and I’m having an issue with the audio waveforms. It’s a bug that existed in previous versions, but now it’s happening a lot. The problem is that the audio waveform doesn’t generate correctly—when I look at the timeline, it shows an (incorrect) waveform, and only when I zoom in on an audio track does the correct waveform appear. How can I fix this? It’s horrible not being able to properly visualize the real audio waveform.

Premiere Pro Just Destroyed Three Weeks of Work — This Is UnforgivableI’ve been editing a professional project for nearly three weeks — countless hours of careful, detailed work — when Premiere Pro crashed without warning. And not only did it crash, it corrupted the project file in the process. No explanation. No recovery. Just the dreaded message: “The project appears to be damaged and cannot be opened.”Let me be absolutely clear: this is not a hardware issue. This happened to me before on a high-end PC, and now again on a powerful Mac. Plenty of RAM, GPU, and SSD storage. This is not the user’s fault — this is Adobe’s fault.In 2025, it is inexcusable that a software marketed as “industry standard” is still capable of corrupting entire projects without warning or protection. There is no professional justification for this kind of catastrophic failure in a program millions rely on for commercial, creative, and time-sensitive work.Adobe has known about these issues for years. Forums, Re