Bug Reports

I tried using premiere 2026 and it won’t open without closing or crashing. I’m not even trying to open a specific project but it closes on the home page. I’ve updated my graphics driver and even tried re-installing the app but neither of those worked. Any suggestions?Running on a windows with a Intel Core Ultra 9 and GeForce RTX 5080 and a z890 Aorus Pro Ice Motherboard. I’ve included a video in case it provides clarity.

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

Subject: Bug Report — Custom Effect Presets Not Appearing in Effects Panel (Premiere Pro 26.00) Hello Adobe Support / Premiere Pro Product Team, I would like to report a bug in Adobe Premiere Pro version **26.00** related to saving and displaying custom effect presets. **Issue Summary**When I save a custom effect preset (via Effect Controls → right-click → “Save Preset”), Premiere Pro successfully generates the preset file (e.g., “Effect Presets and Custom Items.prfpset”), but the preset **does not appear in the Effects panel** under “Presets.”  In some cases, the folder appears briefly but disappears when the Effects panel is closed and reopened. The preset never stays visible even after restarting the application. **Steps to Reproduce**1. Open Adobe Premiere Pro 26.00.2. Apply motion/keyframe adjustments to a clip.3. Open **Effect Controls**.4. Right-click the effect group (e.g., Motion / Transform) and select **Save Preset…**.5. Name the preset and click OK.6. Open the **Effects** p

Use the template below to provide us with information: Issue – Aucune image affichée sur arrêt video. Steps to reproduce – quelque soit l’endroit de la vidéo, si je fais un arrêt sur image, l’écran est noir.  Expected result – normalement dans la fenêtre Edition on voit l’image. Actual result – voir la video en PJ.  Adobe Premiere Pro version – 26.0.2 (build 2) Operating system – Apple M2 Ultra Studio 26.3.1 (a) Video format – issue is related to video playback 3488 × 2616HEVC. Comparative information helps us understand more about when the issue occurs:  All projects  avec la nouvelle version j’en profite pour dire que la langue est passée en Anglais sur les menus   

Have Premiere transcribe a clip and then make cuts manually. If the cut is close to a word at the end or beginning of a clip then sometimes it will remove that word from the transcription even though I can still hear the full word clearly.This has only been a problem recently and the transcriptions were nearly perfect before the past few updates.If this sensitivity is intentional then it should be fixed because it’s important in short form content to leave very little dead space between sentences/clips

Detailed Bug ReportSystem Environment: Device: HP OMEN 16-ah0xxx (2026 Model) CPU: Intel Core Ultra 9 275HX (Arrow Lake Architecture) GPU: NVIDIA GeForce RTX 5080 Laptop GPU (16GB VRAM) RAM: 64GB DDR5 (5600MHz) OS: Windows 11 Home Single Language (Build 26200.8246) Display Setup: Internal 165Hz display + External ASUS VG27AQL1A via HDMI (1440p @ 144Hz) The Issue: In Premiere Pro v26.2, clicking or hovering over any item on the top menu bar (File, Edit, Clip, Sequence, etc.) causes a significant UI hang/freeze lasting 2 to 5 seconds. This issue is most severe when an external high-refresh-rate monitor is connected.Observations & Technical Data: Monitoring via Task Manager shows that during the menu click, GPU 0 (Intel Integrated Graphics) spikes to 40-50% utilization, while GPU 1 (RTX 5080) remains at 1-2%. It appears that the UI rendering thread is being incorrectly routed through the iGPU instead of the dGPU, creating a bottleneck on the new Intel Ultra 9 architecture.

We work in broadcast TV and our source material is recorded and broadcasted in 1920x1080 50i (interlaced).Version 26 is not treating interlaced video the same as previous versions (25.xx)Issue: Interlaced footage not playing back correctly when speed has been changed Steps to Reproduce: Right click on shot and change speed Expected Result: Smooth looking speed up shot (works fine in v25) see attached Actual Result: Combing and ghosting – jerky playback in V26, see attached Premiere Version: 26.0.2 Operating System: Windows 11 Enterprise, Version 25H2, OS Build 26200.8037 GPU Driver (Windows only): 31.0.101.5522Attached is the same frame in both versions.V26 is not playable quality wise.We cannot upgrade our systems because for this. 

Hello,I would like to report what appears to be an issue with XML exported from Adobe Premiere Pro. Environment Adobe Premiere Pro 26.0.2 DaVinci Resolve 20.3.2 I found a problem related to overlap / Cross Dissolve transitions in XML exported from Premiere. When a timeline containing OL / Cross Dissolve transitions is exported from Premiere as XML and then imported into DaVinci Resolve, the transitions appear visually in the timeline, but during actual playback they are not applied correctly and behave like simple cuts. After comparing the Premiere-exported XML with a Resolve-exported XML of the same edit, I found the following transition parameters in the Premiere XML:<startratio>0</startratio><endratio>0</endratio>If I manually change the XML to:<startratio>0</startratio><endratio>1</endratio> the overlap / dissolve works correctly in Resolve. From what I understand, the original Premiere values may still be technically valid as XML d

Premiere 26.2.0 build 65 Since the update, I've been experiencing instability and slowdown issues in the interface.

I am working on a PC with no internet and the welcome screen that shows the recent opened projects shows empty all the time!Check attachments.Why is that???I am on Windows 10 and Adobe Premiere 2026.2  

From time to time, practically with every project I'm still getting these video artifacts in the programm monitor. I know there was an issue with NVidia drivers, but so much time passed, and there were bugfixes confirmed in the drivers release notes, but I'm still having this issue in Premiere Pro 24.6.1 build 2.With any footage at random moments. I'm on Nvidia Studio driver 561.09 from Sep 7.Is that NVidia again or is it still Premiere Pro to blame? I know I can reset my video drivers with the Ctrl+Shift+Windows+B combination, but in the last project I had to use it 12 times, because the adtifacts reappeared.Will this ever be fixed? Look here, people are still having this issue: https://www.reddit.com/r/premiere/comments/1fre1mk/clip_thumbnail_preview_glitching_on_monitor/

Please fix this major issue: Every time I set my media cache files and media cache database, when I close and re-open Premiere, it defaults back to internal. My external drive is always online and so Premiere should see it but it is not.  This causes major slow-downs on my system as going to internal drive can’t keep up while running the software from the same drive. Result: very sluggish playback.Thanks for looking into this.

Gostaria de relatar um problema recorrente que venho enfrentando no Premiere Pro em relação ao gerenciamento de cores, especialmente ao trabalhar com arquivos gravados em S-Log3 / S-Gamut3.Cine.Ao utilizar a conversão automática do Premiere (tone mapping com preservação de matiz), o resultado apresenta cores bastante imprecisas, principalmente nos realces e nos tons de pele. Em situações de iluminação mais complexa, como pistas de dança ou ambientes com luzes coloridas, o problema se intensifica significativamente, gerando aberrações visuais indesejadas.Ao alterar o método de mapeamento para “Canal”, há uma melhora perceptível na imagem. No entanto, essa configuração precisa ser ajustada manualmente clip por clip, o que torna o fluxo de trabalho inviável em projetos maiores. Não há uma forma clara de aplicar essa alteração globalmente em todo o projeto ou sequência.Uma alternativa encontrada foi trabalhar com sequências em ACES, o que resolve parte do problema. Porém, essa abordagem nã

Premier pro is working very differently in multi and single monitor setup. Premier tends to freeze every time i switch suddenly from anything, any tab / window to another. it also pickes up the colour incorrectly from the second screen. it get's the position all wrong.

The “Export Frame” function shifts the gamma of the frame before exporting, making it useless for making mattes or extending the frame in a Photoshop roundtrip workflow.It should be very easy to click “Export Frame,” open it up in Photoshop and make adjustments, and then have an easy matte that can be applied with the new masking tool.However, as shown in the example below, the Export Frame function applies some kind of gamma shift, rendering this otherwise extremely convenient workflow completely useless.Right side is original frame, left side is a PNG from the Export Frame function simply re-imported and laid on top.I’ve already tried changing the “override color space” in interpret footage to every conceivable setting that could make sense. None of them make the frame match the original footage, so I have no idea what transform Premiere is applying to these exports. 

Posted in another community, reposting here.  In Premiere 26, there seems to be a bug with the drop shadow.   I made graphic, I used the new Object Mask tool (which works great by the way) to make a stat box pop out.  Moved it to the opacity section so I can have it get larger. It was white on white so I wanted to add a drop shadow.  When I do that, no shadow comes up even with opacity all the way up, distance, etc.  When you click to show shadow only, it’s there.   This is the top layer of 3 on a timeline.  I got advice from another editor to try nesting.   That worked, but when I exported the entire effect was off in the export.    

When using “flip horizontal” effect on a clip in a sequence, the object mask tool detects the object but masks it as if the clip has NOT been flipped. You can see in the image it’s masking correctly, but since the footage has been flipped, it’s showing the mask from the pre-flipped footage. 

TEST IN PROJECTSIn the video linked I try to show when this bug happens and when not it seems to me that is something to do with the masks folders there created or with the new rotoscopie system. I’ve tested previously the ruler and box out preview but it dind’t solve either. Premiere is updated 26.0.1. @Ann Bens ​@Ron Rigler ​@Dani_V. Processador    Intel(R) Core(TM) i7-9700KF CPU @ 3.60GHz   3.60 GHzRAM instalada    16,0 GBArmazenamento    447 GB SSD SSD 480GB, 1.82 TB SSD WD Green 2.5 2TB, 932 GB SSD KINGSTON SNV2S1000GPlaca de vídeo    NVIDIA GeForce GTX 1660 (6 GB)ID do dispositivo    78351133-11F7-4BE0-905C-26A65D630A79ID do Produto    00330-80000-00000-AA527Tipo de sistema    Sistema operacional de 64 bits, processador baseado em x64Edição    Windows 10 ProVersão    22H2Instalado em    ‎27/‎04/‎2021Build SO    19045.6466

Hi, I have the latest Pr 25.5.0 on Windows 11.Everytime I open any project file, Pr starts "relinking the media files" again, and it takes ages...My assets are on very fast external SSD's, also my Cache designated SSD is fast and external.I've been working this way since a year now and it was blazing fast.But now it all stopped, I think with the newest Pr version.No idea what happened... Jan

Issue: On Render, click Send to Media Encoder and bug layout preset. Steps to Reproduce: I have an preset layout configured in 2 screen visualization, where i see project, effects and pgm on left screen and the sequence, lumetri and proprieties on right screen. I Export by Crtl+M the sequence that contain CC, videos and audios, clickin on Export to Media Encoder… Later this when I go back to the Premiere, I don’t have the right screen configuration, not anymore, but still on my preset layout selected. I need to click on another preset, and later go back again to preset to “reset” the configs again. Expected Result: Everything like the same way that was after render. Actual Result: bug preset and continue select, but without the right screen. Screen Recording: left screen bug right screen bug​​​​​​ Premiere Version: 26.0.2 Operating System: Win11. GPU Driver (Windows only): Intel(R) Xeon(R) w5-2455X (3.19 GHz). NVIDIA RTX 4000 Ada Generation (20 GB). Video Format: XDCAMHD 50 NTSC (422)

In Premiere Pro 26.0.0, several dropdown-menus are occassionally empty. Here’s a recording of the Project manager:The Dropdown-menu only populates when pressing Ctrl+Shift+Win+B to reset the Graphics driver. The populated menu only lasts for one click, then it is empty again. Empty dropdowns are found all across Premiere, Effects Panel, Options, everywhere. -------------------------------------------------------------------Windows 11 25H2, Build 26200.7462Nividia RTX 4090, Studio Driver 591.74Single 4K MonitorAMD Threadripper 3970X, 128 GB RAMPremiere Pro 26.0.0

Hi, I'm running Premiere and Media Encoder Version 24.3.0 on Windows 11. I'm having a strange issue where if a Sequence in Premiere has been renamed at any point (for example 'Amazing_Edit_V001' to 'Amazing_Edit_V002', whenever I go to export that sequence using Media Encoder, it sets the default Output Filename to the previous sequence name,  'Amazing_Edit_V001'. Regardless of whether or not I shut down all the programs or even restart my computer after renaming the sequence. It was always inherit the original sequence name. This will also happen if then rename the sequence again to 'Amazing_Edit_V003', it will still maintain the original 'V001' filename when sent to Media Encoder. I should specify that this only applies to the 'Output File' filename. It correctly recognises the the sequence name as the source name on the left.

After multiple TrackItem.move() calls on a duplicated sequence, the           ▎ sequence's display and selection state become desynced from the data model:   ▎ clips play correctly and report correct start/end values, but the timeline    ▎ draws ghost clips and Edit > Select All only finds a subset. Cutting and   ▎ pasting the affected clips fully resyncs the state.Steps to reproduce                                          1. Open a Premiere project with one source sequence whose video timebase        reports as 16 fps (a Microsoft Teams MP4 export reproduces this; happy to  attach a sample if useful).                                                     2. Run a CEP/ExtendScript that:                               - calls sourceSequence.clone(),                                                 - razors the duplicate at multiple time boundaries via                        qe.project...getVideoTrackAt(i).razor(timecode),                                  - removes clips outside the kept

We tried every setting, reset, empty cache, re-install etc.  And it still only imports audio only on growing file.   It only imports the video once the growing video is wrapped. We had to revert back to 26.0.2 (build 2) version to make this work for us again.(it was a ProRes 422 Proxy .mov file if that info is helpful).Would love this to get fixed for the next version.  Cheers!

System Specifications:Premiere Version: 26.2.0 (Beta) OS: Microsoft Windows 11 Pro CPU: Intel(R) Core(TM) i7-14700K GPU: NVIDIA GeForce RTX 5070 (Secondary: Intel UHD Graphics 770) RAM: 32 GBIssue 1: Program Monitor "Fit" Scaling Glitch When I import a 4K video (or any resolution video) and set the Program Monitor scale to “Fit”, it does not display correctly. As soon as I play the timeline, the preview scaling breaks and glitches.Steps to Reproduce Issue 1:Import a video into a sequence. Set the Program Monitor zoom level to “Fit”. Play the timeline. Observe the scaling glitch/distortion in the preview monitor.Issue 2: Lumetri Color Panel UI Lag The Lumetri Color panel sliders experience noticeable lag and stuttering when adjusting parameters by moving the mouse up and down.Steps to Reproduce Issue 2:Open the Lumetri Color panel. Click and drag to adjust any of the color sliders (e.g., Exposure, Contrast). Observe that the UI stutters and the adjustment does not track smoothly with th