Skip to main content

Batch Transcription: Transcribe a Folder at Once

Author: Published:

A folder of recordings (a week of field interviews, a stack of client calls, a semester of lecture audio) shouldn’t mean uploading one file, waiting, uploading the next, waiting again. Batch transcription in Hushscript treats the whole folder as one job: stage every file at once, review or adjust each one, and start the batch when you’re actually ready, not the moment you drop the first file. That’s the difference between a folder that takes ten minutes of setup and one that eats an afternoon of half-attention between other work.

Stage the folder, then start

Drop every file in the folder onto the upload area at once. Nothing transcribes the instant it lands; each one sits in a queue as a staged item, waiting for you to hit start. That gap between “dropped” and “started” is where the actual batch behavior lives: check the language setting on a file that’s in a different language than the rest, turn on multichannel for the one recording that came from a call recorder, add a one-off keyterm to the interview with an unusual name in it, then start everything together, or start individual files as you finish reviewing them. A folder of twenty files doesn’t have to be twenty separate trips through the same upload screen.

Merge the files that are really one recording

Not every file in a folder is a separate recording. A phone recorder that saves in chunks, a long interview split because a device restarted mid-session, a voicemail and the callback that answered it: these arrive as multiple files but represent one continuous conversation. Select the related staged files, put them in order, and merge them into a single transcript instead of transcribing separate fragments you’d have to stitch together by hand afterward. Speakers are tracked consistently across the whole merge, so the person labeled “Speaker A” in file one keeps that label in file three, and nobody resets to “Speaker A” again just because the recording did. If you’d rather hand Hushscript one file to begin with, the free in-browser audio joiner stitches the clips together locally first, so you upload a single merged result instead of a batch.

Batch cost and safeguards

A folder of five short call recordings and a folder of forty lecture files follow the same three steps: stage them, review them, start them. Each file can be up to 10 hours long, with no file-size limit. The minutes in your balance determine what the batch costs, while service safety and active-job safeguards determine how much work runs at once.

What trips up a batch upload elsewhere

Two failure patterns show up often enough to name plainly, without pointing at any one tool. The first is a forced one-at-a-time flow: upload, wait for that job to finish, then upload the next, with no way to queue several and walk away. The second is a small plan allowance that a real batch blows through without warning. Staging a folder and starting it as one batch avoids repeated setup. Hushscript still applies high service-safety and active-job safeguards, so an unusually heavy batch may queue rather than run all at once.

What a folder actually costs

A field researcher gets back from a trip with ten audio files: eight separate interviews, plus one interview that the recorder split into two parts partway through when it hit a file-size limit. All ten go into the upload area as a batch. The eight standalone interviews get reviewed and left staged; the two-part interview gets merged into a single ordered transcript first. Once everything looks right, the whole batch starts together: nine transcripts out of ten files.

Combined, the eight interviews plus the merged ninth run 250 minutes of audio. Against the $5.99 pack (300 minutes), that draws about $4.99 worth of the pack (5.99 × 250 ÷ 300), leaving roughly 50 minutes banked for the next trip. One upload session, one price for the whole folder, no per-file transaction and no separate charge for the file that happened to arrive in two pieces.

Where to start

Batch uploading and merging both live on the same upload screen as every other job. See audio to text for the full upload flow, including the options you can set per file before you start. If most of what fills your folders is calls, memos, and voicemails specifically, voice recording to text covers that case in more detail, merge included. And because a folder rarely costs the same twice, pay-as-you-go transcription is worth reading before you buy a pack: you’re charged for total minutes, not per file, so the math above scales to whatever’s actually in your folder. For the single longest file in that folder, how to transcribe a long recording covers the up-to-10-hour case on its own.

Frequently asked questions

Is there a limit to how many files I can batch upload?

Stage a batch and start it together. Each file can be up to 10 hours long, with no file-size limit; your prepaid balance plus service safety and active-job safeguards apply.

What happens if I merge files that aren't actually the same recording?

Merging is deliberate, not automatic. You choose which staged files join a merge and the order they play in before you start. Only combine files you intend to read as one continuous conversation.

Does merging files cost more than transcribing them separately?

No. Cost is based on the total minutes transcribed, the same per-minute rate as any other job, whether that duration comes from one file or several merged together.

Can I start some files right away and leave others staged?

Yes. Start an individual file the moment you drop it, or leave several staged and start them together later; the queue doesn't force either approach.

Do all the files in a folder need to be the same audio format?

No. Drop whatever formats you have. Hushscript prepares each one appropriately, and for a merge, brings mismatched audio into a matching format automatically before combining them.

Start with 30 free minutes

Start — 30 free minutes