How to Copy a File

Copying a file creates a second independent instance of the file in a target location while leaving the original untouched. For Unturned™ mod developers, copying is the most frequent file operation. You copy mod assets between project working folders and deployment folders. You copy textures from reference libraries into project asset folders. You copy completed bundle outputs into Steam Workshop staging folders. You copy backups of your working files before risky edits. Every productive mod session involves dozens of copy operations.

This article covers the four methods Windows provides for copying files, the underlying clipboard handoff that powers most of them, and the differences between copying and cutting. By the end you will know which method to use for each context and how to copy multiple files efficiently at once. 57 Studios™ professional workflow depends on choosing the right copy method for the situation.

Prerequisites

File Explorer must be open and configured to show extensions and hidden items. If you have not yet done this configuration, read How to View File Extensions and How to View Hidden Files. You should also be comfortable navigating between folders; review How to Navigate to a Folder if needed.

What you will learn

• What copying actually does at the file system level
• How to copy with Ctrl + C and Ctrl + V
• How to copy with right-click menus
• How to copy by dragging while holding Ctrl
• How to copy with the ribbon or command bar
• The difference between copy and cut
• How to handle conflicts when a destination file already has the same name
• How copy speeds vary across drive types, file sizes, and network targets
• How professional modders structure project folders around frequent copy operations
• How to verify a copy completed correctly before deleting the source

What copying does

When you copy a file, Windows reads the file's bytes from the source location and writes those bytes to the destination location. The source remains intact. The destination receives a new, independent file with the same contents.

The two key facts about copying:

1. The original is preserved. Copy never deletes the source.
2. The two files are independent. Editing one does not affect the other.

This makes copy the safe operation. When in doubt between copy and move, choose copy. You can always delete the duplicate later, but you cannot recover an overwritten or lost original.

The independence of the two files is worth emphasising. Once a copy completes, the source and destination files share no link in the file system. They occupy separate sets of disk blocks, hold separate timestamps, and respond to separate edit operations. A change to the destination file does not propagate back to the source. A deletion of the source does not remove the destination. The two files are full peers from the moment the copy finishes.

This is the difference between a copy and a symbolic link or a hard link, both of which create new references to the same underlying data. File Explorer's Copy command always produces a true independent copy and never creates a link. If you specifically want a link instead of a copy, you must use the command line mklink utility, which is outside the scope of this article.

Did you know?

On the same NTFS drive, modern Windows copies very large files significantly faster than older versions because the file system can deduplicate identical block references during the write. Cross-drive copies still require reading and writing all bytes.

Did you know?

The Windows clipboard does not actually store the file's bytes when you press Ctrl + C. It stores a reference to the source path together with a flag indicating whether the operation was a copy or a cut. The actual byte transfer happens at paste time. This is why pressing Ctrl + C on a 4 GB Unity bundle completes instantly, and the visible work happens when you paste.

Method 1: Ctrl + C and Ctrl + V

The keyboard shortcut method is the fastest for almost every situation. It uses the Windows clipboard as an intermediate holding area.

1. Click a file once to select it. To select multiple files, click the first, then Ctrl + click each additional file, or hold Shift while clicking the last file in a range.
2. Press Ctrl + C to copy the selection to the clipboard.
3. Navigate to the destination folder using any method covered earlier.
4. Press Ctrl + V to paste the files into the destination.

Windows shows a progress dialog if the copy takes more than a second. Small files copy nearly instantly. Very large files such as Unity asset bundles can take several seconds.

The progress dialog has several useful features that many users overlook. The More details button expands the dialog to show a real-time transfer-speed graph in megabytes per second, the count of items remaining, the estimated time remaining, and the size of the data transferred so far. The Pause button suspends the operation without cancelling it, which is useful when a copy is consuming bandwidth that you need for another task.

Pro tip

Ctrl + C and Ctrl + V work in nearly every Windows application. The same shortcuts copy text in Notepad, cells in Excel, and layers in Photoshop. Building muscle memory for these two keystrokes pays back in every program you use.

Pro tip

You can press Ctrl + C multiple times in succession to overwrite the clipboard with new selections. Only the most recent Ctrl + C is held. If you want to copy multiple separate selections that are not contiguous in a folder, use Ctrl + click to build the multi-selection in one operation rather than repeated Ctrl + C presses.

Method 2: Right-click menu

The right-click context menu provides a discoverable alternative for users who have not memorized shortcuts.

1. Right-click the file you want to copy.
2. Choose Copy from the context menu. On Windows 11, the Copy command appears as an icon at the top of the menu next to Cut, Rename, Share, and Delete.
3. Navigate to the destination folder.
4. Right-click an empty area inside the destination folder.
5. Choose Paste from the context menu.

The right-click method is slower than keyboard shortcuts but is reliable when your hands are already on the mouse.

On Windows 11 the context menu was redesigned to surface the most common file operations as icons at the top of the menu. Copy is the second icon, between Cut and Rename. Hover over each icon to confirm its function via the tooltip. The full text menu beneath the icons still includes the same Copy command for users who prefer reading menu items.

If the right-click menu does not show a Copy command, you may have right-clicked an empty area rather than a file. The Copy command appears only when a file is right-clicked. Empty-area right-clicks show the Paste command instead, along with New, View, and Sort options.

Method 3: Drag-and-drop with Ctrl held

Dragging a file from one File Explorer window to another defaults to either Move (same drive) or Copy (different drive). Holding Ctrl forces the operation to Copy regardless of the drive.

1. Open File Explorer to the source folder.
2. Open a second File Explorer window to the destination folder. Press Windows + E twice or right-click the taskbar icon and choose File Explorer.
3. Arrange the two windows side by side so you can see both at once.
4. Click and hold the file you want to copy in the source window.
5. Press and hold the Ctrl key.
6. Drag the file to the destination window.
7. Release the mouse button first, then release Ctrl.

A small plus sign (+) icon appears next to the cursor while Ctrl is held, confirming a copy is in progress. Without Ctrl, the cursor shows an arrow indicating a move within the same drive.

The cursor indicators are critical visual feedback. A plus sign means copy. A straight arrow means move. A curved arrow means create shortcut. Watch the cursor before releasing the mouse button. If the cursor does not show the expected indicator, release Ctrl, return to the source, and try again with the modifier key held throughout the drag.

Common mistake

Releasing the Ctrl key before releasing the mouse button cancels the copy-forcing behavior. If you accidentally moved a file you meant to copy, immediately press Ctrl + Z to undo, then try again with Ctrl held until after the drop.

Common mistake

Dragging a file to a folder icon rather than into a folder window drops the file inside that folder rather than placing it next to that folder. This can confuse new users who expect the file to land in the current view. Confirm the cursor indicator and the tooltip text near the cursor before releasing the mouse button.

Method 4: Ribbon or command bar

File Explorer's ribbon (Windows 10) or command bar (Windows 11) exposes copy and paste as toolbar buttons.

Windows 10:

1. Select the file in the file list.
2. Click the Home tab in the ribbon if it is not already active.
3. Click Copy in the Clipboard group.
4. Navigate to the destination folder.
5. Click Paste in the Clipboard group.

Windows 11:

1. Select the file in the file list.
2. Click the Copy icon (looks like two stacked rectangles) in the command bar near the top.
3. Navigate to the destination folder.
4. Click the Paste icon (looks like a clipboard) in the command bar.

The ribbon and command bar methods are slowest but are useful when you want a visual confirmation of which command you are about to invoke.

The command bar in Windows 11 is more condensed than the Windows 10 ribbon. On smaller displays the bar may collapse some commands into an overflow menu accessed through a three-dot icon at the right edge. Copy and Paste remain visible at all common display widths, but Cut and Rename sometimes shift into the overflow.

Copy vs cut: a critical distinction

The clipboard stores not just the file reference but also a flag indicating whether the operation was a copy or a cut.

Operation	Source after paste	Use case
Copy (Ctrl + C)	Source remains	Want two independent copies
Cut (Ctrl + X)	Source is removed	Want to relocate the file

A cut file appears faded in File Explorer between the cut and the paste. If you cancel the operation (press Escape, or copy something else), the faded appearance returns to normal and the source is preserved.

The faded appearance is a state indicator, not a commitment. The file is not actually moved or removed until you press Ctrl + V at the destination. If you change your mind, press Escape, copy a different selection, or close File Explorer entirely. The faded state clears and the source remains untouched.

Best practice

Default to Copy for any operation involving a file you cannot easily recreate. Use Cut only when you are certain you want to relocate the file. A copy followed by a delete in the source is safer than a cut, because you can verify the destination before destroying the source.

Best practice

Pair copy operations with explicit verification. After pasting, navigate into the destination folder and confirm the file appears, has the expected size in the Details view, and opens correctly in its associated application. Only after this verification should you delete the source if you intended a relocation.

Method usage among professional modders

The dominance of keyboard shortcuts is even more pronounced for copying than for File Explorer launching. Most professional modders use Ctrl + C and Ctrl + V for nearly every copy operation because the speed advantage compounds across the hundreds of copies in a typical workday.

A 57 Studios™ internal time study tracked one mod developer across a full eight-hour work session and counted 218 distinct copy operations. At an average of 1.4 seconds per operation using keyboard shortcuts, versus 4.8 seconds per operation using the ribbon, the developer would have spent an additional 12 minutes per day on copy operations alone if they used the slowest method. Across a working year that compounds to roughly 50 hours of recovered time.

Comparison of copy methods

Method	Speed	Skill level	Best context
Ctrl + C / Ctrl + V	Fastest	Beginner	Any time, any context
Right-click menu	Medium	Beginner	Mouse already in hand
Ctrl-held drag	Fast	Intermediate	Two folders visible side by side
Ribbon or command bar	Slow	Beginner	Learning the interface

Copy speed by source and destination

Copy speed depends primarily on the slower of the two drives involved and on the file size distribution within the selection. A single large file copies at near-maximum sustained transfer rate. Many small files copy slower per byte because each file involves directory-entry overhead.

Source	Destination	Typical sustained speed	Notes
NVMe SSD	NVMe SSD (same drive)	1.0 - 3.5 GB/s	Limited by source read or destination write
NVMe SSD	NVMe SSD (different drive)	0.8 - 2.8 GB/s	Bus contention can reduce throughput
SATA SSD	SATA SSD	250 - 500 MB/s	SATA interface ceiling
7200 RPM HDD	7200 RPM HDD	100 - 180 MB/s	Spinning platter limits
NVMe SSD	USB 3.2 external SSD	400 - 950 MB/s	USB controller-dependent
NVMe SSD	USB 3.0 external HDD	80 - 120 MB/s	HDD platter limits
NVMe SSD	Gigabit LAN network share	100 - 115 MB/s	Network interface ceiling
NVMe SSD	Wi-Fi 6 network share	30 - 90 MB/s	Wireless signal-dependent

The figures above are typical sustained rates for sequential copies of large files. Bursts of small files copy slower because each file requires a directory-entry update at both source and destination, and the cost is amortised across fewer bytes.

Did you know?

Copying ten thousand 1 KB files takes substantially longer than copying one 10 MB file, even though the total bytes are identical. The per-file overhead dominates the wall-clock time for small-file collections. Mod project asset folders containing many small icon files exhibit this slowdown.

Handling filename conflicts

When you paste a file into a folder that already contains a file with the same name, File Explorer presents a dialog with three options.

1. Replace the file in the destination. Overwrites the existing file with the new one. The replaced file goes to the Recycle Bin in most cases, but not always.
2. Skip this file. Leaves the existing file untouched and does not copy the new one.
3. Compare info for both files. Opens a side-by-side comparison and lets you choose which version to keep based on date, size, and source.

For multiple file conflicts, the dialog includes a Do this for the next N conflicts checkbox.

The conflict dialog also offers a Keep both behaviour, accessed through the comparison view. Choosing Keep both renames the incoming file with a numeric suffix in parentheses, such as Crate (1).dat, and writes it alongside the existing file. This is the safest option when you are uncertain which version is the more recent or authoritative one.

Critical warning

Choosing Replace for a file you did not intend to overwrite can result in unrecoverable data loss. The Recycle Bin sometimes does not catch overwrites, especially on removable drives. Always read the conflict dialog carefully before clicking Replace. If you are unsure, click Compare and inspect both files first.

Critical warning

The conflict dialog's default highlighted button can vary between Windows versions and even between system configurations. Do not assume Enter will choose the safe option. Read the button text before pressing any key. An accidental Enter press while the Replace button is highlighted has overwritten countless source files.

Decision flow for conflict resolution

When in doubt, choose Compare info or Keep both. The Replace and Skip options are irreversible at the file-system level once confirmed, while Keep both leaves you with both versions on disk and lets you make the discard decision after closer inspection.

Advanced considerations

Long copy operations show a progress dialog with bytes-per-second and estimated time remaining. The dialog has a Pause button and a More details button that expands to show a transfer speed graph. You can pause a long copy, do other work, and resume.

Copying across drives is slower than same-drive copies because every byte must be read from one drive and written to another. A 4 GB Unity bundle can take a minute or more to copy from an internal SSD to an external USB drive.

Copying to a network location can be slower than copying across drives and is more prone to interruption. Use the More details view to monitor the speed; if it drops to zero, the network connection has stalled.

Copying a folder copies every file and subfolder inside it. The same dialog appears once per duplicate file inside the folder unless you choose Apply to all.

Copying with the Robocopy command is the recommended approach for unattended bulk copies, network mirrors, or large-folder backups. Robocopy ships with Windows and offers retry-on-failure, file-attribute preservation, multithreaded transfer, and a per-run summary report. Mod developers maintaining backup pipelines often script Robocopy invocations rather than relying on File Explorer.

Copying a read-only file preserves the read-only attribute on the destination. If you need a writable copy, right-click the destination file, choose Properties, and uncheck the Read-only checkbox after the copy completes.

File attributes preserved by a copy

A Windows copy preserves most file attributes but not all. Knowing what is preserved and what is reset prevents surprises when the destination file behaves differently than the source.

Attribute	Preserved on copy?	Notes
File contents (bytes)	Yes	This is the definition of copy
File size	Yes	Identical to source by definition
Filename	Yes	Unless renamed via conflict dialog
Extension	Yes	Identical to source
Created timestamp	No	Set to copy-completion time
Modified timestamp	Yes	Preserved from source
Accessed timestamp	No	Set to copy-completion time
Read-only attribute	Yes	Preserved as-is
Hidden attribute	Yes	Preserved as-is
System attribute	Yes	Preserved as-is
NTFS permissions	Sometimes	Depends on destination folder permissions
Alternate data streams	Usually	NTFS-to-NTFS only

The Created timestamp surprise is the most common source of confusion. A file copied today will show today's date as Created and the original date as Modified. Sorting by Created sorts copies to the top of the file list, not by their original creation date.

How copy fits the mod project workflow

A typical 57 Studios™ Unturned™ mod project involves a structured copy pipeline:

1. Source assets are copied from reference libraries into the project's _Source folder. This freezes the reference state inside the project.
2. Working copies are made inside the project's Assets folder. Edits happen on the working copies, leaving _Source untouched.
3. Compiled outputs are copied from the Unity Editor output to the project's Bundles folder. This isolates the deployable artifacts.
4. Final bundles are copied from Bundles into the Steam Workshop staging folder. This is the last step before publication.
5. Daily backups are copied from the project root into a dated backup folder. This is the resilience layer.

Each step is a Copy operation. None are Moves. The pipeline depends on the source remaining intact at every stage so a downstream error can be recovered by re-copying from an upstream stage.

Best practice

Treat Copy as the primary operation in your mod project pipeline. Reserve Move for the rare case where you are reorganising a single working folder and the source is genuinely safe to remove. The Copy-first discipline is the foundation of a recoverable project.

Recovering from a bad copy

Bad copies happen. Common failure modes include partial copies due to disk-full conditions, copies to the wrong destination folder, copies that overwrote a file you needed, and copies that completed but with unexpected attributes such as the read-only flag set.

Failure mode	Symptom	Recovery
Disk full	Copy fails partway with error dialog	Free space at destination, retry
Wrong destination	File arrived in unexpected folder	Locate via search, move or delete
Overwrote needed file	Destination file is now the new content	Check Recycle Bin, restore if present
Read-only attribute set	Cannot save edits to destination	Properties, uncheck Read-only
Encrypted source on unencrypted destination	Cannot open destination on other accounts	Re-copy with administrator account
Path too long error	Copy fails before starting	Shorten destination path, retry
Source file locked by application	Copy fails with sharing violation	Close application, retry

Press Ctrl + Z immediately after a bad copy if you noticed the mistake quickly. Windows tracks recent file-system operations and can undo the most recent copy if it has not been superseded by other actions.

Frequently asked questions

Why does my copy operation say it cannot complete because a file is in use? Another application has the source file locked. Close the application or, for mod project files, ensure Unity Editor and Unturned™ are not running. Try the copy again. If the lock persists, you can sometimes copy a locked file by first making a copy of the source file using PowerShell with the -Force flag, which can bypass certain types of soft locks.

Can I copy and paste between two computers? Not directly through Ctrl + C and Ctrl + V. You can copy through a shared network folder, a USB drive, or a cloud sync service such as Google Drive. The clipboard does not span computers. Some remote-desktop tools provide a clipboard-sharing feature that creates a virtual bridge, but this is a tool-specific feature, not a Windows feature.

The destination already has a file with the same name. Can I copy without overwriting? Choose Keep both in the conflict dialog. Windows appends a numbered suffix such as (1) or (2) to the new file. This is safer than replacing when you are not certain which version you want to keep.

Why does the copy progress dialog show a slower speed than my drive's rated speed? Several factors reduce real-world speeds below the manufacturer's rated maximum: file fragmentation on spinning platters, drive caching that fills early in long transfers, USB or network controller overhead, and small-file overhead. The rated speed is a peak under ideal conditions and is not the typical sustained rate.

Can I copy a file to multiple destinations at once? File Explorer does not support multi-destination copy in a single operation. You must paste once per destination. PowerShell's Copy-Item cmdlet accepts a single source and a single destination per call, but you can loop over destinations in a script. For repeated multi-destination copies, a small PowerShell or batch script is the standard approach.

Does a copy preserve the file's NTFS permissions? A copy inside the same drive often preserves permissions, but a copy across drives or to a different folder typically inherits the destination folder's permissions instead. This is by design: the destination folder's security descriptor takes precedence to prevent accidental permission leakage. Use the icacls command to inspect or adjust permissions after a copy if precise permission control matters.

What happens if I disconnect a USB drive in the middle of a copy? The copy fails immediately with a sharing or device-not-ready error. Files that finished copying are intact on the destination. The in-flight file may be partial or zero bytes. The source is untouched. Reconnect the drive and re-run the copy to complete any remaining files.

Can I copy a file that is currently being downloaded by my browser? The file is typically locked by the browser for the duration of the download. Wait for the download to complete, then copy normally. Some browsers write to a temporary file with a different name and only rename to the final filename when the download finishes, in which case the partial download is not visible at the final path.

Why does copying an Excel or Word document sometimes fail with a permissions error? Microsoft Office often creates a hidden lock file with a name beginning with ~$ when a document is open. The lock file holds a shared exclusive on the main document. Close the document in Office first, then copy.

Does a copy operation use CPU resources? A copy uses minimal CPU because the work is primarily disk I/O. Modern Windows uses DMA to transfer bytes from one drive to another without routing through the CPU for each block. Encryption operations during copy (such as copying to or from a BitLocker-encrypted volume) consume more CPU because the bytes must pass through the encryption layer.

Can I cancel a copy that has already started? Yes. Click the X in the upper-right of the progress dialog. Files that already finished copying are intact on the destination. The in-flight file may be deleted automatically by Windows or may remain as a partial file at the destination. Same-drive metadata-only copy operations cannot be cancelled because they complete in milliseconds.

How do I copy a file's permissions along with the file? Use the xcopy /O or robocopy /COPY:DATSO commands at the command line. File Explorer does not preserve permissions across all copy types, but command-line utilities can.

Best practices

• Default to Ctrl + C and Ctrl + V for nearly all copy operations.
• Choose Copy over Cut whenever the source is irreplaceable.
• Use side-by-side File Explorer windows with Ctrl-drag when you need to copy many files between two known folders.
• Read the conflict dialog carefully before clicking Replace.
• Verify the destination contains the copy before deleting the source if you intended a move.
• Watch the progress dialog's More details view on long copies to confirm the operation is progressing rather than stalled.
• Use Robocopy or PowerShell's Copy-Item for unattended, scripted, or repeated bulk copies.
• Treat Copy as the primary operation in your mod project pipeline; reserve Move for explicit reorganisation.
• Run a quick post-copy verification by opening the destination file in its associated application before committing to a downstream action.

Appendix A: PowerShell copy patterns

For mod developers who maintain scripted backup pipelines or scaffold project folders, PowerShell offers several useful copy patterns that File Explorer cannot match. The cmdlets below are the foundation of most automated mod-project copy workflows.

# Single file copy
Copy-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'C:\Project\Bundles\'

# Folder copy with all subfolders
Copy-Item -Path 'C:\Project\Assets' -Destination 'C:\Backups\Assets' -Recurse

# Copy and overwrite if exists
Copy-Item -Path 'C:\Project\Source\Crate.dat' -Destination 'C:\Project\Bundles\' -Force

# Copy with verbose output for logging
Copy-Item -Path 'C:\Project\Assets' -Destination 'C:\Backups\Assets' -Recurse -Verbose

# Copy with filter
Copy-Item -Path 'C:\Project\Source\*.dat' -Destination 'C:\Project\Bundles\'

# Copy with exclude pattern
Copy-Item -Path 'C:\Project\Source\*' -Destination 'C:\Project\Bundles\' -Exclude '*.tmp', '*.bak'

For larger transfers and unattended operation, Robocopy is preferred over Copy-Item because it offers retry-on-failure, multithreaded transfer, and a per-run summary report.

# Robocopy with multithreading and retry
robocopy 'C:\Project\Assets' 'C:\Backups\Assets' /E /MT:8 /R:3 /W:5 /LOG:'C:\Backups\backup.log'

The flags above mean: /E copies all subfolders including empty ones, /MT:8 uses eight threads for parallel transfer, /R:3 retries each file up to three times on failure, /W:5 waits five seconds between retries, and /LOG writes a detailed report.

Appendix B: Copy operation in the modder's project log

A disciplined project log captures every significant copy operation so the project state can be reconstructed after a failure. The log entries below illustrate the format used in 57 Studios™ internal project documentation.

Date	Operation	Source	Destination	Reason
2026-05-12	Copy	Reference library	_Source\Models\Items	Acquire reference crate model
2026-05-12	Copy	_Source\Models\Items\Crate.fbx	Assets\Items\Crate.fbx	Begin work copy
2026-05-13	Copy	Assets\Items\Crate.png	Bundles\Items\1000_Crate\Crate.png	Promote icon to bundle
2026-05-13	Copy	Bundles\Items\1000_Crate	Workshop\Items\1000_Crate	Stage for Workshop
2026-05-14	Copy	Project root	Backups\2026-05-14_v3	Pre-edit safety snapshot

Each row captures the operation type, the source path, the destination path, and the reason for the operation. A project log of this form is invaluable when reconstructing the sequence of changes that led to a current project state, and is the documentary basis for the file-based versioning practice that 57 Studios uses across all active mod projects.

Appendix C: Copy versus other operations comparison

Operation	Source after	Destination after	Reversible?	Typical use
Copy	Unchanged	New independent file	Yes, delete destination	Most common; safe duplication
Cut + Paste	Removed	New file in place of source	Yes, cut+paste back	Relocation
Move	Removed	New file in place of source	Yes, move back	Relocation
Rename	Renamed in place	Not applicable	Yes, rename back	Identifier change
Delete	Removed (Recycle Bin or permanent)	Not applicable	Sometimes, from Recycle Bin	Removal
Create shortcut	Unchanged	Small .lnk file at destination	Yes, delete shortcut	Reference without duplication

Understanding how copy differs from the other primary file operations clarifies when to choose each. Copy is the only operation that produces a true independent duplicate. Cut and Move both relocate. Rename changes identity without changing location. Delete removes. Create shortcut creates a reference, not a copy.

Common copy patterns in mod development

A working mod project produces a repeating set of copy patterns that recur across every project. Recognising these patterns lets you optimise your folder layout and your tooling around the operations you perform most often.

Pattern 1: The reference-to-source copy. Every project begins with a copy from a reference library into the project's _Source folder. The reference library holds the canonical version of frequently used assets — common crate models, standard texture packs, base material libraries. Copying from the library into the project's _Source folder freezes the reference state at the moment of the copy. Subsequent updates to the reference library do not propagate into the project.

Pattern 2: The source-to-working copy. Inside the project, assets move from _Source (the frozen reference) to Assets (the editable working folder) through copy operations. Edits happen on the working copies. The _Source folder remains a clean baseline that the project can return to if a working copy is damaged or if a downstream consumer needs the unmodified original.

Pattern 3: The working-to-bundle copy. Once a working file is ready for compilation, it is copied into the Bundles folder where the Unity Editor builds it into a .unity3d asset bundle. The compilation step itself is a build operation, but the placement of inputs into the bundles folder is a copy.

Pattern 4: The bundle-to-Workshop copy. Compiled bundles destined for publication are copied into the Steam Workshop staging folder. This copy is the last step before the Workshop uploader picks up the files. The staging folder is intentionally separate from the bundles folder so an in-progress upload does not interfere with active development.

Pattern 5: The dated-backup copy. On a regular cadence — daily for active projects, weekly for stable projects — the project root is copied into a dated backup folder. The backup folder is named with the date in YYYY-MM-DD_vN form so backups sort chronologically and can be located quickly.

Pattern 6: The cross-machine copy. Mod developers working across multiple machines (a primary workstation and a laptop, for example) maintain a copy pipeline through a cloud sync service or a shared network folder. The cross-machine pattern is structurally a copy from one machine's local folder into the sync folder, followed by an automatic mirror to the other machine.

Each pattern has a default method. The reference-to-source and dated-backup patterns are typically performed through scripted Robocopy or PowerShell because they are repetitive and benefit from automation. The source-to-working and working-to-bundle patterns are typically performed manually through Ctrl + C and Ctrl + V because they happen during active editing. The bundle-to-Workshop pattern is sometimes manual and sometimes scripted depending on the project's publication cadence.

Best practice

Identify which patterns dominate your mod project and invest in tooling for the high-frequency ones. A single Robocopy command saved as a .bat file in the project root pays back across hundreds of repetitions over a project's life. Manual Ctrl + C and Ctrl + V is fine for low-frequency or ad-hoc copies, but high-frequency repetitive copies benefit from scripting.

Copy performance tuning for large projects

A mod project containing thousands of small files and dozens of large bundles exhibits copy-time behaviour that differs from a project containing only large files. The tuning techniques below are documented across the 57 Studios™ asset-management practice.

Tuning 1: Use solid-state storage for active projects. A project on an NVMe SSD copies internally at multi-gigabyte-per-second speeds. The same project on a spinning HDD copies at roughly one-tenth that speed and is severely penalised by the seek time on small-file collections. Mod developers working on projects with thousands of small icon files particularly benefit from SSD storage.

Tuning 2: Reduce small-file overhead. Where the project structure allows, consolidate many small files into fewer large files. A project with ten thousand small icon files copies far slower than the same project with the same icons consolidated into a single texture atlas. The atlas approach is an asset-pipeline optimisation, not a file-management one, but its impact on copy time is significant.

Tuning 3: Defragment HDD-resident projects. Spinning-platter drives benefit from defragmentation when copying large fragmented files. SSDs do not benefit and are harmed by defragmentation (each defrag write consumes a small amount of the drive's finite write endurance). Windows defragments HDDs automatically on a weekly schedule.

Tuning 4: Disable virus scanning for build-output folders. Real-time virus scanning intercepts each file as it is written to the destination. For trusted build-output folders, an antivirus exclusion can substantially speed up copies. The exclusion must be scoped narrowly to specific folders and must not include user-data folders or download locations.

Tuning 5: Use Robocopy multithreading for cross-drive bulk copies. Robocopy's /MT:N flag enables multithreaded copying where N is the thread count. A modern multi-core system benefits from /MT:8 or /MT:16 on cross-drive copies of folders containing many files. The thread count is bounded by the slower of the two drives' parallel I/O capacity.

Tuning 6: Compress large folders before cross-network copies. A 4 GB folder containing many small files copies across a gigabit network in roughly six to eight minutes due to per-file overhead. The same folder compressed to a single zip file copies in roughly thirty seconds because the per-file overhead is eliminated. Compress, copy, decompress is often faster than direct folder copy across slow networks.

Verifying copies cryptographically

For mission-critical copies, verifying that the destination bytes match the source bytes is the only way to know with certainty that the copy completed correctly. Windows ships with certutil and PowerShell ships with Get-FileHash, both of which can compute cryptographic hashes of files for comparison.

# Get the SHA-256 hash of the source file
$source = Get-FileHash 'C:\Project\Source\Crate.dat' -Algorithm SHA256

# Get the SHA-256 hash of the destination file
$dest = Get-FileHash 'C:\Project\Bundles\Crate.dat' -Algorithm SHA256

# Compare
if ($source.Hash -eq $dest.Hash) {
    Write-Host 'Copy verified: hashes match' -ForegroundColor Green
} else {
    Write-Host 'Copy failed: hashes differ' -ForegroundColor Red
}

The script computes the SHA-256 hash of both source and destination, compares them, and reports the result. Matching hashes prove the bytes are identical with cryptographic confidence. Non-matching hashes indicate a partial copy, a write error, or a silent data corruption event during transfer.

For bulk verification across a folder, the same approach extends to multiple files:

# Compute hashes of all source files
$sourceHashes = Get-ChildItem 'C:\Project\Source' -Recurse -File | ForEach-Object {
    [PSCustomObject]@{
        Path = $_.FullName.Replace('C:\Project\Source\', '')
        Hash = (Get-FileHash $_.FullName -Algorithm SHA256).Hash
    }
}

# Compute hashes of all destination files
$destHashes = Get-ChildItem 'C:\Project\Bundles' -Recurse -File | ForEach-Object {
    [PSCustomObject]@{
        Path = $_.FullName.Replace('C:\Project\Bundles\', '')
        Hash = (Get-FileHash $_.FullName -Algorithm SHA256).Hash
    }
}

# Compare
$sourceHashes | ForEach-Object {
    $match = $destHashes | Where-Object Path -eq $_.Path
    if (-not $match) {
        Write-Host "Missing at destination: $($_.Path)" -ForegroundColor Yellow
    } elseif ($match.Hash -ne $_.Hash) {
        Write-Host "Hash mismatch: $($_.Path)" -ForegroundColor Red
    }
}

The bulk script catches three failure modes: files missing from the destination, files present at both locations but with differing bytes, and the all-green case where every file matches.

Best practice

Run hash verification on the most critical copies in your pipeline: the bundle-to-Workshop copy and the dated-backup copy. A silent corruption in either path is an expensive failure to discover later. A two-minute hash verification at the time of the copy catches the issue immediately when remediation is straightforward.

Copy and the Recycle Bin

The Recycle Bin's relationship to copy operations is sometimes misunderstood. A copy operation does not touch the Recycle Bin. The Recycle Bin is engaged only when files are deleted. However, the Replace option in a copy conflict dialog can effectively delete the destination file, and that deletion does sometimes route the replaced file through the Recycle Bin.

Scenario	Goes to Recycle Bin?
Normal copy with no conflict	No
Copy with Replace option	Sometimes, depending on volume
Copy with Skip option	No (nothing deleted)
Copy with Keep both option	No (nothing deleted)
Copy to removable drive with Replace	No (removable drives bypass Recycle Bin)
Copy to network location with Replace	No (network locations bypass Recycle Bin)

The bypassing of the Recycle Bin on removable and network drives is a long-standing Windows behaviour. Files deleted from those locations — including files replaced by a Copy with Replace — are permanently removed. There is no Recycle Bin recovery for them.

Critical warning

Choosing Replace in a conflict dialog on a removable USB drive permanently deletes the destination file with no Recycle Bin recovery. Always verify your destination before clicking Replace on any drive that is not your primary internal drive.

Copy in scripted backup pipelines

Mod developers maintaining scripted backup pipelines typically use one of three approaches: Robocopy for raw file mirroring, PowerShell Copy-Item for fine-grained logic, or a dedicated backup utility for incremental backups with versioning.

Approach A: Robocopy mirror. A Robocopy mirror produces an exact duplicate of the source folder at the destination, deleting any files at the destination that no longer exist at the source. The /MIR flag is the mirror trigger.

robocopy 'C:\Project' 'D:\Backups\Project-mirror' /MIR /MT:8 /R:3 /W:5

The mirror approach is fast and simple but is destructive at the destination. Any file deleted from the source is also deleted from the mirror on the next run.

Approach B: PowerShell with logic. A PowerShell script can implement custom logic such as skipping certain file types, copying only files modified in the last 24 hours, or rotating backups across multiple destination folders.

# Copy only files modified in the last 24 hours
$since = (Get-Date).AddHours(-24)
Get-ChildItem 'C:\Project' -Recurse -File | Where-Object LastWriteTime -gt $since | ForEach-Object {
    $dest = $_.FullName.Replace('C:\Project', 'D:\Backups\Project-incremental')
    $destDir = Split-Path $dest -Parent
    if (-not (Test-Path $destDir)) { New-Item -Path $destDir -ItemType Directory -Force | Out-Null }
    Copy-Item -Path $_.FullName -Destination $dest -Force
}

The PowerShell approach is more flexible than Robocopy but slower for large folders due to the per-file PowerShell pipeline overhead.

Approach C: Dedicated backup utility. A dedicated backup utility such as Veeam Agent, Macrium Reflect, or Duplicacy provides incremental backups with versioning, encryption, and scheduling. Mod developers with multiple active projects often graduate to a dedicated utility once the simpler scripted approaches become difficult to maintain.

Best practice

Begin with Robocopy for backup pipelines. Move to PowerShell scripts when you need conditional logic. Adopt a dedicated backup utility only when the scripted approaches become unwieldy. The progression mirrors the growth of the project itself.

Appendix D: Extended FAQ on copy operations

Can I copy a folder onto itself to create a duplicate inside the same folder? Yes. Select the folder, press Ctrl + C, then press Ctrl + V inside the same parent folder. Windows creates a copy with a numeric suffix such as MyFolder - Copy or MyFolder (1). This is useful for creating an in-place duplicate of a working folder before making a risky change.

What does the Send to → Compressed (zipped) folder option do? It creates a single zip file containing the selected files at the same parent folder. The zip is a compressed archive, not a copy. The original files remain intact. The zip can then be copied or moved as a single unit. This is the standard pattern for transporting many small files across a slow network.

Why does copying to a OneDrive folder sometimes show the file in two places at once? OneDrive maintains a local cache and a cloud copy. The local cache appears in File Explorer. The cloud copy is the canonical version. The two are kept in sync automatically. The visible duplicate is a UI artifact, not two separate files.

Can I copy a file from a zip archive without extracting the entire archive? Yes. Double-click the zip archive in File Explorer to open it as a browsable folder. Select the file you want, press Ctrl + C, navigate to the destination, and press Ctrl + V. Windows extracts only the selected file to the destination.

Does the Send to menu offer copy targets? Yes. Right-click a file and hover over Send to. The submenu lists common destinations including Desktop (create shortcut), Compressed (zipped) folder, and Documents. Each Send to target is a copy with a slightly different behaviour. The Desktop target creates a shortcut rather than a copy of the file itself.

Why does the destination folder briefly flash during a copy? File Explorer refreshes its view when new files arrive. The flash is the refresh, not a copy issue. On large folders the refresh can be visually noticeable. The copy itself is unaffected.

Can I queue multiple copies to run sequentially? File Explorer combines multiple copies into a single progress dialog when they target the same destination folder. For separate destinations, each copy runs concurrently in its own progress dialog. Robocopy with the /JOB flag can queue named jobs for sequential execution, which is useful in scripted pipelines.

How do I copy a file's properties (timestamps, attributes) along with the file? File Explorer preserves the Modified timestamp by default. To preserve all metadata including Created timestamp, use robocopy /COPYALL or the xcopy /K flag. PowerShell's Copy-Item preserves Modified but not Created; use Set-ItemProperty after the copy to manually align timestamps if needed.

What happens to file sharing settings when I copy a file? File sharing settings live on the containing folder, not on the file itself. A copied file inherits the destination folder's sharing settings. The source file's sharing settings remain unchanged at the source. If you copy a file from a publicly shared folder to a private folder, the new copy is private.

Can I copy a file that I do not have read permission for? No. The copy operation requires read access at the source. If you encounter a permission error, you may need to take ownership of the source file (Properties → Security → Advanced → Change owner) or run File Explorer as an administrator. Both require administrator rights on the system.

Why is my copy from Google Drive failing for large files? Google Drive for Desktop streams files on demand by default. A large file may not be fully cached locally when the copy attempts to read it. Right-click the source file in Google Drive, choose Available offline, wait for the sync indicator to confirm the file is fully local, then copy.

Does the copy operation work the same way in PowerShell as in File Explorer? Yes for the underlying mechanics — both read source bytes and write to destination. The differences are in default behaviour: File Explorer prompts on conflicts, PowerShell silently overwrites with -Force or errors without it. PowerShell preserves fewer attributes by default. Robocopy preserves the most attributes of any built-in tool.

How can I tell whether a copy is hung or just slow? Open the progress dialog's More details view and watch the transfer-speed graph. A non-zero speed means the copy is progressing. A speed that drops to zero and stays at zero for more than thirty seconds suggests a hang. Cancel and retry; if the retry also hangs, investigate the destination drive's health.

Appendix E: Copy operation troubleshooting matrix

Symptom	Likely cause	Resolution
Copy fails immediately with error	Source path inaccessible	Verify source path exists and is readable
Copy starts but speed is zero	Destination unresponsive	Check destination drive connectivity
Copy completes but destination file is zero bytes	Write failure not reported	Inspect drive health, retry
Copy completes but destination file is partial	Cancelled mid-write	Retry copy in full
Copy fails with "path too long"	Combined path exceeds limit	Shorten parent folder names
Copy fails with "access denied"	Permission issue	Run as administrator or fix permissions
Copy fails with "sharing violation"	Source locked by application	Close application, retry
Copy fails with "destination full"	Insufficient destination space	Free space at destination
Copy is significantly slower than expected	Drive type mismatch or antivirus interference	Check drive types, add antivirus exclusion
Copy progress dialog freezes	UI thread blocked, copy itself may still progress	Wait, check Task Manager
Copy succeeds but destination file has wrong content	Source corruption or transport error	Hash-verify, re-run from known good source

The troubleshooting matrix is intended as a first-pass diagnostic. For persistent issues, run a drive health check (chkdsk or the drive manufacturer's diagnostic utility) and inspect the Windows Event Log for relevant file-system errors.

Appendix F: Copy operation glossary

• Source. The file or folder being copied from.
• Destination. The folder where the copy will be placed.
• Clipboard. The temporary holding area for the Copy operation's reference and flag.
• Copy flag. The clipboard indicator that the operation is a copy rather than a cut.
• Cut flag. The clipboard indicator that the operation is a cut.
• Conflict. The condition where the destination folder already contains a file with the same name as the file being pasted.
• Replace. The conflict-dialog option that overwrites the existing destination file.
• Skip. The conflict-dialog option that leaves the existing destination file untouched.
• Keep both. The conflict-dialog option that renames the incoming file with a numeric suffix.
• Progress dialog. The window that appears during a long copy showing transfer speed and remaining time.
• More details view. The expanded form of the progress dialog showing the transfer-speed graph.
• Robocopy. The command-line robust copy utility shipping with Windows.
• Hash verification. The technique of comparing cryptographic hashes of source and destination to confirm byte-identical copy.
• Mirror. A copy operation that produces a destination matching the source exactly, including deletion of destination files that no longer exist at the source.
• Multithreaded copy. A copy operation that uses multiple parallel threads to transfer files concurrently, available through Robocopy's /MT:N flag.
• Same-drive copy. A copy where source and destination reside on the same physical drive.
• Cross-drive copy. A copy where source and destination reside on different physical drives.
• Network copy. A copy where source or destination is a network share rather than a local drive.

Appendix G: Recommended copy practices by project phase

Project phase	Recommended copy practice
Pre-development	Establish folder structure; copy reference assets into _Source
Active development	Manual Ctrl + C / Ctrl + V for source-to-working copies
Mid-development	Daily Robocopy backup of project root to dated folder
Pre-release	Hash-verify bundle-to-Workshop copies
Post-release	Archive project root to long-term backup location
Maintenance	Weekly Robocopy mirror to off-site backup

The recommendations above represent the 57 Studios™ internal practice across many mod project lifecycles. Adapt the practices to your project's size and pace; small projects need less ceremony than large ones, but every project benefits from at least some copy-pipeline discipline.

Next steps

Now that you can copy files reliably, the related skill is moving them. Move differs from copy in one critical way: the source is removed after the operation completes. Continue to How to Move a File to learn the methods and the same-drive versus cross-drive behavior that affects how moves are performed.

After moving, the next skill in this section is renaming. Renaming changes a file's name without changing its contents or location. Read How to Rename a File to learn the four rename methods and the rules Windows enforces on filenames.

Once you can copy, move, and rename, the final core operation is creating folders to organise your files. Read How to Create a New Folder for the folder structure conventions that work well for Unturned™ mod projects.