File timestamps look tiny until they betray you. A photo folder that once read like a family calendar suddenly becomes a shuffled deck; project files lose their sequence; a NAS migration turns “created” into “copied today.” If you move files between Mac, Windows, and NAS devices, preserving timestamps is not cosmetic. It protects sorting, search, audits, backups, and your own sanity. In about 15 minutes, you can learn which timestamps matter, which tools keep them intact, and how to move files without turning your archive into digital confetti.
Why Timestamps Break During File Moves
The short version: every platform keeps time differently, and every transfer method has opinions. Finder, File Explorer, cloud sync apps, SMB shares, zip tools, backup software, and NAS indexing services may all touch file metadata. Some preserve modified dates. Some overwrite created dates. Some preserve dates only if you copy, not if you export. It is a tiny bureaucracy wearing a hard drive costume.
I once moved a client’s 2014 event photos to a NAS using a drag-and-drop copy. The images survived, but the folder view looked like everything had been born at 9:42 p.m. on a Tuesday. The files were fine. The timeline was soup.
The three main reasons timestamps change
First, copy behavior differs from move behavior. A true move on the same volume usually keeps more metadata. A copy to another file system often creates a new file record, so “created” may become the copy date.
Second, file systems store metadata differently. APFS on Mac, NTFS on Windows, exFAT on portable drives, and Linux-based NAS file systems do not treat every timestamp the same way.
Third, network protocols translate metadata. SMB is the usual bridge between Mac, Windows, and NAS. It can preserve key fields, but permissions, time zones, NAS settings, and client tools matter.
- Modified dates are easiest to preserve.
- Created dates are more fragile across platforms.
- Metadata-aware tools beat casual drag-and-drop for important archives.
Apply in 60 seconds: Pick one test folder with 20 mixed files and copy it using your planned method before moving the real archive.
Which Timestamps Actually Matter
Before choosing a tool, decide what “preserve timestamps” means for your situation. The word “timestamp” is a small drawer with several smaller drawers inside it.
Modified date
The modified date is the date a file’s contents were last changed. For most workflows, this is the timestamp you must protect. Project sorting, code reviews, photo exports, manuscript drafts, scanned documents, and evidence folders often depend on modified date.
Good news: modified dates are usually the most portable timestamp. Robocopy, rsync, FreeFileSync, ChronoSync, Carbon Copy Cloner, Synology Drive, QNAP tools, and many NAS backup systems can preserve modified dates when configured correctly.
Created date
The created date is the file system birth date. It is useful, but slippery. When a file is copied to a new disk, a new file record may be created. On some systems, that means the created date becomes the copy date. The original creation date may still live inside embedded metadata, especially for photos and videos, but the file system date can change.
I learned this the boring way after copying invoice PDFs from a Mac to a Windows workstation. The modified dates stayed correct. The created dates all became migration day. Accounting did not laugh. Accounting rarely does.
Accessed date
The accessed date tells when a file was last opened or read. Many systems disable or reduce access-time updates for performance. For everyday archiving, it is usually less important than modified and created dates.
Embedded metadata dates
Photos, videos, office documents, audio files, and PDFs may contain internal dates. A JPEG may include DateTimeOriginal in EXIF. A video may have creation time in its media metadata. A Word document may store authoring dates. These can survive even when the file system date changes.
If your real goal is to preserve when a photo was taken, do not rely only on Finder or File Explorer dates. Check embedded metadata too. For a deeper workflow on photo batches, your internal guide on batch renaming large photo collections pairs well with this step.
| File Type | Most Important Date | Why It Matters | Best Check |
|---|---|---|---|
| Photos | EXIF taken date plus modified date | Timeline sorting and albums | Photo app metadata panel or ExifTool |
| Videos | Media creation date plus modified date | Event order and editing workflows | MediaInfo or app metadata view |
| Office files | Modified date | Version history and draft order | File properties |
| Legal or audit files | Modified date, hash, chain notes | Evidence integrity | Checksum report plus read-only copy |
| Code projects | Modified date plus Git history | Builds and audits | Git status and file listing |
Who This Is For / Not For
This guide is for people who need a reliable file move, not a heroic data-center migration with blinking lights and a man in a vest whispering into a headset.
This is for you if...
- You are moving files from a Mac to a Synology, QNAP, TrueNAS, Unraid, or other NAS.
- You are copying Windows folders to network storage and need modified dates to stay intact.
- You are consolidating photos, videos, client folders, podcast assets, scans, or family archives.
- You sort files by date and cannot afford a migration that makes everything look new.
- You want a repeatable workflow for future moves.
This is not for you if...
- Your drive is clicking, disconnecting, or showing SMART errors. Stop and consider recovery help.
- You need forensic-grade evidence handling for court. Use a specialist workflow.
- You only need a casual copy of a few downloads where timestamps do not matter.
- You expect every created date to survive perfectly across all file systems without testing.
For people managing many client folders, timestamp preservation belongs inside a bigger folder system. Your own related post on practical folder organization for multiple clients is a useful companion because date integrity means little if the folder map is a haunted attic.
Best Transfer Methods for Mac, Windows, and NAS
The tool you choose should match the job. A 40-file folder can survive Finder. A 4TB archive deserves a proper copy utility and verification. The bigger the move, the less you should trust vibes.
Best overall options
| Method | Best For | Timestamp Strength | Watch Out For |
|---|---|---|---|
| Robocopy | Windows to NAS or Windows to Windows | Excellent for modified dates | Command syntax and permissions |
| rsync | Mac, Linux, NAS shell transfers | Excellent when flags are right | Old macOS rsync version and metadata flags |
| FreeFileSync | Visual cross-platform sync | Very good for normal archives | Need to review sync direction |
| ChronoSync | Mac power users | Strong | Paid software |
| NAS backup app | NAS-to-NAS or cloud backup | Strong if configured | App-specific settings |
| Finder or File Explorer | Small, low-risk copies | Mixed | Created dates may reset |
Decision card: choose your safest path
Decision Card
If you are on Windows: use Robocopy for serious transfers. Start with a test run and log file.
If you are on Mac: use rsync, ChronoSync, Carbon Copy Cloner, or a tested sync app. Finder is fine for a snack-sized copy, not the banquet.
If you are moving to a NAS: connect by SMB, use a wired network, avoid sleep, and verify a sample before deleting the source.
Visual Guide: The Timestamp-Safe Move
Copy a small folder with mixed file types.
Use Robocopy, rsync, or a trusted sync app.
Compare file counts, sizes, dates, and hashes.
Keep the source untouched until the audit passes.
Mac to NAS Timestamp-Safe Workflow
Mac users often meet timestamp trouble when moving from APFS to a NAS share. The NAS may be running a Linux-based file system under the hood, while your Mac connects through SMB. Everyone shakes hands politely, then quietly disagrees about metadata.
Step 1: Connect through SMB
In Finder, use Go > Connect to Server, then enter your NAS address, usually something like smb://nas-name.local or smb://192.168.1.20. SMB is generally the best modern choice for Mac-to-NAS file sharing.
Avoid mixing connection methods during one migration. Do not copy half over SMB, half through a web upload panel, and half through a sync app unless you enjoy debugging with a lantern.
Step 2: Use rsync carefully
For many Mac users, rsync is the cleanest command-line option. A practical starting point is:
rsync -avh --progress "/Users/you/Documents/Archive/" "/Volumes/NASShare/Archive/"The -a archive flag preserves permissions, symbolic links, and modification times. The trailing slash after the source folder means “copy the contents of this folder,” not the folder wrapper itself.
I once forgot that trailing slash during a late-night migration. The result was a folder inside a folder inside a folder, a little nesting doll of regret. The timestamps were fine. My pride needed a checksum.
Step 3: Consider metadata beyond modified dates
Mac files can carry extended attributes, resource forks, Finder tags, and package structures. If you care about Mac-specific metadata, test with representative files: Photos libraries, Logic projects, Final Cut bundles, fonts, and app project folders.
Show me the nerdy details
On macOS, file system metadata can include POSIX permissions, modification time, creation time, extended attributes, Access Control Lists, Finder flags, and resource fork data. Standard rsync archive mode protects modification time, but not every Mac-specific attribute in every scenario. Apple ships file-copy tools such as ditto, and third-party sync tools may expose options for extended attributes and ACLs. A NAS share over SMB may translate or omit some metadata depending on server settings, permissions, and file system support. For timestamp preservation, test modified time first, then creation time, then extended attributes if your workflow depends on Finder tags, bundles, or app libraries.
Step 4: Keep the Mac awake
Large transfers and sleep mode are natural enemies. Use Energy Saver or Battery settings to prevent sleep. For serious migrations, plug in the Mac and use Ethernet. Wi-Fi is convenient, but a wired transfer has fewer little gremlins hiding in the walls.
- Use SMB for modern NAS access.
- Test rsync on a small folder first.
- Use Ethernet for big archives.
Apply in 60 seconds: Copy one folder with rsync, then compare the same files in Finder before starting the full move.
Windows to NAS Timestamp-Safe Workflow
Windows has a wonderfully sturdy built-in tool for this job: Robocopy. It feels like it was designed by someone who owned three clipboards and trusted none of them. That is good news for timestamp preservation.
Use Robocopy for important transfers
For a normal folder copy from Windows to a NAS share, start with:
robocopy "D:\Archive" "\\NAS\Share\Archive" /E /COPY:DAT /DCOPY:DAT /R:2 /W:5 /LOG:"C:\transfer-log.txt"Here is what the key parts mean:
- /E copies subfolders, including empty ones.
- /COPY:DAT copies data, attributes, and timestamps.
- /DCOPY:DAT copies directory data, attributes, and timestamps.
- /R:2 retries failed files twice.
- /W:5 waits five seconds between retries.
- /LOG saves a transfer record.
Use /MIR carefully
Robocopy’s /MIR option mirrors source and destination. It can delete files at the destination that do not exist at the source. This is powerful, but it is also the command-line equivalent of handing a raccoon a label maker and a key to the archive.
Use /MIR only after a dry run and only when you truly want the destination to match the source.
Do a dry run first
Robocopy offers /L to list what it would do without actually copying. Example:
robocopy "D:\Archive" "\\NAS\Share\Archive" /E /COPY:DAT /DCOPY:DAT /LUse it before a large transfer, especially if the destination already contains files. Logs are not glamorous, but when a move fails at file 38,204, glamour will not rescue you.
Moving Files Between Mac and Windows
Mac-to-Windows transfers introduce two extra wrinkles: file system compatibility and filename rules. If you have ever met a file named with a colon, trailing space, or invisible character, you know the archive can contain tiny goblins wearing punctuation.
Avoid exFAT for your only archive
exFAT is convenient for portable drives because Mac and Windows can both read and write it without extra drivers. But convenience is not the same as resilience. For temporary shuttling, exFAT is useful. For long-term storage, prefer a NAS, APFS for Mac-only drives, or NTFS for Windows-managed drives with a proper backup plan.
Normalize filenames before migration
Windows rejects certain characters and reserved names. Mac users may not notice until the transfer throws errors. Before copying a large archive, scan for problematic names. Your internal article on auto-generating consistent filenames is helpful here because clean naming reduces transfer failures and makes date verification easier.
Use zip archives only when you understand the tradeoff
Zip files may preserve internal file modified dates, but extracting them can alter created dates. Some zip tools handle metadata better than others. For moving many small files, a zip can reduce transfer overhead, but test extraction dates on the target system.
Short Story: The Folder That Arrived Tomorrow
A photographer once sent a drive that looked perfect on her Mac. The wedding folders were tidy: rehearsal dinner, morning prep, ceremony, reception. On a Windows editing machine, several folders appeared to have been modified “tomorrow.” The problem was not time travel, sadly. It was a mix of time zone handling, daylight saving changes, and a copy tool that rounded timestamps differently on the destination file system. We made a small sample transfer, compared the original files against the copied set, then switched to a tool that preserved modified times consistently. The lesson was simple: do not judge the whole migration by one file browser column. Compare a sample, check the metadata that matters, and keep the original untouched until the copied archive proves itself.
Photo, Video, and Media File Gotchas
Media archives are where timestamp preservation becomes emotional. Nobody wants their child’s first beach photo sorted beside yesterday’s tax scan because a file move got dramatic.
File date and capture date are not the same
A photo can have a file modified date, a file created date, and an EXIF DateTimeOriginal. Camera apps, editing apps, export tools, and cloud services may change one while leaving another alone.
For photos, the date taken is often embedded inside the image. For videos, the capture date may be stored in QuickTime, MP4, or camera-specific metadata fields. If your media library depends on date taken, inspect embedded metadata before panicking over file system dates.
Cloud downloads can rewrite dates
Downloading from cloud services may set file created or modified dates to the download time. Some services provide original metadata in the file; others package exports in a way that needs special handling.
I once downloaded a large phone photo archive and watched every file line up under the same afternoon. It felt efficient in the way a library fire is efficient. The rescue was embedded metadata plus a batch tool to rebuild file dates from capture dates.
Use metadata tools for media repairs
ExifTool is widely used by photographers, archivists, and technical users because it can read and write many metadata formats. MediaInfo is useful for inspecting video metadata. Apple Photos, Adobe Lightroom, and other catalog apps may also show capture dates independently of file system dates.
If you manage huge image libraries, internal cleanup matters too. Your post on Google Photos de-duplication fits naturally after a timestamp-safe transfer because duplicates and bad dates often travel together like badly behaved cousins.
Mini Calculator: Transfer Time Estimate
Use this rough calculator before a big NAS move. Real speeds vary by file size, Wi-Fi quality, drive speed, and NAS load.
Estimated transfer time will appear here.
How to Verify Timestamps After Transfer
A transfer is not finished when the progress bar disappears. It is finished when you have proof. The proof does not need to be theatrical. A small audit beats a large assumption.
Use a four-part verification check
- File count: compare total files and folders.
- Total size: compare source and destination size.
- Timestamp sample: check 20 to 50 files across old, new, large, small, and nested folders.
- Checksum sample: verify hashes for critical files or full sets where needed.
Windows verification commands
On Windows, Robocopy logs are useful. You can also use PowerShell to inspect date fields:
Get-ChildItem "D:\Archive" -Recurse | Select-Object FullName, LastWriteTime, CreationTime | Export-Csv "C:\source-dates.csv" -NoTypeInformation Get-ChildItem "\\NAS\Share\Archive" -Recurse | Select-Object FullName, LastWriteTime, CreationTime | Export-Csv "C:\dest-dates.csv" -NoTypeInformationFor basic file integrity checks, Windows includes tools such as CertUtil for hashes:
certutil -hashfile "D:\Archive\important.pdf" SHA256Mac verification commands
On Mac, use Terminal to inspect modified dates:
stat -f "%Sm %N" "/Users/you/Documents/Archive/example.pdf" stat -f "%Sm %N" "/Volumes/NASShare/Archive/example.pdf"For hashes:
shasum -a 256 "/Users/you/Documents/Archive/example.pdf"Risk scorecard: how much verification do you need?
| Risk Factor | Low Risk | High Risk |
|---|---|---|
| Archive value | Replaceable downloads | Client, legal, financial, or family records |
| File count | Under 1,000 files | Over 50,000 files |
| Platforms | Same OS and file system | Mac, Windows, NAS, cloud mixed |
| Verification needed | Sample check | Logs plus checksums plus backup |
- Compare file counts and sizes.
- Spot-check modified dates across folder depths.
- Use hashes for critical files.
Apply in 60 seconds: Pick five old files and five recent files, then compare their modified dates on source and destination.
Common Mistakes That Reset File Dates
Most timestamp damage happens during ordinary, reasonable actions. Nobody wakes up and says, “Today I shall erase temporal order from my archive.” Yet here we are.
Mistake 1: Trusting drag-and-drop for a serious archive
Finder and File Explorer are fine for casual moves. For business archives, media libraries, or NAS migrations, use a tool that logs results and preserves timestamps by design.
Mistake 2: Deleting the source too soon
The source copy is your lifeboat. Keep it until the destination has passed verification and at least one backup exists. If the original drive is failing, clone it first or get help.
Mistake 3: Mixing transfer tools midstream
Copying part of an archive with Finder, another part with a NAS web interface, and another part with a sync app can produce inconsistent dates. Pick one primary method per migration.
Mistake 4: Ignoring time zones
NAS devices, Macs, and Windows PCs should use correct time zone and network time settings. A mismatch may not destroy timestamps, but it can make comparisons look wrong.
Mistake 5: Forgetting folder timestamps
Some tools preserve file timestamps but not folder timestamps unless configured. If folder dates matter to your workflow, use options that copy directory timestamps too, such as Robocopy’s /DCOPY setting.
Mistake 6: Assuming photos are ruined when file dates change
Media files often retain capture metadata. Before declaring disaster, check EXIF or media metadata. The file may still remember the birthday party even if the file system insists it happened yesterday.
Mistake 7: Letting sync conflicts pile up
Cloud sync and NAS sync tools can create conflict copies. Those duplicates may have new dates and messy names. If this is already happening, read your internal guide on large digital asset libraries before expanding the mess.
Tools, Cost, and Decision Guide
You do not need the most expensive tool. You need a tool that matches your risk level, platform, and tolerance for command-line work. A perfect utility you never use correctly is just a tiny museum of good intentions.
Cost table: common timestamp-safe tools
| Tool | Typical Cost | Skill Level | Best Use |
|---|---|---|---|
| Robocopy | Included with Windows | Intermediate | Windows bulk moves with logs |
| rsync | Free | Intermediate | Mac, Linux, NAS transfers |
| FreeFileSync | Free or donation-supported | Beginner to intermediate | Visual folder comparison |
| ChronoSync | Paid | Beginner to intermediate | Mac scheduled sync and archive jobs |
| Carbon Copy Cloner | Paid | Beginner to intermediate | Mac backup and cloning jobs |
| NAS native backup tools | Usually included | Varies | NAS-to-NAS, cloud, and scheduled jobs |
Buyer checklist for sync and copy software
- Can it preserve modified timestamps?
- Can it preserve folder timestamps?
- Does it provide preview or dry-run mode?
- Does it create readable logs?
- Can it resume interrupted transfers?
- Can it compare source and destination before copying?
- Does it handle file permissions in the way you need?
- Does it support your NAS connection method?
Eligibility checklist: is your archive ready to move?
Timestamp-Safe Move Checklist
- I have a current backup of the source.
- I know whether modified date, created date, or embedded date matters most.
- I tested my method on a sample folder.
- My Mac, Windows PC, and NAS time zones are correct.
- I will save a transfer log.
- I will verify file counts, sizes, dates, and critical hashes.
When to Seek Help
File transfers are usually safe, but some situations carry real data-loss risk. This is the practical safety section: not dramatic, not alarmist, just the part where we stop juggling porcelain.
Get professional help before copying if...
- The source drive clicks, grinds, disconnects, overheats, or mounts only sometimes.
- You see file system errors, bad sectors, or SMART warnings.
- The archive is needed for legal, regulatory, tax, insurance, or business dispute purposes.
- You already ran a failed migration and files are missing or duplicated.
- You are moving irreplaceable media with no backup.
The National Institute of Standards and Technology is a useful authority for thinking about data integrity, cybersecurity, and digital evidence practices. For ordinary home or office transfers, you do not need a laboratory process. But the principle still applies: preserve originals, document actions, and verify results.
Do not keep retrying a failing drive
If a drive is physically failing, repeated copy attempts can make recovery harder. A safer path may be a disk image or professional recovery evaluation. The brave move is not always the loud move. Sometimes the brave move is unplugging the drive and making tea while you call someone competent.
For legal or audit evidence, avoid casual handling
If timestamps may be used in a dispute, ask an attorney, IT forensic specialist, or qualified records professional before changing anything. Opening, copying, syncing, or previewing files can alter metadata. A normal business copy is not the same as forensic preservation.
- Failing drives can worsen with repeated attempts.
- Legal files may need special handling.
- Originals should stay untouched until verified copies exist.
Apply in 60 seconds: If your drive is acting strange, disconnect it and write down exactly what happened before taking the next step.
FAQ
How do I preserve timestamps when copying files to a NAS?
Use a metadata-aware copy tool instead of casual drag-and-drop. On Windows, Robocopy with /COPY:DAT and /DCOPY:DAT is a strong choice. On Mac, rsync, ChronoSync, Carbon Copy Cloner, or a tested sync app can preserve modified dates. Always run a sample transfer first and compare source and destination timestamps before moving the full archive.
Does copying files change the modified date?
A proper copy tool can preserve the modified date. Finder, File Explorer, NAS web upload tools, and cloud downloads may behave differently depending on file type, file system, and settings. The modified date is usually easier to preserve than the created date, but you should still test your exact workflow.
Why did my created date change after moving files?
The created date often reflects when a file record was created on the destination file system. When you copy a file to another disk, operating system, or NAS, the destination may create a new file record and set the created date to the copy time. This is common and does not always mean the file contents or embedded metadata changed.
What is the best Windows command to copy files and keep timestamps?
Robocopy is usually the best built-in Windows option. A practical command is robocopy "source" "destination" /E /COPY:DAT /DCOPY:DAT /R:2 /W:5 /LOG:"C:\transfer-log.txt". Use /L first for a dry run if you want to preview actions without copying.
What is the best Mac command to copy files and keep timestamps?
rsync is a common option. A basic command is rsync -avh --progress "source/" "destination/". The archive flag preserves modification times and other standard attributes. For Mac-specific metadata, test carefully or consider dedicated Mac backup software that supports extended attributes and ACLs.
Do photos lose their original date when copied?
The file system date may change, but the photo may still contain the original capture date in EXIF metadata. Before repairing dates, check the image metadata in a photo app or with a tool such as ExifTool. For photo libraries, the embedded capture date is often more important than the file created date.
Is exFAT safe for moving files between Mac and Windows?
exFAT is convenient for temporary transfer drives because Mac and Windows both support it. It is not ideal as your only long-term archive. For valuable files, keep a backup elsewhere and verify timestamps after copying. For NAS storage, use the NAS file system and access it through SMB rather than relying on a shuttle drive alone.
Can cloud storage preserve file timestamps?
Sometimes, but not always in the way you expect. Sync clients may preserve modified dates better than browser downloads. Export tools may package files with metadata, while downloaded files may receive new created dates. Test one folder before trusting a cloud export for a full archive.
How do I check if timestamps were preserved?
Compare file counts, total size, and a sample of modified dates across old and new files. For critical files, compare SHA-256 hashes. On Windows, use Robocopy logs, PowerShell, and CertUtil. On Mac, use Finder, Terminal stat, and shasum. Keep the original source until verification is complete.
Should I preserve folder timestamps too?
Preserve folder timestamps if your workflow depends on folder sorting or historical folder structure. Robocopy can do this with /DCOPY:DAT. Some tools preserve file timestamps but not directory timestamps by default, so test folder dates separately.
What should I do if timestamps are already wrong?
Do not delete the original. Check whether the correct dates still exist in another copy, backup, EXIF metadata, media metadata, or cloud version history. For photos and videos, you may be able to rebuild file dates from embedded capture dates. For legal or business records, ask a qualified professional before mass-editing metadata.
Conclusion
The first fear was simple: you move files, and the calendar inside them collapses. The calm answer is also simple: know which timestamp matters, choose a tool that preserves it, test a small folder, and verify before deleting anything.
Your next 15-minute move is practical. Pick one representative folder, copy it with Robocopy on Windows or rsync on Mac, then compare file count, size, and 10 modified dates. If that test passes, scale up. If it fails, you caught the problem while it was still small enough to hold in one hand.
Timestamp preservation is not about worshiping metadata. It is about keeping memory, order, and work history intact. The files are the books. The timestamps are the shelf labels. Keep both, and the archive stays readable.
Last reviewed: 2026-06
