What is a Runway prompt for microcopy?

It is a structured brief that tells Runway how to produce copywriting output for ux writing. This workflow version stresses step order, checkpoints, and handoffs and keeps "human not cute" in the instructions.

How do I customize this Runway copywriting prompt?

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

Why use the workflow angle for microcopy?

Different angles solve different failures. Workflow helps when ux writing 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 copywriting: Microcopy (Workflow)

Runway · Copywriting · Workflow

Duration: 4–8 seconds. Shot: gentle handheld.
Action: empty, error, success. Keep motion physically plausible.
Look: Headlines, landing pages, and offer copy. Lighting stays motivated. Constraint: human not cute.
Continuity: same wardrobe, same time of day, no sudden prop changes.
Audio intent (if any): quiet ambience.
Audience: ux writing. Focus: step order, checkpoints, and handoffs.

A strong Runway copywriting microcopy prompt names the job, audience, and finish line. This page does that for ux writing. Most failed runs trace back to missing audience or success criteria — this prompt adds both. The workflow version uses operational language and targets step order, checkpoints, and handoffs.

When to use this prompt

For Runway models, copywriting prompts fail when they mix strategy and execution. This microcopy brief separates the job so you can iterate once, not ten times. Pair it with a real sample from your portfolio for best results.

Why this prompt works

Asks for a self-check pass, which cuts hallucinated details.
Repeats the hard constraint: human not cute.
Locks the audience (ux writing) before style so tone stays honest.
Centers empty, error, success so success is observable.
Keeps copywriting vocabulary specific instead of buzzwords.

How to use it in Runway

When ux writing review output, they should see step order, checkpoints, and handoffs without hunting for it. Paste the prompt into Runway and replace bracketed details with your facts. If the first answer is vague, reply with the constraint again: human not cute. Save the winning variant for microcopy — teams with a short library ship faster. Headlines, landing pages, and offer copy. Keep that context in the thread when you iterate.

Swap the audience once. If the microcopy piece still works, the core is solid. For microcopy in copywriting, the failure mode is usually no example. This prompt blocks that by design — especially "human not cute". Expect two minutes customizing and two minutes editing for Workflow output. Runway models still need your facts for microcopy; they cannot invent metrics or brand rules. writers and conversion teams teams bookmark slug microcopy-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 (ux writing, offer, timeline).
Confirm the constraint is still visible: human not cute.
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 microcopy shot, motivated light, single camera move, subject action matches "empty, error, success", no wardrobe changes mid-clip.

Common mistakes

Asking for microcopy plus three other jobs in one message.
Pasting confidential data instead of redacted placeholders.
Accepting the first draft without checking empty, error, success.

Expert notes

Runway users working on microcopy in copywriting should treat "human not cute" as non-negotiable. Headlines, landing pages, and offer copy. When ux writing run the Workflow variant, they usually care about step order, checkpoints, and handoffs more than length.

If video output feels generic, re-paste human not cute 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 microcopy 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

Ship a draft, then tighten. Do not chase a perfect first token.
The Workflow variant is for step order, checkpoints, and handoffs.
Document what changed when you customized slug microcopy-workflow.
If video output drifts, re-anchor with human not cute.
Runway improves when you paste a real snippet or reference still.

FAQ

What is a Runway prompt for microcopy?: It is a structured brief that tells Runway how to produce copywriting output for ux writing. This workflow version stresses step order, checkpoints, and handoffs and keeps "human not cute" in the instructions.
How do I customize this Runway copywriting prompt?: Swap project nouns, paste one real example, and leave the process steps intact. The constraint "human not cute" should stay unless your brief truly changed.
Why use the workflow angle for microcopy?: Different angles solve different failures. Workflow helps when ux writing 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.