Dragging a Google Drive item out of Finder’s File Provider location can move it rather than make a copy. Google warns that the cloud original can be trashed as a result. Choose copying deliberately when you need a separate local artifact.
Check the integration and intention
Confirm the active account and whether Drive uses File Provider. Google’s Mac guide distinguishes this behavior from legacy streaming, so an old habit may no longer produce the same outcome.
Decide whether you need to relocate the synchronized original or create an independent local copy. Record the original link and preserve important content before an operation affecting valuable project files.
Use an explicit copy action
Google’s File Provider guidance describes holding the Option key while dragging to copy rather than move. You can also use an appropriate explicit copy workflow supported by Finder. Check the destination and the operation indicated before releasing the item.
Use a noncritical test file to confirm unfamiliar behavior rather than experimenting on the only original. Ensure the needed ordinary file content is downloaded and readable before treating the local result as complete.
Verify both locations
Open the destination copy and check the cloud original through its authorized link. Confirm that the original remains in its intended location and that the local contents are usable. If the original moved or went to Trash unintentionally, stop and inspect the supported recovery route before making more changes. A local copy is independent of later cloud edits and needs its own approved storage controls. Native Google document entries are not ordinary full local documents, so use the appropriate export when you need a standalone deliverable.
References
Reviewed against the linked official product guidance on November 3, 2026. Features, limits, screen labels, and access can vary by account, platform, region, and organization policy.