How to Make a Feature Walkthrough Video from a Screen Recording

The most common video made with Nook is not a launch video. It is a one to three minute walkthrough of one feature in a business app: approving a purchase order, logging time against a project, exporting the monthly report, filing a leave request, reconciling a transaction, correcting an attendance record. The person making it builds or runs the software, recorded the feature in their own account, and wants two things from it: a narrated video with chapters to put in the help center or send to a customer, and a written step guide for the people who won't press play. A good share of them are made in Spanish and Portuguese. This guide is how to make one well.

#Why a walkthrough beats a long document for one feature

A 20-page manual covers everything, which is why nobody reads it when they are stuck on one screen. A feature walkthrough covers one job, from the screen you start on to the result, in the time it takes to make a coffee. The viewer sees the exact buttons in the exact order, hears why each step matters, and can jump to the chapter they need. The written guide next to it serves the people who prefer to read, who want to copy a field name, or who are on a slow connection.

It also beats a live demo. You record the feature once and send the link a hundred times. When a customer asks "how do I export the orders report," the answer is a link, not a 30-minute call. Our software training video guide covers longer courses. This one is about the single feature.

#What to record

One feature. Not the module, not the product. "Approve a timesheet," not "the HR module." If the feature has two paths, record the common one, and record the other path as its own video.

Start logged in, on the right page. Open the screen where the job begins before you press record. The first second of the video should show where the viewer needs to be. Skip the login unless the login is the point.

A test account with realistic data. Real-looking customers, orders, employees and amounts, with nothing in them that is actually private. "Acme Ltd, invoice 1042, $3,250" is better than "Test test 1". Nook blurs emails, phone numbers, card numbers and API keys it finds on screen, but a tidy test account means less to check.

Say what you're doing, or stay silent. If you talk, say why you click, in whatever language you think in. The words become the script. If you don't talk, a vision model reads the screen and works out the steps from what it sees. Both work. Don't read a script while clicking. It sounds read.

One to three minutes. If the feature takes longer than three minutes to show, it is two features. Split it.

1080p, slow clicks. Record the browser window at full size, 1080p or better. Move the mouse to the control, pause for half a second, then click. Those pauses are where the zooms and chapter breaks land. For more, see screen recording tips.

Any recorder works: QuickTime, OBS, the Windows Snipping Tool, Zoom, a Loom download. Nook takes the MP4, MOV or WebM.

#The five things that make it good

1. One outcome per video. The title says what the viewer will have done at the end: "Export the monthly sales report as CSV." If you can't write that sentence, the recording covers too much.
2. The first second shows where you are. The viewer should recognize the screen and the menu immediately. If they are on a different page, they know within a second and go there.
3. Narrate the why, not the click. "Click Filters" tells them nothing they can't see. "Filter to last month so the report matches the invoice run" tells them why the step exists and when to do it differently.
4. Zoom on the control. A full dashboard at 1080p shrinks a dropdown to a few pixels on a phone. The video should push in on the control being used and pull back out between steps.
5. A written guide next to it. Some people won't watch, some can't play sound at their desk, some want to copy the exact field name. Give them the same steps as numbered text with a screenshot each, in the same article.

#How Nook makes it from that recording

Upload the recording and pick Walkthrough. Nook splits it into steps at your clicks and pauses, then writes one short line for each step. If you talked, the line comes from what you said, cleaned up. If you were silent, it comes from what is on screen. Read the lines and change any that are off. That is the one editing job.

From there:

• Voice in 15 languages. A natural voice reads each line. Record in Spanish or Portuguese and the narration is Spanish or Portuguese, with a native voice. On Pro you can translate the same video into other languages, each as its own MP4 and guide. See translated demo videos.
• Zoom on clicks. Nook finds the clicks and zooms on the control, then pulls back out.
• Captions on every line. The video works with the sound off.
• Blur of private data. Emails, phone numbers, card numbers and keys are flagged and blurred. You check each flag.
• Chapters. Each step is a chapter on the share page, so a viewer can jump to "step 4: choose the date range."
• The written guide. The same steps as a document, with a screenshot of each step, as PDF, Word or Markdown. Paste the Markdown into your help center, or attach the PDF to the onboarding email.
• A share link and an embed code. The share page plays without a login.

When the UI changes, re-record nothing. If the button is renamed, edit the line and re-render. Only when the screen itself changes do you record again, and then only that step's part of the flow, since you can upload a new recording and reuse the words.

Nook doesn't record. You bring the file. And it doesn't publish to your help center. You paste the embed or the link.

#What to do with it

• Help center article. Embed the video at the top, paste the written guide under it. One article, two ways to read it. See help center videos.
• In-app link. Put the share link behind a "How does this work?" link on the feature's own screen, or in the empty state before anyone has used it.
• Onboarding email. Day two: "Here's how to log your first timesheet," with the video link and the PDF. See customer onboarding videos.
• Reply to a support ticket. The link answers the question, and the chapter link answers it precisely.
• Slack or Teams for your own staff. New hire asks how to correct an attendance record. Send the link. See software tutorial videos for internal training.

If your customers or team work in Spanish or Portuguese, Nook has pages in Spanish and Portuguese.

#FAQ

#I recorded without talking. Will the narration make sense?

Yes. A vision model reads the screen, page titles, button labels and field names, and works out what happened at each step. Read the lines before you render. Silent recordings of a clear interface come out well. Silent recordings of a wall of unlabeled icons need more editing.

#My product and my customers aren't in English.

Record in your language and talk in it. Nook writes and voices the walkthrough in that language, with 15 languages available. On Pro you can add other languages to the same video, each with its own MP4 and guide.

#The feature takes ten minutes to show.

Split it. A ten-minute feature is three or four jobs, and each one deserves its own title, its own video and its own help article. Viewers find "Set up approval rules" faster than minute six of "The approvals module."

#The feature changed. Do I have to start again?

Only if the screens changed. For a renamed button or a changed label, edit the line and re-render. For a redesigned screen, record that part again. Your plan includes re-renders with each video.

#How long does it take?

Recording a one to three minute feature takes about as long as the feature. Nook needs a few minutes to make the video and the guide. Checking the lines takes five. Most people have the article live within half an hour of pressing record.

Record one feature, upload it, read the lines and share the link. Make your first video free.