Premiere Pro 27.0: Project Name Reverts After Save As, Risk of Losing Edits
- 6 replies
- 25 views
- Translate
System Information
-
Application: Adobe Premiere Pro 27.0
-
Operating System: macOS
-
Hardware: Mac Studio (Apple M5 Max, 64 GB RAM)
-
Frequency: Recurring across multiple projects
-
Environment: Professional video editing workflow
Summary of the Issue
Since upgrading to Premiere Pro 27.0, I have repeatedly encountered a serious issue where a project unexpectedly reverts to its previous filename during editing, even after using "Save As" to create a project under a new name.
More concerningly, in one instance, Project Manager generated a project file containing none of the edits made after the project was saved under its new name.
This raises serious concerns about project integrity, potential data loss, and the reliability of Premiere Pro's saving mechanisms.
Steps Taken and Observed Behavior
The following incident occurred on November 17, 2026.
-
I opened an existing project named
1111_001.prproj. -
I selected File > Save As and saved the project under a new name,
1117_002.prproj. -
I continued editing the project under the new name.
-
After editing, I used Project Manager to collect the project and associated media files.
-
However, the Project Manager output folder contained the original
1111_001.prprojinstead of1117_002.prproj. -
When I opened the exported
1111_001.prproj, none of the edits made after creating1117_002were present. -
After investigating, I discovered multiple Auto-Save files for
1117_002inside the Adobe Premiere Pro Auto-Save folder. -
I opened the most recent Auto-Save file and appeared to recover my editing work. However, I cannot confidently verify that all edits were preserved.
Additional Observations
I have repeatedly experienced the following behavior in other projects:
-
After using Save As, the project name displayed in Premiere Pro unexpectedly changes back to the previous name during editing.
-
This occurs without intentionally reopening the original project.
-
I checked Window > Projects and confirmed that only one project was open at the time of inspection.
-
This does not appear to be a simple case of accidentally switching between multiple open projects.
The exact action that triggers the filename reversion has not yet been identified.
Major Concerns
1. Unreliable project identity and saving behavior
After using Save As, Premiere Pro may unexpectedly display the previous project name. This makes it difficult to determine which project file is actually receiving subsequent edits.
2. Project Manager output does not reflect recent editing work
In the incident described above, Project Manager produced a project containing none of the edits made after saving under the new name.
3. Auto-Save may not guarantee recovery of the latest editing state
If the project editing state itself unexpectedly reverts to an earlier version and Auto-Save continues afterward, the most recently timestamped backup may not contain the most complete editing work.
I have not confirmed that the editing state itself automatically reverted. This remains a concern requiring investigation.
Expected Behavior
-
A project saved under a new name should retain that name during the editing session.
-
Subsequent edits should be saved to the intended project file.
-
Project Manager should produce a project containing the correct, current editing state.
-
Auto-Save should preserve accurate and recoverable snapshots of the editing state.
Actual Behavior
-
The project name unexpectedly reverts to its previous name during editing.
-
Project Manager generated a project with the previous filename and none of the subsequent edits.
-
The expected project was found among Auto-Save backups.
-
The completeness of the recovered editing work remains uncertain.
Questions for Adobe Engineering
-
Is Adobe aware of this issue in Premiere Pro 27.0?
-
Could this behavior affect which project receives saved edits or which project state is processed by Project Manager?
-
Is there a known workaround?
-
Is a fix being investigated or planned?
-
Are there any diagnostic logs I can provide to help identify the cause?
Request for Investigation
This issue directly affects the reliability of professional editing projects and creates a serious risk of losing completed work.
Until the cause is identified and a fix is available, I intend to revert to an earlier, more stable version of Premiere Pro.
I would appreciate a thorough investigation and guidance on preventing further loss of editing work.
Thank you for your attention to this matter.
