Revise a generated video

For a video, request revisions in the existing conversation. Use Annotate when you want to point to a moment in the preview; use chat for a change that affects the whole video.

Before you revise

Open your own completed conversation and wait for any active request to finish. Revisions can consume credits. Review the selected output before sending another change. Editing a finished premium-model video requires Basic or higher, including a video created with your Free monthly premium allowance. Free accounts can continue editing ngram-flash videos with available credits.

Request a revision

1. Play the video and pause near the moment you want to change.
2. Choose Annotate, then use Pin a change at the current moment or click the frame. You can also type a revision directly in the message box.
3. Name the change and what should remain. For example: “Keep the opening. Hold the closing message longer so there is time to read it.”
4. For a pinned request, choose Add to chat, review the queued request, then choose Send message. Adding it to the queue alone does not submit it.
5. Wait for the next result, then replay the changed section and its neighboring scenes.

Revise the explanation around footage

Name the recording and moment, then state the graphic and audio treatment. For example: “During the compression explanation, keep the instructor’s speech, insert a short pressure diagram and return to the recording in sync.” Ask for clean footage or no text when overlays distract.

For a conversation, name the speaker and answer to change. For depth emphasis, name the word and moment. Review the changed section and its neighboring scenes before sharing.

Earlier rendered outputs can be previewed or downloaded separately. Saved versions are conversation checkpoints: use their restore or fork action when you need to return to a prior project state or try another direction. Simply selecting an older output does not restore the project.

Change the voice, presenter, or look

In an active conversation, open Video settings, choose the available voice, presenter, or style, and save the settings. Then describe the change you want in chat. Review the credit estimate before sending a revision; changing settings alone does not rewrite an earlier output.

Try another direction from a saved version

Open Saved versions in the conversation. Restore a checkpoint to continue from it, or fork one to keep the current path and try a separate direction. Check which project or version is active before requesting another generation.

Give useful feedback to ngram

For a video edit, give ngram three things: the location, the desired change, and what should stay. “Make it better” leaves the next decision open; “At the closing card, replace the headline with ‘Book a demo’ and keep the colors and earlier scenes” gives you a change you can verify.

Choose plan feedback or preview feedback

Use Request changes during plan review for the audience, message, factual claims, script, and scene order. Read Script and Production details again before choosing Approve plan. Use the finished preview to judge pacing, legibility, pronunciation, and whether the picture supports the narration.

A revision template to copy

At [timestamp or named scene], [describe the observed problem]. Change [specific element] to [desired result or exact replacement wording]. Keep [parts already working]. The priority is [constraint]; if needed, [acceptable tradeoff].

Examples of useful video feedback

• Factual correction: “In scene 2, replace the export claim with the exact wording in the attached product sheet. Keep the layout and scene order.”
• Readability: “In the receiving sequence, hold the scan, label, and storage labels longer. Keep the procedure order and box illustrations. If the runtime must stay fixed, shorten the opening.”
• Story: “Explain the barcode mismatch before introducing the product. Keep the final CTA and the approved facts.”
• Tone: “Keep the steps, but explain them for a new warehouse employee. Define receiving before using the term again.”
• Pronunciation: “In the opening narration, pronounce [product name] as [phonetic spelling]. Keep the script wording and visuals.”

Check the next version against the request

1. Read your request while replaying the changed section and its neighboring scenes.
2. Check that the intended change happened and the parts you asked to preserve are still correct.
3. Review facts, on-screen text, narration, music, and the final CTA.
4. If the request missed the mark, make one smaller correction. Use Versions to inspect or download earlier outputs; selecting one is not a restore action.

Combine related notes, and resolve conflicting team feedback before sending it. Revisions can consume credits. Avoid resending while a request is active, and contact Support if the same precise correction fails again.

Rate the result or report a product problem

If the request misses the mark

Describe the remaining problem with a location and exact replacement wording where needed. If Annotate is unavailable, check that you own the conversation and that a playable result is selected. Use chat for the request when appropriate.

Give feedback rates your experience with ngram. To change the video itself, send a revision in the conversation.