> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.

# Analyze a video ad scene by scene

> Break down one video ad into its structure, scene evidence, persuasion choices, and reusable creative lessons.

## What this article shows you

Use StefanBrain to analyze one video ad from its opening hook through its call
to action. The result connects a structured creative breakdown to timestamps,
scene details, and frames you can inspect.

Choose the ad using your account results, then use the report to study its
structure, scenes, and source frames.

## Practical use cases

<CardGroup cols={2}>
  <Card title="Diagnose a slow opening" icon="timer-reset">
    See when the promise, problem, product, and first proof point appear so you
    can identify what the viewer must wait to understand.
  </Card>

  <Card title="Study a competitor's structure" icon="scan-search">
    Separate visible and spoken evidence from interpretation, then reuse the
    strategic pattern without copying the ad's language or claims.
  </Card>

  <Card title="Build a shot list or script brief" icon="list-video">
    Turn scene roles, visual changes, dialogue, and on-screen text into a clear
    brief for a new concept.
  </Card>

  <Card title="Find claim and proof gaps" icon="shield-check">
    Compare what the ad says with the proof it shows before adapting an idea
    for another product or audience.
  </Card>
</CardGroup>

## Watch the walkthrough

<Frame caption="Watch StefanBrain turn one video into a scene-by-scene creative breakdown with visual evidence. Duration: 4:59.">
  <video className="w-full h-auto rounded-xl" controls preload="metadata" poster="/images/tutorials/covers/analyze-a-video-ad.png" playsInline alt="A walkthrough of analyzing a video ad scene by scene" aria-label="Narrated Video Analyzer walkthrough">
    <source src="https://stefanbrain.com/api/tutorials/videos/video-analyzer" type="video/mp4" />

    <a href="https://stefanbrain.com/api/tutorials/videos/video-analyzer">
      Watch the Video Analyzer walkthrough
    </a>
  </video>
</Frame>

## How the analysis works

Give StefanBrain exactly one source: either one uploaded video or one public
video URL. It processes the source as a run, then returns a complete report and
a scene-by-scene breakdown.

Depending on the source, each scene can include its timestamp, role, tone,
visual action, dialogue, on-screen text, an explanation of why the moment may
work, and a frame from that point in the video.

<Tip>
  You normally do not need to select **Video Analyzer** yourself. Describe the
  analysis you want and let StefanBrain choose the right capability. Select it
  from **Tools** only when you need this exact scene-by-scene workflow.
</Tip>

## What you will do

1. Add one video to a Chat.
2. Ask for an evidence-first scene analysis.
3. Let the analysis finish.
4. Inspect the report, timestamps, and frames.
5. Turn verified patterns into a fresh creative brief.

## Before you start

Prepare:

* One video file or one public video URL.
* The question you want the analysis to answer.
* The product, audience, or campaign context needed for a useful comparison.

If a public page prevents StefanBrain from reading its media, upload the video
file instead.

## Follow along

<Steps>
  <Step title="Open Chat from the home page">
    Open **Chat** and start a new conversation. If the analysis should use
    saved business context, mention the relevant Product or Project in the
    request.
  </Step>

  <Step title="Add exactly one video source">
    Attach one video file or paste one public video URL into the message.

    Do not add several videos or combine an attachment with a URL in the same
    analysis request. If StefanBrain finds more than one possible source, it
    will ask you to choose one.
  </Step>

  <Step title="Ask for an evidence-first breakdown">
    State what to observe, what to interpret, and what useful result should
    come next.

    ```text theme={"system"}
    Analyze this video ad scene by scene.

    Identify the opening hook, visual changes, spoken claims,
    on-screen text, proof, objections, offer, and call to action.
    Separate what is visible or heard from your interpretation.

    Finish with three transferable principles for
    [product, audience, or campaign].
    ```

    If you need the rigid workflow, open **Tools** and select **Video
    Analyzer** before sending the same request.
  </Step>

  <Step title="Let the analysis finish">
    Follow the activity shown in the Chat. The final report appears after the
    run completes; a long video can take longer than a short clip.

    If the source cannot be acquired from its URL, attach the video file and
    run the request again.
  </Step>

  <Step title="Inspect the report against the source">
    Read the overall structure first. Then review the scene rows and compare
    the timestamps, dialogue, on-screen text, and frames with the original
    video.

    Treat **Why it works** as an interpretation to evaluate, not as measured
    performance evidence.
  </Step>

  <Step title="Create the next brief">
    Name the patterns worth keeping and the boundaries the new work must
    respect.

    ```text theme={"system"}
    Turn the strongest three patterns from this analysis
    into a fresh script brief for @Your Product.

    Keep the strategic pattern, not the source wording or claims.
    Separate verified facts from creative hypotheses,
    and flag anything that needs supporting evidence.
    ```
  </Step>
</Steps>

## Make the result useful

Review the output in three layers:

| Layer | What to verify | Useful next decision |
| - | - | - |
| **Observation** | What is visibly shown, spoken, or written at a timestamp | Correct any missed or misread evidence |
| **Interpretation** | The proposed job of the scene, persuasion choice, and transition | Decide which explanation is credible |
| **Application** | The principles, hooks, or brief derived from the source | Adapt the pattern without copying claims or wording |

For a performance diagnosis, compare this creative analysis with the ad's
actual account metrics. A strong scene explanation and a strong business result
are different kinds of evidence.

## Common mistakes and troubleshooting

<AccordionGroup>
  <Accordion title="StefanBrain asks me to choose a source">
    The message contains more than one attachment, more than one video URL, or
    both an attachment and a URL. Send a new request with exactly one source.
  </Accordion>

  <Accordion title="The public URL cannot be analyzed">
    The page may be private, expired, blocked, or not expose a readable video.
    Download the source and upload the video file instead.
  </Accordion>

  <Accordion title="The scene description does not match the video">
    Open the relevant timestamp or frame, state the exact mismatch, and ask
    StefanBrain to revise that scene using only the visible and spoken evidence.
  </Accordion>

  <Accordion title="The report sounds certain about performance">
    Ask StefanBrain to label observations, interpretations, and hypotheses
    separately. Use account results to evaluate performance claims.
  </Accordion>

  <Accordion title="The result is too broad">
    Name the decision you need to make, such as revising the first five seconds,
    finding the proof sequence, or building a shot list. Then request that
    specific deliverable from the existing analysis.
  </Accordion>
</AccordionGroup>

## Next steps

* [Run a CRO funnel review](/knowledge-base/creative-strategist-research/run-a-cro-funnel-review)
* [Find campaign angles with Angle Finder](/knowledge-base/creative-strategist-research/use-angle-finder)
* [Give Chat the right context](/knowledge-base/chat/give-chat-the-right-context)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.