PowerPoint AutoSave Creates Conflict Copy After Coauthoring: Fix

You are working on a shared PowerPoint presentation with a colleague. When both of you edit the same slide, AutoSave kicks in and creates a file named “Conflict Copy of [filename].pptx.” This duplicate file appears in your OneDrive or SharePoint folder, not in the Recycle Bin. The conflict copy is a safety mechanism, but it can confuse version history and clutter your storage. This article explains why AutoSave creates conflict copies during coauthoring and provides steps to prevent or manage them.

Why AutoSave Creates Conflict Copies During Coauthoring

PowerPoint uses AutoSave to write changes to the cloud every few seconds. When two or more people edit the same presentation simultaneously, the coauthoring engine tries to merge edits in real time. A conflict copy appears when the merge fails because two users changed the same piece of content—like the same text box or image—at nearly the same instant. The engine cannot decide which version to keep, so it saves the conflicted data as a separate file.

This behavior is designed to prevent data loss. Without conflict copies, one user’s changes would overwrite the other’s without warning. However, the mechanism creates duplicate files that are not automatically deleted. Users often find these copies in the OneDrive or SharePoint document library, not in the presentation’s version history.

Technical Root Cause

The conflict arises from the way PowerPoint handles collaborative editing locks. When User A edits a paragraph, PowerPoint places a temporary write lock on that paragraph. If User B edits the same paragraph within the same sync cycle—usually 1 to 3 seconds—the server receives two conflicting write requests. The server saves User A’s changes to the main file and creates a conflict copy containing User B’s changes. This is not a bug; it is a deliberate safety design in the Office coauthoring protocol.

Steps to Stop AutoSave From Creating Conflict Copies

You can prevent conflict copies by disabling AutoSave for shared presentations or by adopting editing practices that avoid simultaneous edits on the same object. Follow these methods in order.

Method 1: Disable AutoSave for a Single Shared Presentation

1. Open the shared presentation
   Launch PowerPoint and open the file that is stored on OneDrive or SharePoint. The file must be a cloud-saved file for AutoSave to be active.
2. Locate the AutoSave toggle
   Look at the top-left corner of the PowerPoint window. The AutoSave toggle is a switch next to the file name in the title bar. It shows “On” with a blue background or “Off” with a gray background.
3. Turn AutoSave off
   Click the toggle to set it to “Off.” A confirmation dialog may appear warning that changes will no longer save automatically. Click “Disable” to confirm. PowerPoint will now require manual saving with Ctrl+S or File > Save.
4. Communicate with coauthors
   Tell everyone editing the file to turn off AutoSave on their copies. If one person leaves AutoSave on, conflict copies can still occur when that person saves.

Method 2: Disable AutoSave Globally for All Presentations

1. Open PowerPoint options
   Click File > Options. The PowerPoint Options dialog opens.
2. Go to the Save tab
   In the left pane, click Save. This tab contains all AutoSave and AutoRecover settings.
3. Uncheck AutoSave
   Under the Save Presentations section, uncheck the box that says “AutoSave OneDrive and SharePoint Online files by default on PowerPoint.” Click OK to apply.
4. Restart PowerPoint
   Close and reopen PowerPoint. AutoSave will be off for all new and existing cloud files until you re-enable it.

Method 3: Use Version History Instead of Conflict Copies

1. Open the presentation
   Open the file where a conflict copy appeared.
2. Access Version History
   Click File > Info > Version History. A pane opens on the right showing a list of saved versions with timestamps and author names.
3. Review and restore a version
   Click a version to open it in a separate window. Compare it with the current file. If you need to restore that version, click the three dots next to it and choose “Restore.” This method keeps all changes in one file and avoids creating conflict copies.

If PowerPoint Still Creates Conflict Copies After Disabling AutoSave

Conflict copies appear even with AutoSave off

If AutoSave is off but conflict copies still appear, check the OneDrive sync status. Right-click the OneDrive icon in the system tray and select “Pause syncing” for 2 hours, then resume. A stalled sync can cause the server to treat manual saves as conflicting writes. Also verify that all coauthors have AutoSave disabled. If one person has it on, that person’s manual save can still trigger a conflict.

Conflict copies have names like “v1.0” or “v2.0”

These are not true conflict copies. They are version labels created by SharePoint when a file is uploaded or replaced. They appear in the document library as separate items but do not contain conflicted data. You can safely delete them from the library. To prevent them, avoid uploading a new version while someone else is editing. Use File > Save As to create a new file instead of overwriting the existing one.

Conflict copies appear for files stored locally

AutoSave and coauthoring only work for files stored on OneDrive or SharePoint. If you see conflict copies for a local file, check whether the file is actually synced to the cloud. Open File Explorer, navigate to the file, right-click it, and select “Properties.” On the General tab, look for the location path. If it contains “OneDrive” or “SharePoint,” the file is cloud-based. If it is truly local, the conflict copy is likely a system backup created by AutoRecover, not a coauthoring conflict.

AutoSave On vs Off: Conflict Copy Behavior Comparison

Item	AutoSave On	AutoSave Off
Conflict copy creation	Automatic when simultaneous edits conflict	Only if two users save manually at the exact same moment
Data loss risk	Low — conflicted data is saved in a separate file	Higher — manual saves can overwrite without conflict detection
Version History availability	Automatic versions every few seconds	Only versions created at manual save points
Recommended for	Teams that need real-time collaboration and accept occasional conflict copies	Teams that prefer manual version control and zero duplicate files

Now you can prevent conflict copies by disabling AutoSave for shared presentations or by using Version History as the primary recovery method. If you continue coauthoring with AutoSave on, ask your team to avoid editing the same text box, shape, or chart at the same time. For advanced control, set up a SharePoint document library with required checkout to prevent simultaneous edits entirely.