What should you screenshot when taking notes from YouTube?

Screenshot the moment when converting what you see into plain text would damage the information. That single rule prevents both extremes: missing important visual context and collecting hundreds of useless frames.

Screenshot when spatial structure carries meaning

Architecture diagrams, flow charts, annotated slides, maps, geometry, mind maps, and system diagrams encode relationships through position and shape. Rewriting every box and arrow is usually slower and less faithful than keeping the visual.

Screenshot when exact formatting matters

Code, terminal commands, equations, configuration files, spreadsheet formulas, and structured tables are easy to corrupt when captured through speech transcription. Keep the frame, then add one sentence explaining why it matters.

Screenshot state changes

UI tutorials often depend on what a screen looks like before and after an action: a selected setting, an error state, a layer panel, a browser network request, or a chart after a filter is applied. Those states are difficult to reconstruct from narration alone.

Screenshot evidence, not decoration

A chart that supports an argument is evidence. A title card, stock photo, presenter reaction, or decorative background usually is not. Ask whether the image would help future you understand, verify, reproduce, or compare something.

Good screenshots to keep

• architecture and process diagrams;
• equations and multi-step derivations;
• code, terminal output, and configuration;
• charts whose shape or axes matter;
• comparison tables;
• annotated slides;
• UI settings and before/after states;
• whiteboards where layout reflects the explanation.

Screenshots you can usually skip

• talking heads;
• intro and title slides;
• paragraphs already captured well by the transcript;
• repeated views of the same state;
• every slide “just in case”;
• images you cannot explain without rewatching the video.

Add a caption or concept beside every screenshot

A screenshot without context decays quickly. Future you needs to know what to notice. Write a short note such as “Back-pressure sits between consumer and producer” or “This flag disables certificate verification — do not use in production.”

ScribeShot automates the filing part: the screenshot is kept under the timestamped note section it belongs to. You still provide the judgment about which moment is worth capturing.

For the broader workflow, see how to take notes from YouTube effectively and why transcripts miss visual information.

Common questions

Should I screenshot every slide in a lecture?

Usually no. Capture a slide when its layout, diagram, notation, table, or visual relationship adds information that your short written note would lose.

Is it better to screenshot code or copy it?

If you need runnable code, prefer the original repository or text source when available. A screenshot is useful for preserving the exact on-screen state, surrounding context, or code that is not provided elsewhere.

How many screenshots should I take?

There is no ideal number. A useful constraint is to capture only images you can explain why you kept. If you cannot name the future use, skip the screenshot.