Skip to main content
Participant
October 14, 2026
Open for Voting

Severe Lag in the Properties Panel in Premiere Pro 26.2 and Later

Severe Lag in the Properties Panel in Premiere Pro 26.2 and Later

I'm experiencing severe lag when adjusting Position and Scale values in the Properties panel in Adobe Premiere Pro.

The issue occurs even in a completely new project containing only a graphic clip with text and a rectangle. No large video files or other resource-intensive media have been imported.

Version Comparison Results

I tested multiple versions of Premiere Pro on the same PC:

  • Premiere Pro 25.x: Works normally

  • Premiere Pro 26.0.x: Works normally

  • Premiere Pro 26.2: Severe lag

  • Premiere Pro 26.3: Severe lag

  • Premiere Pro 26.5.2: Severe lag

The Properties panel works smoothly in version 26.0.x, but the issue occurs in all tested versions from 26.2 onward.

System Information

  • OS: Windows

  • GPU: NVIDIA GeForce RTX 3060

  • GPU Driver: NVIDIA Studio Driver 617.42

Troubleshooting Already Performed

  • System Compatibility Report: No issues detected

  • Disabled GPU-accelerated UI rendering: No improvement

  • Windows Text Cursor Indicator: Already disabled

  • Windows Magnifier: Already disabled

  • Tested with a completely new project: Issue still occurs

Steps to Reproduce

  1. Launch Premiere Pro 26.2 or another affected version.

  2. Create a new project and sequence.

  3. Create a graphic clip containing only text and a rectangle.

  4. Select the graphic clip and open the Properties panel.

  5. Try adjusting the Position or Scale values.

Expected Behavior

Position and Scale values should respond smoothly and immediately, as they do in Premiere Pro 26.0.x.

Actual Behavior

The Properties panel becomes extremely sluggish when adjusting Position or Scale values, making editing difficult.

Additional Information

Since Premiere Pro 26.0.x works normally on the same system, I suspect that a change introduced between versions 26.0.x and 26.2 may be contributing to this issue.

I would appreciate it if the Adobe team could investigate this issue and consider addressing it in a future update.

Thank you for your time and support.