Skip to main content
POST
Picks one of U1–U4 from the parent grid (grid_image_url) to produce a single image. This is implemented by cropping from the existing 4 images, composed locally and usually returns instantly.

Parameters

Request examples

By index:
Pass a button directly:

Response

Submission returns a new task_id, usually SUCCESS within milliseconds. On SUCCESS, image_urls has a single element (one image), and buttons contains follow-up actions (zoom / inpaint / pan / variation, etc.).

Notes

  • The parent task must be in SUCCESS state, otherwise it returns 400 (task is not in SUCCESS state).
  • index must be 14; out of range returns 400. custom_id and index are mutually exclusive; if both are passed, custom_id wins.
  • The resource-consuming step is imagine; upscale only picks from existing images and rarely fails.
  • The single image after upscale can continue with Zoom / Inpaint / Variation.

HD upscale (HD enlargement, outputs a single 2x image)

A regular upscale is composed locally—it crops one of the 4 images already in the parent task and returns instantly. If you later want to perform fine-grained operations such as zoom / inpaint on a single image, we recommend using HD upscale instead: it performs a real enlargement, outputs a single 2x HD image, takes about 60–120s to complete, and the resulting single image more reliably supports subsequent zoom / inpaint. HD upscale specifies the enlargement command via custom_id; different imagine versions correspond to different commands:

HD upscale example

Once complete, you get a true single 2x HD image task, which you can continue to zoom / inpaint.

Comparison with regular upscale

⚠️ pan is still unavailable

Even for the HD single image produced by HD upscale, pan operations are still rejected (returns “invalid image generation request”)—this is a Midjourney limitation on the pan operation itself, unrelated to the enlargement method. See Pan for details.