How-to GuidePublished Updated 7 min read

How Long Does Transcription Take? Text Length and Hours per Hour of Audio

You've recorded a one-hour meeting, but until you know how long transcribing it will take, you can't plan around it. This article sets out roughly how much text an hour of audio produces, how the time multiplies for verbatim, clean and edited transcripts, and how to shorten the work, using figures you can actually apply. Text lengths are for Japanese, measured in characters.

How much text an hour of audio produces

People read a script aloud in Japanese at about 300 characters per minute. Announcers and speech-script guidelines both fall around this figure. Simple arithmetic gives 18,000 characters an hour, but a real meeting recording rarely reaches that, because it always includes silences, hesitations, pauses to look at documents and moments when people talk over each other.

Type of recordingCharacters per hourNotes
Read script / narrationAbout 18,000Few pauses, high density
Lecture / seminarAbout 14,000–17,000One person talking throughout
Meeting / discussionAbout 10,000–15,000Includes silences and pauses to check documents
InterviewAbout 12,000–16,000Questions and short responses come in between
Casual talk / brainstormAbout 8,000–13,000Plenty of overlap and inaudible parts

In other words, one hour of audio comes to 25–45 Japanese manuscript sheets of 400 characters. That wide range is what makes estimates hard. If you're unsure, the surest method is to transcribe just the first 5 minutes, count the characters and multiply by 12. The Reading & Speaking Time Calculator uses a read-aloud speed of 300 characters per minute, so you can also use it in reverse, to check how many minutes of speech a given length represents.

How many times the audio length the work takes

Manual transcription generally takes 4–6 times the length of the audio. A one-hour recording works out to nearly half a day. For someone inexperienced, a poor-quality recording or a meeting full of technical terms, it can exceed 8 times.

MethodTime for 1 hour of audioNotes
Typing by hand (inexperienced)5–8 hoursLots of rewinding
Typing by hand (experienced)3–4 hoursAssumes shortcuts and a foot pedal
Speech recognition + corrections1–2 hoursOnly for recordings that are recognized well
Speech recognition only (draft)5–30 minutesNot usable as it is
OutsourcingNo hands-on workTypical turnaround is 1–3 business days

Speech recognition shortens things dramatically, but only the typing time goes away; the checking time remains. Correcting the output against the audio means listening to it all again anyway, so allow 1–2 times the audio length. Estimate "five minutes with AI" and you will always run late. You can judge whether you count as experienced from your own typing speed: measure how many characters you type in a minute and you'll see which row applies to you (how to measure is covered in Typing Speed Benchmarks).

Verbatim, clean and edited transcripts

How far you tidy the text changes both the workload and what you end up delivering. It's the first thing to agree on, whether you're asking for a transcript or being asked for one.

TypeWhat it meansLengthWorking time
VerbatimWrite down everything, including "um" and "uh"LongestBaseline
CleanRemove hesitations and short responses80–90% of verbatimBaseline + 10%
EditedTidy into readable prose60–80% of verbatimBaseline + 30–50%
Summary / minutesKeep only the key points10–20% of verbatimSeparate task
  • Court records and research interviews need verbatim transcripts, because the way people speak is itself part of the material.
  • For minutes shared within a company, an edited transcript or a summary is enough. Nobody reads a circulated verbatim transcript.
  • When drafting an interview article, keep a clean transcript so you can pick up phrasing later.
  • Outsourcing rates vary by type, so when comparing quotes, always make sure the conditions match.

If you only need to record what a meeting concluded, deciding the headings in advance makes it faster. Headings and how to write them are covered in How to Write Meeting Minutes.

Steps to shorten the work

  1. 1

    Get the recording conditions right first

    Audio quality affects transcription time more than anything else. Just placing the microphone close to the speakers and away from directly below the air conditioner greatly reduces how often you have to replay. Checking that your microphone is picking up properly before the meeting can change the later work by several hours.

  2. 2

    Note speakers and proper nouns in advance

    List participants' names, product names and internal abbreviations beforehand. Having candidates ready is faster than stopping to look up each word you can't catch, and it also keeps spelling consistent.

  3. 3

    Listen through at speed before you start

    Don't begin typing right away. Listen to the whole recording once at around 1.5x. With the flow of the talk in your head, you can use context to fill in parts that are hard to hear. A run-through of one hour of audio takes only 40 minutes.

  4. 4

    Type without stopping and mark what you can't catch

    Rewinding for a single word breaks your concentration each time. Put a marker such as "■" at unclear spots, keep going and replay them together at the end; you'll finish sooner.

  5. 5

    Check against the audio at the end

    Check only the marked spots, numbers and proper nouns. Listening to everything again is only worthwhile when you're delivering a verbatim transcript.

How far you can raise playback speed depends on experience and how difficult the content is. With specialist material you're hearing for the first time, you start missing more above 1.5x. For how to find your limit, see How Fast Can You Set Playback Speed?.

How short to make it afterward

A transcript usually isn't the end goal; it's the stage before cutting the text down to something people will read. Share the 12,000 characters from a one-hour meeting as they are, and nobody will read them. At a silent-reading speed of 500 characters per minute, 12,000 characters takes 24 minutes. That's almost half the length of the meeting spent on reading, at which point listening to the recording at double speed would be quicker.

Shared withTarget lengthReading time
Decisions only300–600 charsAbout 1 min
Minutes for absentees1,500–2,500 chars3–5 min
Material for an interview article6,000–10,000 charsAssumes an editor reads it
Full text for the record10,000+ charsSearch and read only the relevant part

Paste your text into the Reading & Speaking Time Calculator to see how many minutes it takes for careful reading, normal silent reading and skimming. The basis for those speeds is explained in Estimating Reading Time. Before sharing, checking in numbers how many minutes you're asking people to read makes it easier to decide what to cut. And if you'd rather share the content again as audio, the same screen shows the read-aloud time.

FAQ

How much text does a one-hour meeting produce?
A meeting recording generally comes to about 10,000–15,000 Japanese characters. Reading a script aloud runs at about 300 characters per minute, so simple arithmetic gives 18,000, but real meetings include silences, pauses to read documents, hesitations and overlapping speech, so the total is lower. For an accurate estimate, transcribe just the first 5 minutes, count the characters and multiply by 12. Differences between recordings then show up directly in the result.
How many times the audio length does transcription take?
Typing by hand takes about 4–6 times the audio length, so a one-hour recording takes 4–6 hours. If you're inexperienced or the sound is poor, it can exceed 8 times. Drafting with speech recognition brings it down to 1–2 times, but the time to correct the output against the audio remains, so it never drops to zero. When estimating, always set aside separate time for checking.
What's the difference between verbatim and clean transcripts?
A verbatim transcript writes down everything exactly as heard, including hesitations like "um" and "uh" and short responses. A clean transcript removes hesitations and responses that don't affect the meaning, making it easier to read, and comes to 80–90% of the verbatim length. Beyond that come edited transcripts tidied into prose, and summaries keeping only the key points. Outsourcing rates differ by type, so always specify which you want.
Can I transcribe while listening at higher speed?
It's useful for a run-through to get the overall picture, but when you're actually typing, going back to normal speed or about 0.8x ends up faster. Typing at high speed means more missed words and more rewinding. The approach we recommend is one pass at 1.5x to get the flow, then transcribing at normal speed. Even after spending those 40 minutes up front, the total working time comes out shorter.

Tools in this article

Related articles

How-to Guide15 min read

How to Make a Word Cloud: Visualise Open-Ended Survey Responses for Free and Read Them Correctly

A training survey came back with 100 open-ended comments. You don't have time to read them all, but you still need to report what people said. That's where a word cloud helps: the more often a word appears, the bigger it is drawn. Made carelessly, though, it fills up with filler words, splits “group work” into two words, and counts “not fun” as “fun”. This guide covers how word clouds count words, step-by-step instructions for survey comments, how to remove and merge words, how font size is calculated, which shapes and colours work best, and how to read the result without drawing the wrong conclusion, all with numbers we actually counted.

Read article →
How-to Guide7 min read

How Long Should a Video Script Be? Working Back from Your Runtime

Deciding to make a 10-minute explainer doesn't tell you how long the script should be. Write too much and you end up rushing; write too little and it drags. This article covers typical narration speeds, how to work back from a runtime to a script length, and how to check the length before you record. The speeds are for Japanese, measured in characters, but the method works in any language once you know your own pace.

Read article →