When working on an iPad or tablet in Adobe Fresco or Photoshop, you may occasionally see duplicate files appear with names like [Document Name] - Conflict Copy, or receive a prompt asking you to choose which version of a document to keep. These conflict copies are created when the cloud document engine detects that changes were made to a file from two different places before the latest version finished uploading. This commonly happens when switching between devices quickly, working with an unstable Wi-Fi connection, or letting your iPad go to sleep while changes are still syncing in the background.
Fast Fix
Do not delete either file immediately. Open both the original document and the Conflict Copy side by side to see which one has your latest layer edits. Copy any updated layers into the primary document, save it, and wait for the small cloud icon in the top navigation bar to display a check mark before closing the app.
Quick Status Snapshot
- Severity: Medium (duplicates files, uses extra storage, and can cause confusion about which version is current).
- Target Layer: Cloud Document sync engine (
.psdcpackage synchronization) and iPadOS background execution limits. - Devices Affected: Apple iPad (Photoshop for iPad, Adobe Fresco), Windows touch devices.
How Conflict Copies Are Generated
Cloud Documents rely on a continuous background process that uploads your changes in small, incremental chunks (deltas) as you paint or edit.
[iPad: Fresco/Photoshop Painting Session]
│
├── Edits Layer 4, 5, 6
│
▼
[iPad Screen Closes / Wi-Fi Drops] ──► Sync pauses mid-upload (Manifest v12 stalled)
│
▼
[User Opens Project on Desktop PC] ──► Reads last confirmed cloud version (v11)
│
├── User makes edits and saves (Creates v13)
│
▼
[iPad Reconnects to Wi-Fi] ──► Resumes upload of stalled v12 changes
│
▼
[CLOUD SERVER DETECTS DIVERGENT HISTORIES]
│
┌──────────────┴──────────────┐
▼ ▼
[Master Document] [Conflict Copy]
Retains Desktop Edits Forks iPad Edits to Safe Duplicate
This split happens for three specific reasons:
- iPadOS Background App Refresh Limits: iPadOS restricts background tasks to preserve battery life. If you leave an app or lock your iPad screen while an upload is in progress, the system can pause the app before the sync finishes.
- Multi-Device Race Conditions: If you work on an iPad and quickly switch to a desktop computer before the cloud sync finishes, the desktop opens an older version of the document. When the iPad reconnects later, the server protects your work by creating a conflict copy rather than overwriting your changes.
- Unstable Network Connections: High-latency Wi-Fi connections can cause the cloud document engine to time out while uploading large layered files. If it cannot verify that the file was written successfully, it creates a duplicate branch to avoid losing data.
If your brushes or library swatches are also failing to sync across your iPad and desktop apps, see Why Your Adobe Libraries Won’t Sync (Metadata Conflict).
Diagnostic Path: Merging and Cleaning Up the Conflict
[Conflict Copy Appears on Home Screen]
│
├──> Open both files: Are all the latest changes present in the Conflict Copy?
│ ├── YES ──► Delete the older file, then rename the Conflict Copy.
│ └── NO
│
└──> Are changes split between both documents?
└── YES ──► Merge layers manually across documents.
If mobile capture tools also report sync timeouts on your device, check the troubleshooting steps in Fixing Adobe Capture Asset Sync Failures on Android/iOS.
Step-by-Step Resolution
Step 1: Compare and Consolidate Your Documents
Never delete a conflict copy without checking its layers first:
- On your iPad, open the original file and review your recent adjustments.
- Return to the Home screen and open the file labeled Conflict Copy.
- Check the Layers panel to see which version contains your most recent work:
- If the Conflict Copy has everything: Open the Home screen, tap the three dots (…) on the older document, and select Delete. Tap the three dots on the Conflict Copy, select Rename, and remove the “Conflict Copy” suffix.
- If edits are split between both files: Open the Conflict Copy, tap the layer group containing your newest work, tap Copy Layers, open the main document, and select Paste Layers.
Step 2: Ensure Uploads Complete Before Closing the App
To prevent conflict copies from forming in the future, get into the habit of confirming that your files have finished syncing before closing your app or locking your screen:
- Look at the top navigation bar inside Fresco or Photoshop for the small Cloud icon.
- Do not exit the app or lock your iPad screen if the cloud icon shows an active spinner or an upload arrow.
- Wait until the icon changes to a Cloud with a check mark. This confirms that all layer deltas have been saved to the server and the version manifest is up to date.
┌──────────────────────────────────────────────────────────┐
│ iPad Navigation Header (Photoshop / Fresco) │
├──────────────────────────────────────────────────────────┤
│ [Back] Project_Layout_v2 (☁✓) [Undo] [Redo] [Share] │
│ ▲ │
│ │ │
│ WAIT FOR THE CHECK MARK BEFORE CLOSING │
└──────────────────────────────────────────────────────────┘
Step 3: Prevent iPadOS Background App Suspensions
Configure your iPad to give Adobe applications more time to complete uploads:
- Open iPad Settings.
- Scroll down the left sidebar and select Fresco or Photoshop.
- Ensure Background App Refresh is toggled On.
- Go to Settings > Display & Brightness > Auto-Lock, and temporarily set it to 5 Minutes (or Never) when working on large, multi-gigabyte illustrations to prevent the tablet from sleeping mid-sync.
Step 4: Clear Duplicate Files from the Cloud Trash
Once you have merged your layers, delete the conflict copy and remove it from the cloud trash so it doesn’t take up extra storage space:
- Delete the duplicate file from the app Home screen.
- Open a browser and visit
https://assets.adobe.com/deleted. - Locate the deleted conflict copy and select Permanently Delete (see Recovering Deleted Assets from the Adobe Cloud Recycling Bin).
Hard Stops
- Do not force-quit the application (swiping up from the app switcher) while working on large canvas files. Force-quitting immediately terminates the local sync engine’s write cycle, which almost guarantees a conflict copy or a damaged local manifest on the next launch. Always return to the Home screen and allow the cloud status check mark to appear before closing the app.