Bug Reports

when i press the locate button in the link media dialogue and press search, it tries to suggest a clip that is totally the wrong name thent he clips its supposed to be searching for.  Premiere 2025  version 25.6.6 (build 5). mac os tahoe. (then i used syncalia to sync something for me, and i imported the XML into premiere and every single clip was offline. not sure if thats premieres fault or syncalia but ive never had an XML come into premiere as offline. this isnt normal) 

I've had this bug come up throughout numerous versions over the years. There's often no levels on the mix channel in the audio track mixer channel. Obviously I need to see my levels before export. 

Issue – I've been working on a number of longer projects recently and I'm noticing that everytime I open the projects, the IN and OUT points that I had set on my sequences have randomly moved. Sometimes the IN point will be a few seconds later. Sometimes the OUT point will be a few seconds earlier. The duration of the jump is never the same each time.  Steps to reproduce – I have a slate at the start of all my sequences, which we use to make internal notes and caveats when providing WIPS to client. When reviewing internally, we don't need to use these, so I set an IN point on the sequence at the begining of the edit proper. And an OUT point on the final frame. These points do not move while we're working on the edit. I'll save the project for the day, and the next day when I open the project, one or both of these IN/OUT points has moved a few seconds and I'll have to re-set them.Expected result – IN/OUT points should not be moving unless I've moved th

In Premiere Pro 2025 (25.5), once a media file has had its audio peak file generated, Premiere reuses that existing peak file whenever the same media is imported into another project. This avoids unnecessary cache generation and significantly improves workflows that reuse the same media across multiple projects.In the latest Premiere (26.3), this behavior appears to be broken. Premiere regenerates the audio peak file every time the same media is imported into a new project, even when a valid peak file already exists in the Media Cache.As a result, identical media can end up with duplicate peak files, increasing cache generation time and slowing down workflows that frequently reuse the same assets.(While testing use a longer media file so that peak generation takes long enough to clearly observe whether Premiere is reusing or regenerating the cache.)Steps to Reproduce (Scenario 1 – Across Projects)Create a new project. Import a media file with audio. (or just a long audio) Wait for Prem

When applying the “grow” effect to an adjustment layer that has beed sped up or slowed down, it doesn't work anymore and just zooms in a lot. Does not seem to apply to video layers. Also some of the other “clip length based” effects like “spin” act weird on adjustment layers that have been changed in speed.Steps to reproduce: - Add an adjustment layer to a sequence​​​​​​​- speed it up using the rate stretch tool​​​​​​​- apply the grow effect to the adjustment layerMacBook Pro M2 Pro, macOS Tahoe 26.2Premiere 26.3.0 (Build 93)

When trying to play .MOV files shot on an Alexa Mini in ProRes 4444 23.976 fps in V26.3.2, certain files (potentially shot upside down with the intention of being rotated correctly in post) does not playback properly and will not show in the Program Monitor. Scrubbing with the cursor will ‘play’ the file, but upside down. If an export is attempted, a solid black frame is generated with no data. Reverting to the latest update of Premiere Pro 2025 resolves this playback issue and all files appear on the timeline with no issue in the correct orientation and also does not generate black frames on these files upon export. Something in the latest update appears to prevent correct decoding and encoding of certain ProRes 4444 files. (V25.6.6)

When I use a PSD file to scroll through my credits. It works OK when I Export or use a jpeg file. Premiere Pro Version 26.3.0 (build 93) 

I’m using Adobe Premiere Pro 26.3.2 (Build 2). 1 month ago. When I open Premiere, everything works normally at first. I can see the Source Monitor and import/drop my files without any issues.However, after a short time, the panel suddenly disappears and I cannot restore it.When I go to Window → Projects and click on my project, instead of reopening the Project panel/resource panel, Premiere only creates a duplicate of the project tab name without showing the actual contents or panel.I’ve already tried reopening the panel from the Window menu, but the issue persists.Also creating a new project and import the old one into it doesn't work and reseting to saved layout too. i have Mac mini m2 at home and everything works fine. :(Has anyone experienced this issue or knows how to fix it?

I’ve used Project manager in Premiere (currently in 26.2.2) for a couple of months already without an issue. Now I have this short but rather complicated project with tons of effects and overlays and when I’m trying to make an archive copy with it I get this:Of course I cleared the cache, reset the preferences, there’s ton of free space on my SSDs and I tried to save the archive with Project manager on each of them. Every time the process either stops at the beginning like this (an hour wait was in vain):or gives me this error I added above. I do not transcode or include previews or audio conforms, nothing, these are my settings:The calculation process does not start either.I also tried to duplicate the project and run it there, copy all the media to a new project (which I cannot use as a solution because I have audio mixer set up and the new project or sequence has none).The only one time I could export an archive from the Project manager was unchecking this setting:So I think Adobe s

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

Premiere Pro 25.6 freezes/white-screens on repeated playback of the same timeline section — all threads blocked on single internal thread Premiere Pro repeatedly freezes (Windows "Not Responding" state, playback audio/video continues briefly in background) when rewatching the same section of a timeline more than 2-3 times. This happens across different projects, including a brand new project with fresh footage — not tied to one sequence or clip.System specs:Premiere Pro version: 26.3 CPU: Intel Core Ultra 9 285K GPU: RTX 4070 Ti Super, Nvidia Studio Driver (latest) RAM: 32GB (31GB installed), Premiere allocated 25GB OS: Windows 11 Storage: Boot NVMe (Gen 4), ~50% free, media cache on same drive Renderer: Mercury Playback Engine GPU Acceleration (CUDA)What I've already ruled out:GPU/renderer settings (confirmed CUDA active, GPU usage stays near-idle even during freeze) H264/HEVC hardware decode routing (tested Intel+Nvidia both enabled, then Nvidia-only  freeze duration shortened slight

IssueWhen using the Motion Tween transition for zooming out, the transition shows black bars, although the video as enough room.The black bars fade into the video at the end of the transition.Steps to reproduceI set the fist video to 120%, the second to 100%.Then I select both clips and add the Motion Tween transition.Result: I added the actual result and the expected result (made with keyframes on scale property) as attachments.Adobe Premiere Pro version26.3.2Operating systemWindows 11Video formatDifferent formats (mp4 h264, mov prores 422),Resolution 4K and FHD, both in FHD sequence

Good morning, community.Every time I use Premiere (2026 latest version), whenever I move around the interface and panels, the program freezes. 😫I’ve already reinstalled Premiere, created a test project on 3 different SSDs, and the freezing issue still persists.I’m using a laptop with an R5 8645HS + 32 GB DDR5 RAM + RTX 4050 (updated Studio driver) + 1 TB NVMe + 1 TB SSD.I only have issues with Premiere—After Effects runs without any problems.Any solution?P.S. I’ve reinstalled, reset, and cleared the cache. Only the program freezes; the laptop keeps working normally and can still play YouTube videos.   

Have been using Premiere Pro 2025, the app updated itself to the latest version (26) and is saying all my clips (hundreds) are offiline. When I try to relink them it says there is an issue with the audio channels type. Its ridiculous because I've been working on this project for months and have never had this issue. I re dowloaded the older version of PP and now thats doing the same thing...  not sure if this is a bug or somethng Ive doneExtra info: working on a Macbook Pro 2019,Graphics: AMD Radeon Pro 5500M 8 GB, Intel UHD Graphics 630 1536 MBVarious files shot on iphone, drone, pocket 3, go pro.Working off an SSD (Samsung T7 shield)Memory: 64 GB 2667 MHz DDR4OS: TahoeProcessor: 2.4 GHz 8-Core Intel Core i9

The auto-save feature isn't working. Premiere freezes. I've been experimenting—I set the autosave interval to 10 minutes, and after 10 minutes, Premiere freezes. I set it to 3 minutes, and after 3 minutes, it freezes. Sometimes this corrupts the project, and I have to redo some of the work. This is terrible; professional software shouldn't work like this. I use the latest versions of all updated software on Windows 11

I am using the default Light Leak transition on a clip coming out of black on my timeline to get a wash of color over the video as it fades up. I also use the same effect between subsequent clips in my timeline. Everything looks great until I try to export the clip using a loudness normalization effect as part of the export. When loudness normalization is applied as part of the export, the transition coming out of black is devoid of color and the color pops on as soon as the transition ends. The following light leak transitions following it that are between two video clips look fine in the export, only the one coming out of black is effected. It shows in any type of export reliably, even ProRes 422 HQ uncompressed. Here are two clips uploaded to my google drive showing exactly this, as well as a screenshot of the effect in question on my timeline.https://drive.google.com/file/d/1FoHCIHadZKYKSuCXFkkd0PloHCHvlNRx/view?usp=sharinghttps://drive.google.com/file/d/1T3aXgDq6RJNSwG5oy1LE2fywn4

I'm having the same problem. I have large projects with a lot of media, organized in a production, and every time we open Premiere the media relinking process takes several minutes. The media is on a Qnap NAS unit with excellent read and write speed; each project's caches are being directed to the HDs of the editing workstations.We've already tried deleting the caches, redirecting them to the NAS, removing the projects from the production, and disabling media analysis — none of these attempts resolved or reduced the media relinking time. We are loading additional metadata into some "dynamic media" fields to optimize our searches, but we've also tested projects without inserting metadata and we have the same problem.We are using 3 workstations: Mac Studio, M4 Max, M2 Max, and M1 Max, connected on a 10GB network with proper cabling and electrical protection.We are starting a large project, and because of this issue we are reevaluating our use of Adobe Premiere. We've had previous experie

Hello,I have now clearly isolated the issue.My iPhone HDR footage is recorded as:HEVC 10-bit 4:2:0 Rec.2100 HLG 4K at 60 fpsWhen I import this footage into Premiere Pro 26.3 on Windows 11, its colors and brightness change. The exported result also appears brighter, less saturated, and different from the original iPhone video—even after uploading it to YouTube.I then disabled “HDR Video” on my iPhone and recorded a new test clip. The new clip was:HEVC 8-bit 4:2:0 Rec.709This Rec.709 clip appeared exactly like the original inside Premiere, after export, and during playback. Therefore, the problem occurs only with iPhone Rec.2100 HLG footage.I do not want to disable HDR permanently because I want to benefit from the HDR recording quality of my iPhone.Could you please provide the precise Premiere Pro settings for either:Editing and exporting the iPhone footage as true Rec.2100 HLG HDR for YouTube, while preserving its original appearance, or Converting the iPhone HLG footage to Rec.709 SDR

I’ve never had any problems using a network attached storage with any other software except Premiere.It is ultimately the biggest pain and hinders my work when it decides to forget where all of my footage and assets were.I store all footage on my local NAS and it is always connected to my workstation via physical network connection.The project file I’m working on now has decided to forget that i have a NAS and all of my assets are offline.I tried to re-link them, but it cannot automatically relink for the 1000+ assets that it cannot find.I must add that the re-linking user-experience is the worst. It takes a minimum of 10 seconds to an average of 20 seconds for a folder load any contents when browsing using Premiere’s media browser.Selecting media with ‘Automatically re-link media’ enabled does not automatically relink the footage or assets on the NAS.This needs a proper update or rewritten function for an acceptable solution, not a band-aid or workaround.

Zusammenfassung:Preview-Wiedergabe ruckelt stark bei 50%-Zeitlupe (Frame Sampling) auf 10-bit 4:2:2 All-Intra-Material, obwohl Export und lokales Rendering einwandfrei flüssig sind. Proxys, GPU-Beschleunigung und schnelle Storage-Lösungen ändern nichts am Verhalten. Bemerkenswert, da All-Intra (jedes Frame unabhängig, kein GOP-Referenz-Overhead) decoder-technisch eigentlich einfacher zu handhaben sein sollte als Long-GOP-Codecs.Quellmaterial:Codec: H.264, 10-bit, 4:2:2, All-Intra Auflösung: 4096×2160 (C4K) Framerate: 50fps (konstant, bestätigt via Frame-Count/Dauer-Berechnung, kein VFR) Bitrate: ~600 Mbps Farbraum: Rec. 709 Sequenz: 25fps TimelineWorkflow:Clip in 25fps-Sequenz einfügen Speed/Duration auf 50% setzen (Time Interpolation: Frame Sampling, Standard) Preview abspielen → deutliches Ruckeln, wirkt wie ~12,5fps statt sauberem 25fpsBereits ausgeschlossene Ursachen:✅ Framerate-Interpretation korrekt (Interpret Footage zeigt korrekt "50,0000 fps aus Datei") ✅ Kein VFR (Variable Fr

Over the last few days I’ve been getting the following error message across all projects in Premier:“Gaussian Blur 26.3.0 error at 0:00:00:00Illegal address. (code 700)”I’ve tried uninstalling and reinstalling and it still occurs. I’m running Windows 11 version 25H, what I believe to be the latest version. This issue just occurred out of nowhere, as its been running glitch free till now.

Premiere Pro 26.3 becomes unstable and repeatedly freezes when interacting with the application UI. Opening menus, changing settings, or performing basic UI actions causes Premiere to hang and eventually stop responding.This issue does not occur in Premiere Pro 25.5 on the same computer. The same hardware, drivers, and Windows installation work correctly with Premiere Pro 25.5, Photoshop, and After Effects.This appears to be a Premiere Pro 26.x-specific compatibility issueI tried every fix listed online such as Completely uninstalled and reinstalled Premiere Pro. Installed previous versions of Premiere Pro 26.x. Reset Premiere preferences/settings. Disabled third-party plugins. Cleared Premiere media cache. Updated NVIDIA drivers. Performed a clean NVIDIA driver reinstall. Used Display Driver Uninstaller (DDU) to completely remove and reinstall graphics drivers. Tested Premiere using both GPUs: NVIDIA RTX 3060 Laptop GPU Intel Iris Xe integrated graphics And after all of that I decide

Premiere Version26.3.0 (macOS)IssueDragging an existing sequence onto the New Item button creates a new sequence whose Composite in Linear Color Mode setting does not match the original sequence.Steps to ReproduceCreate a sequence. Disable Sequence Settings → Composite in Linear Color Mode. Add a clip. Add a Color Matte above the clip with a blend mode such as Overlay or Soft Light and adjust opacity so the effect is obvious. Drag the sequence onto the New Item button to create a parent sequence. Open Sequence Settings for the newly created sequence.Expected ResultThe new sequence should inherit Composite in Linear Color Mode = Off, matching the source sequence, so nested compositing is visually identical.Actual ResultThe newly created sequence has Composite in Linear Color Mode = On, causing blend modes to render differently (lighter in this example).WorkaroundInstead of dragging the sequence to New Item:Duplicate the original sequence. Delete all clips. Drag the original sequence int

Splash screen on startup - “requires access to the following folder(s): Desktop." This issue has only occurred in v26 updates of Premiere Pro. Insufficient workaround it to reboot in an older version of Premiere Pro. 

My videos have been exporting using the proxies, as in the video quality is very reduced and grainy and looks exactly like my proxies. I know this is the issue because I tried multiple solutions and then when I just detached my proxies, it exported perfectly fine in full quality.Then, when I try to relink the proxies, it only allows me to link one clip at a time, even though they are all in one location on my hard drive in the same folder. It does not recognize the other proxies and relink automatically the way that it should.PLEASE help, this is a massive inconvenience because now I either have to create all new proxies and wait for them to export in Media Encoder, or go in and manually attach EACH proxy, and I have well over 400+ clips. This has been going on for over a month. Premiere Pro version 26.3, all other Adobe apps are updated, working on a 2020 MacBook running Sonoma 14.6.1.