How to Move a File

Moving a file relocates it from one folder to another, leaving nothing behind at the source. Where copying produces two independent files, moving produces only one file in a new location. For Unturned™ mod developers, moving is the operation you perform when reorganizing project folders, promoting prototype assets from a scratch folder into the official project structure, archiving completed work, or relocating misplaced files into their correct directories.

This article covers four methods to move files in Windows File Explorer, the important distinction between same-drive moves and cross-drive moves, and the safety considerations that distinguish move from copy. 57 Studios™ project organization relies on disciplined use of move operations to keep working folders clean and structured.

Prerequisites

You must have File Explorer open, configured with file extensions and hidden items visible, and be comfortable with navigation and copying. If you have not read the previous articles in this section, start with How to Open File Explorer and work forward.

What you will learn

• What moving actually does at the file system level
• The critical difference between moving on the same drive and across drives
• How to move with Ctrl + X and Ctrl + V
• How to move by dragging within the same drive
• How to move by dragging with Shift held to force a move across drives
• How to use right-click drag to choose copy or move from a menu
• When moves can fail and how to recover
• How move differs from copy in performance, safety, and recoverability
• How to verify a move completed correctly
• How professional modders structure project reorganisation around safe move patterns

What moving actually does

Moving works very differently depending on whether the source and destination are on the same drive or on different drives. Understanding this distinction is essential because it affects speed, reliability, and recoverability.

Same-drive moves are nearly instantaneous regardless of file size. Windows does not read or write any file bytes. Instead, it updates the file system's directory entries so the file's listing moves from the source folder to the destination folder. The bytes on disk stay exactly where they are.

Cross-drive moves are effectively a copy followed by a delete. Windows must read every byte from the source drive, write every byte to the destination drive, then delete the original file. The operation takes as long as a copy of the same size and can fail partway through.

This dual behavior matters in practice. Moving a 4 GB Unity asset bundle within C:\ is instant. Moving the same bundle from C:\ to D:\ takes as long as a full copy plus the source delete time.

The dual behaviour also affects recoverability. A failed same-drive move is unusual because the operation is metadata-only and is either fully committed or never started. A failed cross-drive move can leave the file in one of several states: source intact and destination empty (Windows aborted before writing), source intact and destination partial (write was interrupted), source intact and destination complete (write succeeded but source delete failed), or source missing and destination complete (the successful end state). The cross-drive failure modes are documented later in this article along with the recovery procedures for each.

Did you know?

The same-drive instant move is a property of the file system, not File Explorer. Any tool that uses the underlying Windows file APIs benefits from it, including PowerShell's Move-Item, the command-line move command, and most third-party file managers.

Did you know?

The metadata-only same-drive move means that a 100 GB file can be moved within a drive in roughly one millisecond. The file's bytes never leave their original disk blocks. Only the directory entries that point to those blocks are updated. The same is true for moving a folder containing terabytes of data: the move completes in milliseconds because only the folder's parent reference changes.

Method 1: Ctrl + X and Ctrl + V

The cut-and-paste keyboard shortcut is the most reliable move method.

1. Select the file or files you want to move.
2. Press Ctrl + X to cut the selection. The selected files appear faded in File Explorer.
3. Navigate to the destination folder.
4. Press Ctrl + V to paste.

The files disappear from the source folder and appear in the destination. If the move involves a cross-drive transfer, a progress dialog appears.

The faded appearance between cut and paste is the visual indicator that a cut is pending. The cut is not committed until you press Ctrl + V at the destination. If you change your mind before pasting, press Escape, copy a different selection, or close File Explorer. The faded appearance clears and the source remains untouched.

Pro tip

If you cut a file with Ctrl + X but then change your mind, press Escape or copy something else with Ctrl + C. The cut is cancelled and the source file remains intact. The faded appearance returns to normal.

Pro tip

The cut-and-paste shortcuts work across multiple File Explorer windows. You can cut in one window and paste in a completely separate window opened minutes later, as long as nothing has overwritten the clipboard in between. This makes Ctrl + X and Ctrl + V particularly useful when you need to navigate deeply to find the destination after the cut.

Method 2: Drag-and-drop within the same drive

When you drag a file between two folders on the same drive, File Explorer defaults to a move operation.

1. Open File Explorer to the source folder.
2. Open a second File Explorer window to the destination folder.
3. Verify both folders are on the same drive by checking the address bar.
4. Click and hold the file in the source window.
5. Drag the file to the destination window.
6. Release the mouse button.

The cursor displays a small move-arrow icon during the drag, confirming the operation is a move. Watch the tooltip text that appears near the cursor; it reads "Move to" followed by the destination folder name.

The cursor indicator is the primary visual feedback that distinguishes a move from a copy during drag. The straight arrow indicates move. A plus sign indicates copy. A curved arrow indicates create shortcut. Watch the cursor before releasing the mouse button. If the cursor shows an unexpected indicator, abort the drag by pressing Escape or dragging the file back to a neutral area before releasing.

Method 3: Drag-and-drop with Shift held (force move)

When the source and destination are on different drives, drag defaults to copy instead of move. Holding Shift forces a move.

1. Arrange source and destination windows side by side. The two folders must be on different drives for the default behavior to differ.
2. Click and hold the file in the source window.
3. Press and hold the Shift key.
4. Drag the file to the destination window.
5. Release the mouse button first, then release Shift.

The cursor displays the move-arrow icon while Shift is held, even though the drives differ. After the drop, the file disappears from the source and appears in the destination.

Common mistake

Forgetting to hold Shift during a cross-drive drag results in a copy, not a move. You end up with two files: one in the source and one in the destination. If you intended a move, you must then manually delete the source. This is an easy mistake to make and a common reason mod folders fill up with duplicates.

Common mistake

Releasing the Shift key before releasing the mouse button cancels the move-forcing behavior. The operation reverts to the default cross-drive behaviour, which is copy. If you accidentally produced a copy when you intended a move, the recovery is to delete the source file manually after verifying the destination.

Method 4: Right-click drag with menu

Right-click drag is the most explicit method. Windows presents a menu at the drop point so you choose the operation deliberately.

1. Click and hold the file in the source window using the right mouse button, not the left.
2. Drag the file to the destination folder.
3. Release the right mouse button at the destination.
4. A menu appears with four options:
   • Copy here
   • Move here
   • Create shortcuts here
   • Cancel
5. Click Move here.

This method is verbose but eliminates any ambiguity about what will happen. New mod developers benefit from using right-click drag for the first several weeks of file management work because the menu prevents accidental copies and moves.

The right-click drag menu also offers Cancel as an explicit fourth option. If you started the drag and then realised you targeted the wrong destination, choose Cancel to abandon the operation without any file-system change. This is more reliable than dragging back to a neutral area, which can sometimes trigger an unintended drop.

Comparison of move methods

Method	Speed	Skill level	Best context
Ctrl + X / Ctrl + V	Fastest	Beginner	Any move, any drive
Same-drive left drag	Fast	Intermediate	Both folders visible, same drive
Shift-held drag	Fast	Intermediate	Cross-drive move, both visible
Right-click drag menu	Medium	Beginner	When deliberate confirmation matters

Move behavior decision flowchart

Move method usage among professional modders

Ctrl + X and Ctrl + V dominates the move workflow for the same reason it dominates copy: keyboard shortcuts are faster than mouse operations and they behave consistently across same-drive and cross-drive contexts. Professional modders default to the cut-and-paste shortcuts and reserve drag methods for the specific case where both folders are visible side by side and the operation is clearly safe.

The 18 percent share for right-click drag with menu is higher than the equivalent figure for copy operations. This reflects the higher stakes of move: because the source is removed after the operation, modders are more inclined to use the verbose right-click method that surfaces the explicit Move command in a menu.

Cross-drive moves: failure modes and recovery

Cross-drive moves can fail in ways same-drive moves cannot. Knowing the failure modes lets you recover gracefully.

Failure mode	Cause	Result	Recovery
Destination drive full	Not enough free space	Move fails before delete	Source intact, free space and retry
Source file locked	App holding file open	Read fails	Source intact, close app and retry
Network drive disconnects	Wi-Fi drop, cable unplug	Move partially complete	Source intact unless near end
Filename too long	Combined path exceeds limit	Write fails	Source intact, shorten parent folder
Permission denied	No write access at destination	Write fails	Source intact, fix permissions
Antivirus blocks write	Real-time scanner flagged content	Write fails	Source intact, add exclusion or retry
USB drive removal mid-operation	User unplugged drive	Indeterminate state	Reconnect, verify both ends
Power loss during write	System lost power mid-copy	Indeterminate state	Verify both ends after reboot

In every common failure mode, the source file is preserved until the destination write is fully verified. This means a failed cross-drive move usually leaves you in the same state you started in. Same-drive moves are atomic at the file system level and either succeed completely or do not start.

Critical warning

Never move a file off a USB drive that is currently being unplugged or losing power. If the move is partway through writing the destination and the source drive disappears, the file system can be left in an inconsistent state. Always use the Safely Remove Hardware feature to disconnect external drives, and never move files immediately before unplugging.

Critical warning

Cross-drive moves of large files across slow or unreliable networks are vulnerable to mid-transfer failures. For a 10 GB cross-drive move that depends on a flaky Wi-Fi connection, prefer a copy followed by a manual delete after verification. The two-step approach lets you confirm the destination is intact before destroying the source.

Same-drive move versus cross-drive move

The same-drive versus cross-drive distinction is significant enough that it warrants a dedicated comparison.

Aspect	Same-drive move	Cross-drive move
Speed	Milliseconds regardless of size	Proportional to file size and drive speed
Bytes transferred	Zero	All bytes of the file
Atomicity	Atomic; either completes or never starts	Multi-step; can fail partway
Progress dialog	Not shown (too fast)	Shown for any move over a second
Recoverability on failure	Not applicable; never fails	Source preserved until destination verified
Cancellation	Not possible (too fast)	Possible during write phase
Drive contention	None	Both source and destination drives active
Effect on Recycle Bin	None	None for the move itself; replaced files may go to Recycle Bin

The asymmetry between same-drive and cross-drive moves has practical implications for mod project structure. Keeping all working assets on a single drive lets you reorganise the project structure freely with instant same-drive moves. Splitting assets across drives makes reorganisation slower because each cross-drive move becomes a full data transfer.

Moving an entire folder

Moving a folder is no different from moving a file in terms of method. Select the folder, then use any of the four methods. Windows moves the folder and every file and subfolder inside it.

For same-drive folder moves, the operation is still instantaneous regardless of how many files the folder contains. For cross-drive folder moves, the time depends on the total bytes of all files combined.

The progress dialog for a cross-drive folder move shows the count of items remaining alongside the bytes transferred. A folder containing many small files often shows a high item count and a slow byte-progression rate because the per-file overhead dominates. A folder containing a few large files shows a low item count and a fast byte-progression rate.

Best practice

Before moving a large folder across drives, verify there is enough free space at the destination. Right-click the source folder, choose Properties, and read the Size value. Compare it against the destination drive's free space shown in This PC. A few extra gigabytes of safety margin is wise.

Best practice

For cross-drive folder moves of important project assets, prefer a copy followed by manual deletion of the source after verification. The Copy-then-delete approach gives you an explicit verification step before destroying the source. Move's automatic delete is convenient but does not provide the verification opportunity.

Move and the Recycle Bin

The move operation does not engage the Recycle Bin for the moved file itself. The file is not deleted; it is relocated. However, if the destination folder already contains a file with the same name and you choose Replace in the conflict dialog, the replaced destination file may go to the Recycle Bin (on fixed drives) or be permanently removed (on removable or network drives).

Scenario	Recycle Bin involvement
Move with no conflict	No Recycle Bin involvement
Move with Replace option, fixed drive	Replaced file may go to Recycle Bin
Move with Replace option, removable drive	Replaced file permanently removed
Move with Skip option	No Recycle Bin involvement
Move with Keep both option	No Recycle Bin involvement

The Recycle Bin gap for removable and network drives is a frequent source of accidental data loss. A modder moving a file onto a USB drive that already contains a same-named file, and choosing Replace, permanently destroys the destination file with no recovery. Treat such moves as irreversible.

Verifying a move completed correctly

For routine moves, the post-move state is obvious: source folder no longer contains the file, destination folder does. For mission-critical moves or moves where the destination was uncertain, a verification step is worth the time.

# Verify a single move
$source = 'C:\Project\Assets\Crate.dat'
$dest = 'D:\Bundles\Crate.dat'

if (-not (Test-Path $source) -and (Test-Path $dest)) {
    Write-Host 'Move verified: source removed, destination present' -ForegroundColor Green
} else {
    Write-Host 'Move incomplete or failed' -ForegroundColor Red
    if (Test-Path $source) { Write-Host "  Source still exists at: $source" }
    if (-not (Test-Path $dest)) { Write-Host "  Destination missing at: $dest" }
}

The script verifies that the source path no longer exists and the destination path does. For a successful move, the first condition is true and the second is true. Any other combination indicates a partial or failed move that requires manual intervention.

For folder moves with many files, the verification extends to comparing file counts:

# Compare file count and total size before and after a move
$beforeCount = (Get-ChildItem 'C:\Project\Assets' -Recurse -File).Count
$beforeSize = (Get-ChildItem 'C:\Project\Assets' -Recurse -File | Measure-Object -Property Length -Sum).Sum

# Perform the move externally, then check destination
$afterCount = (Get-ChildItem 'D:\Bundles' -Recurse -File).Count
$afterSize = (Get-ChildItem 'D:\Bundles' -Recurse -File | Measure-Object -Property Length -Sum).Sum

if ($beforeCount -eq $afterCount -and $beforeSize -eq $afterSize) {
    Write-Host 'Folder move verified by count and size'
} else {
    Write-Host "Move discrepancy: $beforeCount/$afterCount files, $beforeSize/$afterSize bytes"
}

Best practice

For any cross-drive folder move involving more than a hundred files, run a count-and-size verification after the move. Same-drive moves can be trusted to be atomic; cross-drive moves benefit from explicit confirmation.

Move-equivalent operations in PowerShell

PowerShell provides several patterns that achieve a move with different semantics than the File Explorer move.

# Standard move (Move-Item)
Move-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'D:\Project\Bundles\'

# Move with overwrite if destination exists
Move-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'D:\Project\Bundles\' -Force

# Move multiple files matching a pattern
Move-Item -Path 'C:\Project\Source\*.dat' -Destination 'D:\Project\Bundles\'

# Move and rename in one operation
Move-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'D:\Project\Bundles\Crate_Final.dat'

# Move a folder
Move-Item -Path 'C:\Project\OldFolder' -Destination 'C:\Project\Renamed\NewFolder'

The Move-Item cmdlet handles same-drive and cross-drive moves transparently. Behind the scenes it uses the same underlying file system API as File Explorer, so the same-drive instant-move behaviour applies.

For unattended scripted moves, the cmdlet's -Force flag overwrites destination files without prompting. Use this flag carefully because it bypasses the conflict dialog that File Explorer shows interactively.

Move and file attributes

A same-drive move preserves all file attributes exactly because no data is transferred and no new directory entry is created — only the parent reference changes. A cross-drive move behaves like a copy followed by a delete, so it has the same attribute-preservation characteristics as a copy.

Attribute	Same-drive move	Cross-drive move
Created timestamp	Preserved exactly	Set to copy time at destination
Modified timestamp	Preserved exactly	Preserved from source
Accessed timestamp	Preserved exactly	Set to copy time at destination
Read-only attribute	Preserved exactly	Preserved
Hidden attribute	Preserved exactly	Preserved
System attribute	Preserved exactly	Preserved
NTFS permissions	Preserved exactly	Inherits destination folder's permissions
Alternate data streams	Preserved exactly	Preserved (NTFS-to-NTFS)

The Created-timestamp behaviour is the most surprising difference. A same-drive move preserves the original Created timestamp; a cross-drive move resets it to the move-completion time. If you depend on Created timestamps for sorting or auditing, prefer same-drive moves when possible.

Move operations in the mod project workflow

A typical 57 Studios™ Unturned™ mod project uses move less frequently than copy. Most asset placement is a copy because the project pipeline depends on preserving each stage's outputs. Move is reserved for explicit reorganisation:

1. Promoting prototype assets from a scratch folder into the official structure. A developer working in a _Sandbox folder moves completed prototype assets into _Source when they are ready for promotion.
2. Relocating misplaced files into their correct folders. When a developer realises an asset was placed in the wrong category folder, a move corrects the placement.
3. Archiving completed work to a long-term archive folder. Once a mod release ships, the project folder is sometimes moved into an _Archive folder to free space in the active project area.
4. Reorganising folder structure mid-project. When a project's structure no longer matches the asset growth pattern, a move reorganises the affected folders into the new structure.

Best practice

When moving folders for reorganisation, perform the move in a single operation rather than multiple incremental moves. A single move of the parent folder is atomic at the file system level on same-drive operations. Multiple incremental moves of children risk leaving the project in an intermediate state if one of the moves fails.

Frequently asked questions

Why did my move become a copy? You either crossed a drive boundary without holding Shift, or you dragged with the left mouse button when Windows interpreted the operation as a copy. Use Ctrl + X and Ctrl + V to avoid this entirely; cut-and-paste always performs a move regardless of drive boundary.

Can I move a file that is currently open in another application? Usually no. Windows locks files that applications have open for writing. Close the application first, then move the file. Some applications hold a softer lock that permits moves; the only way to know is to try and observe the error if one occurs.

Is a same-drive move actually instant for a 100 GB file? Yes. The file system updates a few directory entries; the file's bytes never move. A 100 GB move within C:\ finishes in milliseconds.

What happens if the destination already has a file with the same name? The same conflict dialog from copy operations appears, with options to Replace, Skip, or Keep both. Choose carefully; Replace can destroy the destination file.

Why does my cross-drive move take longer than the equivalent copy? Cross-drive move includes the source delete after the destination write completes. The delete itself is fast, but the entire operation must wait for the write phase to finish before deletion can begin. The total time is approximately copy-time plus source-delete-time, which is marginally longer than copy alone.

Can I cancel a cross-drive move in progress? Yes. Click the X in the progress dialog. Files that already finished moving will remain at the destination with the source removed. The file being actively transferred when you cancel may be left in a partial state at the destination and may be deleted automatically. The source for that specific file remains intact.

What does the Move to option in the right-click menu do? The Move to option in the Windows 11 right-click menu opens a folder picker dialog where you choose the destination. After confirming, Windows moves the selected file to the chosen folder. This is a single-step alternative to cut-and-paste that bypasses the clipboard entirely.

Does the move operation work the same way in PowerShell as in File Explorer? Yes for the underlying file system mechanics. The differences are in defaults: File Explorer prompts on conflicts, PowerShell silently overwrites with -Force or errors without it. PowerShell's Move-Item is suitable for scripted moves where interactive confirmation is undesired.

Can I move a file across drives without holding Shift if both folders are open? Use Ctrl + X and Ctrl + V instead. Cut-and-paste always performs a move regardless of drive boundary. The Shift-drag requirement only applies to drag operations.

Why does my move sometimes show a Recycle Bin animation? You may have triggered a delete-by-drag rather than a move-by-drag. Dragging a file to the Recycle Bin icon, or onto a folder that is actually a shortcut to the Recycle Bin, deletes the file rather than moving it. Confirm the destination is the intended folder, not the Recycle Bin or a shortcut to it.

How do I move a folder while keeping its contents in their current location? You cannot. A folder move always carries the folder's contents with it. To leave contents in place, copy the folder to the new location (which leaves contents in both places), then delete the original folder (which removes the empty original). Alternatively, leave the folder and contents in place and create a shortcut to the folder at the new location.

Can I move a file from a zip archive to a folder? Opening a zip archive in File Explorer presents it as a browsable folder. You can cut and paste files from the zip archive into a folder, but the operation is effectively a copy from the archive plus a delete from the archive. Some zip formats and applications do not support deletion from within the archive, in which case the cut behaves as a copy and the source remains in the archive.

Best practices

• Default to Ctrl + X and Ctrl + V for any move. It works identically across all drives and avoids the Shift-drag pitfall.
• Verify the source and destination drives before dragging. A glance at the address bar saves a duplicate every time.
• Use right-click drag during the learning phase. The explicit menu prevents mistakes while you build intuition.
• Always finish a cross-drive move before disconnecting external drives.
• For mission-critical cross-drive moves, prefer copy followed by manual delete after verification.
• Run a post-move verification on folder moves involving more than a hundred files.
• Keep working assets on a single drive when possible to benefit from instant same-drive moves.
• Treat moves on removable and network drives as irreversible because the Recycle Bin does not catch replaced files on those drive types.

Appendix A: Move command-line reference

The Windows command line offers several move-equivalent commands. Each has its own syntax and behaviour quirks worth knowing.

:: Standard move (Command Prompt)
move "C:\Project\Source\Crate.dat" "D:\Project\Bundles\"

:: Move multiple files with wildcard
move "C:\Project\Source\*.dat" "D:\Project\Bundles\"

:: Move with overwrite (Command Prompt prompts by default)
move /Y "C:\Project\Source\Crate.dat" "D:\Project\Bundles\"

# PowerShell move
Move-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'D:\Project\Bundles\'

# PowerShell move with overwrite
Move-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'D:\Project\Bundles\' -Force

# Robocopy move
robocopy 'C:\Project\Source' 'D:\Project\Bundles' Crate.dat /MOV

# Robocopy move with all files
robocopy 'C:\Project\Source' 'D:\Project\Bundles' /MOVE /E

The Robocopy /MOV flag moves files (deleting source files after successful copy). The /MOVE flag moves files and folders (deleting source folders after successful copy). Robocopy's move is robust against transient failures because it retries each file and produces a per-file summary report.

The differences between the three commands:

Command	Same-drive instant move	Conflict default	Reliability features
move (cmd)	Yes	Prompts to overwrite	None
Move-Item (PowerShell)	Yes	Errors on conflict	None unless -Force
robocopy /MOV	No (always copies)	Skips by default	Retry, logging, multithreading

The trade-off is between speed and reliability. The native move and Move-Item commands use the same instant same-drive move that File Explorer uses, but they offer no retry on cross-drive failures. Robocopy is robust against failures but cannot use the same-drive metadata-only trick because it always reads and writes the file's bytes.

Appendix B: Move operation troubleshooting matrix

Symptom	Likely cause	Resolution
Move fails with "access denied"	Source or destination permission issue	Run as administrator or fix permissions
Move fails with "sharing violation"	Source locked by application	Close application, retry
Move completes but source still present	Operation actually became a copy	Verify drive, retry with Ctrl + X
Move completes but destination missing	Operation went to wrong folder	Search for the file by name
Move on USB drive fails repeatedly	USB drive failing or full	Check drive health and free space
Cross-drive move hangs partway	Network or drive issue	Cancel, verify connectivity, retry
Same-drive move took several seconds	Operation actually was cross-drive	Verify both folders are on same drive letter
Move says "path too long"	Combined path exceeds limit	Shorten parent folder names
Move says "filename in use" at destination	Existing destination file is locked	Close the application holding the destination
Right-click drag shows no Move option	Drag was to a location that does not accept moves	Verify destination is a writable folder

The troubleshooting matrix is a first-pass diagnostic. For persistent issues, run a drive health check and inspect the Windows Event Log for relevant file-system errors.

Appendix C: Move operation glossary

• Source. The file or folder being moved from.
• Destination. The folder where the moved file will reside after the operation.
• Same-drive move. A move where source and destination are on the same physical drive.
• Cross-drive move. A move where source and destination are on different physical drives.
• Atomic move. A move that either completes fully or does not occur at all, with no intermediate state.
• Directory entry. The file-system record that names a file and references its disk blocks.
• Metadata-only operation. A file-system operation that updates only directory entries, not file content.
• Cut. The clipboard operation that flags a file for move on next paste.
• Faded appearance. The visual indicator that a file has been cut and is awaiting paste.
• Drag with Shift. The mouse gesture that forces a cross-drive operation to be a move.
• Right-click drag. The drag gesture using the right mouse button, which produces a menu at the drop point.
• Move here. The right-click drag menu option that performs a move.
• Copy here. The right-click drag menu option that performs a copy.
• Create shortcuts here. The right-click drag menu option that produces a .lnk shortcut at the destination.

Appendix D: Move versus copy decision matrix

Situation	Move or Copy?	Reason
Reorganising project folders	Move	Source location is no longer wanted
Promoting prototype to official	Move	Sandbox copy is no longer needed
Deploying compiled bundle to Workshop	Copy	Source needs to remain for next build
Backing up project root daily	Copy	Source is the live project
Archiving completed project	Move (or copy then delete)	Active project area should be cleared
Moving downloaded file from Downloads to project	Move	Downloads folder should not accumulate
Migrating project to new drive	Move	Old drive copy is no longer needed
Sharing asset with collaborator	Copy	Original must remain for own use
Fixing misplaced file	Move	Correct location should hold the only copy
Creating a working version of a reference	Copy	Reference must remain unchanged

The decision matrix encapsulates the question "does the source still need to exist after the operation?" If yes, copy. If no, move. Some operations are technically reversible (move-back is an option) but reversibility should not be the basis for choosing move when the source is genuinely still needed.

Appendix E: Move and project reorganisation case studies

Real mod projects sometimes require major folder restructures. The case studies below illustrate how disciplined move operations support project reorganisation without losing work.

Case A: Mid-project folder rename. A modder six weeks into a project realises that the top-level folder name no longer reflects the project's scope. The folder is named MyCrateMod but the project has expanded to include crates, lockboxes, and storage barrels. The modder renames the top-level folder to StorageMod. This is a rename, not a move, but it has the effect of relocating every reference to the folder. Tools and scripts that referenced the old path must be updated.

Case B: Promoting prototype assets. A modder maintains a _Sandbox folder for experimental assets. When an experimental crate reaches a quality bar suitable for inclusion in the mod, the modder moves the asset from _Sandbox/Crates/PrototypeV3 into _Source/Items/Crate_v1. The move is same-drive and instant. The promotion is recorded in the project log.

Case C: Archiving a shipped release. Once a mod release ships, the modder moves the entire project folder from the active project area into the _Archive folder. The archive folder is on a separate slower drive used for long-term storage. The move is cross-drive and takes several minutes for a large project. After the move, the project's active drive is freed for the next project.

Case D: Splitting a project into two. A modder discovers that what started as a single mod has grown into two distinct mods that should ship separately. The modder creates a new project folder for the second mod, then moves the relevant assets out of the original project into the new project. Each move is same-drive within the project area. The original project log records each move with the source path, destination path, and reason.

Best practice

For any project reorganisation, record each move in the project log with the source path, destination path, and reason. The log lets you reconstruct the project's state at any point and serves as a reference for tool configurations that depend on the project's folder structure.

Appendix F: Move performance benchmarks

The performance characteristics of move operations vary widely across drive types and file sizes. The benchmarks below were measured on a representative mid-range workstation and serve as a guide for what to expect on similar hardware.

Source → Destination	File size	Move type	Wall-clock time
NVMe SSD → NVMe SSD (same drive)	10 MB	Metadata	< 1 ms
NVMe SSD → NVMe SSD (same drive)	4 GB	Metadata	< 1 ms
NVMe SSD → NVMe SSD (same drive)	100 GB folder	Metadata	< 100 ms
NVMe SSD → NVMe SSD (different drive)	10 MB	Cross-drive	5 - 20 ms
NVMe SSD → NVMe SSD (different drive)	4 GB	Cross-drive	2 - 5 seconds
NVMe SSD → SATA SSD	4 GB	Cross-drive	8 - 15 seconds
NVMe SSD → 7200 RPM HDD	4 GB	Cross-drive	25 - 45 seconds
NVMe SSD → USB 3.2 external SSD	4 GB	Cross-drive	5 - 12 seconds
NVMe SSD → USB 3.0 external HDD	4 GB	Cross-drive	30 - 60 seconds
NVMe SSD → Gigabit LAN share	4 GB	Cross-drive	35 - 45 seconds
NVMe SSD → Wi-Fi 6 LAN share	4 GB	Cross-drive	60 - 180 seconds

The dominant variable is whether the move is same-drive or cross-drive. The same-drive metadata move completes in milliseconds regardless of file size. The cross-drive move scales with the slower of the two drives and the volume of data.

A subtle benchmark observation: same-drive moves of folders containing many small files still complete in milliseconds because the operation updates only the parent folder's directory entry, not the directory entries of each child. A folder containing ten thousand small files moves in the same time as a folder containing a single small file.

Did you know?

The same-drive instant-move characteristic is exploited by professional video editors to organise tens of terabytes of footage into project folders without waiting on data transfer. The same trick works for mod developers: an asset library of 500 GB can be reorganised on the same drive in seconds, where a cross-drive move of the same library would take an hour.

Appendix G: Move operation patterns in long-running projects

A mod project that runs for many months accumulates a recognisable set of move patterns. The patterns below are drawn from 57 Studios™ internal project retrospectives across multiple Unturned™ mod releases.

Pattern 1: The mid-project promotion. The most common move pattern in the first three months of a project. Prototype assets move from a sandbox folder into the official structure once they reach a quality bar. The move is same-drive and instant. The promotion is recorded in the project log.

Pattern 2: The structural rename. Roughly halfway through a typical project, the folder structure no longer matches the asset growth. A modder restructures by moving folders into new parent folders. The move is same-drive and instant. The restructure is recorded in the project log along with the rationale for each move.

Pattern 3: The drive migration. When a modder upgrades to a larger or faster drive, the entire project area moves from the old drive to the new drive. The move is cross-drive and takes substantial time. Most modders run the migration overnight or while away from the workstation.

Pattern 4: The pre-release consolidation. In the final weeks before a mod release, working files move into a tighter project structure suitable for the release. Scratch files, archived prototypes, and intermediate outputs move into archive folders. The active project area shrinks to only the files needed for the release.

Pattern 5: The post-release archive. After a release ships, the entire project folder moves into an archive area. The active project drive is freed for the next project. The archive move is often cross-drive to a slower long-term storage drive.

Each pattern has a default method. Same-drive patterns use Ctrl + X and Ctrl + V or same-drive drag. Cross-drive patterns use Ctrl + X and Ctrl + V or scripted Robocopy /MOVE.

Best practice

Schedule structural-rename moves for a moment when the project is in a stable state — typically immediately after a milestone check-in. Restructuring mid-edit risks losing track of where in-progress files were intended to land. Restructuring at a stable point preserves the project's coherence.

Appendix H: Move command flag reference

The Robocopy command's move-related flags are the most extensive of any built-in Windows utility. The principal flags:

Flag	Effect
/MOV	Move files (deletes source files after copy succeeds)
/MOVE	Move files and folders (deletes source folders after copy succeeds)
/E	Copies subdirectories, including empty ones
/MT:N	Uses N threads for parallel copy (1-128, default 8)
/R:N	Retries N times on failure
/W:N	Waits N seconds between retries
/Z	Resumes interrupted copies from the point of interruption
/B	Uses backup mode (bypasses some file-system access checks)
/COPY:DAT	Copies Data, Attributes, Timestamps
/COPYALL	Copies all file info including permissions, owner, audit info
/LOG:file	Writes a detailed log to the specified file
/TEE	Outputs to console and log simultaneously
/NP	No progress; suppresses the percentage display
/NFL	No file list; suppresses the per-file output
/NDL	No directory list; suppresses the per-directory output

A typical Robocopy move for a project archive uses several flags together:

robocopy 'C:\Project\Active\OldProject' 'D:\Archive\OldProject' /MOVE /E /MT:8 /R:3 /W:5 /COPYALL /LOG:'D:\Archive\move-log.txt'

This command moves the source folder and all contents to the destination, using eight parallel threads, retrying each file up to three times on failure, copying all file metadata including permissions, and writing a detailed log file.

Appendix I: Extended FAQ on move operations

Can I move a file while it is being scanned by antivirus software? The antivirus scanner typically holds a brief read lock on the file during scanning. Most scanners release the lock quickly and the move proceeds normally. If the move fails repeatedly with a sharing violation, the scanner may be holding the file for a deeper inspection. Wait a moment and retry, or add a temporary exclusion for the source folder.

Does the move operation preserve a file's last-write timestamp? For same-drive moves, every timestamp is preserved exactly because no data transfer occurs. For cross-drive moves, the Modified timestamp is preserved but the Created and Accessed timestamps reset to the move time. This matches the timestamp behaviour of a copy.

What happens if I move a folder containing a file that is open in an application? The move usually fails with a sharing violation on the locked file. Some applications hold a soft lock that permits the move; others hold a hard lock that prevents it. Close the application first to be safe.

Can I move files from a search-results view in File Explorer? Yes. The search-results view supports drag-and-drop and cut-and-paste like any folder view. The selected files are moved from their actual locations to the chosen destination, regardless of which folders they originated in. This is useful for bulk reorganisation when files of a particular type are scattered across multiple folders.

Why does moving a Word document sometimes leave a hidden file behind? Microsoft Word creates a hidden lock file with a name starting with ~$ while the document is open. If you move the main document while it is open, the lock file may remain at the source. Close the document first, or manually delete the orphaned ~$ file after the move.

Can I move files from a OneDrive folder to a non-OneDrive folder? Yes. The move detaches the file from OneDrive sync. The destination file is a normal local file, no longer synced to OneDrive. The source location in OneDrive will reflect the file's absence after the next sync cycle.

Does the move operation work on files I do not have write permission for? No. The move requires read access at the source (to read the bytes for cross-drive moves), write access at the destination (to write the destination file), and write access on the source's parent folder (to delete the source). If any permission is missing, the move fails with an access-denied error.

Can I move a file to its current location to refresh its timestamp? Moving a file to its current folder is a no-op and does not refresh timestamps. To update a file's Modified timestamp without changing content, use PowerShell's Set-ItemProperty or (Get-Item path).LastWriteTime = Get-Date.

Why does the cross-drive move show "0 seconds remaining" for a long time before completing? The progress dialog's time estimate is based on a rolling average of transfer speed. Near the end of a large move, the estimate often converges to zero before the operation actually completes because of write-buffer flush and source-delete time that are not factored into the estimate. The operation will finish shortly.

Can I move a file from a network share to a local drive? Yes. The move reads bytes from the network and writes them to the local drive, then deletes the source on the network share. The operation is treated as a cross-drive move. If the network share is on a slow connection, the move can take substantial time.

What is the safest way to move a folder containing thousands of small files? For same-drive moves, the standard cut-and-paste is fast and safe because the operation is metadata-only. For cross-drive moves, Robocopy with /MOVE /E /MT:8 /R:3 is safer than File Explorer because Robocopy retries individual files on transient failures and produces a complete log of the operation.

Can I undo a move with Ctrl + Z? Yes, immediately after the move. Press Ctrl + Z in File Explorer to undo the most recent file operation. If you have performed other operations since the move, the undo stack may no longer include the move. In that case, manually move the file back to its original location.

Appendix J: Move and project audit trails

For projects that require an audit trail of file movements — typically projects with multiple collaborators, projects under version control, or projects where compliance requires a record of where files have been — a move log is the basis of the audit trail.

A move log entry captures the date, time, source path, destination path, operator, and reason for the move:

Date	Time	Source	Destination	Operator	Reason
2026-05-15	09:14	_Sandbox/Crate_proto	_Source/Items/Crate_v1	Lead modder	Prototype promotion
2026-05-16	14:30	_Source/Items/OldCrate	_Archive/Items/OldCrate	Lead modder	Deprecation
2026-05-17	11:02	_Active/Project_v2	_Archive/Project_v2	Lead modder	Release archive

The log can be maintained manually in a text file or spreadsheet, or it can be generated automatically by a PowerShell wrapper around the move command. An automated wrapper logs every move as part of the operation:

function Move-WithLog {
    param(
        [string]$Source,
        [string]$Destination,
        [string]$Reason
    )
    $timestamp = Get-Date -Format 'yyyy-MM-dd HH:mm:ss'
    Add-Content -Path 'C:\Project\move-log.txt' -Value "$timestamp | $Source -> $Destination | $Reason"
    Move-Item -Path $Source -Destination $Destination
}

# Usage
Move-WithLog -Source 'C:\Project\_Sandbox\Crate_proto' -Destination 'C:\Project\_Source\Items\Crate_v1' -Reason 'Prototype promotion'

The wrapper writes a log entry before performing the move, so the log is updated even if the move fails. For a complete audit trail, also log the move's success or failure status after the operation completes.

Best practice

Maintain a move log for any project that involves more than a few major reorganisation moves over its lifetime. The log is the only reliable way to reconstruct the project's file-system history later, especially when collaborators need to understand why a file is in its current location.

Appendix K: Move and version snapshots

The 57 Studios™ project versioning practice uses copy operations to produce dated snapshots of project state. Move operations are explicitly avoided in the snapshot pathway because a move would destroy the source. The relationship between move and the version-snapshot practice is therefore one of separation: move is for active project reorganisation, copy is for snapshot creation.

When a snapshot is no longer needed and is being retired, the move operation is appropriate. Old snapshots move from the active backup folder into a long-term archive folder. The move frees the active backup area for new snapshots while preserving the old snapshots in long-term storage.

Snapshot operation	Method	Reason
Create snapshot	Copy from project root	Preserve project state for rollback
Promote snapshot to release	Copy from snapshot to release area	Source snapshot remains for reference
Retire snapshot to long-term archive	Move from active backups to archive	Active backup area should be cleared
Restore from snapshot	Copy from snapshot back to project	Source snapshot remains for further rollback

The pattern aligns move with operations where the source location should not retain a copy, and copy with operations where the source must remain. The distinction is the single most important discipline in mod-project file management: a copy is always recoverable through deletion of the destination; a move is recoverable only through a return move that itself can fail.

A modder who internalises this discipline avoids the most common source of project state confusion — files that have been moved but should have been copied, or files that have been copied but should have been moved. Reviewing the move-versus-copy decision matrix in Appendix D and the project-phase recommendations in Appendix G is the recommended starting point for the discipline.

Next steps

With copy and move covered, the third core file operation is rename. Renaming is straightforward when you know the rules, and dangerous when you do not. Continue to How to Rename a File to learn the four rename methods and the rules Windows enforces on filenames.

After rename, the final core operation is creating folders. Read How to Create a New Folder for the methods and the structure conventions that work well for Unturned™ mod projects.

For a deeper look at how copy and move fit into the mod-development pipeline, refer back to How to Copy a File and study the project workflow section that lays out the Copy-first discipline that 57 Studios™ uses across active mod projects.