Skip to main content
Participant
Oct 27, 2026 1:47 AM UTC
Answered

Why is Premiere mask data bloating my auto save folder? It’s over 1TB

I used the automatic masking tool to mask out roughly two hours worth of footage. Over the course of working on my project for approximately 12 hours, this has led to my auto-save folder to bloat to over 1TB. I thought it was safe to delete old masking data from previous auto-saves, but then my project crashed and set me back 3 hours. When I tried to open an auto-saved project file, it was asking for mask data from a few days prior that I had already deleted. So it seems like the latest auto-saved mask data was not sufficient to open the latest auto-saved project file, which makes zero sense to me. 
 

Can anyone help? I’m trying to either cut down on the amount of mask data or find which files are safe to delete, but I’d like to keep auto-save on for project files because Premiere is crashing constantly on my computer.

    R Neil Haugen
    R Neil HaugenCorrect answer
    Legend
    Oct 27, 2026 4:57 PM UTC

    Yea, that’s what I would recommend. The masking data with the newer system is far more detailed than the old one was, and that could put tons of data in the project file in a hurry for long tracking.

     

    So typically one would make the tracking on a sequence, to the point it’s just as wanted, then dupe that ‘clip’ … then do a render/replace on the duped clip to dump the tracking data on the clip.

     

    And at that point, the next step .. and it’s a very solid safety move too! … is to do a Save-As to a new iterated project name, without the “now old” tracked clip in that project. You can always go  back to the previuos project and import that clip if you need to redo tracking, but … you don’t have the tracked data bloating the autosaves on the new project going forward.

     

    If you don’t, each autosave saves the exact same massive amount of data, and your autosaves balloon.

    Everyone's mileage always varies ...

    3 replies

    Participant
    Oct 27, 2026 11:53 AM UTC

    Thank you for your reply! That is indeed very frustrating since this a very useful tool for both color and VFX but has rendered it useless with my current workflow. 
     

    Just to make sure I understand your suggestion, I should do an initial masking, then export the masked section as a fully rendered asset to make further adjustments on? Or would rendering the masked section using the “In/Out Render Selection” tab also work to prevent this massive data bloat?

    Translate
    R Neil Haugen
    R Neil HaugenCorrect answer
    Legend
    Oct 27, 2026 4:57 PM UTC

    Yea, that’s what I would recommend. The masking data with the newer system is far more detailed than the old one was, and that could put tons of data in the project file in a hurry for long tracking.

     

    So typically one would make the tracking on a sequence, to the point it’s just as wanted, then dupe that ‘clip’ … then do a render/replace on the duped clip to dump the tracking data on the clip.

     

    And at that point, the next step .. and it’s a very solid safety move too! … is to do a Save-As to a new iterated project name, without the “now old” tracked clip in that project. You can always go  back to the previuos project and import that clip if you need to redo tracking, but … you don’t have the tracked data bloating the autosaves on the new project going forward.

     

    If you don’t, each autosave saves the exact same massive amount of data, and your autosaves balloon.

    Translate
    Everyone's mileage always varies ...
    R Neil Haugen
    Legend
    Oct 27, 2026 4:34 AM UTC

    That masking data is not tiny … when you have hours of data! That was your issue, actually. Yea, it’s frustrating but adding intensive masking always causes mass data storage. Which is why most of the colorists and vfx folks I know like to do as simpllified a masking trail as they can yet keep needed quality. And … as soon as possible, ‘render’ out a comp or something to replace the masked bit to get away from mass data issues.

    Translate
    Everyone's mileage always varies ...