What is a Runway prompt for microcopy?

It is a structured brief that tells Runway how to produce copywriting output for ux writing. This starter version stresses first successful run with safe defaults 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 starter angle for microcopy?

Different angles solve different failures. Starter helps when ux writing need first successful run with safe defaults. 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 (Starter)

Runway · Copywriting · Starter

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: first successful run with safe defaults.

This Runway copywriting microcopy prompt helps you empty, error, success without rewriting instructions from scratch each time. Teams report saving 15–30 minutes per task when prompts include constraints up front. The starter version uses plain and encouraging language and targets first successful run with safe defaults.

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

Separates draft from critique so you can steal the structure later.
Repeats the hard constraint: human not cute.
The starter angle adds first successful run with safe defaults without extra fluff.
Forces an output contract: headings, examples, and a final version.
Centers empty, error, success so success is observable.

How to use it in Runway

Use plain and encouraging follow-ups only — mixing tones mid-thread confuses Runway models. Paste the prompt into Runway and replace bracketed details with your facts. Headlines, landing pages, and offer copy. Keep that context in the thread when you iterate. Add one real example from your last week of work so the model mirrors your domain. Save the winning variant for microcopy — teams with a short library ship faster.

Have Runway list assumptions about copywriting before drafting. Delete any you cannot defend. 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 Starter output. Runway models still need your facts for microcopy; they cannot invent metrics or brand rules. writers and conversion teams teams bookmark slug microcopy-starter when first successful run with safe defaults 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

Slug microcopy-starter: a writers and conversion teams-oriented copywriting brief. Headlines, landing pages, and offer copy. Pair it with one real asset from your portfolio before the second run.

Refresh quarterly: Runway models change. Keep constraints; update examples. Mark the page stale if human not cute no longer matches policy.

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

State the job (empty, error, success) in one line before any style talk.
Compare against other Runway angles on the same use case before you standardize.
Keep human not cute visible in the prompt, not only in your head.
Ship a draft, then tighten. Do not chase a perfect first token.
The Starter variant is for first successful run with safe defaults.

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 starter version stresses first successful run with safe defaults 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 starter angle for microcopy?: Different angles solve different failures. Starter helps when ux writing need first successful run with safe defaults. 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.