Gemini 4 Explainer Video: A Practical Tutorial

Can Gemini 4 explain how a parcel finds the right delivery lane in just 25 seconds? We built an animated sorting line in iArt, then improved the ending with one follow-up prompt. Watch both versions and use the same approach for your own process, product or lesson.

The result: The first version made the scan-to-lane sequence easy to follow. One focused edit gave the ending a closer view and a larger headline, while the earlier sampled frames stayed unchanged. The useful lesson is to define the process first, then review reading size and camera distance separately.

1. Start with the one thing viewers should understand

The point of this explainer is simple: a label identifies the route, and the sorter sends the parcel to the corresponding lane. A viewer should be able to follow one coral box from scanner to destination B without needing a voiceover.

This is a simplified teaching diagram. USPS documentation describes barcode and address recognition in automated parcel processing; our imaginary conveyor illustrates that idea without claiming to reproduce a particular facility.

2. Give Gemini 4 a visual brief it can follow

Open iArt, choose Animation and Gemini 4, use a 16:9 canvas, and turn narration off for this example. Set thinking to Medium to match this test. The prompt supplies the story and the facts that must stay consistent, while leaving the model room to design the miniature and motion.

Create a 25-second explainer called "HOW YOUR PARCEL FINDS ITS WAY". Explain a simplified barcode-based parcel sorting line through one continuous illustrated cutaway.

Create a 25-second explainer called "HOW YOUR PARCEL FINDS ITS WAY". Explain a simplified barcode-based parcel sorting line through one continuous illustrated cutaway. Follow ONE coral box marked "B" from arrival to destination B. Sequence: the box enters the conveyor; a scanning arch reads its barcode; a clearly labelled routing panel displays "Destination B"; a diverter guides the same coral box into lane B (lanes A and B must both be visible); the box reaches a matching B loading cage. Other neutral parcels may stay in the background, but the featured parcel must remain trackable. On-screen chapter labels: "Scan the label", "Choose the route", "Send to lane B". End: "One label. The right route." Use a refined isometric miniature: warm white architecture, ink-blue conveyor structures, coral hero box, mustard scanner light, fine mechanical detail and soft coherent shadows. Motion should show cause and effect: scan before route choice, route choice before diverter movement. This is a simplified explanatory diagram, not a particular carrier's exact system. Use selective close-ups but retain spatial continuity, short readable labels and subtle original mechanical/electronic sound cues. No narration or external assets. Avoid random gears, dashboard clutter, teleporting parcels and photorealistic claims.
Deliver one complete 1280x720 code-drawn animation with a coherent beginning and ending. Use intentional art direction, strong hierarchy and smooth purposeful motion. No external assets or narration. A subtle original synthesized soundtrack is welcome. Inspect rendered frames and fix visible errors before delivering. Do not show player controls. 

Try this prompt in iArt AI →

Three parts of this brief are especially reusable: name one object to follow, describe what causes each change, and specify the closing message. Art direction helps the result feel cohesive; those three constraints make the explanation understandable.

3. Review the first video against the brief

What worked: The coral parcel stays visually distinct from the neutral packages. The scanner, Destination B panel and labelled branch establish a readable chain of events. A consistent isometric setting lets the viewer follow the journey without rebuilding the scene at every step.

What needed attention: The first ending leaves the featured parcel small in a wide view, with a secondary subtitle that becomes hard to read at phone size. Several machinery labels are also small; they add detail but should not carry essential information.

Review the animation once for the story and again for the details. Follow the featured parcel through the entire scene. Then check the labels, lane choice, scan timing and ending separately. A good-looking still cannot show whether an object jumps between positions.

4. Make one focused edit in the same project

The process already read clearly, so the follow-up targeted the ending: keep the first 20 seconds, move closer to the B cage, enlarge the closing headline and remove the tiny subtitle.

Revise only the final 5 seconds (20–25 seconds) of the existing parcel explainer to make the takeaway readable on a phone. Move to a closer view of the coral parcel arriving in the B cage, while keeping the B label and enough of lane B visible to understand the destination. Make the final headline "One label. The right route." at least 48 px on the 1280×720 canvas, with strong contrast and a clear safe margin. Remove the tiny secondary closing subtitle. Keep the total duration 25 seconds. Preserve everything before 20 seconds, all parcel routing, the palette and the original sound. Inspect the revised ending and deliver the saved revision.

Send this as a follow-up in the existing project, after generating the original brief. A new project does not have the animation to edit.

After the edit: The final view moves much closer to the coral parcel in cage B. The headline is visibly larger and the small closing subtitle is gone. The first six sampled frames, all before 20 seconds, match the initial version; the total duration remains 25 seconds. At the end the machinery is deliberately cropped, so this view works as a conclusion rather than an overview of the entire sorter.

Compare this revised video with the first version above. Check both the requested change and the rest of the sequence before deciding that the edit is finished.

5. Check the ending, then export

Watch at normal speed and at the size you plan to publish. Every important label needs enough time to read. Make sure the final frame resolves the story and leaves the ending visible rather than cutting off the last action.

In this workflow, Gemini 4 Argon produces text and code, and iArt turns that code into the animated preview and MP4. These article videos were rendered locally from the saved iArt project at 1280×720; they are not a test of hosted export speed.

Generation time and cost

This is one project tested on October 19, 2026 with Gemini 4 Argon at medium reasoning. Costs are the actual iArt credits deducted for generation and the revision. Video export is excluded. The initial and revised source are preserved separately; no animation code was manually edited for the article.

Where to take the next explainer

Try another process with a clear object or state to follow: a support request moving to the right team, a library book being checked out, or a reusable container completing a return cycle. Keep the first film focused on one route; add exceptions only after that route reads clearly.

For more visual directions, see our six Gemini 4 animation examples and prompts. For shorter business briefs, see the DeepSeek Flash 1017 video tests. For a general workflow, start with the iArt explainer video maker.

FAQ

Can Gemini 4 make an explainer video?

Yes, through a code-animation workflow in iArt. Gemini 4 writes the animation code; iArt provides the preview, editing and MP4 workflow. This tutorial shows a parcel-sorting explainer from initial prompt through one revision.

What should a Gemini 4 explainer prompt include?

Include one takeaway, a short sequence of visible actions, exact on-screen labels and a consistent object to follow. Add visual direction and duration, then explain what must remain unchanged across scenes.

Do I need a voiceover?

Not for this example. Short labels and visible cause-and-effect explain the sorting sequence. For a more complex topic, decide on narration before generating so the visuals can support the script.

Can I use the same approach for a product tutorial?

Yes. Replace the parcel sequence with a real user action, a visible system response and a clear result. Check all interface details against the actual product.