What is a Runway prompt for exploded view?

It is a structured brief that tells Runway how to produce product photography output for product design. This workflow version stresses step order, checkpoints, and handoffs and keeps "accurate proportions" in the instructions.

How do I customize this Runway product photography prompt?

Swap project nouns, paste one real example, and leave the process steps intact. The constraint "accurate proportions" should stay unless your brief truly changed.

Why use the workflow angle for exploded view?

Different angles solve different failures. Workflow helps when product design need step order, checkpoints, and handoffs. It is not longer for its own sake — each line has a job.

Is this Runway prompt updated for 2026?

Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Runway models. Always verify facts before client delivery.

Runway prompt for product photography: Exploded View (Workflow)

Runway · Product Photography · Workflow

Duration: 4–8 seconds. Shot: slow push-in.
Action: show parts relationship. Keep motion physically plausible.
Look: Pack shots, lifestyle scenes, and catalog consistency. Lighting stays motivated. Constraint: accurate proportions.
Continuity: same wardrobe, same time of day, no sudden prop changes.
Audio intent (if any): no score.
Audience: product design. Focus: step order, checkpoints, and handoffs.

Looking for a Runway prompt for exploded view? Start here — the workflow angle focuses on step order, checkpoints, and handoffs. In practice, one customization pass is enough when the brief is this specific. The workflow version uses operational language and targets step order, checkpoints, and handoffs.

When to use this prompt

For Runway models, product photography prompts fail when they mix strategy and execution. This exploded view brief separates the job so you can iterate once, not ten times. Swap only nouns when adapting — keep the process intact.

Why this prompt works

Asks for a self-check pass, which cuts hallucinated details.
Names a clear job so Runway does not wander into generic advice.
The workflow angle adds step order, checkpoints, and handoffs without extra fluff.
Forces an output contract: headings, examples, and a final version.
Separates draft from critique so you can steal the structure later.

How to use it in Runway

Use operational follow-ups only — mixing tones mid-thread confuses Runway models. Generate two seeds or takes, then pick the clearer silhouette or motion. Pack shots, lifestyle scenes, and catalog consistency. Keep that context in the thread when you iterate. Save the winning variant for exploded view — teams with a short library ship faster. Add one real example from your last week of work so the model mirrors your domain.

Ask for a checklist product design would use. Then grade the draft against show parts relationship. For exploded view in product photography, the failure mode is usually too many jobs in one ask. This prompt blocks that by design — especially "accurate proportions". Expect two minutes customizing and two minutes editing for Workflow output. Runway models still need your facts for exploded view; they cannot invent metrics or brand rules. brand and ecommerce teams teams bookmark slug exploded-view-workflow when step order, checkpoints, and handoffs matters.

Step-by-step

Open Runway and paste the prompt block unchanged.
Replace placeholders with your project facts (product design, offer, timeline).
Confirm the constraint is still visible: accurate proportions.
If output is vague, ask Runway to restate assumptions as questions first.
Reply with one fix list, then regenerate the final version only.

Example output

Example clip brief: 6s exploded view shot, motivated light, single camera move, subject action matches "show parts relationship", no wardrobe changes mid-clip.

Common mistakes

Accepting the first draft without checking show parts relationship.
Pasting confidential data instead of redacted placeholders.
Ignoring shot continuity notes.

Expert notes

Runway users working on exploded view in product photography should treat "accurate proportions" as non-negotiable. Pack shots, lifestyle scenes, and catalog consistency. When product design run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.

If video output feels generic, re-paste accurate proportions as the first follow-up message — do not rewrite the whole prompt.

Comparison / variations

Approach	When	Tweak
Bare request	You only need a spark	Write a exploded view piece.
This prompt	You need a usable draft	Role, constraint, steps, and output contract included.
Plus examples	Voice must match yours	Paste 120 words of your writing or a still you like, then rerun in Runway.

Key takeaways

The Workflow variant is for step order, checkpoints, and handoffs.
product design should recognize themselves in the first paragraph.
State the job (show parts relationship) in one line before any style talk.
If video output drifts, re-anchor with accurate proportions.
Ship a draft, then tighten. Do not chase a perfect first token.

FAQ

What is a Runway prompt for exploded view?: It is a structured brief that tells Runway how to produce product photography output for product design. This workflow version stresses step order, checkpoints, and handoffs and keeps "accurate proportions" in the instructions.
How do I customize this Runway product photography prompt?: Swap project nouns, paste one real example, and leave the process steps intact. The constraint "accurate proportions" should stay unless your brief truly changed.
Why use the workflow angle for exploded view?: Different angles solve different failures. Workflow helps when product design need step order, checkpoints, and handoffs. It is not longer for its own sake — each line has a job.
Is this Runway prompt updated for 2026?: Yes. Pages follow our SEO Bible, refresh on a rolling schedule, and include current best practices for Runway models. Always verify facts before client delivery.