Published: 2026-08-04
Reading time: ~12 min
TL;DR: MiniMax H3 accepts multimodal inputs (9 images + 3 videos + 3 audio clips) and outputs 2K/15s video with built-in subtitle rendering and lip-sync. We analyzed 20 high-performing posts on X and extracted 7 reproducible prompt patterns that turn this API into a production-grade video pipeline.
If you've worked with video generation APIs before, you know the drill: throw a text description at the model, pray for something usable, iterate 20 times, settle for "good enough." MiniMax H3 changes the game because its input schema is fundamentally richer than "one string in, one clip out." You're not prompting a model — you're programming a director.
This post breaks down 7 techniques distilled from 20 viral X posts, each with working prompt templates you can drop into your pipeline today. Every example includes the original creator's output and a link to their post.
The Input Schema: Why H3 Prompts Are Structurally Different
Before diving into techniques, let's look at what you're actually working with:
| Input Type | Max Slots | Role |
|---|---|---|
| Text prompt | 1 | Timeline, scene description, style directives, camera movement |
| Reference images | Up to 9 | Character identity, environment, product shots, style references |
| Reference video | Up to 3 | Motion rhythm, transition style, camera behavior |
| Reference audio | Up to 3 | Mood, pacing, music sync |
Output: 2K resolution, 15 seconds, native subtitle rendering, lip-sync, music synchronization.
This multimodal input model means your prompt isn't just a text string — it's a configuration object where each input has a defined role. The techniques below are essentially patterns for wiring these inputs together effectively.
Technique 1: Embed Timeline Markers in Your Prompt — Control Pacing Programmatically
The pattern: Instead of describing a single frame, describe a sequence of timed events. Think of it as keyframe animation expressed in natural language.
Traditional video generation APIs treat your prompt as a single scene description. MiniMax H3 interprets time-anchored instructions ("at 3s", "[0s-4s]") as timeline markers, giving you frame-accurate control over pacing and transitions.
Working Example: Anime Opening with Music-Synced Prompt
Creator @fal generated a 15-second anime opening from 5 static frames. The key insight: embed music timing directly into the prompt text so the model synchronizes visual changes to beat drops.
Output frame: Title card and subtitles at the opening's climax (~12s). Text is clearly readable — the result of timeline markers + music beat anchoring working in concert.
画面从黑屏渐入，背景出现城市天际线轮廓。
低频鼓点在第 3 秒敲响，画面随节奏推进到角色特写。
爵士贝斯在第 6 秒加入，镜头拉远展示全景。
弦乐在第 12 秒推向高潮，画面切换为标题卡。
Why this works for developers:
- Time anchors (
第 3 秒,第 6 秒) act like keyframes in an animation curve — the model interpolates between them - Each marker pairs a visual action with an audio event, creating deterministic sync
- The model treats missing intermediate frames as interpolation targets, similar to CSS keyframe animations
Original post: @fal — anime opening
Technique 2: Dual-Image Role Separation — Lock Identity and Environment Independently
The pattern: Assign each reference image a single responsibility — character OR environment — and state this explicitly in the prompt. Never let one image carry both.
Character consistency is the hardest problem in AI video generation. MiniMax H3's multi-image input gives you a clean solution: constraint-based reference assignment. Think of it like dependency injection — each input has one job.
Working Example: Realistic Thriller Short Film
Creator @Diplomeme built a realistic war thriller using two reference images with strict role separation:
| Reference 1: Character Lock | Reference 2: Environment Lock |
|---|---|
 |
 |
- Image 1 → facial features, clothing, hairstyle (identity anchor)
- Image 2 → bridge, city skyline, color palette (environment anchor)
Then storyboard timecodes drive the sequencing:
参考图 1 为角色 A，保持其面部特征和服装不变。
参考图 2 为城市桥梁环境，作为全片背景基调。
[0s-4s] 角色 A 站在桥头，低头看向河面，逆光剪影。
[4s-8s] 镜头缓慢推近，角色抬头，表情紧张。
[8s-15s] 角色转身奔跑，镜头跟随，城市天际线在背景中展开。
Output frame: Same character, same city, same dawn color palette — all maintained across shots thanks to the dual-image constraint.
The developer takeaway:
- One image per dimension. If you need character + environment + style reference, use 3 images — don't cram everything into one
- Explicitly state
"保持其面部特征和服装不变"(maintain facial features and clothing unchanged) — the model respects these constraint declarations - This is analogous to type hints in code: the more specific your input declaration, the less the model "guesses"
Original post: @Diplomeme — realistic thriller short
Technique 3: Explicit Text Rendering Directives — Get Crisp On-Screen Typography
The pattern: Add a dedicated sentence for text clarity, specifying font style, color, and outline. Treat it as a rendering hint the model needs to be told explicitly.
Most video generation models produce pseudo-text — shapes that look like letters but aren't legible. MiniMax H3 has genuine text rendering capability, but only if you opt in via prompt. Think of it as enabling a feature flag.
Example A: Large Title Text in Anime Openings
Creator @slash1sol produced an anime opening with razor-sharp title text behind the character:
Output: The ARDEN VOSS text has clean edges and remains legible even during motion — a textbook example of H3's text rendering when properly prompted.
屏幕中央出现标题文字「XXX」，字体清晰锐利，边缘无模糊，
白色文字带黑色描边，确保在动态画面中保持可读性。
Example B: Mobile UI Text for Client Ads
Creator @0xInk_ used other models for main footage but switched to MiniMax H3 specifically for scrolling text shots — because H3's text output is cleaner and more controllable for UI-type content.
Output: Scrolling French text on a mobile screen, sans-serif, clean, uniform scroll speed. This shot was generated by H3 while the rest of the ad used a different model.
手机屏幕显示滚动的法语文本，字体为无衬线体，
文字清晰可读，滚动速度均匀，屏幕反光自然。
Key directives for text rendering:
- Always specify:
清晰锐利(clear and sharp),边缘无模糊(no edge blur),可读性(readability) - Declare font style:
无衬线体(sans-serif) vs衬线体(serif) - Declare color + outline:
白色文字带黑色描边(white text with black outline) - For mixed-model pipelines: use H3 only for text-heavy shots, other models for non-text scenes
Original posts:
Technique 4: Multimodal Input Orchestration — Assign Each Input a Role
The pattern: Map each input to a specific output dimension: images → visual content, video → motion/rhythm, audio → mood/atmosphere. Declare each role in the prompt.
This is where MiniMax H3's Omni capability really shines. The model can process images, video, and audio simultaneously, but only if you tell it what each input is for. Otherwise it guesses — and guessing leads to incoherent output.
Think of it like passing arguments to a function with unlabeled parameters. Label your arguments.
Example A: 6-Image Asset Composition + Video as Rhythm Template
Creator @influencer_seo used a particularly clean separation:
- 6 reference images → each is a visual "building block" for one shot
- 1 reference video → not for visuals, but purely for editing rhythm and transition timing
参考图 1-6 分别为 6 个镜头的视觉参考。
参考视频用于提取剪辑节奏和转场风格，不要直接复制画面。
整体节奏：前 5 秒慢推，中间 7 秒快切，最后 3 秒定格。
Example B: Full Omni Workflow
Creator @YaseenK7212 demonstrated the complete Omni pipeline: text → intent, images → visuals, audio → atmosphere, video → motion. His key insight: the value of multimodal input isn't "more data" — it's "more consistent output."
Example C: After Effects Motion Proxy
Creator @seiiiiiiiiiiru created a rough AE graphic animation and fed it as a motion reference. The model doesn't copy the AE visuals — it extracts the motion vector (direction, speed, easing) and applies it to the static reference image.
参考视频为运动参考，提取其运动节奏和方向。
画面内容以参考图为准，保持静帧的构图和色调。
按照参考视频的节奏让画面缓慢运动。
Input role mapping (use this as a template):
| Input | Role | Prompt Declaration |
|---|---|---|
| Image | Visual content / character identity | `参考图为视觉参考，保持构图和色调` |
| Video | Motion / rhythm / transitions | `参考视频用于提取运动节奏，不要复制画面` |
| Audio | Mood / pacing / music sync | `参考音频用于控制整体氛围和节奏` |
Original posts:
Technique 5: Single-Image Product Ads — Prompt Template for E-Commerce Pipelines
The pattern: One product image + a structured prompt with camera movement instructions + timeline markers = a 15-second commercial ad. No filming crew, no post-production.
This is the technique most directly applicable to automated content pipelines. If you're building a product that generates ad videos from product photos, this is your base template.
Working Example: Single Image → 15-Second Product Ad
Creator @ai_for_success demonstrated the complete flow from a single product image to a polished 15-second ad:
Output: Commercial-grade product shot — coral, sea turtle, and watch in frame, watch face text legible. All from one input image.
产品图作为主视觉参考。
镜头从产品正面开始，缓慢环绕拍摄，展示产品细节。
背景为浅灰色渐变，光线柔和，营造高级质感。
第 8 秒镜头推近到产品 LOGO 特写。
第 12 秒拉远，展示产品全貌，背景出现品牌标语。
整体风格：简洁、高级、商业广告质感。
Creator @thisismariaa25 applied the same pattern to a menu concept image, producing a vertical food video for local business marketing:
Reusable prompt template for product ads:
[产品图] 作为主视觉参考。
镜头从产品正面开始，缓慢环绕拍摄，展示产品细节。
背景为 [背景描述]，光线 [光线描述]。
第 [N] 秒镜头推近到 [重点部位] 特写。
第 [M] 秒拉远，展示产品全貌。
整体风格：[风格关键词]。
For vertical (9:16) output: append 竖屏 or 9:16 to the prompt.
Original posts:
Technique 6: Style Composition — Combine 2-3 Style Tags for Novel Aesthetics
The pattern: Don't use a single style label. Compose 2-3 specific style keywords, add color grading directives, and reference well-known visual styles by name.
"Anime style" gives you generic anime. "赛璐珞着色 + 新海诚式光影 + 丁达尔效应" gives you something nobody else is producing. MiniMax H3's style encoder responds strongly to specific, composable style tokens — similar to how SD models respond to weighted prompt tokens.
Example A: Fashion Editorial × Cyber-Grunge × Rap MV
Creator @Strength04_X fused three visual languages:
时尚 editorial 质感 + cyber-grunge 字体 + 地下说唱 MV 剪辑节奏。
画面在高端时装秀场和地下停车场之间切换。
字体风格：粗体无衬线，带霓虹光晕。
色调：高对比，暗部偏青，亮部偏橙。
Example B: Photo-to-Illusion Morph
Creator @aichof21 used a real photo as reference and prompted a continuous style transition — realism dissolving into watercolor illustration:
参考图为实拍照片。
画面从写实照片开始，逐渐过渡为手绘插画风格。
过渡过程中保持构图不变，只改变画面的笔触和色彩。
最终画面为水彩插画风格，保留照片的光影关系。
Example C: Anime with Specific Art Direction
Creator @hafuma went beyond "anime style" with precise art direction:
日式动画风格，赛璐珞着色，线条清晰。
角色表情丰富，动作流畅。
背景为新海诚式光影，天空有丁达尔效应。
Style composition formula:
[渲染风格] + [字体/线条风格] + [色调/调色] + [知名参考风格名]
Pro tips:
- Specific color grading (
暗部偏青，亮部偏橙) is 100× more effective than vague descriptors (好看) - Naming real artists/styles (
新海诚式,赛璐珞着色) gives the model a concrete reference point - Camera movement + style composition together create the "cinematic" feel — don't rely on style alone
Original posts:
Technique 7: Storyboard Timecodes — Treat the Prompt as a Shot List
The pattern: Split the 15-second output into 3-5 time segments. Each segment gets one action or camera change. Use [0s-3s] format with no gaps.
This is the most powerful technique and the closest to "programming" a video. When you write timecodes into the prompt, the model stops interpreting and starts executing. You're no longer hoping for a good output — you're specifying it.
Example A: Jet Formation Aerial
Creator @Kuriyama890 produced a three-jet formation video with smooth, precise shot transitions:
Output: Three jets leaving contrails spelling "is coming" — storyboard timecodes + text rendering firing simultaneously.
[0s-3s] 广角航拍，三架战斗机以 V 字编队飞过雪山。
[3s-7s] 切换到座舱特写，飞行员戴上头盔。
[7s-11s] 编队拉升，喷出白色尾迹。
[11s-15s] 仰角镜头，三架飞机在天空中拉出「H3」字样。
Example B: Story Trailer Structure
Creator @john_my07 demonstrated H3's combined strength in prompt following, text rendering, and camera control by encoding a classic trailer structure:
[0s-4s] 黑屏，白色字幕淡入片名。
[4s-8s] 快速闪切 3 个场景镜头，每个约 1.3 秒。
[8s-12s] 主角正面特写，缓慢推近。
[12s-15s] 黑屏，出现上映日期文字。
Timecode rules (treat these as constraints):
| Rule | Why |
|---|---|
| Each segment: 3-5 seconds | Too short → model can't complete the action; too long → pacing drags |
| One action per segment | Multiple actions per segment cause the model to "average" them |
| No gaps between timecodes | Gaps create dead frames or unpredictable interpolation |
| Use `黑屏渐入` / `淡出黑屏` at edges | Creates cinematic fade-in/fade-out framing |
| Format: `[0s-3s]`, `[3s-7s]`, `[7s-15s]` | Consistent format improves model adherence |
Original posts:
Additional Cases Worth Studying
Beyond the 7 core techniques, these posts showcase edge cases and advanced patterns:
Cinematic Multi-Shot Test — @maxescu
~280 likes. The most detailed storyboard prompt we found — specifies timeline, camera physics, lighting, and dialogue for every shot. If you want to see how far you can push H3's prompt adherence, start here.
Japanese Spec Sheet + Demo — @seiiiiiiiiiiru
Benchmark case from the Japanese community. Combines a product specification breakdown with live demo output.
PixVerse Platform Demo — @PixVerse_
Product launch–quality output. Useful as a style ceiling reference for your own experiments.
| Case | Creator | Why It's Useful | Link |
|---|---|---|---|
| Cinematic multi-shot test | @maxescu | Ultra-long prompt with every parameter specified | Post |
| Japanese spec + demo | @seiiiiiiiiiiru | JP community benchmark | Post |
| Vertical lip-sync | @qaHEqxyzUF99214 | Lip-sync capability test | Post |
| Platform demo | @PixVerse_ | Production-quality reference | Post |
| Pure text-to-2K 15s | @MrDavids1 | T2V baseline test (no images/video input) | Post |
| MV production | @apilpirman | Music video workflow exploration | Post |
The Golden Formula: A Complete Prompt Template
All 7 techniques collapse into one composable structure:
[Timeline Markers] + [Camera Movement] + [Scene Content] + [Style/Color Grading] + [Multimodal Input Roles]
Here's a complete, production-ready prompt example combining every technique:
参考图 1 为角色 A（女性，黑色短发，白色衬衫）。
参考图 2 为办公室环境（落地窗，城市天际线）。
参考视频用于提取运镜节奏。
[0s-4s] 中景，角色 A 坐在办公桌前，低头看电脑，自然光从落地窗洒入。
[4s-8s] 角色抬头，表情惊讶，镜头缓慢推近到面部特写。
[8s-12s] 角色站起身，走向落地窗，镜头跟随。
[12s-15s] 角色背影站在窗前，城市天际线在窗外展开，画面定格。
整体风格：电影感，色调偏冷，浅景深，自然光线。
What makes this prompt work:
- Input role declarations at the top — the model knows what each reference image does
- No-gap timecodes — every second of the 15s output is accounted for
- One action per segment — clean, deterministic shot transitions
-
Explicit style directives —
电影感+色调偏冷+浅景深+自然光线= 4 composable style tokens - Reference video declared for motion only — prevents the model from copying the video's visuals
Practical Recommendations for Pipeline Integration
If you're integrating MiniMax H3 into a production workflow, keep these principles in mind:
Storyboard first, details second. Split the 15 seconds into 3-5 segments. Define the core action for each segment before adding style or camera details.
One image, one job. Character image, environment image, style reference image — keep them separate. Combining roles in a single reference image degrades consistency.
Name your styles explicitly. "赛璐珞着色，新海诚式光影" outperforms "anime style" every time. The model's style encoder has stronger associations with specific named styles.
Label every multimodal input. Don't make the model guess whether a video input is for visuals or for motion. Declare
参考视频用于提取运动节奏，不要复制画面and remove the ambiguity.Use H3's text rendering strategically. If your video needs titles, subtitles, or UI text, route those shots to H3 even if the rest of the pipeline uses a different model. It's currently one of the strongest models for readable on-screen text.
Iterate on the timecode structure, not the prose. If the output doesn't match your vision, check the timecodes first — wrong pacing or gaps between segments are the most common failure mode.
All output frames and tweet screenshots in this post are from the original creators linked above. Click through to their X posts to see the full videos and prompt details.
If you'd like to try MiniMax H3, visit: https://minimaxh3.art/
Top comments (0)