Build better products with our product team
When opening a photo from Lightroom into Photoshop as a Smart Object, Lightroom/Camera Raw settings are embedded in the Smart Object. Please allow resetting Camera Raw settings per duplicated Smart Object layer, so one instance can remain edited while another can be reset to the true RAW/original — without duplicating files or reopening Camera Raw. This would enable clean, non-destructive comparison between edited and original RAW data inside a single Photoshop document.
Hi Team, With the integration of more AI models (Firefly and Third-Party Partner Models), managing generative credits has become a workflow bottleneck. Currently, we have to leave the app and check the web dashboard to see our balance, which breaks the creative flow. I would like to suggest two UI improvements: Real-time Balance: Display the remaining generative credits directly on the Contextual Task Bar or within the Generative Fill/Expand dialogs. Cost Transparency: Show exactly how many credits a specific generation will consume before we click "Generate," especially when using high-compute Partner Models (like Nano Banana or Video models) that might have different credit costs than standard Firefly. Knowing the "cost per click" and our total balance in-app would allow for much better resource management and a smoother professional experience. Thank you!
There already is an option to copy & paste sequence markers but what's missing for me is the possibility to insert sequence markers when opening a sequence as a source. When I open a squence as source that has sequence markers, those will be ignored when inserting or overwriting.The only way is to select all the clips in the in to out area and copy them, then paste them in the desired sequence but that adds an extra step and I need to open the source sequence as timeline (in that case opening the sequence as source is useless in the first place as the only option is copy & paste). This feature would make working with source sequences more painless and more logical (compared to normal sources that will include their markers on insert).
Every time I update After Effects, I have to remember to go back into the Application folder and restore the scripts that were previously in the 'Scripts' and 'Script UI Panels' folders, which is very inconvenient. I'd like to request that updating After Effects doesn't remove files from these folders (or at least offers this as an option).
Dear Premiere Pro Development Team,I am a video editor specializing in commercials and music videos, and I use Premiere Pro daily. I am writing to propose a new feature: "Absolute Clip Lock" (the ability to lock selected clips to a specific point on the timeline).The Problem: Currently, when editing commercials (e.g., a 30-second spot), specific elements like the Brand Visual Identity (VI) at the final 2 seconds must remain fixed. Similarly, in music videos, certain shots must align perfectly with specific beats. However, when trimming or ripple-editing adjacent clips, these "fixed" shots often shift. Constantly double-checking their alignment is a significant source of stress and slows down the creative process.The Solution: I request a feature that allows users to lock an individual clip (or multiple selected clips) to its absolute position on the timeline. •Unlike the current Track Lock, this would only affect the specific clip, allowing other clips on the same track to be edited freely.•This would be invaluable not only for CM and MV editors but also for TV editors who need to lock commercial break timings to specific timestamps. Additional Suggestion: It would also be incredibly helpful to have a "Solo" button for individual clips, allowing us to isolate a specific clip’s audio/video without muting entire tracks.Thank you for your hard work and for considering these ideas to make Premiere Pro even more powerful for professional editors.Best regards,
Hi! There should be an option to adjust the volume of selected clips. It's strange that when you select multiple clips, the volume only changes for one.
Now that version 26.0 of Premiere Pro has been released I'd like to draw everyone's attention to the main problem of this update - projects created in Pr 26 cannot be opened in its earlier versions. Trying to do so leads to a project error. Project downgrader sites you can find in the Internet are useless, they don't work with this release. So what should do those Premiere Pro users that cannot update? I work in a big company with not-so-modern hardware which has Pr 25 and 25 installed and the company isn't gonna update because the newer Pr version the better hardware you need.Since Adobe does not recommend to use third-party project downgraders because:and they haven't come up with a credible solution of their own, I'd like to request an Adobe tool or a Premiere Pro feature (like in After Effects where you can save a project as 24.x or 23.x versions) to be able to downgrade a project or save it downgraded. I understand that the new Object mask needed to rework the save structure, but between saving a project with a mask but in 26.0 only and saving it without a mask but in any older version I think most people will choose the second variant.
Hello @adobe ,I am beginning to get frustrated about the fact that is is taking soooo long to improve the language of the adobe stock website.Problem (that has been there for years now): when I open the Adobe Stock website the language is in French. I live in Belgium (Flanders) and the language spoken here is Dutch. I know that Frenche is teached in schools here but the language spoken is Dutch.Questions: can you please improve the language module of adobe accounts???Ideas: 1 - change the settings for people in Belgium:- When people live in Flandersregion of Belgium, change the language standard to Dutch.- When people live in Walloon region of Belgium, change the language standard to French. 2 - If the first idea is so hard, please make it easier to change the language with a simple dropdow or switch at the top of the website. Please be so kind and make finaly make this change after al these years.
https://adobevideotraining.com/video/getting-started/ https://community.adobe.com/t5/premiere-pro-discussions/premiere-pro-beginner-tutorials-missing-audio-files/m-p/15658230#M577688 https://community.adobe.com/t5/premiere-pro-discussions/tutorial-files/td-p/15674271 There are several tutorials with audio files missing in their project files.
Speed ramping is now a basic requirement in professional video editing. In 2026, editors expect to create smooth, cinematic speed changes quickly and intuitively. DaVinci Resolve and Final Cut Pro meet this expectation. Adobe Premiere Pro does not.Final Cut Pro makes speed ramping straightforward and fast. Speed changes are visible directly on the clip, easing is handled automatically, and results are smooth with minimal effort. The workflow is designed for speed and consistency.DaVinci Resolve offers an equally modern experience. Its speed curve editor gives editors full visual control over motion, allowing precise shaping of ramps without unnecessary steps. The system feels current, efficient, and purpose-built for modern footage like drone and gimbal shots.Premiere Pro, on the other hand, still relies on an outdated time remapping workflow. Editors must dig through menus, split keyframes manually, and carefully adjust small handles just to achieve basic results. Even after all that, motion often feels stiff without extra tweaking.For professionals working under deadlines, this is more than an inconvenience — it’s a workflow problem. Many editors now leave Premiere entirely or use Resolve or Final Cut specifically for speed ramps.The frustration isn’t about missing features. It’s about missing modern design. In 2026, speed ramping should be visual, intuitive, and fast. Resolve and Final Cut prove this is possible. Premiere Pro’s approach feels stuck in the past — and that gap is becoming harder to ignore.
I would appreciate having a feature Final Cut just launched and should have been in PP for a decade:Edit to beat / Music grid by BPM. Let me pick my BPM and let it display a grid where I can edit to 8th/16th 1 bar of music etc. There's no need for AI. this can be done quickly.
Quick Preface:Sorry for dumping a quick AI written feature request. I'm currently mid project and I wanted to quickly get this up before I forget, but after realizing that premiere's console feature is so robust at isolating and identifying bottlenecks, I at a loss for why they don't just translate this information for less technically inclined individuals. Of course, a lot of these issues are true RTFM or "let me google that for you" type things, but realistically it would be way easier if they were to cut out the middle man and just identify your bottlenecks and recommend solutions / link to help or FAQ threads.SummaryPremiere Pro should include a user-facing "Performance" or "Bottleneck" panel that surfaces the diagnostic information the application already collects internally. This would help users identify what's causing timeline slowdowns without needing to dig through debug logs or guess at solutions.The ProblemPremiere Pro already tracks detailed performance metrics internally:Async source timeouts (with specific file names and frame numbers)Frames dropped during playbackPreroll and prefetch timesRender times per frameCodec decode issuesGPU acceleration failuresVFR detectionProxy/source mismatches This information is logged to debug consoles and log files that most users don't know exist, can't easily interpret, and aren't designed for troubleshooting. Meanwhile, users experience sluggish timelines and have no insight into why—leading to hours of trial-and-error troubleshooting, forum searches, and frustration.The application knows exactly what's causing the slowdown. It just doesn't tell the user.Suggested SolutionAdd a "Performance" panel (Window > Performance) that displays real-time and historical diagnostics in plain language:Real-time indicators:Current playback status (smooth / dropping frames / buffering)Which clip or effect is causing delaysWhether the bottleneck is CPU decode, GPU render, disk I/O, or RAMIssue detection with recommendations:"Variable Frame Rate detected in [clip]. This may cause proxy sync issues. [Learn more] [Conform to CFR]""Async decode timeout on [clip]. Consider transcoding to an edit-friendly codec or creating proxies.""GPU acceleration unavailable for [effect]. Rendering on CPU.""Disk read speed insufficient for [resolution/codec]. Media is on [drive type]."Session log:Scrolling list of performance events during the sessionFilterable by severity (info / warning / error)Clickable entries that navigate to the problem clip in the timelineWhy This Matters:Users shouldn't need to enable debug consoles and parse log files to understand why their edit is lagging. When Premiere detects a problem—and it does detect these problems—that information should be accessible in a way that helps users take action.This is especially important as source media becomes more varied. Content from smartphones, screen recordings, streaming rips, and consumer cameras often uses codecs and frame rate modes that aren't ideal for editing. Users working with this footage deserve to understand what's happening rather than assuming their hardware is inadequate or that Premiere is simply "slow."Surfacing existing diagnostic data in a user-friendly way would significantly improve the editing experience and reduce support burden.EnvironmentPremiere Pro 2025Windows 11Issue encountered while troubleshooting VFR HEVC footage with proxy workflow
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.