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 work

Trusted by teams at

HubSpotDeelZapierITVVeevaDP WorldGenpactSafetyCulture
Made with ngram

Create Explainer Video with AI videos made with ngram

Real videos created by teams using ngram for create explainer video with ai.

View all videos

“I have the notes. What should the video actually say?”

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

The old way
Before ngram
The ngram way
After ngram

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.

1Written sources
Bring the current source
PDF · Markdown · public URL

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 video
2Visual sources
Bring the real demonstration
Recording · screenshots

Use 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 video
ngram

An 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.

script generationcaptionsmotion graphics

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

1

Define the audience and supply the source

Prepare

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.

2

Check the proposed explanation

Review

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.

3

Test one edit, then export

Verify

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

Explore all features
Built for teams

Who owns the next first explainer update?

All solutions

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.

All use cases
Starting from something else?

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.

The rest of the toolkit

Tools to support your first explainer

All ngram tools

Choose how to produce your first explainer based on the work

Manual productionCommissioned productionngram
Starting materialAssemble sources and write the scriptAgree the brief and supply source assetsProvide supported sources and a brief
Story controlWrite and arrange each sceneReview the agreed script and creative directionReview generated script and storyboard
Making a changeEdit the project and render againAgree revision scope with the producerUse chat, script, or scene controls; review output
Factual reviewSource owner checks final videoSource owner checks the delivered cutSource owner checks generated and edited video
Cost to evaluateDepends on tools and production effortDepends on agreed scope and revisionsPlan allowances cover generation and editing; exports do not use credits
Integrations

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.

Zapier
no-code

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.

Integrate with Zapier
MCP Server
agentic

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.

Integrate with MCP Server
Chrome Extension
browser

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.

Integrate with Chrome Extension
n8n
workflow

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.

Integrate with n8n
LinkedIn
Beta publish

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.

Integrate with LinkedIn
X (Twitter)
Beta publish

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.

Integrate with X (Twitter)
YouTube
Beta publish

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.

Integrate with YouTube
REST APIMCP serverWebhooksBuild your own integration in ~30 lines.

Will it work for my situation?

How do I create an explainer video with AI from notes?

Write a brief that names who will watch, what they should understand, and what they should do next. To create an explainer video with AI in ngram, add the source and ask for a script and scene plan first. Correct the wording before rendering, then check the full video and its captions.

What does a useful explainer brief look like?

For example: explain our onboarding process to new customers using the approved guide; show the normal sequence and one exception; finish with the next action. Name the source version and the facts that must remain exact. This is a planning example, not a claim that a particular video was generated.

What does it cost to try and keep making explainers?

The Free plan includes 1,000 credits per month and public video sharing. The base rate for premium AI video generation is 10 credits per second, and a cheaper model costs 3 credits per second. Paid plans include video downloads: Basic starts at $29 per month, Premium is $59 and Ultimate is $299 on monthly billing. Model choice, video length and revisions affect usage; check the estimate before generating.

What should I fix in the first draft?

Check the main takeaway first. Remove background that distracts from it, define unfamiliar terms, and make the example specific enough to follow. Once the meaning is right, inspect timing, captions, pronunciation, and visual labels before exporting.

When should I use a different production approach?

Use specialist production when the job requires a bespoke animation style you cannot achieve in a reviewed sample. Keep real task footage for demonstrations that need to prove an action. Check account limits before relying on hosting or team workflows, and evaluate the export your audience will actually receive.

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.