Short answer: When Premiere Pro autosave is sending files to the wrong location, it is almost always because of two things: the Scratch Disks setting and the location of the project file itself. When either of those changes — because the project was moved, a drive was renamed, a scratch disk path was never explicitly set, or a cloud sync service restructured the folder path — autosave starts sending files somewhere unexpected. The fix is to explicitly set a stable, consistent autosave path in Scratch Disks preferences rather than relying on the default “Same as Project” behavior.
Autosave is one of the most important safety features in Premiere Pro — until you need a recovered version and cannot find where it went. When Premiere Pro autosave is sending files to an unexpected folder, it does not mean something is broken with the software. It means the autosave path is being determined by a setting that either was never explicitly configured, or changed quietly as a side effect of something else — a moved project file, a renamed drive, or a cloud sync service reorganizing folders in the background.
Understanding how Premiere Pro decides where autosave sends files makes the fix straightforward. There is one main preference to adjust and a handful of common scenarios that cause that preference to behave unexpectedly. Once the path is set to a fixed, reliable location, Premiere Pro autosave sending files to the wrong place stops happening — and stays stopped.
This guide explains exactly how Premiere’s autosave path logic works, covers every scenario that disrupts it, and gives you a clear fix for each one — including how to set a permanent autosave destination that does not shift every time a project moves or a drive changes.
Why Premiere Pro Autosave Sends Files Where It Does
Before getting into fixes, it helps to understand how Premiere determines the autosave location in the first place. There are two layers involved.
Layer 1 — The Scratch Disks Setting
Premiere Pro stores autosave files based on the Project Auto Save path defined under Scratch Disks. You can access this in two ways: through Edit → Preferences → Scratch Disks (Windows) or Premiere Pro → Preferences → Scratch Disks (Mac), or per-project through File → Project Settings → Scratch Disks. The setting has three possible states:
How the autosave path gets resolved
.prproj fileLayer 2 — Whether the Project File Has Been Saved
If you are working on a new project that has never been saved to disk, Premiere does not have a project folder to use as a reference point. In that case, it falls back to a temporary system directory — typically deep inside your AppData (Windows) or Library folders (Mac) — which is why autosave files sometimes appear in locations that seem completely unrelated to your work.
The practical takeaway is simple: save your project file to a proper, local folder the moment you create it. Everything else — autosave location, media cache proximity, scratch disk behavior — becomes much more predictable once the project file has a real home.
What’s Making Premiere Pro Autosave Send Files to the Wrong Location
Scratch Disks left as “Same as Project”
The default setting follows the project file location. If the project file moves or lives in a cloud-synced folder, autosave moves with it — often somewhere unexpected.
Project file was moved after creation
Moving the .prproj file to a new folder changes where “Same as Project” points, so new autosaves go to the new location while older saves remain in the old one.
Drive letter or name changed (Windows)
If the drive where your project lives was reassigned a different letter, the scratch disk path Premiere remembered is now broken — and it falls back to an unpredictable default.
Cloud sync interference
OneDrive, Dropbox, and Google Drive can redirect or shadow folder paths. Projects saved inside cloud-synced folders often produce autosaves in sync cache subdirectories rather than the expected location.
Project was never saved before editing began
Working on an unsaved new project means Premiere has no project folder to reference, so it writes autosaves to a system temp location.
Per-project scratch disk override
Scratch disk settings can be saved per-project as well as globally. A per-project setting from an older project can conflict with your current global preference, sending autosaves somewhere you didn’t expect.
How to Fix It — Step by Step
Set an Explicit Autosave Path in Scratch Disks Preferences
This is the most reliable, permanent fix. Instead of letting Premiere determine the autosave location based on where the project file is saved, you specify a fixed folder that never changes. Every project — regardless of where its .prproj file lives — will write autosaves to the same predictable location.
Create a dedicated folder on your local drive for autosaves — for example, D:\Premiere Autosave on Windows or /Users/[Name]/Documents/Premiere Autosave on Mac. Using a local drive (not a cloud-synced folder) is strongly recommended.
Open Premiere Pro and go to:
Windows: Edit → Preferences → Scratch Disks
Mac: Premiere Pro → Preferences → Scratch Disks
Find the Project Auto Save row. Click the dropdown next to it — it likely says Same as Project — and change it to Browse.
Navigate to the dedicated autosave folder you created in Step 1 and click Select Folder (Mac) or OK (Windows).
Click OK to close the Preferences panel. From this point on, every autosave will go to the folder you specified — regardless of where the project file is saved.
Premiere Autosave → [Project Name] keeps everything clean and searchable when you need to recover a specific version.
Check and Update the Per-Project Scratch Disk Setting
Premiere Pro stores scratch disk settings both globally (in Preferences) and per-project (in Project Settings). If a project was set up with its own scratch disk path at some point — even from a template or a duplicated project — that per-project setting overrides the global preference. This is a common reason autosave goes to an unexpected location even after you’ve updated your global Preferences.
With your project open, go to File → Project Settings → Scratch Disks.
Look at the Project Auto Save row. Note the path shown — if it differs from your intended autosave folder, this is the conflict.
Click the dropdown and select Browse, then navigate to the correct autosave folder and confirm.
Click OK and save the project. Premiere will now use this path for all future autosaves within this specific project.
Save the Project File Locally Before Editing Begins
If your project file is unsaved, living in a temporary location, or hasn’t been given a proper destination yet, Premiere falls back to a system temp folder for autosaves. The fix is immediate: save the project file properly before you start editing.
As soon as you create a new project, go to File → Save As and save it to a dedicated project folder on your local drive — for example, D:\Projects\[Project Name]\[Project Name].prproj.
Make this the first thing you do before placing any media or making any edits. Once the project file has a stable location, “Same as Project” scratch disk behavior becomes reliable again.
Avoid saving project files to the Desktop or Downloads folder — these are not stable long-term locations and tend to get cleaned up or reorganized in ways that disrupt relative paths.
Move the Project File Out of Cloud-Synced Folders
Storing active Premiere Pro project files in a cloud-synced folder — OneDrive, Dropbox, Google Drive — is one of the most common causes of misdirected autosaves. Cloud sync clients can restructure folder paths, lock files mid-write, or create local cache copies of files in subdirectories that Premiere then treats as the project’s location.
Close the project in Premiere Pro.
Pause syncing in your cloud app (OneDrive, Dropbox, or Google Drive) before moving any files.
Move the .prproj file — and its accompanying media folder if applicable — to a local drive location outside the cloud-synced directory. For example, move it from C:\Users\[Name]\OneDrive\Projects\ to D:\Projects\[Project Name]\.
Reopen the project from its new local location. Premiere may ask you to relink media — use File → Link Media to point it to the moved files.
Resume cloud syncing. If you want cloud backup, sync the project folder manually after each session rather than keeping it inside a live sync directory during active editing.
Reassign the Scratch Disk After a Drive Letter Change (Windows)
On Windows, if the drive where your project lives was reassigned a different letter — after reconnecting an external drive, after a system change, or after a Windows update — Premiere’s saved scratch disk path now points to a location that no longer exists. Premiere falls back silently rather than throwing an error, which means autosaves continue to run but land somewhere unexpected.
Go to Edit → Preferences → Scratch Disks and look at the path shown for Project Auto Save.
If the path references a drive letter that is no longer valid or not connected, that is the problem. Open File Explorer to confirm which drive letter your project drive is currently assigned.
Back in Scratch Disks preferences, click Browse next to Project Auto Save and navigate to the correct path using the current drive letter.
Click OK to save the preference.
To prevent drive letter changes from causing this again: in Windows Disk Management, right-click the drive and assign it a permanent letter that won’t conflict with other drives on the system.
Practical Tips for Reliable Autosave Going Forward
Keep one dedicated autosave folder
Set a fixed, global autosave path in Scratch Disks preferences rather than relying on “Same as Project.” One folder for all autosaves is easier to search and harder to lose.
Always edit from a local drive
Keep active project files on a local SSD or HDD. Use cloud storage for finished backups, not for live editing. This prevents cloud-sync interference with scratch disk paths entirely.
Save the project file first, edit second
Before placing a single clip, do a File → Save As to give the project file a proper location. This ensures the autosave path is defined from the very first save interval.
Increase the autosave count
In Preferences → Auto Save, increase “Maximum Project Versions” to at least 20. More versions means a longer recovery window if you need to go back several steps after an unexpected issue.
Shorten the autosave interval for long sessions
The default interval is 15 minutes. For intensive editing sessions, reducing it to 5 minutes in Preferences → Auto Save means you lose at most 5 minutes of work if something goes wrong.
Know where to look for lost autosaves
If you need an autosave and can’t find it, check alongside the project file first, then C:\Users\[Name]\Documents\Adobe\Premiere Pro\[Version]\ on Windows or ~/Documents/Adobe/Premiere Pro/[Version]/ on Mac — these are common fallback locations.
Quick Reference — Situation and Fix
| What You’re Experiencing | Most Likely Cause | Start With |
|---|---|---|
| Autosaves going to a random folder, no clear pattern | Scratch Disks left as “Same as Project” with no stable project location | Fix 1 (set explicit autosave path) |
| Autosave location changed after you moved the project file | “Same as Project” followed the file to its new location | Fix 1 or Fix 2 (set a fixed path) |
| Autosave goes to a different place for each project | Per-project scratch disk overrides differ between projects | Fix 2 (check per-project settings) |
| Autosaves appear inside a OneDrive / Dropbox folder | Project file stored in a cloud-synced directory | Fix 4 (move project out of cloud folder) |
| Autosaves going to a system temp folder | Project file was never saved before editing began | Fix 3 (save project locally first) |
| Autosave path broke after reconnecting an external drive | Drive letter changed, old scratch disk path now invalid | Fix 5 (reassign scratch disk after drive change) |
Common Variations
Autosave files are going to the right folder for some projects but the wrong folder for others
This is the per-project scratch disk override pattern. Each project can store its own scratch disk settings independently of the global preference. Open each affected project and check File → Project Settings → Scratch Disks to see what path it has stored. Updating each one to match your intended path, or switching all of them to “Same as Project” after confirming a stable project file location, resolves the inconsistency.
Premiere Pro is creating the autosave folder correctly but inside a cloud sync directory
The project file is saved inside a OneDrive, Dropbox, or Google Drive folder, and “Same as Project” is working as intended — it’s just that “the project” is inside a cloud directory. The resolution is to move the project file to a local folder (Fix 4) rather than changing the autosave path, which keeps your project structure clean and predictable.
Can’t find any autosave files at all
If autosave files don’t appear to exist, first confirm that auto-save is actually enabled: go to Edit → Preferences → Auto Save (Windows) or Premiere Pro → Preferences → Auto Save (Mac) and check that “Automatically Save Projects” is checked and the interval is set to a reasonable value. Then use your operating system’s search function to search for files named *.prproj that were modified in the last few hours — this reveals wherever Premiere has been writing them, even if it’s somewhere unexpected.
Autosave is working but filling up the wrong drive with large files
If the autosave folder is set to a drive with limited space — particularly a system SSD — it can fill up quickly during long editing sessions with large projects. Update the scratch disk path (Fix 1) to point to a secondary drive with more available space, and set a reasonable maximum version count in Preferences to prevent the folder from growing indefinitely.
After updating Premiere Pro, autosave started going somewhere new
Major Premiere Pro updates occasionally reset certain preferences to defaults. If that happened, the Scratch Disks preference may have reverted to “Same as Project” even though you previously had a fixed path set. Check Edit → Preferences → Scratch Disks after any significant update and re-confirm your autosave path is still set correctly.
