Create an explainer video with AI from a clear brief
Create an explainer video with AI by starting with one audience and one takeaway. Bring your notes, review the proposed scenes, and check the first cut before you share it.
Or pick a video type to get started
Video generation uses credits. Review your estimate in ngram. MP4 downloads require Basic or higher.
How credits workTrusted by teams at
Create Explainer Video with AI videos made with ngram
Real videos created by teams using ngram for create explainer video with ai.
“I have the notes. What should the video actually say?”
- Notes
You have a document full of relevant material but no clear brief. Before making scenes, decide who is watching and which question this particular explanation should answer.
- Audience
The notes mix beginner context with specialist detail. Without choosing a starting knowledge level, the draft can confuse one viewer while repeating what another already knows.
- Example
The draft states the idea but never shows how it works. A worked example or actual task recording gives the explanation something concrete the viewer can follow.
- First cut
The narration fits, but a label is too dense to read during playback. Check the complete draft at its intended size instead of approving the script in isolation.
- Next version
The brief never stated what the viewer should do next. A polished ending cannot repair an unclear purpose; revise the takeaway before producing another version.
“A common first explainer planning scenario, not a customer testimonial.”
Give your first explainer a source and a review step
Paste the entire document into a generic request to make a video. The draft gives minor background and the main idea the same weight.
Write one takeaway and identify the passage that supports it. Ask ngram to propose a script and scenes for that audience before rendering.
Choose visuals before deciding how to explain the idea. A sequence of attractive images leaves the viewer to infer the mechanism.
Use a definition, a worked example, and a recap where the topic needs them. Specify what each scene should explain and review it against the source.
Share the first cut after reading only its script. Unclear pronunciation, dense labels, or an incorrect caption remain in the finished video.
Watch and listen to the exported draft. Correct one issue, inspect the new version, and repeat until the intended viewer can follow the explanation.
Start your first explainer with usable material
Choose the source that contains the facts for your first explainer brief. Upload only material you have permission to use.
Use a document or public page
Upload a PDF or Markdown document, provide a supported deck, or paste a public URL. Identify the exact section to explain and supply any facts that require login separately as approved material.
Docs to videoUse actual footage or screenshots
Bring the recording or screenshot that shows the real task. State what viewers should notice and which names or numbers must stay exact. Review any generated visuals as illustrations, not evidence that an action occurred.
Screen recording to videoAn editable first explainer draft
Review the explanation in the editor, check the finished playback, then download the MP4. Source complexity and revision scope affect how much work and usage the video needs.
A slide deck can also be a source. Supported PPTX/PDF input does not mean the finished video exports as an editable presentation.
Keep your first explainer open to revision
The next change has a clear starting point
Keep the source and the intended takeaway together for your first explainer brief. When the source changes, request a bounded update and compare it with the previous version.
Judge the explanation, not only the finish
Check whether the viewer can follow the mechanism or decision. Read the captions and listen to the narration; visual polish does not establish source accuracy.
Use a review your subject requires
Ask the appropriate owner to review procedures, pricing, and technical details. ngram drafts and edits the video; the source owner remains responsible for what it says.
Build your first explainer from source to review
Define the audience and supply the source
For your first explainer brief, choose one takeaway and one example. Use the composer above to keep the brief with the creation flow, and upload supported source material.
Check the proposed explanation
Ask for a script and scene plan before rendering. Verify names, numbers, relationships, and exceptions against the source; replace vague visual directions with specific instructions.
Test one edit, then export
Change a sentence or a scene and compare the revised playback with the prior version. Check captions and audio, then download the finished MP4. Generation and editing use plan allowances.
Controls for your first explainer at each review step
Who owns the next first explainer update?
Product Marketing
Explain the value behind a release using approved claims and current screenshots. Keep a separate demonstration for the exact clicks, and revise the explainer when positioning or product behavior changes. Add it only when the first brief needs this step.
Founders
Turn the company or product story into a short explanation a new audience can follow. Start from the approved pitch, then check that the video has not turned an ambition into a claim. Add it only when the first brief needs this step.
Product Managers
Explain a decision or capability to stakeholders using the current specification. Distinguish shipped behavior from plans in the script, and keep a record of the source version used for the explanation. Add it only when the first brief needs this step.
Growth & Marketing
Adapt the explanation for a specific audience and destination. Review each version as its own output, with a clear hook and a supported next step; measure results instead of assuming a conversion lift. Add it only when the first brief needs this step.
Sales Enablement
Explain a buyer question with the approved talk track and evidence. Keep buyer-facing explanation separate from rep training, and verify that the finished video adds no new promise about outcomes or price. Add it only when the first brief needs this step.
Customer Success
Explain a recurring customer question using the current help material and real screens. When the product changes, replace the affected explanation and check that the viewer can still follow the next step. Add it only when the first brief needs this step.
Developer Relations
Use technical documentation and diagrams to explain a mechanism before the code walkthrough. Check terminology and relationships with the subject-matter owner, especially after the API or its behavior changes. Add it only when the first brief needs this step.
Educators
Educators can use first explainer projects to explain approved material to a specific audience. Keep the source current, name the takeaway in the brief, and review the changed scene when the underlying facts change. Add it only when the first brief needs this step.
HR & Internal Comms
HR & Internal Comms can use first explainer projects to explain approved material to a specific audience. Keep the source current, name the takeaway in the brief, and review the changed scene when the underlying facts change. Add it only when the first brief needs this step.
Choose the explanation your audience needs
Each job starts from different material and has a different review. Use an existing workflow rather than a blank brief.
Bring the source for your first explainer
Choose the supported source workflow that matches your material. Check the input requirements on its page before starting.
Tools to support your first explainer
Choose how to produce your first explainer based on the work
| Manual production | Commissioned production | ngram | |
|---|---|---|---|
| Starting material | Assemble sources and write the script | Agree the brief and supply source assets | Provide supported sources and a brief |
| Story control | Write and arrange each scene | Review the agreed script and creative direction | Review generated script and storyboard |
| Making a change | Edit the project and render again | Agree revision scope with the producer | Use chat, script, or scene controls; review output |
| Factual review | Source owner checks final video | Source owner checks the delivered cut | Source owner checks generated and edited video |
| Cost to evaluate | Depends on tools and production effort | Depends on agreed scope and revisions | Plan allowances cover generation and editing; exports do not use credits |
Wire explainers into the publishing stack you already run.
These are workflow options you configure. Check connector access, review the generated output, and verify the destination before relying on an automation.
whenThe approved source for your first explainer brief is ready
thenConfigure the trigger and video-creation action with the approved brief, then check the completion result before publishing.
whenThe approved source for your first explainer brief is ready
thenUse a supported authenticated client to request the explainer. Creation access depends on the client and workspace; inspect the result in ngram.
whenThe approved source for your first explainer brief is ready
thenStart from the public source page with the ngram extension, then review the proposed explanation before using the output.
whenThe approved source for your first explainer brief is ready
thenConfigure n8n to call ngram and check render completion. A self-hosted n8n workflow still uses the hosted ngram service.
whenThe first explainer has passed its source and playback review
thenConnect LinkedIn through Social Publishing Beta, compose the post, and verify the scheduled or published destination.
whenThe first explainer has passed its source and playback review
thenConnect X (Twitter) through Social Publishing Beta, compose the post, and verify the scheduled or published destination.
whenThe first explainer has passed its source and playback review
thenConnect YouTube through Social Publishing Beta, compose the post, and verify the scheduled or published destination.
Will it work for my situation?
How do I create an explainer video with AI from notes?
What does a useful explainer brief look like?
What does it cost to try and keep making explainers?
What should I fix in the first draft?
When should I use a different production approach?
Bring one source for your first explainer and one change to test
Start with the composer above. For a team evaluation, bring an approved source and a specific revision you want to assess; choose Talk to sales to discuss the workflow.


