Is a walkthrough a recording or a document?
Both, if you want both: the recording shows the screen, the transcript holds the words. The order of the sentences is the order of the actions, so the text reads as the list of steps it really is.
Loom transcript: a walkthrough as written steps, in the order the words were said, so a colleague can follow it without watching the screen. Free $0.
Upload the recording of the walkthrough and you get the instructions in writing, in the order the words were said, so the steps can be followed without scrubbing back and forth. One file is up to 30 minutes, and the free plan is $0 with 3 files a day.
The person who recorded it gives you the file, and the service opens no Loom links: there is no connector to Loom and no account of ours inside it.
Drop the file on the widget above. A walkthrough of a few minutes is far below the limit of 30 minutes per file on the free plan, no minute limit, so it fits as it is.
The sentences come back in the order they were spoken, and each one carries the start and the end of it, so the order of the actions is kept.
Markdown for a wiki page, TXT for a mail, DOCX for an editor on Pro, and CSV when each step has to keep the moment it was said.
Plain text for an email, a note or a chat
Subtitles for video editors and platforms
Subtitles for a browser and a website
A table: time, speaker, text
A Word document with speakers and times
Text with headings for notes
| What | Value |
|---|---|
| One recording | up to 30 minutes per file on the free plan, no minute limit on Pro |
| The order | the sentences come back in the order they were said, so the order of the actions is kept |
| The screen | not analysed: only the sound of the file is transcribed |
| The price | $0: 3 files a day. Pro is $10 a month paid yearly ($120 a year) |
A screen recording is a good way to show a colleague where the button is and a bad way to tell them what to do. The picture is gone in a month, the voice is gone in a week, and the person who was watching has to ask again. What a walkthrough really is, underneath the screen, is a list of steps in the order they were done, and that list is what a transcript gives you.
A walkthrough is a list of steps in disguise.
Number the steps while you read the transcript.
Put the text where the team already works.
Keep the recording next to the written guide.
Both, if you want both: the recording shows the screen, the transcript holds the words. The order of the sentences is the order of the actions, so the text reads as the list of steps it really is.
Yes: TXT or Markdown for a doc, DOCX for an editor on Pro, and CSV when each step has to keep the moment it was said next to it.
Only the sound of the file is transcribed. The labels and the buttons you see in the recording are not in the transcript, so a written guide still needs the picture.
Descript is an audio and video editor with transcription at its centre, and it announces 23+ transcription languages in its llms.txt (descript.com/llms.txt, read on 21 October 2026). Ours does the other half of the job: it gives the text and leaves the recording alone.
Speakers by name, a time on every line, export to TXT, SRT, VTT, CSV and Markdown.