Skip to content
Floskool

Chapter 1 · The resource

Prep your screen before recording

Free lesson 7 minGroup Flokup

Follow this course in your space: your progress is saved, and the community answers your questions.

Follow for free

A failed demo often fails before the first click. A notification popping up mid-take, fifteen open tabs, a bookmarks bar full of personal stuff, text too small to read on a phone. All of that takes ten minutes to fix, before you record.

Screen recording guides (from capture tool makers and university e-learning teams) keep giving the same advice: a clean screen, a slow pace, and as little mouse movement as possible. Here's the version you can tick off.

1. Do not disturb

  • "Do Not Disturb" (or "Focus") mode on, on both your phone and computer
  • Messaging apps closed (email, chat, social): a pop-up is a private message going out on social media
  • Reminders and alarms off during the recording
  • On a phone: airplane mode if your demo doesn't need the internet, otherwise Wi-Fi only

Why: a notification ruins the take, and it can show a name or a message you never meant to publish.

2. Tabs and bookmarks hidden

  • One browser window, one tab: the demo tab
  • Bookmarks bar hidden
  • Extensions that show icons or pop-ups turned off while you record
  • Ideally, a separate, empty browser profile used only for demos
  • Desktop tidied, taskbar or dock hidden if they're visible

Why: nobody needs to see your bookmarks. They pull the eye away from what matters, and sometimes they say too much about you.

3. Browser zoom at 125 to 150%

Your demo will be watched on a small phone screen. A website shown at 100% on a large computer screen becomes unreadable once it's shrunk into a vertical video.

  • Browser zoom raised to 125%, or even 150% (Ctrl and + on Windows, Cmd and + on Mac)
  • Window not too wide: you can shrink it so the page takes a shape closer to what people will see
  • Check the layout doesn't break at that zoom (menus, buttons)

On a phone, there's no zoom to set: the website already shows up large. Just check the text size in your display settings if you changed it.

4. Real data

An empty cart, a "test test" account or a page full of placeholder text gets noticed right away and breaks trust.

  • Real or realistic content: real products, real time slots, real dishes
  • No personal data from a real customer on screen (name, email, phone, address)
  • A demo account if your demo goes through a logged-in area
  • A form prefilled with believable but made-up details ("Julie, 555-0100")

5. Slow mouse, steady gestures

  • Move the mouse slower than usual, in a straight line to the button
  • Once on the button: short pause, click, then let go of the mouse
  • No circling around an element to "point it out": people follow the mouse, not your text
  • On a phone, clean gestures: one tap, one scroll, no back and forth

Why: when the mouse wanders, the eye follows the mouse. And steady gestures make editing easier: every cut lands on a calm moment.

6. Pause on the result

  • After the last click, wait without moving until the final screen is fully displayed
  • Count "one, two" in your head before stopping
  • The whole result is on screen (not cut off at the bottom)

This is the most forgotten rule. You know what's going to appear, so you want to stop right away. Your viewer is seeing it for the first time.

7. A dry run

  • Go through the whole path once without recording
  • Pages already loaded once (less waiting during the take)
  • You know exactly where to click, and in what order

Example: Lea, ceramicist

Lea wants to show a bowl being added to the cart. She turns on "Do Not Disturb," closes her messaging app, opens an empty browser profile and sets the zoom to 125%. She empties her test cart and restocks the blue bowl. She rehearses twice, then records three takes. On the third, she stays on the cart for two seconds before stopping. That's the one she keeps.

Your turn

Copy the seven sections into your notes under the heading "Before recording." Prep your screen following the list, then do a dry run of your script from lesson 1. Write down what slowed you down: that's what to fix before the real take.