Why Managing Your Audio Across Google Drive, OneDrive, Old Phones and Hard Disks Is a Nightmare

Anyone who’s collected audio for a while — ripped CDs, downloaded audiobooks, saved podcast episodes — usually ends up storing it the same way: a folder on Google Drive, some files on OneDrive, an old phone with things nobody’s moved off it, a hard disk from three computers ago. It works, in the sense that the files still exist. It doesn’t work as a library, and the reason is specific: cloud drives are built for documents, not for audio.

What a document tool gets wrong for audio

Google Drive, OneDrive, and Dropbox are genuinely good at what they’re built for — storing and syncing files. What none of them do is anything an audio app needs:

• No resume position. Close a two-hour audiobook file on Drive and reopen it later, and it starts from zero. There’s no concept of “where you left off,” because Drive doesn’t know it’s an audiobook — to it, it’s just a file.
• No playback speed control. Most audiobook and podcast listeners use 1.25–2x. A file viewer doesn’t have a speed setting.
• No cross-device sync of anything except the file itself. The file syncs. Your position in it doesn’t, because that’s playback state, and playback state isn’t a thing a drive stores.
• No real organization for audio specifically. A 20-hour audiobook split into 40 chapter files just looks like 40 unrelated files in a folder, in whatever order the filesystem happens to sort them.

None of this is a bug. Drive, OneDrive, and Dropbox were never designed to be audio players — they’re designed to store and sync arbitrary files, and they do that well. Audio just isn’t an arbitrary file when you’re the one listening to it.

Where the actual mess comes from

The scattering isn’t usually one bad decision — it’s years of reasonable small ones. A phone fills up, so some files move to a laptop. The laptop gets replaced, so whatever wasn’t backed up stays on the old one, in a drawer. A new cloud account gets used for something specific and slowly accumulates its own separate pile. None of these were mistakes at the time. The result, a few years on, is a library split across four or five places with no single one of them being “the real one.”

The duplicate problem nobody notices until it’s big

Scattering has a second cost beyond inconvenience: duplication. The same audiobook downloaded again because the original couldn’t be found, the same album ripped twice at two different bitrates years apart, a podcast episode saved in three different folders because it seemed important each time. None of this shows up as a problem in the moment — it’s one extra file, easy to ignore. Multiplied across years of “just download it again,” it’s a meaningful chunk of a collection that’s redundant, unindexed, and taking up space nobody’s tracking, because nothing in a plain folder structure ever flags that the same thing already exists somewhere else.

Metadata rots faster than the files do

The files themselves usually survive years of scattering just fine — audio doesn’t corrupt from sitting still. What actually degrades is everything around the files: an audiobook ripped years ago with a filename like book2_final_v3.m4b instead of a title, a podcast episode with no episode number so it sorts wherever the filesystem feels like putting it, an album split across two folders because half of it got re-ripped at a different time. None of that breaks playback. It just means that a few years in, finding a specific thing means remembering what you happened to name it, not what it’s actually called — and that gap gets wider every year the collection sits in plain folders instead of something that reads the audio itself to know what it is.

When a cloud drive is genuinely fine

If it’s a handful of files, on one device, for one person who doesn’t need resume position or cross-device sync, a cloud drive folder is a perfectly reasonable place to keep them — there’s no reason to add a dedicated app for a use case that small. This becomes a real problem specifically at collection size, or the moment more than one device or person needs to reach the same files.

What we’re building

own.audio is a library built around what audio actually needs — resume position, playback speed, real organization by book and album rather than by file — instead of a document tool asked to do a job it was never built for.

It’s still in development. Register on the front page if you want to know when it’s ready.