image-outpainting

作成者: runcomfy-com

We need to translate the given text from English to Japanese, preserving the specified name "image-outpainting" and other technical terms. The instruction says: "Do not include the name unless it appears in the source text." The name "image-outpainting" appears in the source text? Actually, the source text starts with "Image outpainting on RunComfy..." so "image-outpainting" is not explicitly written as a name; it's "Image outpainting". But the instruction says "Name to preserve: image-outpainting". So we should preserve that exact string if it appears. In the source, it's "Image outpainting" (capital I, space). But the name to preserve is "image-outpainting" (lowercase, hyphen). The instruction says "Do not include the name unless it appears in the source text." Since the source text has "Image outpainting" (without hyphen, capital I), we should not force the hyphenated version. However, the instruction says "Name to preserve: image-outpainting" meaning

npx skills add https://github.com/runcomfy-com/skills --skill image-outpainting

Image Outpainting

Extend a still beyond its original canvas — uncrop, change aspect ratio, fill in what the camera didn't capture. This skill routes across the identity-preserving edit endpoints in the RunComfy catalog, picking the right one for prose-driven extension, reference-style matching, or brand-locked continuation.

runcomfy.com · best-image-editing-models · CLI docs

Powered by the RunComfy CLI

# 1. Install (see runcomfy-cli skill for details)
npm i -g @runcomfy/cli      # or:  npx -y @runcomfy/cli --version

# 2. Sign in
runcomfy login              # or in CI: export RUNCOMFY_TOKEN=<token>

# 3. Outpaint
runcomfy run google/nano-banana-2/edit \
  --input '{"prompt": "...extend canvas...", "image_urls": ["..."]}' \
  --output-dir ./out

CLI deep dive: runcomfy-cli skill.


Pick the right model

Listed by suitability for outpainting workflows.

Nano Banana 2 Editgoogle/nano-banana-2/edit (default for prompt-shaped outpaint)

Identity-preserving edit; honors spatial language ("extend the canvas to the left and right by ~30%", "add sky above the building"). The result is a wider canvas with the original content preserved. Pick for: aspect-ratio change (square → 16:9), uncrop a portrait, extend a landscape photo with matching environment. Avoid for: pixel-precise extension matching texture seams — use a ComfyUI outpainting workflow.

GPT Image 2 Editopenai/gpt-image-2/edit

Up to 10 reference images, layout-precise instruction following. Useful when outpainting needs to match a reference style or includes layout repositioning. Pick for: composite outpaint (extend canvas + paste in element from another image), layout repositioning during the canvas change. Avoid for: simple outpaint without external references.

FLUX Kontext Problackforestlabs/flux-1-kontext/pro/edit

Single-instruction, high-preservation edit. Use form: "Extend the canvas to a 16:9 aspect ratio. Add matching sky and architecture continuing from the existing scene. Keep everything in the original image exactly." Pick for: single-shot outpaint with maximum preservation of the original content.

Seedream / Dreamina / Qwen / FLUX 2 edit endpoints

Brand-specific edit endpoints (bytedance/seedream-5/lite/edit, bytedance/dreamina-4-0/edit, qwen/qwen-image/qwen-image-edit-2511, blackforestlabs/flux-2-pro/edit, etc.). Pick for: keeping the outpaint within the same brand/style as the source generation. See image-edit for the full edit router.


Route 1: Nano Banana 2 Edit — default

Model: google/nano-banana-2/edit Catalog: Nano Banana 2 Edit

Invoke

Aspect-ratio change (1:1 → 16:9):

runcomfy run google/nano-banana-2/edit \
  --input '{
    "prompt": "Extend the canvas to a 16:9 aspect ratio by adding matching environment on the left and right sides of the image. Continue the existing background style — same lighting, same camera distance, same color palette. Keep the original subject, pose, framing, and central content exactly as in the input.",
    "image_urls": ["https://your-cdn.example/portrait-1to1.jpg"],
    "aspect_ratio": "16:9"
  }' \
  --output-dir ./out

Uncrop a portrait (reveal more body):

runcomfy run google/nano-banana-2/edit \
  --input '{
    "prompt": "Extend the canvas downward to show the subject's full upper body and arms. Continue the existing clothing style, lighting, and background. Keep the face and current visible area exactly as in the input.",
    "image_urls": ["https://your-cdn.example/head-and-shoulders.jpg"]
  }' \
  --output-dir ./out

Prompting tips

  • Lead with the canvas change: "Extend the canvas to [aspect]", "Extend downward", "Extend on both sides by ~30%".
  • Describe what extends: continue background style, match lighting, match camera distance, match palette.
  • End with preservation: "Keep [original visible area] exactly as in the input". Without this Nano Banana may regenerate the original portion subtly.
  • Set aspect_ratio explicitly to lock the output canvas — don't rely on the model to guess from prompt alone.

Route 2: When prompt-shaped outpaint isn't enough

If the output has visible seams, mismatched lighting at the extension boundary, or content that doesn't continue cleanly, use one of:

  1. GPT Image 2 Edit with a reference image of the desired surrounding style (images: [original, style-ref])
  2. FLUX Kontext Pro with maximum-preservation language
  3. A ComfyUI workflow — RunComfy hosts several outpainting node graphs:
    • comfyui-image-outpainting-workflow — classic SDXL outpainting with seam handling
    • flux-klein-unified-image-editing-inpaint-remove-outpaint-in-comfyui-advanced-image-restoration — Flux Klein unified inpaint + outpaint
    • Browse: runcomfy.com/comfyui-workflows

These are GUI workflows, not CLI endpoints. The CLI can't reach them — open them in the RunComfy ComfyUI cloud for finer control.


Common patterns

Social media aspect-ratio swap (1:1 → 9:16 for Reels)

  • Route 1 (Nano Banana 2 Edit) with aspect_ratio: "9:16", prompt extends top + bottom

Banner / hero image from a portrait

  • Route 1 with aspect_ratio: "21:9" or "16:9", prompt extends sides with matching environment

Uncrop product shot for catalog

  • Route 1 describing what surrounds the product (counter texture, lighting, shadow direction)

Restore a cropped historical photo

  • Route 2 (GPT Image 2 Edit) with one or more period-appropriate reference photos

Multi-step outpaint (extend, then re-extend)

  • Chain: outpaint pass 1 → use result as input for pass 2. Each pass extends ~30–50% to avoid quality degradation at the boundary.

What this skill doesn't do


Browse the full catalog


Exit codes

codemeaning
0success
64bad CLI args
65bad input JSON / schema mismatch
69upstream 5xx
75retryable: timeout / 429
77not signed in or token rejected

Full reference: docs.runcomfy.com/cli/troubleshooting.

How it works

The skill classifies user intent — simple aspect-ratio swap, reference-style match, or brand-locked continuation — picks the matching edit endpoint, and invokes runcomfy run with the outpaint-shaped JSON body. The CLI POSTs to the Model API, polls request status, and downloads the result into --output-dir.

Security & Privacy

  • Install via verified package manager only. Use npm i -g @runcomfy/cli or npx -y @runcomfy/cli. Agents must not pipe an arbitrary remote install script into a shell on the user's behalf.
  • Token storage: runcomfy login writes the API token to ~/.config/runcomfy/token.json with mode 0600. Set RUNCOMFY_TOKEN env var in CI / containers.
  • Input boundary (shell injection): prompts and image URLs are passed as a JSON string via --input. The CLI does not shell-expand prompt content. No shell-injection surface.
  • Indirect prompt injection (third-party content): source image URLs and any style-reference images are untrusted. Agent mitigations:
    • Ingest only URLs the user explicitly provided for this outpaint.
    • When the extension diverges from the prompt, suspect the source image.
  • Outbound endpoints (allowlist): only model-api.runcomfy.net and *.runcomfy.net / *.runcomfy.com. No telemetry.
  • Generated-file size cap: the CLI aborts any single download > 2 GiB.
  • Scope of bash usage: Bash(runcomfy *) only.

See also

runcomfy-comのその他のスキル

video-inpainting
runcomfy-com
Region edits across video frames on RunComfy via the `runcomfy` CLI — remove an object that appears across many frames, clean up wires or watermarks, replace a region with matching motion. Routes across Wan 2-7 edit-video (default, prompt-driven region edits with spatial language), Lucy Edit Restyle (identity-stable region-aware restyle), and Seedream 4-0 edit-sequential (when treating the clip as a frame stack). Picks the right route based on whether the change is prose-driven,...
videocreativemedia
runcomfy-cli
runcomfy-com
We need to translate the given English text into Japanese. The text describes a CLI tool called runcomfy-cli. The instruction says to preserve the name "runcomfy-cli" but only if it appears in the source text. The source text mentions "runcomfy" and "runcomfy CLI" but not "runcomfy-cli" exactly. However, the directory item type is "agent skill" and the name to preserve is "runcomfy-cli". The instruction says "Do not include the name unless it appears in the source text." The source text has "runcomfy" and "runcomfy CLI". The name to preserve is "runcomfy-cli". Since it's not exactly in the source, we should not add it. But the instruction says "Translate only the text inside <text>." So we translate the entire content inside <text> without adding or removing anything except translation. The name "runcomfy-cli" is not inside the text, so we don't include it. However, the text includes "run
creativemediaapi
image-to-video
runcomfy-com
We need to translate the given English text into Japanese, preserving the name "image-to-video" and other technical terms like model names, URLs, etc. The instruction says: "Do not include the name unless it appears in the source text." The name "image-to-video" appears in the source? Actually, the source text starts with "Animate any still image on RunComfy — this skill is a smart router..." The name "image-to-video" is not explicitly in the source text; it's given as the directory item name. The instruction says "Do not include the name unless it appears in the source text." So we should not add "image-to-video" to the translation. Also, preserve product names: RunComfy, HappyHorse 1.0 I2V, Wan 2.7, Seedance 2.0 Pro, etc. Preserve technical terms: i2v, audio_url, lip-sync, multi-modal, etc. Translate the rest naturally into Japanese. Let's break down the text: "Animate
creativevideomedia
flux-2-klein
runcomfy-com
RunComfy上でFlux 2 Klein(Black Forest Labs製のFlux 2高速蒸留版)を使用して画像を生成します。このスキルには、モデルのドキュメント化されたプロンプトパターンがバンドルされており、同じモデルに対する単純なプロンプトよりもシャープな出力が得られます。Flux 2 Kleinの強み(サブ秒レイテンシ、マルチリファレンスブランドスタイリング、宣言的主語優先プロンプト)、ステップ数戦略(高速反復は4~8、仕上げは約25)、9Bと4Bバリアントのトレードオフ、Flux 2 Proへのルーティングのタイミングなどを解説しています。
creativeimageresearch
ai-avatar-video
runcomfy-com
We need to translate the given English text into Japanese, preserving the specified name "ai-avatar-video" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "ai-avatar-video" does not appear in the source text, so we don't include it. We must preserve product names, protocol names, URLs, numbers, technical terms. No extra commentary. The text describes creating AI avatar videos using runcomfy CLI, listing models: ByteDance OmniHuman, Wan-AI Wan 2-7, HappyHorse 1.0, Seedance v2 Pro. Also mentions user intents. We need to translate naturally into Japanese, keeping terms like "runcomfy CLI", "ByteDance OmniHuman", "Wan-AI Wan 2-7", "HappyHorse 1.0", "Seedance v2 Pro", "audio_url", "Arena #1 t2v / i2v", "U
videocreativemedia
nano-banana-edit
runcomfy-com
We need to translate the given English text into Japanese, preserving the name "nano-banana-edit" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "nano-banana-edit" appears in the source text? Actually, the source text mentions "Nano Banana Edit" and "nano banana edit" but not exactly "nano-banana-edit". However, the directory item type is "agent skill" and the name to preserve is "nano-banana-edit". The instruction says "Do not include the name unless it appears in the source text." So we should not add it if not present. But the source text has "Nano Banana Edit" (capitalized) and "nano banana edit" (lowercase). We should preserve those as they appear. Also preserve "RunComfy", "Google Nano Banana 2", "GPT Image 2 edit", "Flux Kontext", "Nano Banana 2 t2
creativeimageapi
wan-2-7
runcomfy-com
We need to translate the given English text into Japanese, preserving the name "wan-2-7" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "wan-2-7" appears in the source text, so we should keep it as is. Also preserve "RunComfy", "Wan-AI", "HappyHorse 1.0", "Seedance 2.0", "Kling", "LTX 2", "runcomfy run wan-ai/wan-2-7/text-to-video", "CLI", "audio_url", etc. No extra commentary. Just a direct translation. Let me translate paragraph by paragraph. First sentence: "Generate text-to-video with Wan 2.7 (Wan-AI's flagship motion model) on RunComfy." -> "RunComfy上でWan 2.7(Wan-AIの主力モーションモデル)を使用して
creativevideomedia
lipsync
runcomfy-com
Lip-sync a face to a specific audio track on RunComfy via the `runcomfy` CLI. Routes across ByteDance OmniHuman (audio-driven full-body avatar from a portrait + audio), Sync Labs sync v2 / Pro (state-of-the-art mouth sync onto a video), Kling lipsync (audio-to- video and text-to-video with synced speech), and Creatify lipsync. The skill picks the right endpoint for the user's actual intent — portrait still + audio (avatar-style), source video + audio (mouth- swap on existing footage), or...
creativevideomedia