File copy engine for WindowsNever aborts a job100% on device
File Explorer gave up at 92%. Copyr doesn't.
A locked file, a bad sector, or a file that vanished mid-transfer and Windows stops the whole batch. Copyr skips what it can't read and keeps going, then hands you a retry list when it's done.
v1.1.0 beta · Windows 10 (1809+) & 11 · 64-bit · Installs without admin rights · No account
01 How it works
Drop. Preflight. Copy. Report.
Give it the files
Drag them onto the window from File Explorer, or press Ctrl O to choose files and folders. There's no Explorer right-click entry in this beta yet, so the window is the way in.
Read the preflight
Before a byte moves: how much free space you'll have left, which files are OneDrive placeholders about to be downloaded, anything already unreadable, and whether the destination is a network location.
Watch it run
A live speed graph of the last minute, plus the same numbers as a plain readout, because a shape can't be the only channel. Pause any time; it flushes to disk first, so a pause is always a safe moment to unplug.
Read the report
Every skip and failure, each with a reason and a Windows error code. A name that's already taken is never a mid-job interruption. It's recorded and walked past, then waiting for you in a review sheet once the transfer finishes.
02 Features
Everything File Explorer's copy isn't.
A copy engine you can pause, resume, interrupt and verify, built for the case where the copy is the only remaining copy.
Never aborts on one file
A file that can't be read costs one line in the end-of-job report (with a reason and a Windows error code), not the rest of the job. Explorer stops the whole transfer; Copyr keeps going and tells you exactly what it skipped.
Skip & continue
Never waits for you, either
Nothing in the copy loop can block on a window. A name that's already taken is recorded and walked past, and you're asked once the whole transfer is finished, so a job left running overnight comes back done, with the questions still waiting in a review sheet. Answering "Replace" or "Keep both" queues a small follow-up job over just those files.
Non-blocking
Pause and resume mid-file
At a chunk boundary, not just between files. Pausing flushes to disk first, so a pause is always a safe moment to unplug the drive.
Mid-file
Survives an unplugged drive
Pull the drive mid-copy and the job waits for it. Plug it back in and Copyr continues from the last durable checkpoint, so at most 64 MB is ever redone. Resume survives quitting the app entirely, too.
Checkpointed
Nothing half-written wears a real name
Content is written to
Atomic rename
<name>.copyr-part and renamed into place only once it's completely written (and verified, if you asked for that). The classic failure where a file looks fine and then stops playing 40 minutes in can't happen.Optional SHA-256 verification
Reads each file back after it lands and compares it to what was read from the source. Off by default, because it roughly halves throughput, and most people offloading a card don't want that every time. Turn it on when the copy is the only remaining copy.
Verify-after
Honest preflight, honest speed
Before a byte moves: free space (the amount actually available to you, not just the disk total), OneDrive placeholders about to be downloaded, anything already unreadable, and a network-location warning. While it runs, a live speed graph shows the last minute, reported as a plain readout too, so the shape isn't the only channel.
Preflight
Real Windows timestamps
Created, modified and accessed dates are preserved with the Win32
SetFileTime
SetFileTime call, the one that can actually set "Date created," which Python's ordinary file-timestamp APIs can't touch.Long paths, junctions, done right
Every filesystem call goes through a
Windows-native
\\?\-prefixing helper, so a destination past the old 260-character limit works instead of failing three hours in, and that prefixed spelling never leaks into the UI or Explorer. Junctions and reparse points are never followed (that's how a folder walk finds a cycle); they're recreated as real links where Windows allows it, and recorded as an advisory where it doesn't.The mark of the web, handled honestly
NTFS alternate data streams (including the hidden
Opt-in
Zone.Identifier stream that marks a file as downloaded) are not carried over by default, so copying your own files never quietly tags them as "from the internet." An opt-in checkbox carries streams forward when you actually want them, and the preflight says which way it went either way.Move, safely
Copy and Move are a per-job choice, never a saved default, because a destructive setting turned on once and forgotten is how someone loses a shoot. Choosing Move turns verification on for you, and each original is deleted only after its copy is completely written and checksummed.
Never a default
100% on your PC
Copying happens entirely on your machine. File names, sizes and paths are never uploaded, there's no account, and there's no usage analytics. The only network call Copyr makes on its own is the update check.
Private
13 languages
English, Spanish, French, German, Italian, Portuguese (BR), Dutch, Polish, Russian, Turkish, Japanese, Simplified Chinese and Korean. Copyr follows your Windows display language automatically.
Localized
Built for everyone
Fully keyboard-driven (choose files with Ctrl O), with live announcements for job-state changes, Windows High Contrast support, reflow with no horizontal scrolling, and measured WCAG 2.1 AA contrast in light and dark.
WCAG 2.1 AA
03 Works with
Local drives
USB & external drives
OneDrive placeholders
Junctions & symlinks
Long paths past MAX_PATH
Network locations (best-effort)
04 Beta
You're testing the first Windows build.
Copyr has been on the Mac for a while. This is the Windows port's first public build: a copy engine built from scratch on Win32 APIs, not a wrapper around the Mac one. It passes its own headless test suite.
What would help most
Copies you can check
Turn on SHA-256 verification for a job and compare the result against files you know. Any mismatch, however small, is the most important thing you could report.
Real numbers, real hardware
Does the throughput reading and the speed graph's shape look plausible for your drive? A number that's obviously wrong is exactly what this beta needs to catch.
Pull the plug
On a copy you don't mind redoing, unplug the drive mid-transfer. It should wait, then resume correctly (redoing at most 64 MB) when you plug it back in.
The install itself
Whether SmartScreen let you through, whether the shortcut and taskbar icon look right, whether uninstall leaves anything behind.
06 Pricing
Free for you. Fair for work.
Personal use is free forever: the full engine, unlimited copies, no key, no account, no nag screens. If Copyr earns its keep at your job, a one-time commercial license keeps it supported.
Personal
Free forever
For individuals and personal projects
- The full engine, every feature
- Unlimited copies, any size, any volume
- Pause, resume, verify, move
- 100% on-device, nothing uploaded
- No account, no nag screens
- Free updates forever
Commercial
$9 / device
One-time payment, no subscription
- Everything in Personal
- Use commercially at work
- One-time payment, no subscription
- Free updates forever
- Supports solo indie development
The personal tier is the full app. Buy a commercial license only if you use Copyr commercially. One seat per device, paid once, yours for life. Secure checkout via Stripe; your license key is emailed instantly. Copyr has no license gate to unlock: the key is your record of the purchase, and the same key covers the Mac build too.
07 Download & install
Get set up in about a minute.
Run the installer and Copyr lands in your own user folder: no admin password, no UAC prompt, nothing else to install.
Version 1.1.0 beta · Copyr-Setup.exe · about 12 MB · Free updates forever
Windows 10 (version 1809 or later) or Windows 11 · 64-bit
Everything Copyr needs is inside the installer: no Python, no runtime to chase down. It does use the Microsoft Edge WebView2 Runtime to draw its interface, which ships with Windows 11 and reaches almost every Windows 10 machine through Windows Update. On the rare PC without it, Copyr will say so on launch and Microsoft's free installer is a one-click fix.
No admin rights needed
Copyr installs per-user into
%LOCALAPPDATA%\Programs\Copyr, so there's no UAC prompt and no argument with your IT department. Uninstall from Settings → Apps → Installed apps like anything else.Windows may warn you the first time. Here's the honest story.
Copyr is Authenticode-signed, so the publisher shows as a real, verified name rather than "Unknown publisher." But signing alone does not switch SmartScreen off: Microsoft builds reputation per file, and a brand-new build starts with none. Until this exact file has been downloaded enough times, you may still see a blue "Windows protected your PC" box.
- Click More info
- Check the publisher name shown
- Click Run anyway
08 FAQ
Common questions.
Is Copyr really free?
Personal use is free forever: the whole app, unlimited copies, no account, no trial timer, no nag screens. If you use Copyr at work, a one-time $9 commercial license per device keeps it supported.
Is this like TeraCopy?
Same idea: a copy queue with pause, resume and verification, instead of File Explorer's all-or-nothing copy. Copyr is its own independent implementation, not affiliated with TeraCopy or Code Sector, built around a specific set of guarantees: a bad file never stops the job, a name collision never interrupts it mid-transfer either, and a verified copy really has been read back and compared, not just assumed.
What happens when a file can't be read?
The job keeps going. The bad file is recorded with its reason and Windows error code, and everything else copies normally. At the end you get a report listing every skip and failure, which you can copy as text or save as CSV. That's the whole point: one unreadable file on a failing card shouldn't cost you the rest of the job.
What if I unplug the drive mid-copy?
The job pauses and waits for that volume to come back. Plug it in again and it continues from the last durable checkpoint. Copyr checkpoints its position every 64 MB, so at most 64 MB is ever redone. This survives quitting the app too. Pausing deliberately flushes to disk first, so a paused job is always a safe moment to unplug.
Can a copy leave me with a half-written file?
No. Content is written to a file named
<name>.copyr-part and only renamed into place once it is complete (and verified, if verification is on). So the classic failure where a file looks fine in File Explorer and then stops playing 40 minutes in can't happen. Cancelling a job deletes the partial; an interruption deliberately leaves it, because that partial is what makes resuming possible.Should I turn on verification?
It's off by default, on purpose. SHA-256 hashing both sides roughly halves throughput, and most people offloading a card don't want that every time. Turn it on when the copy is the only remaining copy: archiving a shoot, or migrating a drive you're about to erase.
Does Copyr replace File Explorer's Ctrl+C?
Not yet. This beta has no right-click "Copy with Copyr" entry in File Explorer. You hand it files by dragging them onto the window or pressing Ctrl O to choose them. It's a separate window you route a copy through, not a drop-in replacement for Explorer's own copy command.
Can Copyr move files, not just copy them?
Yes. Move is a per-job choice next to Copy, and it is deliberately not a saved default. Every job starts at Copy. Choosing Move turns verification on for you, since the originals are deleted on the strength of those writes, and a file left waiting on a name-clash question keeps both its original and its partial destination alone until you answer.
What's this OneDrive placeholder warning in the preflight?
A file that looks normal in File Explorer but whose bytes are still up in OneDrive, not on this PC. Copyr detects these before a byte moves (via the same Windows attribute Explorer itself uses) and tells you how much would need to download first, rather than silently stalling mid-copy while Windows fetches it.
Does it work over the network?
It runs, and Copyr says so plainly rather than promising something it can't guarantee: a network location is flagged in the preflight as best-effort for both speed and resume. Local drives, USB and external drives are the fully supported case.
Does Copyr upload anything?
No. Copying happens entirely on your PC. File names, sizes and paths are never uploaded, there is no account, and there is no usage analytics. The one network connection Copyr makes on its own is the update check described below, which sends nothing about your files.
How do I update Copyr?
It updates itself. Copyr checks about once a week and lets you know when there's something new. Click through and it downloads the new installer, verifies its Authenticode signature and version before running anything, installs over itself and reopens. If any of those checks fail it deletes the download and sends you here instead. Your settings carry over.
Why did Windows show a blue "protected your PC" warning?
Because the file is new, not because it's unsigned. SmartScreen builds trust per file over downloads and time, and a fresh build starts from zero. Code signing gives you a verified publisher name in the dialog but does not skip the warning by itself. Click More info → check the publisher → Run anyway. See the install section for the full explanation.
How is this different from the Mac version?
Same core guarantees (skip-and-continue, pause/resume, atomic renames, optional verification), rebuilt on Win32 APIs rather than Apple's. This beta doesn't yet have a few things the Mac build has: an Explorer right-click entry, a saved checksums manifest you can check later, and a one-click "retry just what failed." It does have things the Mac build has no equivalent for: OneDrive placeholder detection, NTFS alternate-data-stream handling, and a collision system built from the ground up to never interrupt a running job. A commercial-license key covers both builds.
Where do my settings live, and what does uninstalling remove?
Preferences and any in-progress job records (so an interrupted copy can resume) sit in
%APPDATA%\Copyr. Uninstalling removes the app from %LOCALAPPDATA%\Programs\Copyr; delete the folder above too if you want every trace gone. Nothing is written outside your user account.