The drive is not broken and your internet is not (always) the villain. An S3 drive pays an internet round trip for every file it touches — here is what that means, and how to work with it instead of fighting it.
Almost everyone who mounts an S3 drive has the same week-one complaint: opening a folder of small files feels sticky and slow, while one big video copies just fine. That is not a fault. This guide explains the reason honestly, lists the habits that make it worse, and covers big files — the one area where S3 quietly beats your expectations.
Illustration of relative feel, not a benchmark. Every small file costs its own internet round trip — that is the whole story.
A local disk answers in millionths of a second. Your S3 drive answers in internet time: every folder open, every file open, every save is a round trip to Amazon's servers. One round trip is fast. Hundreds of small files means hundreds of round trips, and that — not your drive tool — is what makes an S3 drive feel slow. No setting deletes physics; you can only work with it.
Be honest with the tool. A mounted S3 drive is the wrong home for: a live accounting or database file that a program keeps rewriting in small pieces, a folder another program constantly scans, or two people editing the same document at the same time — S3 keeps whole objects, so the last save simply overwrites the other person's work, with no locking and no warning.
The healthy pattern: work locally, store on S:. Edit on your real disk, then copy the finished file to the bucket drive.
Large files are actually where S3 shines, because big uploads use multipart upload: the file is cut into parts, parts go up in parallel, and a failed part can retry without starting the whole file again. AWS recommends multipart for files above roughly 100 MB, and a single object in S3 can be as large as 5 TB when uploaded this way. Drive tools handle this behind the scenes for large copies.
Every click shown live — installing TntDrive, adding the S3 account and mapping the drive in Windows.
▶️ Watch Full VideoBecause the bottleneck is not bandwidth, it is round trips. A folder of 500 photos needs hundreds of separate requests, and each request includes internet travel time plus Explorer asking for thumbnails. One 2 GB video is a single smooth stream, so it feels faster than 500 small files of the same total size.
Far bigger than you own: uploaded with multipart upload, a single S3 object can reach 5 TB. In practice your limits will be your patience and your upload speed, not S3.
They can open it, but they should not edit it together. S3 has no file locking for drive tools — whoever saves last wins, and the other person's version is silently overwritten. Work in separate copies, or use a real collaboration tool for shared live documents.