Recommended Free Tools
For thousands of small files, start with Robocopy’s multithreaded mode and a log file: /MT keeps several file operations in flight, while /LOG removes console-output overhead and gives you an audit trail. Use a moderate thread count, cap retries and waits, then compare elapsed time on your actual source and destination. More threads are not automatically faster, and /MIR can delete files from the destination.
Why thousands of small files copy slowly
Microsoft describes a large small-file workload as hundreds, thousands or even millions of files, commonly under 1 MB each. The problem is not simply the total number of bytes. Every file requires separate directory, metadata and file-system work, and an SMB transfer repeats network operations for each object. When one file is being created, the connection may not be transferring much payload data, so a copy can show low network throughput even when the network is not the only bottleneck.
As an Amazon Associate I earn from qualifying purchases.
Per-file work dominates
A single large file can keep a transfer moving continuously. A directory containing the same number of bytes in thousands of small files instead spends time opening, creating, closing and recording each file. On an SMB path, those operations cross the network as well. Repeated antivirus inspection can add another per-file delay on the source, destination or both.
Free tools Windows power users keep installed
One-click scans. No signup required.
Low bandwidth does not prove a bad network
If the workload is dominated by file creation and metadata, a faster network link may not fix the elapsed time. Measure storage and CPU activity on both ends, as well as the network, before deciding what to change. Robocopy’s multithreading is intended to overlap those waits; it is not a guarantee of a particular speedup.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Why file count matters more than total size
Two jobs can contain the same 20 GB yet have very different completion times. A few large files mostly exercise sustained read and write bandwidth. Millions of tiny files repeatedly exercise namespace lookups, permissions checks, timestamp updates and close operations. Directory depth and the number of entries in each directory also affect the amount of metadata work. Record these characteristics when comparing runs; a timing from a different file mix is not a useful benchmark.
Use this safe starting command
Create the log directory first, replace the example paths, and run Robocopy from Command Prompt:
mkdir "C:Logs"
robocopy "C:Source" "D:Destination" /E /COPY:DAT /MT:16 /R:2 /W:5 /LOG:"C:Logscopy.log"This is a starting experiment, not a benchmark-backed optimum. It recursively copies the source, includes empty directories, preserves the standard data, attributes and timestamps, uses 16 worker threads, retries a failed operation twice and waits five seconds between retries, then writes the run output to a file.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →| Switch | What it does | Why it matters here |
|---|---|---|
/E |
Copies subdirectories, including empty ones. | Reproduces the directory structure without using the deletion behavior of a mirror operation. |
/COPY:DAT |
Copies data, attributes and timestamps. | Preserves the standard file information specified for this command. It is not a request to copy every possible security or ownership field. |
/MT:16 |
Runs 16 copy threads. | Overlaps work on many small files so one file’s creation wait does not leave the transfer idle. |
/R:2 |
Retries a failed file operation two times. | Prevents a transient problem from turning into an effectively endless run. |
/W:5 |
Waits five seconds between retries. | Sets a deliberate recovery delay instead of accepting Robocopy’s very long default wait. |
/LOG:"C:Logscopy.log" |
Writes output to the named log file. | Reduces time spent continuously printing status and lets you inspect the result after completion. |
Microsoft’s general Robocopy guidance strongly recommends creating a log and checking it after the run. Make sure the log location is writable and is not inside the source tree you are copying. If the destination is on a share, store the log on a reliable local path or another location that will remain available if the share disconnects.
What this command does not do
It does not make an exact mirror, copy every security descriptor or guarantee that locked files can be read. Those are separate requirements. Decide first which metadata the destination needs, then choose a copy mode that matches it. Adding switches without testing can change permissions, ownership handling, deletion behavior or failure semantics.
Choose the right thread count
Robocopy’s documented default is eight threads when multithreading is enabled without a number (for example, /MT). The documented range is 1 to 128 threads. Microsoft also warns that too many threads may harm performance, so treat 16 in the example as a test point rather than a universal answer.
A repeatable tuning procedure
- Choose a representative portion of the workload or a complete run that you can repeat. Include the same mix of file sizes, directory depth and file count in every trial.
- Run with
/MT:8, record the start and finish time, and keep the log. - Repeat with
/MT:16, then test higher values only if the source, destination and network still have capacity. - Compare total elapsed time, not just the instantaneous transfer rate shown during a run.
- Record source and destination CPU use, storage activity, memory pressure and network utilization. Stop increasing the thread count when one of these becomes saturated or elapsed time stops improving.
- Use the fastest stable setting that completes without excessive retries or errors. Keep the command and log for the setting you select.
| Trial | Example setting | Purpose |
|---|---|---|
| Baseline | /MT:8 |
Matches the documented Robocopy multithread default. |
| Moderate increase | /MT:16 |
Tests more overlap without jumping immediately to the upper range. |
| Higher concurrency | /MT:32 or /MT:64 |
Tests whether the actual storage and SMB path can use additional workers. |
| Upper limit | /MT:128 |
The documented maximum; use only as a measured experiment, not as a default. |
Microsoft’s Azure Files migration guidance reports balanced initial-copy performance between eight and 20 threads for that particular service and scenario. That observation should not be treated as a general Windows optimum; a local disk, a conventional SMB server and another cloud service can behave differently.
Why a very high value can backfire
Each worker adds scheduling, queueing and metadata pressure. On a busy disk, workers can contend for the same device. On a server, simultaneous opens and directory updates can consume CPU before the network link is full. Antivirus may inspect more files concurrently, increasing that overhead rather than hiding it. If /MT:64 takes longer than /MT:16, that is a useful result: keep the lower setting instead of treating the maximum as a goal.
Set retries and waits deliberately
Robocopy’s documented defaults are one million retries and a 30-second wait between retries. A disconnected share, locked file or unavailable destination can therefore make a command appear stuck for a very long time. Explicit values such as /R:2 /W:5 make the failure policy visible and bounded.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Choose values according to the failure you expect. A brief network interruption may justify several retries and a longer wait; a permanently missing path does not. Whatever values you choose, inspect the log for files that exhausted their retries instead of assuming that command completion means every file was copied successfully.
Retry settings also affect benchmarking. Use the same /R and /W values in every trial, and report failures separately from elapsed time. A run that finishes quickly because it gave up immediately is not faster in any useful sense. Correct connectivity, permissions, free space and file locks before drawing conclusions from a failed pass.
Do not use /MIR as a speed switch
/MIR is equivalent to /E plus /PURGE. It makes the destination an exact mirror by deleting destination files and directories that are not present in the source. That behavior is appropriate only when deletion is an intentional part of the synchronization plan.
For a one-way copy in which existing destination-only data must remain, use /E as in the starting command and leave /MIR out. If you do need a mirror, verify the source and destination paths character by character, use a log, and test with a non-critical destination before allowing deletions on production data.
Copy versus synchronization
A copy adds or updates items at the destination while leaving unrelated destination data alone. A mirror also removes items that no longer exist at the source. Decide which outcome the project requires before optimizing speed. A destructive synchronization can complete quickly and still be a serious operational failure if the wrong path is supplied.
Make the command fit the transfer path
Local disk to local disk
Local copies avoid SMB protocol latency, but each small file still creates file-system and metadata work. Test thread counts rather than assuming that a faster SSD or a high /MT value will solve the problem. If storage activity is already saturated, additional workers can compete for the same device and increase overhead.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11SMB share to SMB share or a mapped path
This is the scenario emphasized by Microsoft’s small-file guidance. Confirm that both endpoints are reachable and then tune concurrency against the real server, share and workload. Source and destination storage, SMB processing, antivirus scanning and the network can each become the limiting factor. A low network percentage during the run is consistent with a file-creation bottleneck.
Use the same path style when comparing tests, whether you use UNC paths or mapped drives. Keep other activity on the shares as constant as possible. A backup job, user traffic or server-side scanning can change the result more than a small adjustment to thread count.
Cloud or appliance migration
Service-specific guidance takes precedence over a generic local-copy recipe. Azure Files migration instructions use an example with /MT:16, low retry values and a repeat run to copy changes after the initial pass. Treat those switches as guidance for that migration scenario, not as a universal command for every cloud endpoint.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
A repeat pass is useful when the source remains active: the first run transfers the bulk of the data, and a later run catches files created or changed afterward. Schedule that pass according to the service’s migration procedure and verify the log from each run.
When archiving can help
Combining many small files into an archive can reduce the number of individual file operations during the transfer. However, the end-to-end result depends on compression and decompression speed. A fast or no-compression mode reduces processing overhead, while a heavily compressed archive may spend enough CPU time compressing and extracting to erase the transfer benefit.
Compare the complete workflow: archive creation, transfer and extraction. Include verification and cleanup in the elapsed time. Do not assume that archiving is faster on every PC, storage system or network path, and do not compare only the time spent copying the archive itself.
Archiving also changes operational behavior. The destination receives one or a few large objects instead of the original directory tree until extraction finishes, so you need enough temporary space and a plan for interrupted extraction. If users or applications need individual files during the transfer, a direct multithreaded copy may be more practical despite lower apparent bandwidth.
Special Azure Data Box Disk limits
Microsoft gives separate recommendations for Azure Data Box Disk. For a workload consisting mostly of files under 512 KB, its scenario-specific table recommends four Robocopy sessions with 16 threads per session. The same documentation states a per-session ceiling of 7,000 directories and 150 million files.
Those figures describe Data Box Disk usage, not general Robocopy limits. Do not multiply them into a rule for a local disk, ordinary SMB share or another appliance. Use the service’s migration instructions when the destination is a managed appliance, because its session limits and ingestion behavior determine the useful concurrency.
Four sessions at 16 threads means 64 active Robocopy workers in that particular recommendation, but it is not a reason to launch 64 threads against an unrelated destination. Respect the appliance’s directory and file ceilings, divide work according to its documented procedure, and validate that each session’s log identifies the intended source and destination.
Measure before and after each change
A useful test records more than a progress percentage. Keep the source data, destination and command constant while changing one variable at a time.
| What to record | Why it helps |
|---|---|
| Source and destination paths | Separates local, SMB and service-specific behavior. |
| File count, size distribution and directory depth | Shows whether two trials actually represent the same workload. |
| Thread count | Identifies the concurrency setting used for each run. |
| Total elapsed time | Provides the result that matters to the person waiting for the copy. |
| Retries and errors in the log | Distinguishes a fast complete copy from a fast run that skipped files. |
| CPU and storage load at both ends | Reveals whether workers are waiting on processing or devices rather than bandwidth. |
| Network utilization for SMB transfers | Shows whether the link is full or whether per-file overhead is dominating. |
| Metadata requirements | Confirms that the selected /COPY mode preserves what the destination needs. |
Use the same retry and logging policy for every trial. A run that finishes quickly only because it stopped retrying is not an improvement. Review the log before accepting the timing.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Make tests repeatable
Run trials when competing workloads are comparable, use the same destination state where possible, and avoid mixing an initial copy with an incremental update. Warm caches, changed files and server-side activity can all affect timing. Record whether the run was a first pass or a repeat pass, and note any errors before changing the command.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshoot common results
More threads make the copy slower
Reduce the thread count and check resource use. The destination may be saturated, the source may be spending more CPU time on antivirus inspection, or the SMB server may be handling too many simultaneous operations. Microsoft’s warning that too many threads may harm performance applies directly here.
The network graph stays low
Check file count and size distribution first. Thousands of tiny files can spend most of their time in creation and metadata operations. Inspect CPU and storage activity on both endpoints before changing the network configuration.
The command waits for a very long time
Review the retry policy. If you did not specify /R and /W, Robocopy can use the documented defaults of one million retries and 30 seconds between waits. Stop the run if the destination is clearly unavailable, correct the path or connectivity problem, and restart with explicit bounded values.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Files remain on the destination that are not in the source
That is expected when using /E; it does not purge destination-only data. If exact mirroring is required, plan for /MIR and its deletion behavior, validate the paths, and review the log. Do not add /MIR merely because a copy is slow.
Some files fail while most succeed
Use the log to identify the affected paths and the reason reported by Robocopy. Check whether the files are locked, the destination has sufficient space, permissions allow the operation and the share remained available. After correcting the cause, rerun with a bounded retry policy and verify the resulting log.
Antivirus activity dominates
Small files can trigger repeated scanning on each endpoint. Measure whether CPU or storage activity rises during the copy, and follow your organization’s security policy before changing scanning behavior. Do not disable protection simply to obtain a faster timing.
The log is missing or incomplete
Check that the parent directory existed, the account running Robocopy could write there and the path was not on the failing destination share. Use a local log path for network jobs when practical. Without a complete log, you cannot reliably distinguish copied files, skipped files, retries and errors.
A practical decision path
- Start with
/E /COPY:DAT /MT:8 /R:2 /W:5and/LOGon a representative workload. - If the run is stable, compare
/MT:16and then higher values only when measurements justify them. - Keep the setting with the shortest complete elapsed time and acceptable resource use, not the highest thread count.
- Use archiving only after timing the full archive-transfer-extract workflow.
- Use Azure Files or Data Box Disk commands and limits only for those services.
- Reserve
/MIRfor an explicitly approved synchronization plan because it deletes destination-only data.
Robocopy is already included with Windows, so the main optimization is disciplined concurrency, bounded failure handling and verification through logs. The right setting is the one demonstrated by your own source, destination and file mix.
Frequently Asked Questions
What is the best Robocopy thread count for thousands of small files?
There is no universal optimum. Robocopy uses eight threads by default with /MT, accepts 1 through 128, and Microsoft warns that too many threads may reduce performance. Benchmark /MT:8, /MT:16 and higher values on the actual workload, then keep the fastest complete and stable result.
Does /MT:128 always copy faster than /MT:16?
No. Higher concurrency can saturate storage, CPU, SMB processing or antivirus scanning and make the run slower. The documented maximum of 128 is a limit, not a recommendation.
Why is network utilization low during a small-file copy?
Each file requires separate creation, metadata and SMB operations. Workers may be waiting on file-system, storage or antivirus work rather than transferring payload bytes, so low bandwidth does not by itself indicate a network fault.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What are Robocopy’s default retry settings?
The documented defaults are one million retries and a 30-second wait between retries. Set explicit values such as /R:2 /W:5 when you need a bounded, predictable failure policy.
Should I use /MIR to speed up a copy?
No. /MIR is /E plus /PURGE and deletes destination files and directories absent from the source. Use it only for an intentional, validated mirror operation.
Is /J useful for thousands of small files?
Microsoft recommends /J for large files because it uses unbuffered I/O. It is not the first small-file optimization; test multithreading and logging first.
Can archiving thousands of files make the transfer faster?
Sometimes, because fewer objects cross the transfer path. Compare archive creation, transfer, extraction, verification and cleanup together. Compression and decompression speed can eliminate the benefit, especially with heavy compression.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →What is the Azure Data Box Disk recommendation for mostly tiny files?
For files mostly under 512 KB, Microsoft’s scenario-specific guidance recommends four Robocopy sessions with 16 threads per session. It also lists a per-session ceiling of 7,000 directories and 150 million files. Those figures do not apply to ordinary disks or SMB shares.
The Bottom Line
Begin with /MT:8 or /MT:16, log every run, and set explicit retry and wait limits. Measure complete elapsed time alongside CPU, storage and network load, then keep the fastest stable setting for your source and destination. Use /MIR only when deletion is intentional, and follow separate Azure guidance for Azure Files or Data Box Disk.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
