Skip to main content
Participating Frequently
Nov 19, 2026 11:44 PM UTC
Investigating

Premiere Pro 27.0: Project Name Reverts After Save As, Risk of Losing Edits

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.

  1. I opened an existing project named 1111_001.prproj.

  2. I selected File > Save As and saved the project under a new name, 1117_002.prproj.

  3. I continued editing the project under the new name.

  4. After editing, I used Project Manager to collect the project and associated media files.

  5. However, the Project Manager output folder contained the original 1111_001.prproj instead of 1117_002.prproj.

  6. When I opened the exported 1111_001.prproj, none of the edits made after creating 1117_002 were present.

  7. After investigating, I discovered multiple Auto-Save files for 1117_002 inside the Adobe Premiere Pro Auto-Save folder.

  8. 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

  1. A project saved under a new name should retain that name during the editing session.

  2. Subsequent edits should be saved to the intended project file.

  3. Project Manager should produce a project containing the correct, current editing state.

  4. 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

  1. Is Adobe aware of this issue in Premiere Pro 27.0?

  2. Could this behavior affect which project receives saved edits or which project state is processed by Project Manager?

  3. Is there a known workaround?

  4. Is a fix being investigated or planned?

  5. 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.

    6 replies

    Amy the Stuv
    Community Manager
    Community Manager
    Nov 20, 2026 12:52 AM UTC

    Hello ​@秀雄23658077bjav 

    Welcome to the Premiere Community Forums. I was unable to reproduce this issue following the listed steps. The new project file was saved and remained open. I removed one of the 3 clips from the timeline, saved, then used the Project Manager and successfully just copied the new timeline and the 2 clips used in it. 

     

    This was off my One Drive. Could you let me know a little more about your setup? Where are your projects stored? Is this in a Premiere Production because I was only testing an individual project? If it was, did you Save As the same project within the Production and keep both within the Production? 

     

    If I can reliably reproduce your issue on my system, it can help expedite finding a solution and/or workaround, so please let me know any other information you think may be useful regarding your workflow. Thank you for bringing it to our attention!

    Amy

    Translate
    Participating Frequently
    Nov 20, 2026 12:55 AM UTC

    Hello Amy,

    Thank you very much for taking the time to test this issue and for your detailed response.

    I would like to clarify one important point about the behavior I am experiencing.

    The project name does not necessarily revert immediately after using "Save As." Instead, it unexpectedly changes back to the previous project name at some point while I am continuing to edit.

    This has occurred repeatedly across multiple projects since upgrading to Premiere Pro 27.0.

    My System and Project Setup

    • Computer: Mac Studio (Apple M5 Max, 64 GB RAM)

    • Operating System: macOS

    • Premiere Pro version: 27.0

    • Project storage location: Internal SSD of my Mac Studio (local storage, not OneDrive or a network drive)

    • Premiere Productions: Not used. I work with regular, standalone .prproj project files.

    Details of the Incident

    On November 17, 2026, I experienced the following issue:

    1. I opened an existing project named 1111_001.prproj.

    2. I used File > Save As to save it under a new name, 1117_002.prproj.

    3. I continued editing the project under the new name.

    4. After editing, I used Project Manager to collect the project and its associated media.

    5. However, the Project Manager output folder contained 1111_001.prproj instead of 1117_002.prproj.

    6. When I opened the collected 1111_001.prproj, none of the edits made after creating 1117_002 were present.

    7. I subsequently discovered multiple Auto-Save backups under the 1117_002 name, which appeared to contain my more recent editing work.

    In another occurrence, I checked Window > Projects and confirmed that only one project was open, even though the project name had unexpectedly reverted to the previous name.

    Important Clarification

    This is not simply an issue with the filename displayed in Finder. The project name shown inside Premiere Pro itself unexpectedly changes back during editing.

    I am particularly concerned that this behavior may affect which project file receives subsequent saves or which editing state is processed by Project Manager.

    I understand that the issue may be difficult to reproduce because I have not yet identified the exact action that triggers the name change.

    However, since this has happened repeatedly across multiple projects, I believe it deserves further investigation.

    Please let me know if there are any diagnostic logs, project files, or additional details I can provide to help reproduce and identify the issue.

    Thank you again for your assistance and for looking into this potentially serious problem.

    Best regards

    Translate
    Amy the Stuv
    Community Manager
    Community Manager
    Nov 20, 2026 8:39 PM UTC

    Hello ​@秀雄23658077bjav 

    Can you confirm that your Mac OS is 27.0 Golden Gate? Do you have Siri enabled system wide or is Premiere listed as an exception? Can you also confirm the primary language installed on your system? I’m running a wide sweep to try and get this diagnosed. I agree that this is potentially very series but I have still not been able to reproduce it. 

     

    Thank you for confirming that it is a solo project, not a Production. Can you give us an estimate of how long you might be editing before noticing this issue has occurred? If I provide you with a private upload link, would you be willing to provide the project files that presented this issue?

    Hoping to help!

    Translate