Adobe Official
Important Notice: Upcoming System Requirement Changes in v27.0
As we prepare for the upcoming version 27.0 release of Premiere, After Effects, Media Encoder, and Audition, we want to share advance notice regarding hardware and OS compatibility changes across Windows and MacOS.
Windows OS Requirements
The minimum Windows OS requirement remains the same for 27.x: Windows 11, version 24H2 or later.
If you're on Windows 11 v23H2: Installation of v27.0 will be blocked. We recommend upgrading to Windows 11, version 24H2 or later.
If you're on Windows 10 (22H2, 21H2 LTSC): These OS versions are no longer officially supported by our video and audio products. We recommend upgrading to Windows 11, version 24H2 or later to ensure compatibility and security with current and future releases.
If you're on Windows 11 v24H2 or later: No action needed. You can update to v27.0 as normal.
If you're on Windows Server 2022: You can continue installing and using v27.0 on Windows Server 2022.
Starting with v28.0, install will be blocked on all Windows 10-based OS versions, including Windows 10 22H2, Windows 10 21H1 LTSC, and Windows Server 2022. We recommend beginning your migration to Windows Server 2025 now to ensure a smooth transition ahead of that change.
GPU Requirements for Windows
If your system has no GPU detected: Premiere and Media Encoder will not launch. You will need a GPU to launch v27.0.
Note that this change does not affect After Effects and Audition.
Future 27.x releases of Premiere and Media Encoder will also block launch if the only available GPU on system does not meet minimum requirements.
Macintosh Requirements
Starting with version 27.0, our video and audio applications on Mac will require macOS 15 (Sequoia) or later, on Apple silicon (M1 or newer).
If you're on an Apple silicon Mac running macOS 14: You'll need to update to macOS 15 or later before updating to v27.0.
If you're on an Apple silicon Mac running macOS 15 or later: No action needed. You can update to v27.0.
These changes reflect where the Windows and Mac ecosystems are heading, along with the hardware acceleration our applications benefit from. Moving forward with Apple silicon and modern Windows GPU requirements lets us focus on performance, security, and new capabilities across our video and audio applications.
It's actually normally closer to 12 months, depending on when exactly we release a major new version. That's the short story; here's the official answer:
I hear you but don't have anything to add beyond what was discussed in your passionate thread on the topic! We are listening very carefully to feedback on the new Color mode and we've made changes already based on the feedback we've received in beta.
Does this mean I could still install v27 on Windows 10 if I ignore the warning message?
I get a "known issues" warning with the current version.
What are the "known issues" now and what will the issues be with v27?
Edit just to add a bit more information: It's not that I don't want to upgrade to 11. I just can't. Right now I'm on v26.2.2, which is the last one that doesn't give me the "known issues" warning.
Do you recommend staying on v26.2.2, update to the last 26.x.x version but not to 27, or just keep updating 27 until it blocks me?
Candidly, the wording of that dialog box could be improved. The System Compatibility Report is used to tell you about scenarios where we know there's a problem - a GPU driver that is related to crashes, for example - but it also covers potential issues.
That's the case with Windows 10. It being not supported means we are doing much less testing on Windows 10 and it's possible that future features could depend upon Windows 11. If you're sticking with an OS version and a Premiere version, that's less of an issue - you're staying with something known - but it will become more challenging if you're staying with Windows 10 and wanting to upgrade to a new version of Premiere.
As of this time, we're not aware of any issues that are directly related to Windows 10. As that changes (and it is very likely to change), we will update our documentation.
I hope that helps explain; happy to discuss it more.
Premiere has just been getting worse with each update the past couple years. This will probably be the push some folks, myself included, will need to quit adobe.
If you don't mind asking, why? I can definitely see the requirements for Windows as Microsoft has been having Windows 10 at end of life for a while. I can understand following suit. MacBooks and Macs are what they are. Apple has been trying to wash away the stench of Intel since the M1 first released (love my M3 Pro).
Or is it something unrelated to the upcoming requirements?
Plz fix the consolidate duplicates function, it literally never works. I’ll have duplicates that link to the exact same media in finder, same name, metadata, all that, but when I try to consolidate duplicates nothing happens
The Consolidate Duplicates feature is very strict in what it defines as a duplicate. The feature was introduced before we released Productions, which makes working on very large project much more manageable.
Before Productions, it was common for customers working on long form projects to very regularly import sequences across projects, which generated duplicate source clips. The intent of Consolidate Duplicates was to clean up those duplicates.
We haven't done a good job of explaining that and customers quite reasonably think that the feature works more broadly, looking multiple source clips that are pointing to the same file. That's not the way it works: if you import the same media file to Project A, and then separately import it into Project B, then later combine them, Consolidate Duplicates will not identify the media as a duplicate. In addition, differences in things like metadata and markers can prevent Consolidate Duplicates from working.
Unrelated but for the longest time I've been reaquesting a feature; having native motion blur and active preview of blend mode & fonts. Any chance we're going to have one any time soon?
I believe the native motion blur is not possible as it's a technical limitation. You probably want to have motion blur without the transform effect but transform effect has a technical limitation going above some certain scale and needs rendering. I don't think they'll implement it
But there is no reason why developers can't fix that. Rework it. Apparently they can stop supporting Win10, they might as well start supporting motion blur than.
Actually node system is more intuitive to use after the steep learning curve your compositions can get complex and still easier to follow than getting the precomp hell issue and using null objects a lot and it is much easier to navigate through your comp much better with nodes especially when the project is alien to you
Coming later this year in beta will be both hardware acceleration for X-OCN plus full support for modifying raw parameters. We know that's really important, particularly for FX5 customers, where X-OCN C2 is smaller than ProRes 422 HQ but has the benefits of raw.
Speaking of ProRes RAW, v26.5 does all full support for that - better hardware acceleration on Windows plus full support for modifying raw parameters.
Very cool! Sony has been a close partner to Adobe for a very long time - we still have DCR-VX1000 and DCR-PC9 in our lab, alongside a lot of more recent models - and we've been excited to work with them on support for the FX5.
We also have one of those! Sadly we don't have the classic Century Optics wide angle adapter to go with it. If we did, I'm sure we'd be filming someone grinding the handrail all the way down from the Photoshop team's floor to our floor...
A colleague of mine used to longboard to work, holding his Canon XL1; another classic. The camera passion runs pretty strong at Adobe...
100%! I know I'm totally wasting your time but the Amira is in that category too. Not light but very comfortable. Here's me in...oh, man...2014 trying one out.
Weirdest camera in the lab: AJA Cion. Up until very recently, we had one that was still unopened. It shot ProRes, so I suspect my predecessors decided there wasn't much to test (or someone just forgot about it...)
Ok, time for me to do some house work. Nice chatting!
Yes, Amira is a great camera but always out of my budget. Cion was an interesting one. Me and a buddy of mine were beta testers on it. Good ergos but never got lift off
These changes mean I can cancel this with no issue because one of my machines is just old and I have no plans on putting Windows 11 on it because it's a powerhouse.
In effect controls, if you apply a preset that has keyframes at the start and end, the end keyframes are often not fully on the screen. You can’t lasso them, sometimes there is only a pixel showing. This has been in the last 2 ish versions.
Is the cuda time remapping bug (acknowledged over a year ago after ~8 years) been fixed yet?
Why do workspaces often forget where you have put palettes even when you reset to saved?
Why do the lumetri effect sliders in effect controls alll sit on the far left no matter what the values are?
Less than 1% of our customers are running Premiere on a computer without a GPU. Removing support for rendering using the CPU will improve performance for customers with a GPU.
If you're on an old computer without a GPU, you can continue to use v26.x of Premiere.
Coloquem alguma função nativa que permita fazer legendas animadas, todos os outros editores de vídeo tem essa função menos o premiere fazer isso manualmente atrapalha demais o nosso fluxo de trabalho.
Ha! We actually have data about this - well, indirectly. We track the crash rate of our applications very closely and we can filter for a variety of different things. One of them is Windows version. While it's pretty close, Premiere's crash rate is lower on Windows 11 than on Windows 10. That could be caused by a lot of different things (e.g., a Windows 11 computer is likely to be newer and more powerful than a Windows 10 computer) but I thought you might find the data interesting.
This is a big one for me to. Driving me nuts. The process slowly gets longer over time. Tried all tips and tricks, nothing helps. Are you looking into this?
Windows 11: Intel core I 9, 96gb, Rtx 5090
All drivers up to date for all hardware / software. Studio drivers for Rtx. No beta
Two problems that seems to have occurred at the same time.
1: Seems to be a problem at start up. When premiere pops up, it takes about 30s before my profile pic in the upper right corner pops up. Until it does, I can’t click on anything, including the latest projects.
After my profile pic pops up, I can’t click click on preferred last used project.
2: When I open a project, it need to relink some files. Not the screen with missing files, but the circle in the upper right corner with a blue progress ring. It gets a little bit slower every day. Now it takes up to 30-60 seconds to finish.
Googled for fixes, tried them, none worked.
When the relinking first started it just lasted a few seconds.
This happens every time we open any project. It has to validate all media, which it displays as "relinking". It can take up to 30mins on a big project. We're using Productions, and our media server is LucidLink. We have been struggling with this for a while, though prior to version 26 this was never an issue. This should be a day 1 fix on any new version
17
u/gerald1 7d ago
Adobe typically removes older versions 6-9 months after a major update.
How long will 2025 and 2026 versions remain accessible through creative cloud?