---
id: troubleshooting.copied-but-original-couldnt-be-removed
url: https://storagestudio.us/faq/troubleshooting/copied-but-original-couldnt-be-removed
category: "Troubleshooting & messages"
subcategory: "Moves and copies that didn't finish"
question: "What does \"was copied successfully, but the original couldn't be removed afterwards\" mean?"
alt_questions:
  - "copied successfully but original couldn't be removed"
  - "original still using space after move"
  - "move finished but no space freed"
  - "storage studio couldn't delete the original after copying"
  - "duplicate left behind after move"
short_answer: "The copy finished and was verified, but the original couldn't be cleared, so it still uses space. Your data is safe — quit apps using the folder and run the move again."
tags: ["move", "free space", "cleanup"]
related: ["https://storagestudio.us/faq/troubleshooting/mac-wouldnt-let-storage-studio-move", "https://storagestudio.us/faq/troubleshooting/folder-in-use-right-now"]
applies_to: "all"
last_reviewed: 2026-10-01
---

# What does "was copied successfully, but the original couldn't be removed afterwards" mean?

The copy on your drive finished and was checked, but Storage Studio couldn't clear the original from your Mac afterwards — so the folder is still using space on the internal disk. Your data is safe; you simply have two copies for now.

This usually happens when an app still has a file in that folder open, or macOS refused the removal.

### What to do
1. Quit apps that might be using the folder.
2. Run the move again — it will recognise the copy already on the drive.
3. If it still won't clear, check that Storage Studio has Full Disk Access in **System Settings → Privacy & Security**.

See [why space didn't go up after a move](https://storagestudio.us/faq/moving-folders/).