GPT Image 2.5 Flare & Sunburst are live on EvoLinkTry GPT Image 2.5
Skip to article
Editorial illustration of floating reference-image tiles combining into a coral architectural scene; not an H3 Image output
Tutorial

MiniMax H3 Image: 4K Generation and Editing with 16 References

Explore MiniMax H3 Image: up to 16 references, 4K area presets, Highspeed, prompt review with Context-IR, and practical evaluation workflows.

EvoLink TeamProduct Team
12 min read
MiniMax H3 Image brings text-to-image generation and reference-guided editing into one image workflow, with up to 16 reference images, a default 4K area preset and up to 10 outputs per request. H3 Image also offers a Highspeed version and a standalone prompt-enhancement service, allowing teams to review an expanded brief before generating an image. MiniMax image-generation guide

For teams building product-image tools and marketing-asset workflows, the development worth watching is more control around a single creative task: organize source assets, define the delivery canvas, then generate candidates for review. EvoLink users can use these capabilities as selection criteria alongside the image models already available through a unified API gateway, while checking H3 Image access separately.

MiniMax’s direct APIs use synchronous requests, optional per-image streaming and a default 4K area preset. EvoLink’s route uses asynchronous tasks and defaults to 2K for automatic or ratio-based sizes; this integration covers the standard version. Highspeed, standalone Context-IR and per-image streaming described here are provider capabilities and are not included in this EvoLink integration.

What stands out in the release?

H3 Image can generate a new image from text or accept references and editing instructions. The main controls are:

CapabilitySupported capabilitiesWorkflow implication
Multiple references1–16 input images for editingSpecify the product, person, scene and visual direction separately
Flexible canvas1K/2K/4K area presets; custom output up to 20 million pixelsPrepare assets for different placements and delivery sizes
Batch generation1–10 images per request, with per-image streamingReview completed candidates while others are still generating
Visible promptsReturns the prompt actually used for each imageInspect how a short instruction became a visual description
Prompt preprocessingContext-IR can return an enhanced prompt without imagesReview the expanded brief before text-to-image generation
Model versionsStandard and Highspeed versionsCompare both on the same tasks before choosing a default
These controls let teams decide which sources to use, what to deliver and how to prepare prompts. They also provide a concrete starting point for evaluating a model against actual creative requirements. Generation, editing and output specifications

Bring more creative requirements into one image

Up to 16 references give teams room to distinguish the role of each asset. A product advertisement can supply the item, target location and style separately; a character project can specify identity, clothing and environment independently.

For a skincare-product scene, a front-facing product photo can establish packaging and bottle proportions, another image can show the intended space, and a visual reference can express lighting and color. Text instructions specify what must stay and what should change. Each source requirement then has a clear role that reviewers can trace.

For example, replace the cat in the first image with the Shiba Inu in the second, keeping the background. It demonstrates how to specify a source, a change and preserved elements. Product, character and scene combinations can use the same approach, with results validated on your own assets.

Reference inputs support JPG, JPEG, PNG, WEBP, HEIC and HEIF. Each image's width and height must be within 128–8192 pixels, with a long-side-to-short-side ratio no greater than 4:1. Both a single file and the entire request body have a 64 MiB limit, so support for 16 images does not mean 16 maximum-size files can all be embedded directly. The provider accepts public image URLs, uploaded-file references and Base64 inputs. Prepare large assets according to the transfer method and request-body limit. Reference-image input rules

For product tasks, check the item first: shape, packaging, labels and proportions. For character tasks, compare identity, clothing and accessories across candidates. Multiple references supply more context; whether the output preserves the right details still needs validation with actual assets.

Adapt the 4K canvas to different placements

H3 Image's 4K preset targets an area of 4096 × 4096 pixels. Actual dimensions depend on the chosen ratio. Common aspect ratios produce these dimensions:
Aspect ratio2K preset4K presetExample delivery layout
1:12048 × 20484096 × 4096Square product displays and social images
16:92720 × 15365472 × 3072Landscape ads and video opening frames
9:161536 × 27203072 × 5472Vertical social assets and video opening frames
3:13552 × 11847104 × 2368Ultrawide banners

The layout uses are creative-planning examples.

One area preset can therefore serve different placements, but each placement still needs its own composition. A product-page hero, a banner ad and a vertical social image need different framing and negative space even when their pixel areas are similar.

Teams can choose 1K, 2K or 4K, or set dimensions within the supported 655,360–20,000,000-pixel area and 1:3–3:1 aspect-ratio ranges. Explicit dimensions and ratio-plus-area are mutually exclusive settings. If delivery dimensions are fixed, specifying width and height can avoid a mismatch between automatic framing and the destination. Choose the canvas from delivery requirements, then evaluate detail and file size. More pixels alone do not establish better image quality. Output-size rules

Output format is also configurable: JPG is the default, with PNG and WEBP available. JPEG and WEBP support compression settings, defaulting to 95; PNG ignores this parameter. It controls delivery-file compression, not a model quality or speed tier. H3 Image currently does not support transparent backgrounds, so choosing PNG does not enable transparency.

Review the expanded prompt before generating

Prompt enhancement is part of the H3 Image workflow. Text-to-image enables it by default, while editing always enables it. Each image's actual prompt is returned as revised_prompt, allowing teams to inspect both the original instruction and its expanded visual description.

A brand brief might say only “a warm-toned bathroom product image,” while a reviewer still needs to confirm camera distance, product placement and background elements. Reading the expansion helps reveal whether those interpretations fit the creative direction. It provides a text-level check; the final image still needs review.

The standalone H3-Image-Context-IR service separates these steps further: it returns an enhanced prompt without generating an image. For text-to-image, teams can review or revise that description, then disable enhancement, specify dimensions or a fixed aspect ratio, and submit the approved text.
This adds a review point for brand and creative teams. Context-IR has its own usage charge, but subsequent text-to-image generation can avoid paying for enhancement again. Editing works differently: enhancement is always enabled, so sending a preprocessed prompt to the editing endpoint enhances and charges it again. Context-IR supports only standard H3 Image, not Highspeed. Context-IR workflow and billing

The prompt limit is 32,000 characters, but with enhancement disabled, only about the first 4096 tokens take effect. These are different input capacities. Teams maintaining their own complete prompts should still control length when disabling enhancement and state the subject, preserved details and delivery composition clearly.

Generate several candidates and review each as it finishes

A request can generate up to 10 images, with 1 as the default. With streaming enabled, each completed image is returned separately. Reviewers can inspect the first candidate while the others are still generating.

A product brief can produce a batch to check the item, copy space and brand suitability of the background before choosing an image for further work. Batch generation provides multiple results in one request. If distinct creative directions are required, write separate briefs; do not assume one batch automatically covers ten predefined concepts.

For creative applications, this supports a direct interaction: submit a brief, show completed candidates and retain successful results when some images fail. Streaming returns finished images, not progressively sharpening previews. Results arrive in completion order, so the application must retain image indices to match outputs. Ordinary responses can also be partially successful: at least one successful image produces a success status, but each result still needs inspection. Generation billing counts successful images, and the interface should distinguish usable outputs from failures. Batch generation and streaming

Which production workflows should you evaluate first?

The following scenarios help evaluate these capabilities; they are not completed model tests.

Product scenes and marketing variants

Product teams can keep a product photo as a fixed input while trying different spaces, lighting and compositions. A campaign often needs a square product display, a landscape banner and a vertical social image. H3 Image's reference editing and canvas settings offer a shared starting point for these deliverables.

Check whether the bottle, shoe shape, packaging or other key structure is preserved before judging the setting. If packaging text or brand marks must be exact, list them as separate acceptance criteria; 4K support does not imply correct typography. Also check product proportions and negative space across formats to determine whether the workflow reduces manual cleanup.

Characters, scenes and concept exploration

For game concepts, character designs or story scenes, teams can supply separate character, clothing and environment references, then describe their relationships. When moving the same character into a new location, specify which appearance details must stay and which lighting or environment can change.

Acceptance centers on relationships between references: is the character holding the correct prop, has clothing borrowed unwanted elements from another image, and are positions correct? Multiple inputs make those conditions easier to express, but identity consistency, complex spatial relationships and repeated revisions still require testing.

Review a still image before video production

For a product clip or character video, H3 Image can be evaluated for opening-frame candidates. Approve the subject, set and composition, then pass the selected image to a separate image-to-video model. This provides a still-image review before investing in video generation.

H3 Image delivers images; camera movement, action and duration belong to the downstream video task. Record requests and costs for the two stages separately. For the next stage, see the MiniMax H3 API guide.
Other delivery requirements need a different image workflow. H3 Image does not support masked local edits, transparent backgrounds and preview images. If precise masked replacement or transparent product assets are essential, make that a selection criterion from the beginning.
EvoLink users can compare controls and current prices in the model catalog. Give candidates the same sources and acceptance criteria, then record edit fidelity, completion time and total cost per accepted image. This connects model selection to the actual application deliverable.

Standard, Highspeed and open-source developments

Choose MiniMax-H3-Image or MiniMax-H3-Image-Highspeed through the model field. Both versions share the same parameters and limits, so teams can evaluate them with the same assets, canvas and output requirements. The standalone Context-IR service supports only the standard version.

Compare Highspeed and the standard version on completion time, acceptance rate and cost per accepted asset before choosing a production default. The Highspeed name alone does not establish a speed multiplier or quality ranking.

H3 Image is an open-source model for image generation and editing. The H3 team’s earlier development plan covered a model sharing H3’s foundation, with further post-training for text-to-image and general-purpose editing. For self-hosting, check the H3 Image-specific weights, repository and license. Development background

Self-hosting requires downloadable weights and a suitable model license; API access alone does not establish either. Check deployment conditions before choosing self-hosting, and confirm account access and charges separately when using an API.

Access and cost details for developers

MiniMax’s direct APIs accept text for generation, or text plus references for editing, and can return completed images individually. Use the request format and response handling of the channel you choose.

Confirm direct-provider account permissions and prices through current MiniMax channels. For EvoLink’s model ID, current pricing, playground and integration details, see the MiniMax H3 Image API page and its linked API documentation. Verify access for your account before starting a job; provider access and EvoLink access are separate.

For costs, the provider reports input and output token usage, including reference-image usage and text-token equivalents of prompt-enhancement charges; generation billing counts successful images only. For a product-image task, record reference inputs, prompt processing, generation output and additional requests needed to pass acceptance. This is the basis for cost per accepted asset. Token examples do not substitute for actual H3 Image unit prices, and usage from two different tasks does not establish a fixed editing-price multiplier.

Handle retries explicitly for MiniMax direct access. These provider endpoints are not idempotent: after a client timeout or disconnection, the server may continue generating and bill successful images. A new request creates new generation and charges. This affects how a creative tool implements “try again.” Result links are not guaranteed to last indefinitely; download approved images to durable storage. Usage and response documentation

Frequently asked questions

Is MiniMax H3 Image the same as H3 image-to-video?

No. H3 Image outputs still images. H3 image-to-video takes image input into a separate video-generation workflow.

Does 4K always mean 4096 pixels wide?

No. 4K specifies target pixel area; dimensions depend on the aspect ratio. At 16:9, the 4K output is 5472 × 3072.

Can H3 Image generate transparent PNGs or masked edits?

H3 Image does not support transparent backgrounds or masked local editing. PNG is an output format option, not transparency support.

How does Highspeed differ from the standard version?

Both versions share the same parameters and limits. Compare latency and image quality on the same brief before choosing a production default; do not assume a fixed speed multiplier or quality advantage.

Does Context-IR generate images?

No. It returns an enhanced prompt. For text-to-image, review it and disable enhancement before submitting generation. Editing always enables enhancement.

Is H3 Image already open source?

H3 Image is an open-source image model. For self-hosting, obtain the model-specific weights and check the repository’s release details, license and deployment conditions.
Direct-provider costs require H3 Image-specific token unit prices; example usage is not a quote. For EvoLink’s supported model ID, current rates, playground and integration steps, use the MiniMax H3 Image API page. Confirm account access there before submitting a task, and assess EvoLink pricing separately from MiniMax direct access.

Connect AI models through one API

Compare models and current pricing, then follow the API documentation to integrate your chosen model.