Bug Reports

On an M3 MacBook Pro, Premiere 2025. macOS Sequoia 15The window that opens after clicking "Locate" on the Link Media window is mostly empty space, unable to be expanded/adjusted, and very difficult to navigate. When working on multiple projects, starting a new project, handling media, etc, this window is frequently used, and is very annoying to use like this when handling hundreds of files:  

When adjusting the size of the Program Monitor panel in Premiere, the software almost always freezes, causes my screen to go black for a few seconds, and then comes back with the Program Monitor displaying a completely black, white or otherwise glitched visual. Premiere has to be restarted to fix this glitch. Often Premiere will crash or have to quit when this occurs, and there are occasional crashes when going to the export window.Suspected to be a GPU/driver issue, though rolling back to older drivers and older versions of Premiere has not resolved this.OS: Windows 11Premiere version: 26.0GPU: Intel (R) Arc(TM) 140V GPU (16GB)GPU Driver: Intel® Graphics Driver 32.0.101.8425/32.0.101.8362 (WHQL Certified)Screenshot of bug attached. Unable to capture in video as the bug causes screen recording to fail. 

Using MOGRT in Timeline and changes e.g. text value. "Render and Replace" renders .mov-File with default values! After "Restore Unrendered" and again "Render an Replace" rendered .mov-File is correct. Using MOGRT multiply times in timeline "Render an Replace" always use same filename (not increasing) and replace files thats leads to error retrieving frames. Steps to reproduce:  Import MOGRT via Graphics Templates-Panel multiple times to Timeline Change e.g. text value Render and Replace (Source: Sequnece, Format: Quicktime, Prest: Match Source - Apple ProRes444, Location: Next to Original Media) - select clip for clip (not selct mulitple clips) Result: Renderd .mov-File shows wrong (default) values, all rendered .movs gets same filename, error retrieving frame  Expected result: Rendered .mov-File show right values, multiple files gets increasing filenaming Bug exists in Version 25.5 and still in Beta 25.6.0 (74) not in Version 25.3   System: Mac Studio 2023 (M2 Max)

ProblemaLa función de transcripción automática en Adobe Premiere Pro genera texto, pero la transcripción es muy imprecisa, con errores constantes, palabras incorrectas y frases sin sentido, como si el sistema no reconociera correctamente el idioma, a pesar de que el audio está claramente en ese idioma y se selecciona correctamente durante la transcripción.Pasos para reproducir Abrir Adobe Premiere Pro (última versión disponible). Crear un proyecto nuevo o abrir un proyecto existente. Importar un archivo de video con audio claro. Abrir el panel Texto. Seleccionar Transcribir secuencia. Elegir correctamente el idioma del audio. Iniciar la transcripción. Resultado esperadoQue Premiere Pro reconozca correctamente el idioma seleccionado y genere una transcripción precisa y coherente con el contenido del audio.Resultado realLa transcripción se completa, pero el resultado es muy deficiente, con errores graves de interpretación del idioma, como si el audio estuviera en otro idioma

We are aware that customers who saved projects in Premiere v25.6.0 may find that those files now open only in v26 (beta) and cannot be opened in v25 versions. We know this is disruptive, and we’re working on a fix.    What you need to know:  Projects saved in v25.6.0 save in the v26 version format.  Because of this, they can’t be opened in earlier versions, including v25.6.1 (even though it is the current generally available release)  We’re developing a tool that will let you convert affected projects back to a v25-compatible file.     Our Solution  We’re building a small app that will convert a v25.6.0-saved project back to the v25 format. We’ll share more information, including availability and instructions, as soon as the tool is ready in the coming days.     We know that there is nothing more important than the reliability of a project file, so we’re working with urgency to get this downgrade tool in your hands

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.

I had an issue with Premiere not sending the projects to Encoder, then I noticed they both have a new update so unfortunately I updated them. Since then I am can't start either of them getting the error 0Xc0000142 message. Other adobe applications such as After Effects, Audition and Photoshop are still working fine. I have tried the following fixes depending on what I found on the internet: * Uninstall and reinstall the applications. * Turn off / Unplug my second monitor. (tried with both monitors). * Made sure windows is up to date. * Reverted to an older version of windows. * Disable all windows startup programs. * Turn off windows defender / enable premiere and adobe CC through it.   My PC is strong enough for the CC applications, and I never had any issue with them while they are running, but I am noticing that everytime there is an update I am facing a new issue right afterwards.   Any idea what I can do? I was working on a project I need to export ASAP!

In Premiere 26.0.1, when I create guides in the program monitor, they work fine. But when I switch to full screen, the guides are present but they are not correct.  See attached.  Running Premiere 26.0.1 on a 2025 Mac Studio running Sequoia 15.7.4 

Pretty much what the title already says, sometimes Premiere loads up and reads the waveform (that wheel on top-right corner) but now it simply doesn’t read any audios from the videos I’m working on. Things that I already tried to fix the problem:Sequence - Render Audio Reset preferences  Delete Peak Files Check and unchecking Show Audio WaveformKeep in mind that the issues only shows up with Premiere 26 since I tried working on the 25 and it the waveform showed up there, so I think maybe Premiere 26 have some kind of weird bug to read audio files? Any suggestions to what I could do to get the waveform back? 

Issue – Text-Based Editing pause deletion does not work in, even though pauses are recognized in the static transcript.Steps to reproduce – Open an existing project. Import video clip with spoken content. Open the Text panel → Transcript → Transcribe sequence. In the transcript, verify that pauses are recognized in the static transcript view. Switch to Text-Based Editing mode. Filter for “Pauses” in the Text-Based Editing panel. Attempt to delete pauses using “Delete All Pauses.” Expected result – All pauses in the transcript should be selected and deleted in Text-Based Editing mode.Actual result –• The Text-Based Editing panel shows “0 results” for pauses, even when the static transcript labels them clearly.• The “Delete All Pauses” button is clickable but does nothing.• Issue occurs in all projects, including new blank projects.Adobe Premiere Pro version – 26.2.0 Beta, 26.0.1, and 26.0 (attempted in all 3)Operating system – Windows 11GPU driver version (Windows only) – NV

Here on my systems with RTX 5060TI and 5070 GPUs, yesterday I was editing a conference filmed in 4K, just over 130 minutes long. Exporting in Full HD took over 120 minutes, and this morning, exporting the same project in 4K with the camera's standard codec took much less time, just over 48 minutes. It seems that Premiere's optimization for Full HD is not working well; the performance is much worse than in 4K. Considering that 4K is a heavier file, it should be slower, and Full HD, which is lighter, should export faster.

I have a project (577.prproj) with 24 nested sequences, many assets, and one main sequence (577).  Using the project manager to archive the project to networked long-term storage, I’m only given the option to check the nested sequences.  The main sequence is not detected.  I’m on Windows 10 Enterprise, Premiere Pro 26.0.0 (build 72).  There are no errors reported.  The problem was clear when I saw that the 577 Masks directory was not included in the archive, but because the 577 sequence was not available in the Project Manager dialog I was on the lookout for problems.Workaround: I’m using the file system to copy the working directory to archive, but that won’t capture files from the project that aren’t in the working directory.   

Issue I am experiencing severe system instability and a massive memory leak while using Premiere Pro. Randomly during a session, the software freezes and becomes completely unresponsive. On Windows 11 25H2, Task Manager showed RAM usage maxed out at 90%+, whereas on other builds (24H2/23H2), the system would freeze even when RAM usage was stable at 50%–60%. Even after closing the program, the memory is frequently not released by the OS, necessitating 3–4 full system restarts daily to continue working. This happens whether I am working from Suite Studios (Cloud) or from local 2TB NVMe storage.Steps to reproduce 1. Open Premiere Pro and load any project. 2. Add a text layer to the timeline and begin trimming the layer. 3. Continue standard editing tasks (scrubbing timeline, trimming other clips). 4. Observe the UI becoming sluggish, followed by a total system hang/freeze.Expected result Stable performance and responsive UI during basic text manipulation and trimming, with proper system-l

A really useful tool in Premiere has always been the ability to click and hold a clip on the timeline, then use the “-” and “=” keyboard shortcuts to zoom in and out to make dragging the clip around the timeline much faster.After upgrading my mouse to the Logi MX Master 4, I’ve discovered a very strange and specific bug. Using the MX Master 4 feature of the Action Ring in any other application to specifically “Paste Text” (a built-in customization), then returning to Premiere, the ability to zoom in and out when dragging clips on the timeline no longer functions. If I click and hold, I can zoom, but if I click, hold and move the clip a little, I can no longer zoom. Resetting Premiere app settings does not resolve the issue, but restarting the computer does. Any attempt to paste predetermined text using the MX Master 4 action ring breaks the Premiere feature again. No other Action Ring function appears to replicate the issue thus far, only the “Paste Text” function found in the Action R

I am receiving this error message whenever I try to backup a project.I have reviewed the "Project Manager Error" thread in the Adobe Community and attempted to perform the workaround suggestions.  I have had no success.I am using:  Premiere Pro 25.5.0 on a Mac Pro running Tahoe OS.

HelloI have a Dell Pro Max 16 MC16250 laptop.Storage 954 GBGraphics card 8GB        Multiple GPUs installedInstalled RAM 32GB      Speed 5600 MTsProcessor          Intel Core Ultra 9  285HSystem type      64-bit operating system, x64-based processorWindows specEdition                 Windows 11 EnterpriseVersion                24H2OS Build             26100.7623Experience         Windows Feature Experience Pack 1000.26100.275.0 I’ve used Adobe Premiere Pro for about 12 years. I was given the above work laptop in Nov 2025. To be honest I haven’t used APP since then - until this week. I have literally just opened the software and created a new blank file. Absolutely nothing else. I’ve then gone to make a cup of coffee. When I’ve come back I’ve seen the attached error message on my screen. If I click ‘send report’ or ‘don’t send report’, APP shuts down. This has now happened 6 times. I cannot get to the stage to actually do anything creative.Any ideas?

Hi, I am a french user for Premiere, the auto corrector not seem to work at all with the new version.  

Ich benutze Premiere 2026 und will in den Voreinstellungen eine Änderung vornehmen. Um diese zu bestätigen / sichern und das Einstellungs-Fenster zu schliessen, drücke ich den “OK” Button - aber nichts passiert. Er ist blau und nach dem Drücken auch mit der hellblauen Umrandung gehighlighted, aber nichts passiert.Ich habe den Button per Tabulator angesteuert und Enter gedrückt - kein Effekt.Die einzige Möglichkeit, das Einstellungsfenster zu schliessen, ist “Abbrechen” zu drücken - dann werden aber alle Änderungen verworfen.Ich habe Premiere und den Computer (M1 Macbook Pro) neu gestartet, beim Start von Premiere durch “Option” drücken das Reset-Fenster aufgerufen und alle Möglichkeiten ausprobiert, Premiere komplett deinstalliert, neu installiert, stattdessen eine alte Version (25) installiert - immer das gleiche, nichts hilft: Das Voreinstellungs-Fenster lässt sich nicht über “OK” schliessen und Änderungen vornehmen.

Hello everybody,I’m experiencing a persistent issue when exporting my project in ProRes from Premiere Pro: a green vertical line appears on the right edge of the video.Details:Premiere Pro version: 25.5OS / Hardware: MacBook Pro M3 Max / macOS 13.5, Sequoia 15Sequence settings: 2500x1500, standard frame rate of 25 fps (match source), no adjustment layers or effects that could cause thisExport settings tested:ProRes MOV (422, 422 HQ, LT) → green line appearsProRes MXF OP1a → green line appearsMedia Encoder export → same resultH.264 export → line does not appear Troubleshooting steps attempted: Checked sequence dimensions and confirmed they match standard formats.Tried different ProRes variants (LT, 422, HQ) and both MOV and MXF containers.Exported via Media Encoder instead of direct Premiere export.Considered cropping 1 pixel on the right (temporary workaround, but not acceptable for master quality). The line only appears in ProRes exports, not H.264. This seems like

Link Media shortkey/shortcut does not work. Only when doing it manual with your mouse it works. This happens since a particular update in version 25. I am using version 26.0 now. OS system: MacSteps to reproduce: just set a shortkey (for example command + L) on relink media and you will see it does not work. 

Hi, I’d like to report an issue related to a simultaneous work of Google Chrome and Premiere Pro I’ve had of late.Of course I understand that it might be a Google problem so I should report to Google but I actually did and Google seems to ignore it, because I sent several reports and wrote to their support forum half a year ago and they are dumb.The problem I have is as follows. When exporting from Premiere Pro ( 25.6.4 in particular), should I start watching a video on ANY site except for Youtube (i.e. having a web player different from youtube one), the export in Premiere Pro stops. It does not freeze Premiere Pro - I can close the export window, go to any tab, and another export will start alright until I play back a video again on any site. During this export halt my CPU, iGPU and dGPU load is reduced to 0 (well, obviously the CPU still has some load, but it’s minimal, like 4-5%).I know that Google uses some video rendering pipeline of their own in Chrome (ANGLE + DXVA / D3D11) and

First of all, to clear this out, here’s the screenshot:So you can see the program files VST plugins folder is included in the search. But Premiere Pro find nothing there, and shows only the VSTs found in the COMMON folder. I certainly can copy the plugin files there, but I don’t want to.Here are the contents of my VST folder:… with the corresponding VST modules inside. And here’s the plugin not seen by Premiere Pro inside Davinci Resolve (Supertone is there too): And I hit Rescan several times, checked and unchecked the force rescan and so on. A bug that is.

This doesn’t happen during every session, but from time to time the mouse cursor does not do what I am trying to do.  When I am chagning a value by moving the mouse sideways, it highlights the numbers instead of changing them.  And when I try to lasso something it just won’t do it.  After about five seconds it will then act as intended, and then about five seconds later will not.  Sometime re-launching makes it go away, but not everytime.  This is only happening in Premier and no other Adobe apps or in the OS.I’m in the middle of several projects and I don’t want to update yet.V 25.6.4Mac OS 15.7.1M1 chip

PingFang SC font is an original font of macOS system. Other fonts can be displayed in Premiere Pro, but Pingfang font cannot be displayed. I have tried to roll back to version 25.1, and this font（PingFang SC） can be displayed normally. I hope this issue can be fixed in the next version.

On a video im using multiple lumetri effects to color my image. I use masks to select the subject, add shadows etc. When I scale the video AFTER doing all of my lumetri effects, the masks assigned to the lumetri effects dont scale.