Premiere Pro 2025 Crashes and Takes too much Volumes
Copy link to clipboard
Copied
Since the usage of premiere pro 2025, my mac crashes and freezes, since the volumes get to over 50GB, even though i am working with a very small project. It happens after a while and i dont know why. Never had this problem with the other Premoere Pro versions. I also cannot export. Very strange. I also have enough storage on my mac...
Copy link to clipboard
Copied
Guys, the temporary solution is to go back to the 2024 version. And to open projects from the 2025 edition in the previous version, export the projects in XML.
Copy link to clipboard
Copied
Going back to 2024 doesn't work for me... since I installed 2025, it has screwed up the 2025 version too...
Copy link to clipboard
Copied
Well, the performance of my 2024 version is no longer the same, everything is very slow, however, it was the most viable for me at the moment...
Adobe has to resolve this definitively... Even videos with proxy are crashing in both versions...
Copy link to clipboard
Copied
crashing at the simplest things like adding text graphics. App seems super unstable.
Copy link to clipboard
Copied
I am on a Mac Studio, 132gb RAM and an M2 Ultra... Everything was fine yesterday. Today it says "Adobe Premiere Pro 2025 is damaged and can't be opened" move to trash?
I have uninstalled and reinstalled - i have downgraded from 2025 to 2025.1 - same message. I have restarted my machine after uninstalling and reinstalling...I am on the latest iOS. WTF Adobe!? I have deadlines!!!! Evwerything was fine yesterday. Nothing changed. I was using premiere just fine before I left yesterday. I shut down before I leave, I come into work and turn it back on... what changed while my system was off and NOT using Premiere!? Don't make me have to switch to AVID and never us Adobe again.
Copy link to clipboard
Copied
Same problem i cant find what to do
Copy link to clipboard
Copied
I've been having this problem. It freezes my whole system and I end up losing the last 10 minutes of work.
Copy link to clipboard
Copied
same here on a macbook 14 m3 pro...constantly crashing, even on a small project with proxies prerendered. This was never necessary before, but even with proxies..superslow and unstable. Impossible to continue in a regular editing flow. Adobe MUST fix this issue soon, otherwise I will switch to Resolve and will not come back.
Copy link to clipboard
Copied
PREMIERE BETA 2025 SOLVES IT!!!
Copy link to clipboard
Copied
that works indeed!!! thank you so much!!!
Copy link to clipboard
Copied
I've been having the same issues and I think it's the audio tagging/enhance sound. Once I removed all that and just processed my sound the OG way it stopped crashing!
Copy link to clipboard
Copied
Hi, guys
Third party plugins, like Clarity might crash on exporting from Premiere 2025. The problem was solved by updating Waves Central and Clarity itsef.
Hope this helps.
Cheers,
Renato
Copy link to clipboard
Copied
JUST started having issues this morning. Was editing on 2025 yesterday without any issue, didn't do anything at all on my computer since then. Woke up to hopefully finish a project that's now due in an hour, Premiere Pro wasn't working. Restarted, reinstalled, cleared preferences and cache, even installed 2 previous versions of the program and they all freeze at startup.
MacBook Pro M2 Max
Mac OS 14.7.2 (23H311)
I'm updating the OS now to the latest Seqouia, hopefully that fixes things.
Copy link to clipboard
Copied
Try this:
Go to settings and privacy
Go all the way down to Security
You will find that " Adobe Premiere 2025 is prevented from opening ... " something says it cannot be verified from Adobe if it may harm the device.
Select open anyways. If it lags after you selected Open Anyways, Restart your macbook and try to open Premiere again and select Open.
Worked with me, Hope it works for you.
Copy link to clipboard
Copied
Thanks for this reply. What exactly should I check or change under "security"? These are the options shown:
Allow applications from:
- App store & known developers (:white_heavy_check_mark:️)
- App store
AAllowaccessories to connect:
- Ask every time
- Ask for new accessories (:white_heavy_check_mark:️)
- Automatically when unlocked
- Always
Filevault (on)
Lockdown mode (off)
---
What you've written does not seem to be an option nor do I see a place where that would be written. What should I look for? I'm having the same problem as OP. Thanks!
Copy link to clipboard
Copied
I tried adding it to "full disk access" which is a little before the "securty" section but that didn't work.
Copy link to clipboard
Copied
Literally cannot go a single session or more than an hour with Premiere crashing and all I'm doing is laying raw footage into timeline. Is this a joke?
Copy link to clipboard
Copied
@ninarrr
That sounds very frustarting.
Which version of Premiere Pro are you running? Which operaring system are you running? What are your system specifications? What type of source footage are you using? What Sequence settings are you using? What type of storage media are you using? Are you running any third-plugins, add-ons, or extensions for Premeire Pro? Are you activating any fonts?
Have you been able to make the time to go thorugh the following?
Copy link to clipboard
Copied
Dear friend, there is no point in asking too many questions. We are noticing here that the same frustrating issues are happening on different Apple device models and different configurations and systems... In general Premiere 2024 and 2025 not working properly for Apple users. A solution is needed between Adobe and Apple to understand what is happening.
Note: I'm still trying to cut simple iPhone videos with PROXY at the moment and everything is stuck!
Copy link to clipboard
Copied
First, I "solved" my Premiere crashing on startup issue by doing a full reformat and clean install of everything. It was frustrating because I was in the middle of a critical project and this took a few hours out of my day and couldn't finish the project in time. Mind you, I installed every app and plugin I was using when Premiere wasn't working, and yet it is now working.
Second, just last night I was having a similar issue editing iPhone footage in Premiere with proxies like you. Some clips ran like butter and some would totally lock up Premiere. It would be reading everything else instantaneously from my SSD but a select few clips couldn't be read instantly and slowed Premiere down so much that it wasn't reading the other footage temporarily, there was a delay of about a minute, and they were all in the same resolution, frame rate, color space and codec, but whatever. My solution was to play back ALL of the clips one-by-one, flag each individual clip that was slowing things down, drop those into Media Encoder, make new ProRes 422 HQ versions of those files, and then use those newly transcoded files INSTEAD of the originals OR the proxies, and they ran perfectly. I didn't even have to make proxies, full res was good enough. What's the point of ProRes proxies when I still had to manually transcode the files into ProRes to get it to work right? Why would a 4k ProRes file run faster than a 1080p, low-bitrate ProRes proxy? Something is wrong there. And I think you're right, there's a disconnect between Apple and Adobe, which is weird since so many creatives use Apple products.
Copy link to clipboard
Copied
Hi friend, thanks for your thoughts. It seems that the preview has improved because I uninstalled the program and reinstalled it as you suggested, but I had already done this before and I feel that all that slowness will soon return. I converted it to ProRes 422 HQ and when I tested it, I didn't see much difference in the preview of my project, I just noticed that the files had increased in size quite a bit, for example, an original file of 45.7 MB ended up with 853.8 MB when converted. But it could be a good alternative!
I think I'll stick with the original files because they've already been cut. I'm just not going to use a proxy because it's really slowing down more than the raw videos. If any clip continues to be slow, I'll change the clip. I've already saved these converted videos to use in emergency situations.
In any case, we continue to PLEASE ask Adobe to check these inconsistencies between Premiere projects with iPhone files.
Copy link to clipboard
Copied
Did you ever solve this? I've been having the same issue on my newer MacBook pro for months now, tried every troubleshooting tactic possible outside of doing a clean wipe of my hard drive, which im about to do now. Unfortunately with this issue all I've seen are people replying to their own posts, people responding with the same issue and people posting generic "solutions" and none of them work. This is a nebulous issue, which is frustrating.
Copy link to clipboard
Copied
Same here, have the problem and almost cannot work on my premier pro. 😞
Copy link to clipboard
Copied
Months and months passing and no response from Adobe? I simply can't accept large editing jobs anymore because Premiere doesn't support it... 40-second videos from an iPhone in PROXY are becoming almost impossible to edit... Everything is crashed!
Copy link to clipboard
Copied
Premiere Pro Freezing on Import & Crashing on Export (v25.1, Windows 11 24H2)
Issue Summary:
I’ve been experiencing frequent freezes in Premiere Pro (v25.1) on Windows 11 (24H2). The program consistently freezes when importing footage—whether using Ctrl + I or the File > Import menu option. In the past week alone, it has frozen five times, requiring a force quit via Task Manager.
Additionally, Premiere crashed my system completely during an export, forcing a full machine restart.
System Specs:
• OS: Windows 11 (24H2)
• CPU: Intel i7-14700KF
• GPU: NVIDIA RTX 4070 Ti Super
• RAM: 64GB
• Storage: 1TB Kingston Renegade NVMe (dedicated cache drive)
• Premiere Pro Version: 25.1
Troubleshooting Attempts:
• Reset preferences
• Emptied cache
• Restarted Premiere Pro
• Ensured GPU drivers and OS are up to date
Additional Notes:
• The issue occurs randomly but frequently
• Premiere becomes completely unresponsive when importing, requiring a force quit
• No other programs exhibit similar crashes or freezes
• The crash during export forced my entire system to restart
Has anyone else encountered this?

