Bug Reports

I’m running into an issue creating a step-and-repeat watermark when working with proxies on 4K footage.My source footage is 4K.The watermark file (a Photoshop PNG) is also 4K.When I render proxies, the watermark appears much smaller and shifts to the lower-left corner instead of covering the entire frame.For reference, here’s the PNG file sized at 4K (with blue added for this discussion). It should overlay across the full frame, but it isn’t rendering that way in the proxies.I can’t just use a single watermark in the lower right, since that area may get cropped out in the final video. That’s why I need the step-and-repeat pattern applied across the whole frame. I also have many files that need this treatment, so I’m looking for a workflow solution.Does anyone know why the proxies are handling the watermark this way, or how I can fix it so the step-and-repeat applies correctly?   

Hi Adobe team, this is a known issue for a long time since RTX 5000 series laptop GPU came out. Creators and professionals can't buy new laptops because of this. I just did a side-by-side comparison between RTX 4060 and 5080 on ASUS G14 and G16. G14 with the lower spec RTX 4060 can cut DJI 4K footage buttery smooth. G16 with RTX 4080 can't. I also just bought a new G14 with the same CPU and RTX 5070 Ti from Best Buy to test this. Confirmed! Both used G-Helper to enable everything correctly, both are on the same NVIDIA Studio Driver, both have CUDA enabled. Both project files are on the local OS drive. Both tested with Adobe Premiere Pro 2025 v25.5 and Beta 26.12. It is proven. RTX 5000 series does have issue cutting DJI footage. Video: We need you to fix this ASAP. This is affecting the film and marketing industry every single day. Plus, starting this week, Best Buy and B&H stopped selling mainstream RTX 4000 series laptops...

Bonjour, Je porte ici un problème que beaucoup d'utilisateurs connaissent et qui met mes nerfs à rude épreuve.En lecture, le curseur n'avance pas. Lorsqu'on fait pause il se place à l'endroit ou la lecture s'est arrété. Entre les deux, aucun mouvement !! J'ai évidemment fait toutes les manip recommandées sur les forums, et je ne travaille pas sur un deuxième écran. Je déplore ce problème qui commence à dater car aucune vraie solution n'est proposée par le support. Pour un logiciel payant, cela devient problématique... Merci a ceux qui ont la solution miracle.Merci au support de proposer une "vraie" solution.Cordialement

I just encountered a weird pesky little bug. When I enable the Global FX Mute, as soon as I move my playhead, all monitors turn black (program and source). The only way to get it working again is by restartring Premiere. Anyone else encountered this bug? I'm on Premiere 25.5.0, Windows 11, working with ProRes Proxies (source media is offline).

I attached a video of the problem in practice, I can't use the eyedropper tool directly through the fill and outline shortcut, this problem applies to all effects that have eyedroppers, such as ultra key, fill, essential graphics panels and external plugins.https://youtu.be/e74V0MvY3qw

On versions 25.4, 25.3, 25.2 (and their fixes) occurs GPU error:Selector 9error code: -1609629695If YOU have experienced simmilar error - drop down any comment so that Adobe would see this error.It happens on random timestamps (sometimes even outside in/out points), at random moments. Only going back to the 25.1 version fixes the problem. New Premiere Pro versions are just UNUSABLE cause you can't render anything. Tried:-clearing cache-reseting preferances-restarting PC-reinstalling Adobe Creative Cloud with Adobe Apps-new GPU drivers (reinstall)Technical:Windows 11 (newest), GPU Nvidia drivers (newest - 580.97)i9 13980HX, 64Gb RAM, 4090 Laptop GPU I would love to use new 25.4 timeline performance cause it works great, BUT I can't render with it anything ://This problem goes from version 25.2 and heared that a lot of people have simmilar issues. Don't know if it's Adobe's problem or Nvidia's problem or both - it just would be nice for things to work as they shouldIn the

App version: Premiere Pro 25.5Platform/OS: Windows 113 Edit-PCs (all Windows 11, using PPro 25.5) connected to a NAS (Grack) over 10GbEBasic Steps: - One of the Edit-PCs can open PPro Project and/or Production (created in 25.5) on the NAS- When they try to open “Scratch Disks” for a Project or Production, Premiere crashes on their machine. - Premiere also crashes if they try opening            - “Project >> General Settings”, or            - “Production >> General Settings”            - Premiere also crashes if a Production is open (no Projects opened yet), and we try to view "General Settings" or "Scratch Disks". - We found they had backed up their “C:/[User]/Documents” (including the “C:/[User]/Documents/Adobe” folder) to OneDrive.- We logged into their OneDrive & told Windows to save the “D

I’ve noticed a consistent problem when trying to create multiple presets for the Transform effect. Every time I save more than a few, the program seems to automatically replace or delete the earlier ones. I can only ever keep three Transform presets before the first one gets overwritten no matter what I do. Transform is one of those effects where it makes sense to have a whole library of presets for different tasks. Zooms, pans, anchor point setups, etc. Instead of being able to build that library, I find myself constantly recreating presets I had already saved, which is really annoying.

Bonjour à tous,Depuis mon passage à Windows 11 et après la dernière mise à jour de Premiere Pro, je n’arrive plus à ouvrir aucun projet.J’ai déjà :remis à jour complètement ma carte graphique RTX 3070,testé avec une version antérieure de Premiere,mais rien n’y fait.Le service d’assistance étant fermé, je suis vraiment en galère…Si quelqu’un a déjà rencontré ce problème ou a une solution, je suis preneur.Merci d’avance 🙏

Issue – scrubbing causes premiere to crash (maybe just when waveforms are displayed).Steps to reproduce – with waveforms displayed use the mouse to scrub a timelineExpected result – curser follows mouse movementActual result – crashAdobe Premiere Pro version – 25.5.0Operating system – Mac OS 14.7.4GPU driver - Apple M1 MaxVideo format – Prores LT (3996x2160)Does it affect all projects or only some projects? - all projectsDoes it affect new projects? yesWhen did the problem begin? After update to 25.5 - I did a clean install of all CC apps, reset prefs, deleted media caches

It seems that if you create a title (text / graphic) track item and change its label color, it will be reset to the default after changing the sequence dimensions.   This happens in both the latest version of Premiere Stable (25.5.0 Build 13) and the latest beta (25.6.0 BETA Build 78).   See screen capture: Steps to Reproduce: In some sequence, in the Properties window click "Create new graphic"  Right click the clip in the timeline, go to Label, and choose any different one than current  Right click the sequence in the Project panel > Sequence Settings > change either of the Frame Size values or both, then click OK Immediately the clip label colors are reverted to their default that they were upon creating the clip   Other Notes: It's not all clip types, and it may even only be text/title clips, but I'm not sure. Adjustment layers, other nested sequences, video clips, and seemingly anything else dropped in the from the project panel don't seem to chan

Premiere Pro version 25 has drastically slowed down export times. I've been producing the same type of footage for over three years, and what once took just 3 to 6 hours to render is now taking between 40 to 60 hours. All exports are H.264. All footage is 4K, no effects, simple transition between clips, only 1 pic image at the start of each video. PC specs.:5950x64GB ramseperate NVME for OS, data files and cacheNvidia 4090  GPU GPU drivers versions tested 5.77 and 5.81.08All other drivers are the lasted for the platform (x570)OS = windows 10 (latest version) In version 24, Premiere Pro made some use of the GPU but it would always max the CPU at 100% until the export was complete.Starting with version 25, the behavior changed significantly. It initially engages the GPU, but drops it almost entirely after reaching just 1% progress. From there, CPU usage remains minimal—averaging around 50% in version 25.2, and closer to 20% average in other 25.x releases. I'

Icon view commonly displays images from other sequences. Not even the footage that's inside that timeline. Ive tried to 'set poster frame' and doesn't work. Ive tried resetting my PP preferences and no luck. 

I set my auto-save to 15 minutes. But during editing, auto-save pops ups like every 2 mins. and even makes my app crash, losing some of my hardworks.

I recently upgrade my computer to a RTX 5090 and have been experiencing a lot of playback and rendering issues within Premiere pro specifically. I've already done a lot of trouble shooting to make sure i do not have overlapping drivers (removing drivers with DDU while in safemode) and I made sure all of my drivers are up to date, even installing the newest available studio drivers that Nvidia offers. I'll put a full spec list down below.Problem:I have been editing for years without these major issues, so I'm assuming my issue is related to my recent GPU upgrade or it's drivers. Whenever I'm editing a video and watching it back on the timeline, it will randomly freeze on one of the frames I was on and stay like that for upwards of 2 minutes until it catches up or I get impatient and try to restart the program. It feels as if my computer is hitching or trying to catch up. I read online that if I switched the video renderer to OpenCL instead of CUDA, it may help and would indicate th

Duplicate frame markers not appearing when duplicating clips within the same timeline or copying and pasting edited clips from another timeline.I've attached a screen recording for your reference.1. Open an existing project in Adobe Premiere Pro with a clip in the timeline.2. Duplicate the clip within the same timeline.3. Check for duplicate frame markers.4. Copy an edited clip from another timeline that contains the same clip.5. Paste the edited clip into the existing timeline.6. Check for duplicate frame markers. Expected ResultDuplicate frame markers should appear for both duplicated clips within the same timeline and pasted clips from another timeline.Actual ResultNo duplicate frame markers appear in either scenario.  Adobe Premiere Pro VersionVersion 25.2.3(build 4)Operating SystemWindows 11 (24H2)GPU Driver & Version RTX 2060_Studio driver v576.02Video FormatAVC_High 4:2:2@L4.2Variabl_46.8-50.0 Mb/s_50.000 FPS

After adding a clip to one of my project folders, the bin keeps on scrolling to the top automatically.  I closed and reopened the app, but the issue persists. The issue happens only for that specifin folder, all others behave as usual. Premiere Pro version is 24.5.0 (Build 57) on Mac OS Sonoma 14.5

I'm visually handicaped; go figure, and while I can manage graphics, I have a hard time withgrey text. In this case I can't see the devide between tracks. Generally I defailt to "Dark Mode": White on. I would sell my soul for a White text option. Can anyone suggest a work around for this problem?  

Cross dissolve seems to stop the insert edit function going from sequence to sequence Steps I've taken:1. Put sequence into source monitor 2. Click the wrench icon and open sequence in timeline 3. Open another timeline and place it below the source timeline 4. Select my in and out points 5. Attempt to insert that section by using the commands , or . 6. Nothing happens 7. If the option for it being nested is on, then it works, un-nested doesn't 8. Remove disolves from source timeline 9. It now works  What I wanted it to do: Transfer all footage from 'source' timeline, to new timeline, un-nested with all videos and audio seperate What it did: Would not copy unless all dissolves had been removed  Prem version: 25.2.3Computer: Mac Studio 2022 Apple M1 Max64gbOS: Ventura 13.1 

Hi, i am hoping this is the correct place to post this... Premier Pro version 25.2.1 build 2 i just started experiencing this issue when i am picking back up a project to work on and i have been working on it just fine....i opened up the project and it spikes my CPU temp to threshold lvls and crashes the application......its happening everytime when i even start a new project and import media.... my main OS drive is an NVME where i have Premier Installed. I have my media on a separate SSD and i even have Media Caching on a separate SSD. I dont understand why this is happening.... I dont get an error, it freezers the application and shuts off and i see my Rog RYUJIN III  Fan displaying CPU Temp either 85 or 90....when i reopen Premier Pro it just says it crashed unexpectedly earlier and reopen last open file.... I also have an RTX 4090. Any help would be appreciateed.

Whenever I enable the trim tool on a clip in the timeline, Premiere pauses for a few seconds with the beach ball spinning.  I've reset the preferences, rebuilt the cache (which is set locally), nothing's worked. Everything else is super snappy - any thoughts?OS 15.6.1, Mac Studio M2 Ultra, 62GB RAM, Premiere 25.2.3, Using Productions on Lucid Link

Hi!    I'm wondering if anyone would have any insight as to what could be causing issues for me in my Adobe products, I've tried multiple versions and it just seems so clunky, I've tried it on multiple PC's too, it just feels very laggy, slow to scrub through footage (even Proxies at 1/4 quality seem to perform with no difference to the base files, which is making me wonder if it's an issue in settigns or files, which is why I've tried different versions, lean installs the works. My Specs are; Windows 11AMD Ryzen 9 9950XRTX 409096GB DDR5 (2x48GB)Samsung 990 Pro NVME SSD (multiple drives, one has my OS, files and Programs, and I have a separate one for the Media Cache as I thought that would help too, but it made no difference, or if anything made it lag and stutter more). It seems even very simple tastks are causing lag, such as yesterday in a Dyanmic Link, I made a circle in a separate pre-comp and that lagged in of itself, any other questions, please let

We've got a live one!Premiere Pro v25.3.0, working in a Productions environment. MacOS Ventura 13.7.x for all parties affected. My editorial team loves their templates. Can't live without them.Here's our standard workflow, which used to work as desired in Premiere 24.6.x (latest LTS release, as of July 23, 2025):Create Template Project containing the desired folder structures and template sequences for edit preparation.- Let's call our example "parent" sequence: "Template-Sequence".Save Template Project, and begin "Make a Copy" ops in the production to build out clones of this template for each necessary prep, avoiding Duplicate IDs. As is tradition.While prepping, rename sequences in the new "Copy-of-Template" projects for team sanity and morale.- My renamed sequences will be called "Sequence_A", "Sequence_B", etc.- Note that I'm not copying the origin sequence, just renaming the sequence in my copied Project.- It's quite possible that the child-Sequences now have

my preview suddenly shows blank (black) while im doing my edits. whats going on? im editing my adjustment layer above my footage, all of the sudden, it shows blank on my preview. when i try to double clock any of my footage, whether its on my project tab or my timeline, it also shows blank. yesterday everything was perfectly fine. but suddenly it happened today. the previous solution was to reinstall the premiere. it worked, but only for like 30 minutes. and then it happened again, and now i dont know what to do. should i reinstall everytime? :)))))))

As a timeline gets more complicated copy/pasting clip audio levels stops working. What's weird is that for some clips it will work fine, but for others it won't. At the same time adjusting a clip's audio level with the clip mixer will not change the horizontal level line in the timeline, (although the level will change). You can still adjust the levels by moving the line vertically, but this then doesn't drive the audio mixer. Again, this is completely random - some clips will be affected, but some will not. For instance I've got a timeline where audio on tracks 1-3 work as expected, but on tracks 4 and above it does not. Rolling back to v24 fixes the problem.    This has been seen by a few of us working on Apple Silicon computers.    Happy to share a project, although I can't do that publically.