When a twenty-minute tutorial turns into an hour of copying sentences, try separating two jobs: keeping a source you can search later, and writing what you actually need to remember or use.

Keep the transcript as reference material. Make a much smaller note containing your question, a few useful moments and something to try. This works in a plain Markdown file as well as in a notes app.

A September 2026 discussion in r/ObsidianMD raised this exact problem: a learner was spending 40–60 minutes or more taking notes on a twenty-minute video. That is one person’s experience, not a benchmark for how quickly anyone should learn. Difficult material can deserve a long pause. The useful question is what you are doing during that pause.

Start with a question you can answer

Before playing the video, write one sentence about what you want from it.

For a programming tutorial, that might be: “When should I use this data structure, and can I implement the simplest example?” For a photography lesson: “How does changing camera position affect the background?”

That question helps you decide what belongs in the note. You do not have to capture every sentence to make the session useful.

Export the reference transcript with BYTE

Workflow checked against BYTE 0.9.2 source on 13 November 2026. This is a source-verified guide, not a recording of a live browser export.

At Hand Tools makes BYTE: Bulk YouTube Transcript Exporter. Here is the part it handles: saving available YouTube captions as a file you can search while writing your own notes. It does not write those notes or transcribe a video with no available captions.

1. Start with one captioned video

Install BYTE in desktop Chrome, then open the video you want to study. Start with one video rather than exporting a whole channel: the aim is to learn the workflow and inspect the result.

Look for BYTE’s Download transcript control on the video page. The controls described here use the extension’s English labels; another interface language may show translated labels.

2. Choose a reference-friendly export

Open Transcript settings using the settings control. Choose Markdown (.md) and turn on Timestamps. Under Included details, enable Video title, Channel name and Video URL.

Those details make it easier to identify the source later. Timestamps give you a place to return when checking a caption against what was actually said or shown. Choose an available caption language that fits your work; do not treat a translated track as the original wording.

3. Download, then inspect the file

Close settings and select Download transcript. Open the resulting Markdown file in a text editor or your notes app.

Check that the title and source link match the video, then search for a phrase you remember hearing. Compare that passage with the video. Caption errors and missing visual information still need your judgment.

If BYTE reports No transcript available, do not treat that as a successful export. Check the video’s caption availability. BYTE exports existing captions; it does not create a transcript from missing audio captions.

4. Write your own note beside the transcript

Keep the exported file as reference material. Create a separate note using the template below. Add the real source URL and the name of the actual transcript file you downloaded.

Illustrative personal note, not BYTE-generated output and not a quotation from a real video:

# Understanding a queue

Source: [Replace with the real video title](PASTE_REAL_VIDEO_URL)
Transcript file: PASTE_ACTUAL_EXPORTED_FILENAME
Question: When is a queue a better fit than a stack?

## My explanation
- A queue handles items in arrival order.

## Check against the video
- Find the passage explaining arrival order.
- Rewatch the diagram; the transcript does not preserve it.

## Try it
- Write a small queue example and test the removal order.

The distinction matters: BYTE supplies the caption reference. The question, explanation and exercise are yours.

When you need several videos

On a public playlist, BYTE’s Download transcripts action opens Choose videos. Review the matching set rather than assuming it contains exactly the sources you intended. The Title contains filter can narrow the set.

For separate reference files, leave Merge into one file off in the bulk settings. Review the final downloaded count and any issues before treating the collection as complete. Captions may be unavailable for some entries. Do not assume every selected item succeeds.

For a single video you do not need to save locally, YouTube’s built-in Show transcript may be enough. YouTube’s guide explains that option.

Keep a source record

At the top of the note, save the video’s actual title, creator and URL. Add the date you watched it. A link named only “YouTube” creates another lookup task later.

This is a concrete capture problem, not just a tidiness preference. In a November 2026 Reddit question about capture workflows, the author described postponing inbox cleanup because saved links lacked useful titles. A small source record lets you identify an item without opening it again.

Capture moments, then explain them

While watching, jot down the time and the reason you want to return. A rough line such as “08:20 — why the first attempt fails” can be enough.

Afterward, explain the useful idea in your own words and decide what to do with it. For a tutorial, try a small example without following the presenter step by step. For research, write what the source contributes to your question and what it leaves unresolved.

This is a workflow to try, not a promise that every video will take less time. If you cannot explain a step, return to it. The aim is to spend the extra time on understanding rather than duplicating narration.

Copy this Markdown template

# Video title

Source: [Actual video title](PASTE_VIDEO_URL)
Creator:
Watched:
Question I want to answer:
Transcript file, if saved:

## Moments to revisit
- 00:00 — Why this moment matters

## My explanation
- The idea in my own words:
- A condition or limitation:

## Try it
- One example, exercise or decision:
- What happened when I tried:

## Verify
- A quotation, number or claim to check:
- A diagram or demonstration the transcript leaves out:

## Still unclear
- A question for the next session:

Replace the placeholder time with a real one. The template uses ordinary headings, lists and links supported by Markdown; Obsidian documents these in its formatting guide. It does not require a plugin or a particular folder system.

Check what the transcript cannot tell you

A transcript does not preserve every diagram, code change or visual demonstration. If the explanation depends on what happens on screen, save a timestamp and describe what to inspect there.

Caption text can also be wrong. YouTube warns that automatic captions may misrepresent speech because of accents, mispronunciations or background noise. Check quotations, names and important numbers against the original before relying on them. YouTube’s automatic-caption guidance explains the limitation.

An AI summary can help you organize reference material, but keep it separate from the transcript and your own conclusions. Check its supporting passages rather than assuming a tidy summary is faithful to the video.

A small test for the next video

Try the template on one video you already intended to watch. When you return the following day, ask whether you can identify the source, find the important moment and explain the idea without rereading the whole transcript. Those are more useful tests than how much text you captured.