MiniMax H3: 2K by default there, 768p by default on Sume

If you leave resolution out on Sume, MiniMax H3 renders at 768p, not 2K. MiniMax's launch post says H3 generates 2K by default and also offers 768p (read 2026-10-04). Sume's catalog sets a different default, and the difference is worth $1.63 against $0.75 on a 10 s clip.

What each tier is

The Sume catalog lists native 480p and 768p. The 2K and 4K options are upscales of the 768p render and are priced only when you request them. So a 2K request is not a higher native render; it is the 768p result at a larger size.

Price per second and for a clip

Rates below are the provider list price times 1.25, with totals rounded up to the cent. All figures are from the Sume pricing tables.

Choosing deliberately

Set resolution explicitly in every request. If you assume the vendor default, you will under-budget on Sume by a factor of two or more, and if you assume Sume's default you will under-deliver on pixel count. The amount is reserved on submit and refunded if the job fails.

H3 Max has its own tiers: 480p, 768p and 1080p, with 1080p a latent refinement of 768p and no 2K or 4K. See the stored H3 versus H3 Max guide.

Compute it yourself

This script reproduces the table with no network access.

import math

LIST = {"480p": 0.05, "768p": 0.06, "2K": 0.13, "4K": 0.16}
for res, per_sec in LIST.items():
    for seconds in (5, 10, 15):
        billed = math.ceil(seconds * per_sec * 1.25 * 100 - 1e-9) / 100
        print(res, seconds, f"{billed:.2f}")