Bug Reports

All video playback is pixelated and blurry.  Playback setting are set to full and high quality playback is enabled. It looks this way in the color workspace and in the normal editing timeline. Export is clear and normal

None of the HUD scopes are clear enough to read. They all pop up pixelated. When adjusting the HUD options, the sample HUD looks normal.

Mask tracker will not track if clip has Color effects on it. It will drop keyframe on the current frame and not move. Rebooting and uninstall and reinstall Premiere Beta allows tracking but will crash when you click 'Stop' on tracker. This is repeatable even after reboot and uninstall+reinstall of Premiere

 This bug also exists in version 26.2.2 System info    Application: Premiere Pro (Beta) v26.5.0.8    OS: Windows v10.0.26200, RAM: 31.82 GB GB, CPUs (logical): 24

Steps to reproduce:    1. ... Result: ...Expected: ... System info    Application: Premiere Pro (Beta) v26.5.0.4    OS: macOS v26.5.0, RAM: 64.00 GB GB, CPUs (logical): 18

Clips wont long snap to the edges of another clips anymore.It will only snap to the red center guides or when using the blue guides Works in 2025 but not in 26.2.2 either. 

No workspaces in headerDoes not let you use the New item icon button for new sequences.Have to use the New Sequence window.26.5.0.2

I have installed the beta version of your new Premiere Pro 2026 recently, where your audio remix tool is not working; it's behaving like a normal arrow tool. Can you please fix this issue, as it's causing me issues? 

I recently upgraded to Premiere Pro Beta 26.5. Instantly, I noticed I’m unable to play back the timeline/program monitor at full resolution. No matter what I select, it only plays at a low resolution. I’m not sure what resolution it is exactly, but I’m guessing it’s 1/8 based on what I’m seeing. It freaked me out because I thought there was something wrong with my footage , but when I checked the source it was fine. I reverted back to 26.3.0 BETA (Build 71) and it’s fine now. I’m wondering if anyone else sees this issue. I’m hesitant to upgrade until I know this has been fixed. I realize this is the risk in using the Beta version, but the normal version of Premiere has stopped opening - it crashes every time I try to open it - I think it is related to a plugin issue because it will start if plugins are disabled. Long story, short, I started using the Beta version almost exclusively becasue I’m not having the crashing issue.Apple M3 Max64GB RAMTahoe 26.5 

Steps to reproduce:Update to beta 26.5.07 Open a project that was last edited in the previous beta version Insert a graphic title  (lower third speaker ID) Copy the graphic clip on the the timeline (Select clip, ctl+c) Go to paste the graphic elsewhere, (ctl+v) but nothing happens. Select clip and go to menu>Edit. Discover that Copy is grayed out as an option. Experiment trying to find a way to copy. Nothing helps, not even copying from the Graphics panel. Discover that if I CUT the item and replace it, then I CAN paste it elsewhere And now copy/paste is working normally System info    Application: Premiere Pro (Beta) v26.5.0.7    OS: Windows v10.0.26200, RAM: 63.79 GB GB, CPUs (logical): 16

Almost every time I make a global adjustment in the new color panel, the video turns to black and the only way to fix it is to close the program and open it up again

I literally updated to the most recent beta today (I was using the previous Beta, so all STILL beta)I tracked and masked multiple items using the mask tool.  It worked great.  Newest update:  still masks people/items/things pretty well, but it won’t “track” them forwards and backwards.  It gets stuck in thinking (spinning) and never resolves.  The previous beta did this in seconds!

I’m on the newest beta, and an issue has arisen that didn’t exist yesterday on beta before the newest update:-when I apply an ellipse mask to a new clip adjustment in color mode (second clip adjustment for that clip) it crashed premiere. -I opened a previous save, saved as a new file, and then added the adjustment and saved. Now that file crashes upon opening (unusable)I’m on a Mac Studio with the newest Mac software, with plenty of ram and processingI’m on the newest beta update as of 8:56am EST May 19th 

Previous beta had no issue with “track select forwards and backwards”.  I used it today. Newest beta just spins and spins.  Here are my Mac specs:Mac StudioM2 Ultra128GbTahoe Version 26.3.1

After using the new Color Mode in Premiere beta, then replacing with an After Effect Composition (also beta), all color grading is lost. Maybe AE doesn’t recognize the color affects from PP yet in this beta version. But if this information doesn’t carry over, then the PP & AE workflow doesn’t work, which is a deal breaker. Unless I’m missing something, this seems like a huge oversight. Hopefully this is coming.  

To replicate, go to Color Mode, scroll down in the grid view, label a clip.The grid view will scroll to the top.

See this thread in the regular forum:  Users report transcription failure resulting in “No dialogue found” for files that appear to have dialogue and that work in earlier versions. Some users report this as early as 26.0.0. More users report this coinciding with upgrading to 26.2.2. I have wondered if some of the users with problems are using non-English installations or non-English files. I took special note of ​​@mattchristensen1’s post that raised the question of the large downloads involved in the extensive updates to transcription in 26.2.0. The user I link to reports that this also occurs in the Beta 26.3.0, build unspecified. I am posting this bug report for him, because I realized that the new forum makes posting a Beta bug report with the system information less straight-forward than previously. I believe the results reported are not in themselves diagnostic. Transcriptions may fail after starting for multiple reasons, and when they do, they often show no transcription and a N

System Information:Hardware: Apple Mac Studio OS: macOS Display: ASUS XG49V (Ultrawide 32:9 Aspect Ratio / Native Resolution 3840x1080) Application: Premiere Pro Beta (New Color Mode Workspace)Description of the Issue:While utilizing the brand-new Color Mode workspace, the real-time scope overlays (both the Transient HUD scopes that appear when dragging/holding the Color & Contrast dials, as well as the new permanent "Video Scopes" panel) are rendered with heavy, blocky pixelation. The pixel-precision is so low that the waveform information is entirely unreadable for fine color adjustments.Steps Taken to Troubleshoot (Unsuccessful):Verified that the Program Monitor playback and paused resolutions are explicitly set to "Full." (Note: Lowering the resolution selection to 1/2 or 1/4 results in no discernable difference in the monitor preview canvas quality, indicating a potential UI texture-buffer refresh mismatch). Enabled "High Quality Playback" via the Program Monitor settings. Att

Bug: Color Mode HUD waveform scope renders at extremely low point density — M5 MacBook ProSystem: M5 MacBook Pro, macOS Tahoe 26.4.1, Premiere (beta) 26.5.0 build 3, Metal GPU rendererWhat's happening: The HUD waveform scope that appears when clicking a Color Mode control (e.g. Contrast) renders at roughly 2–5% of expected point density. Instead of continuous waveform traces, the scope displays a sparse scatter of individual pixels — the underlying data appears correct (sky at ~60–75%, shadows near 0–20%) but the rendering is so low-density the scope is unreadable as a grading tool. The scope background and panel dimensions render at full resolution; only the waveform trace points are affected.Expected behavior: Dense, continuous waveform traces as shown in Adobe's own Color Mode tutorial videos and documentation screenshots.Reproduction: Open any clip in Color Mode → click any control that triggers the HUD waveform (Contrast, Exposure, etc.) → HUD appears with sparse pixelated trace i

Bug: Color Mode HUD waveform scope renders at extremely low point density — M5 MacBook ProSystem: M5 MacBook Pro, macOS Tahoe 26.4.1, Premiere (beta) 26.5.0 build 3, Metal GPU rendererWhat's happening: The HUD waveform scope that appears when clicking a Color Mode control (e.g. Contrast) renders at roughly 2–5% of expected point density. Instead of continuous waveform traces, the scope displays a sparse scatter of individual pixels — the underlying data appears correct (sky at ~60–75%, shadows near 0–20%) but the rendering is so low-density the scope is unreadable as a grading tool. The scope background and panel dimensions render at full resolution; only the waveform trace points are affected.Expected behavior: Dense, continuous waveform traces as shown in Adobe's own Color Mode tutorial videos and documentation screenshots.Reproduction: Open any clip in Color Mode → click any control that triggers the HUD waveform (Contrast, Exposure, etc.) → HUD appears with sparse pixelated trace i

How many cycles is it going to take to finally fix this bug.Broken since 2025Moving the WAB in the source monitor on a 2160P clip opened from the timeline in a 1080p setting26.5.0.3 

PP 26.3.0 Beta Build 71Was switching around color spaces (to Rec2100 PQ)As I push up the exposure the HUD scope changes but the Window | Video Scope (waveform & vector scope), that was formerly responsive, remains unchanged Quit & restart results in no scopes at all visible in that pane.

Clicking the comparison button in color mode (under program monitor) hard crashes PP 26.3 BETA build 71. Repeatable.Had to access the comparison button by clicking the + button and then removing items until it appeared.