
MiniMax H3 covers the 2K tier and the reference rules in detail.
Two places, one setting. In the episode editor: the button in the top bar that shows the current tier’s name, next to Composite. In Settings: Model Preferences → Video Model. Both change the same thing — the tier your next segments render on, in this project and in new ones. Segments already made keep the tier they were made with, and each version records it. The price on a segment’s generate button always shows the tier you are about to use.
Everything but the resolution: 15-second segments, sound always generated with the picture, several shots with genuine cuts in a single generation, and the reference limits below. A segment you set up here runs on H3 unchanged.
Per generation, the H3 family’s budget:
16 credits per second, against 25 on H3. The usual pattern: draft the cuts here, regenerate the keeper on H3. Credits are taken on delivery; if a generation fails, the credits come back or are held until support checks it.
Finding out whether a 15-second segment’s cuts land — the look, the reaction, the insert — before paying the 2K rate. At 768P the blocking and timing are fully visible; fine texture is not the point.
Text and references are checked before rendering. A rejection is not charged: the credits come back and the credit history says so. The count is kept per account: after 12 rejections within 24 hours, the next one is held for review instead of refunded, and video generation pauses for 1 hour. So edit the flagged material rather than retrying the same segment. Content rules and checks explains what gets flagged.
The messages you may meet on this tier:
| What you see | Usual cause | What to do |
|---|---|---|
| “Invalid input — check the reference images and duration, then retry.” | Usually one of the reference files for this segment could not be read | Generate again once; if it keeps failing, check that the character, location and prop images open, then contact support |
| “Blocked by content safety rules — edit the script or description and retry.” | The script or a reference tripped the content check | Edit the flagged part; see the content-check section for when a rejection is refunded |
| “The generation service hit a temporary problem. You weren’t charged — feel free to try again.” | The service was saturated; the site already tried again once for you | Wait a few minutes and generate again; nothing was deducted |
| Video generation paused | More than 12 rejected generations within 24 hours; the next one is held for review | Wait out the pause (1 hour); fix the material before retrying |
Up to H3 for the 2K keeper. Across to a Wan or Seedance 2.5 tier for more than 9 image references, or for a 30-second take if the episode’s storyboard was generated with 30-second segments.
| Reference type | Limit on this tier | Note |
|---|---|---|
| Images | Up to 9 | At least one image is required when any reference is attached |
| Voice clips | Up to 3, about 14 s in total | Voices need an image alongside; with no image the site drops the voice clips and uses the written voice descriptions |
| Over a limit | — | The site leaves out the least important references first; a character whose voice is left out speaks from the written voice description |
On this site it is the 768P tier of the same family, with the same rules and cuts.
The segment had more than 9 images, more than 3 voice clips or too many seconds of voice, or a voice clip had no image with it.
No; 15 seconds per segment.
No. Every render includes sound.
Yes. Every version is kept; the composite uses the active one.
Set up a 15-second segment with real cuts, check it at 768P, then render the keeper on H3.
Updated September 27, 2026
Pricing·Novel to Video·Guides·Samples·Support·Privacy·Terms·Legal·Contact·© 2026 SceneMixer