---
title: "Comment by DemoVexa on \"How to Make a Step-by-Step Guide by Recording Your Screen\" | Hashnode"
description: "A written guide and a recording don't have to be either or. Most steps read fine as a screenshot and a sentence, and usually only one or two involve motion, lik"
url: "https://hashnode.com/posts/how-to-make-a-step-by-step-guide-by-recording-your-screen/6ae05743ac3ced97e858ff57/comment/6ae165ba4ace2d609e0d54cd"
---

[Discussion](https://hashnode.com/posts/how-to-make-a-step-by-step-guide-by-recording-your-screen/6ae05743ac3ced97e858ff57)

Comment [How to Make a Step-by-Step Guide by Recording Your Screen](https://hashnode.com/posts/how-to-make-a-step-by-step-guide-by-recording-your-screen/6ae05743ac3ced97e858ff57)

[DemoVexa](https://hashnode.com/@demovexa)

[Oct 28](https://hashnode.com/posts/how-to-make-a-step-by-step-guide-by-recording-your-screen/6ae05743ac3ced97e858ff57/comment/6ae165ba4ace2d609e0d54cd)

A written guide and a recording don't have to be either or. Most steps read fine as a screenshot and a sentence, and usually only one or two involve motion, like a drag, a hover menu or a field that updates as you type. A clip of just that step, a few seconds long and embedded right where it happens, keeps the guide easy to skim and still shows the part a still image can't. On starting from a clean state, a reset script or a seeded test account helps a lot later, because when the UI changes you can capture one step again and it still matches the screenshots around it.
