Why Reddit is the honest data
Keyword tools tell you what people type into a search box. Reddit tells you what they say when a tool just ate two hours of their work. We read roughly a hundred threads across r/PhD, r/podcasting, r/Journalism, r/AskAcademia, r/QualitativeResearch, r/ProductivityApps and a dozen more, pulling the recurring complaints in people's own words.
The striking part wasn't the variety. It was the repetition. The same four failures showed up whether the poster was a PhD student with 100 hours of interviews, a podcaster with a weekly episode, or a lawyer trying to transcribe one long meeting. Here they are, worst first.
Complaint #1: long files just die
This was the single most common failure. People don't test a tool on a two-hour file before they trust it, so they find the wall the hard way, mid-project. One user in r/software put it flatly: "Everything I've tried kills it at 10 or 30 minutes." A ChatGPT user watched a long recording vanish: "Long Recording goes POOF."
The cruelest version is the silent failure. In r/applehelp, someone transcribed a 1-hour-39-minute meeting fine, then hit a wall at 2 hours 2 minutes with no warning – it was a lawyer's meeting. And the ambition is often bigger than the tools: a poster in r/software was feeding in "12gb / 13.5gb, ~4h each" recordings to turn a life's worth of interviews into a book.
The fix is unglamorous but real: don't cap by length. A tool that splits long audio into chunks, transcribes each, and stitches the timestamps back together has no reason to quit at 30 minutes. If you're building this yourself against a raw API, that's exactly the wall our guide to transcribing audio over 25MB and transcribing long audio walk through.
Complaint #2: the subscription you only needed once
Transcription is bursty. You get a batch of interviews, a season of episodes, a single long deposition – then quiet. Monthly subscriptions are the opposite shape, and people notice. "Everything seems to have a cap at about 15 or 20h per month," wrote a PhD student who needed 100. Another described the workaround everyone lands on: "sign up one month, batch everything, cancel."
The frustration sharpens when a plan gets tighter over time. Journalists in r/Journalism described being priced out ("unaffordable... can't upload more than 10 files a month without the Business plan"). The complaint isn't really about the money. It's about paying a recurring bill for a tool you use in bursts – renting minutes you'll never get back.
What people ask for instead is pay-per-use: buy the minutes you need, keep the ones you don't. That's the whole reason transcription without a subscription is a search people make on purpose.
Complaint #3: you don't even get the file
A surprising number of tools transcribe your audio and then won't hand you the result as a file you own. A commenter in r/ArtificialInteligence hit this with NotebookLM: it will answer questions about your audio, but "will not give it to you as a file." iPhone users hit it with Voice Memos, where you "can only copy and paste to export the transcript" – miserable for a 40-minute interview. And Zoom's own transcript, people keep rediscovering, "is available to the host only."
For anyone whose next step is a coding tool, a captions track, or a document, a chat you can't export is a dead end. The people who care most about this – qualitative researchers importing into NVivo, journalists pulling exact quotes – want real formats: a clean transcript file, SRT/VTT captions, DOCX. If you're stuck on the host-only wall, there's a way to get a Zoom transcript when you're not the host.
Complaint #4: accents and crosstalk quietly wreck it
The threads are honest about where AI still struggles. "The AI transcription I acquired for free is more or less useless" on strong accents, said one poster in r/academia. Another in r/ProductivityApps described the exact failure mode: "background noise, accents, or people talking over each other... results start falling apart."
No tool magically fixes heavy crosstalk – and the honest advice is that most of the win is upstream, before you ever hit transcribe: record separate tracks where you can, place the mic well, and denoise first. A current, large speech model plus a correction pass does the rest. We wrote up the practical version in how to improve transcription accuracy.
The worry under all of it: where does my audio go?
Privacy wasn't a separate complaint so much as a thread running beneath the others – and it has gotten louder. Researchers said it plainly: "also need it to be safe... sharing qualitative data from my PhD research." Others pointed at the headlines: "[a major transcription tool] has already been involved in numerous leaks and lawsuits."
Once a company holds your recordings, that's what an ethics board, a source agreement, or a nervous client actually cares about. The two questions people learned to ask: where are the servers, and does it train on my audio? For genuinely sensitive interviews, the most honest answer is often to keep it local (tools like aTrain or noScribe never upload). When you do use the cloud, confidential transcription comes down to a clear no-training policy you can put in writing.
What everyone actually wants
Stack the four complaints and the wishlist writes itself. People want to transcribe a file of any length without it dying halfway. They want to pay for what they use, not a monthly cap they'll blow mid-project. They want the actual transcript file, in the format their next tool eats. And they want to know the audio isn't training somebody's model.
That list is, more or less, the spec we built Pepys against – pay-once credits that never expire, no per-file length cap, real exports (TXT, SRT, VTT, DOCX, PDF, JSON), and no training on your audio, ever. We didn't invent those priorities. We just read the room. If any of the four complaints above sounds like your last transcription project, that's the room we built for.