B-roll

Master this essential documentation concept

Quick Definition

Supplementary video footage used to support or illustrate the main content, often inserted between primary clips to add context or visual interest.

How B-roll Works

flowchart TD A[Documentation Video Project] --> B[A-Roll: Primary Footage] A --> C[B-Roll: Supplementary Footage] B --> D[Screen Recordings] B --> E[Presenter/Narrator Clips] C --> F[Product Close-ups] C --> G[UI Walkthroughs] C --> H[Animated Diagrams] C --> I[Environment/Context Shots] D --> J[Video Editing Timeline] E --> J F --> J G --> J H --> J I --> J J --> K{B-Roll Insertion Points} K --> L[Cover Jump Cuts] K --> M[Illustrate Concepts] K --> N[Transition Between Steps] K --> O[Reinforce Key Points] L --> P[Final Documentation Video] M --> P N --> P O --> P P --> Q[Published to Knowledge Base]

Understanding B-roll

B-roll is a filmmaking and video production term that has become essential in modern documentation workflows. Originally used in broadcast journalism to cut away from interview subjects, B-roll now serves as a critical tool for documentation professionals creating tutorial videos, product walkthroughs, onboarding content, and knowledge base materials. It transforms static, talking-head recordings into dynamic, visually engaging experiences that improve comprehension and retention.

Key Features

  • Supplementary nature: B-roll complements rather than replaces primary footage, filling gaps and reinforcing spoken or demonstrated content
  • Visual variety: Introduces different camera angles, screen captures, animations, or real-world demonstrations to break visual monotony
  • Contextual layering: Adds depth by showing the 'what' while A-roll explains the 'why' or 'how'
  • Flexible insertion: Can be dropped in at any point in the timeline without disrupting the primary audio narrative
  • Reusability: Well-captured B-roll clips can be repurposed across multiple documentation videos

Benefits for Documentation Teams

  • Improved clarity: Visual demonstrations alongside verbal explanations reduce ambiguity in complex technical processes
  • Higher engagement: Varied visuals keep viewers watching longer, reducing drop-off rates in tutorial content
  • Error concealment: Allows editors to cover mistakes, jump cuts, or awkward pauses in primary footage seamlessly
  • Professional polish: Elevates production quality without requiring expensive reshoots of primary content
  • Accessibility support: Provides visual context that aids comprehension for non-native language speakers or users with auditory processing differences

Common Misconceptions

  • B-roll is optional filler: In reality, strategic B-roll is essential for comprehension, not just aesthetics
  • Any footage works as B-roll: Irrelevant or low-quality B-roll actively harms credibility and viewer trust
  • B-roll requires expensive equipment: Screen recordings, animated diagrams, and smartphone footage can serve effectively as documentation B-roll
  • B-roll is only for long-form videos: Even short 60-second tutorials benefit from a few well-placed supplementary clips

Real-World Documentation Use Cases

Software Onboarding Tutorial Series

Problem

New users watching onboarding videos lose focus when the presenter spends extended time explaining a concept verbally without visual reinforcement, leading to high drop-off rates and repeated support tickets about the same features.

Solution

Insert B-roll screen recordings of the actual UI interactions, animated callouts highlighting specific buttons, and split-screen comparisons showing before-and-after states whenever the narrator explains a feature or workflow step.

Implementation

1. Record the primary A-roll narration or talking-head segment first. 2. Identify every point where a UI element, menu, or workflow is mentioned verbally. 3. Capture dedicated screen recordings of each mentioned interaction at high resolution. 4. Add animated zoom-ins or highlight overlays to draw attention to specific UI elements. 5. Insert B-roll clips in the editing timeline to align with corresponding verbal explanations. 6. Ensure B-roll duration matches the length of the verbal description.

Expected Outcome

Viewer retention increases by providing continuous visual engagement, support ticket volume decreases as users can visually confirm what actions to take, and the tutorial feels more professional and trustworthy.

API Documentation Video Companion

Problem

Developer documentation videos explaining API endpoints and code logic become visually monotonous when showing only a static code editor, causing developers to disengage before reaching critical implementation details.

Solution

Use B-roll footage of terminal outputs, successful API response examples, data flow diagrams, and side-by-side code comparisons to visually break up the primary code walkthrough and reinforce what each code block accomplishes.

Implementation

1. Complete the primary screen recording of the code editor walkthrough. 2. Identify abstract concepts like data flow, authentication handshakes, or error handling. 3. Create animated diagrams or flowcharts illustrating these concepts. 4. Capture terminal or console footage showing live API calls and responses. 5. Record close-up footage of specific code snippets with syntax highlighting. 6. Layer these B-roll elements over the primary footage during editing, synchronized with the narrator's explanations.

Expected Outcome

Developers gain both conceptual understanding and practical visual confirmation, reducing implementation errors and decreasing time spent cross-referencing written documentation alongside the video.

Hardware Setup and Installation Guide

Problem

Documentation videos for physical product setup rely heavily on a single camera angle, making it difficult for users to see small connectors, indicator lights, or precise hand movements required for correct installation.

Solution

Supplement the primary wide-angle setup footage with close-up B-roll shots of each connection point, indicator light states, and hand positioning, captured from multiple angles to eliminate visual ambiguity.

Implementation

1. Film the complete setup process from a standard overview angle as the primary A-roll. 2. Reshoot specific steps with a macro or close-up lens focused on connectors, ports, and small components. 3. Capture footage of correct vs. incorrect connection states for comparison. 4. Record indicator lights in both active and inactive states. 5. Edit B-roll close-ups to appear immediately when the narrator mentions each specific component. 6. Use picture-in-picture or cutaway techniques to maintain spatial context.

Expected Outcome

Users successfully complete hardware setup on the first attempt more frequently, product return rates due to installation errors decrease, and support call volume for setup assistance drops significantly.

Process Documentation for Internal Teams

Problem

Internal process documentation videos for HR, compliance, or operational workflows feel impersonal and disengaging when they consist solely of a screen share or slide deck, reducing completion rates among employees.

Solution

Enrich primary slide or screen-share footage with B-roll showing real employees performing the described tasks, relevant workplace environment shots, and animated process flow visualizations that make abstract procedures feel tangible.

Implementation

1. Record the primary instructional content using slides or screen capture. 2. Identify procedural steps that have real-world physical or interpersonal components. 3. Film short clips of team members performing those actual tasks in the workplace. 4. Create simple motion graphics illustrating decision trees or approval workflows. 5. Obtain necessary permissions for footage featuring employees. 6. Insert workplace and process B-roll at natural transition points between major sections. 7. Keep individual B-roll clips between 3-8 seconds to maintain pacing.

Expected Outcome

Employee training completion rates improve, procedural comprehension scores increase on post-training assessments, and the documentation feels culturally authentic and relevant to the actual work environment.

Best Practices

✓ Plan B-Roll During the Script Stage

Identifying B-roll needs before filming begins ensures you capture all necessary supplementary footage efficiently and prevents costly reshoots. Review your documentation script and annotate every point where a visual demonstration, close-up, or contextual shot would enhance comprehension. Create a dedicated B-roll shot list alongside your primary filming plan.

✓ Do: Create a two-column script format with A-roll narration on one side and corresponding B-roll requirements on the other. Schedule B-roll capture sessions immediately after primary recording while the setup is still available.
✗ Don't: Do not wait until the editing stage to realize you need B-roll footage. Avoid improvising B-roll capture without a shot list, as this leads to inconsistent quality and missing critical visual moments.

✓ Maintain Visual and Contextual Relevance

Every B-roll clip must directly relate to the content being discussed at that moment in the video. Irrelevant or loosely connected footage confuses viewers and undermines the credibility of your documentation. Documentation B-roll should always serve comprehension first and aesthetics second.

✓ Do: Match B-roll content precisely to the verbal or on-screen content it accompanies. Use UI screenshots that exactly match the software version being documented. Show real workflows your audience will actually encounter.
✗ Don't: Do not use generic stock footage of people typing or abstract technology visuals as a substitute for relevant documentation-specific B-roll. Avoid showing outdated UI versions or deprecated workflows that no longer reflect the current product.

✓ Capture B-Roll at Higher Resolution Than Required

Recording supplementary footage at a higher resolution than your final output gives you flexibility to zoom, pan, and reframe during editing without quality loss. This is especially critical for screen recordings and close-up UI footage where fine details like small text, icons, and cursor movements must remain sharp and legible.

✓ Do: Record screen captures at 4K or at least 1080p even if your final deliverable is 720p. Use lossless or high-bitrate codecs for B-roll captures. Ensure UI text is readable at the smallest size it will appear in the final video.
✗ Don't: Do not capture B-roll at the same resolution as your final output, as this eliminates all editing flexibility. Avoid using compressed screenshots or low-resolution screen grabs as B-roll in professional documentation videos.

✓ Keep Individual B-Roll Clips Concise and Purposeful

Documentation viewers are task-oriented and have limited patience for extended visual digressions. Each B-roll segment should be long enough to convey its intended information but short enough to maintain pacing. Overly long B-roll sequences can make documentation feel padded and cause viewers to lose the thread of the primary instruction.

✓ Do: Aim for B-roll clips between 3 and 10 seconds in length for most documentation contexts. Use the natural length of the corresponding verbal explanation as your guide for B-roll duration. Cut B-roll on action to maintain visual momentum.
✗ Don't: Do not let a single B-roll clip run longer than the verbal content it supports unless it contains essential visual information that requires extended viewing. Avoid using B-roll as a lazy solution to pad video length to meet a minimum duration requirement.

✓ Build a Reusable B-Roll Asset Library

Documentation teams frequently cover similar topics, features, and workflows across multiple videos. Establishing a centralized, tagged library of approved B-roll footage allows team members to quickly locate and reuse relevant clips, dramatically reducing production time for new documentation videos and ensuring visual consistency across your content catalog.

✓ Do: Tag and organize B-roll assets by product area, feature name, action type, and date captured. Establish a naming convention that makes assets searchable. Review and update the library when products are updated to remove outdated footage.
✗ Don't: Do not allow B-roll assets to remain siloed on individual team members' local drives. Avoid reusing B-roll footage that shows outdated UI, deprecated features, or old branding, as this creates confusion and erodes viewer trust in the accuracy of your documentation.

How Docsie Helps with B-roll

Build Better Documentation with Docsie

Join thousands of teams creating outstanding documentation

Book a Demo