1. Preserve, cut, or speed up: making deliberate decisions
Screen recordings contain working stretches that look silent but carry essential meaning. Reading documentation, waiting for a dialog to update, or following a complex UI layout require time for the viewer to comprehend. Silence alone is never an instruction to cut. Categorize each segment deliberately before editing.
| Screen action | Visual / audible clue | Recommended decision | Review check |
|---|---|---|---|
| Reading instructions or docs | Cursor still, text visible, silence | PRESERVE at normal speed | Ensure viewer has enough time to read the text |
| Completing a multi-step form | Continuous intentional typing/clicks | PRESERVE at normal speed | Check that each input and result remains clear |
| Searching for a window or file | Erratic cursor wandering, opening wrong tabs | Consider a cut if the step adds no useful context | Verify the cut joins smoothly to the correct window |
| Idle spinner or blank delay | No action, waiting for cloud response | CUT or SPEED UP (if safe) | Confirm transition shows result without jarring jump |
| Long build, upload or render | Progress bar or terminal compilation | Consider a speed change or shorten the wait | Keep the start, result and any necessary explanation visible |
- Preserve: moments where the viewer must read, observe a state change, or follow complex UI logic.
- Cut: unnecessary searching or repeated attempts, once you have checked that the omitted action is not needed to follow the result.
- Speed up: predictable background tasks where seeing time pass builds trust, provided playback rate controls are supported on that clip.
2. Review quiet steps before requesting a cut
An audio-based silence pass can remove quiet actions the viewer needs to follow. A spinner, a reading interval and a completed form can all be silent while serving different purposes. Identify the interval visually, describe what should remain and review the proposed edit before export.
A quiet interval may contain an essential click, reading step or visible result. Listen and watch before shortening it; then review the join and the narration that follows.
3. A written example: preserve, cut or speed up
This fictional 30-second walkthrough illustrates the decisions. It is not a report of an edited or exported Cubix sample. Use the same review questions on your own recording before choosing an operation.
| Source interval | What the viewer sees | Decision to consider | Check in the edited video |
|---|---|---|---|
| 00:03–00:08 | A settings label and a checkbox being selected | Preserve enough time to read the label and see the selection | Can the viewer identify the setting and its new state? |
| 00:12–00:18 | An idle spinner with no narration or useful change | Shorten the wait after checking the join | Does the viewer still see the task start and the resulting dialog? |
| 00:22–00:28 | A progress bar followed by a completed result | Consider a speed change only if the available controls support the intended interval | Does the entire result remain visible, with narration and captions still aligned? |
- Mark your own source intervals before making a request.
- Do not use an interval speed change unless the current control lets you target it; a whole-clip speed change also affects useful steps.
- Record the resulting output timecodes and inspect the downloaded file, rather than assuming source times survive a cut.
4. Zoom for legibility without losing context
Small interface text can become hard to read when a desktop recording is viewed on a phone. Consider a closer framing of the active panel when the current controls support it. Keep enough context to show where the action happens, and inspect the result at the intended viewing size.
- Hold the zoom through the entire multi-step interaction rather than rapidly pulsing in and out.
- If you apply a zoom, frame the relevant panel deliberately and check it through the entire action.
- Pull back to the full overview when screen layout, window arrangement, or broad context matters.
- Tradeoff: Aggressive punch-ins magnify text but discard surrounding layout context; strike a balance between detail and orientation.
5. Webcam, audio and captions
When recording both a camera feed and a screen capture, position the webcam inset in an inactive screen corner that never obscures critical menus, toolbar buttons, or captions. Balance voiceover volume against software notification chimes, and add captions so steps can be followed with audio muted.
- Dock webcam insets away from primary navigation tabs, lower-third caption safe zones, and active toolbars.
- Keep voiceover and cursor actions synchronized across every cut boundary.
- Generate captions to make technical terminology and code commands readable without sound.
- Review any requested zoom or audio adjustment over the full interval; check that it preserves the interface action and the spoken explanation.
6. Keep sensitive information out of the recording
Prevent capture of private information by using dummy accounts and synthetic data, hiding notifications, and closing unrelated tabs before recording. A private browsing window does not hide information already visible on screen. If sensitive information was recorded, prefer removing the entire affected interval or recording that step again.
- Prefer prevention or excision: Cut the clip containing the sensitive data or re-record with synthetic placeholder information.
- If applying a blur or mask: Inspect every single frame across transitions, zooms, and cuts.
- Inspect the downloaded video: step through relevant frames, including transitions and moving interface elements, to check for exposed information.
- Never assume that an in-editor preview blur guarantees complete redaction in the downloaded render without verification.
7. Review the downloaded export
Download the rendered video and review it outside the editor before publishing or sharing it:
- Step completeness: Does the viewer see every click and confirmation needed to replicate the workflow?
- Legibility check: Is text and code readable when tested at a 390px mobile width?
- Narration sync: Does spoken voiceover align with the on-screen action across all cuts?
- Caption clearance: Are captions clear of buttons, lower timeline elements, and webcam insets?
- Privacy verification: Confirm no credentials, personal emails, or private tabs leaked during transitions.
✖ Treating every silent interval as unnecessary
Why it fails: Quiet reading, clicks and state changes may be necessary to understand the demonstration.
✔ Better approach: Watch the action, identify the interval and review a bounded edit instead of cutting every quiet stretch.
✖ Zooming so far that the viewer loses context
Why it fails: A larger label is unhelpful if its panel, surrounding controls or visible result disappear.
✔ Better approach: Balance legibility and orientation, then check the intended viewing size.
✖ Relying on preview blur without verifying the downloaded export
Why it fails: Preview canvas rendering may differ from rendered video frames, potentially leaking sensitive credentials or personal data.
✔ Better approach: Inspect the exported MP4 frame-by-frame across all transitions in an external media player.
Editing workflows in Cubix
Frequently Asked Questions
Common questions around this editing workflow.