Awesome Seedance 2 Prompts: Curated Open-Source Prompt Library

Seedance 2 rewards prompts that read like a single line in a shot list, and punishes prompts that read like a paragraph of mood. Most public prompt collections still optimize for stylistic adjectives — "cinematic, hyper-realistic, beautiful" — which waste the model's prompt budget on words it does not act on. The awesome-seedance-2-prompt repo exists to collect prompts that have actually shipped to production, organized by what the shot needs to do, not by what it looks like in isolation.

Each entry in the repo answers a specific question a creator already has: "How do I get a label-locked hero spin?" "How do I animate a still without identity drift?" "How do I extend past the model's native length cap without a visible cut?" The recipes are short on flourish and long on camera grammar, lighting cues, and the one or two motion verbs Seedance 2 reliably executes. Copy any recipe, paste it into a Seedance 2 video node on the Martini canvas, and you are within one or two iterations of the result the recipe promises.

The library is intentionally model-specific. A prompt that performs on Kling 3 Avatar will often underperform on Seedance 2 Pro, and vice versa. Treating Seedance 2 as its own grammar — rather than a generic "video model" — is the single biggest unlock once teams move past their first week with the model.

The repo is split into folders that map to shot intent. Hero spins, product reveals, and label-locked motion live under product/. Image-to-video recipes — push-ins, parallax, orbits, drifts — live under image-to-video/. Character close-ups (where Seedance 2 holds identity well for a few seconds before lip-sync limits kick in) live under character/. Environmental establishes, weather, and crowd shots live under environment/. Continuation seeds — prompts written specifically to be the second clip in a chain, stitched off the last frame of the first clip — live under continuation/.

Within each folder, recipes are named by the camera move first, then the lighting condition, then the variant of Seedance 2 that produced the cleanest take in QA. A filename like product/orbit-soft-rim-pro.md tells you the shot is an orbit, lit with a soft rim, and benchmarked against Seedance 2 Pro. The body of every recipe contains the prompt text, the recommended Seedance 2 variant (Pro / Lite / Omni), the reference image you should wire upstream of the node, and a notes section calling out edge cases the prompt does not handle.

Recipes that did not survive QA — prompts that produced visible identity drift, rubbery transparency, or motion that compressed multiple actions into a half-second blur — are tracked in a graveyard/ folder with a one-line note about why they failed. This is more useful than deleting them: it tells future contributors which prompt shapes Seedance 2 punishes, so they can avoid re-discovering the same dead ends.

The recipes are designed to drop straight into a Seedance 2 video node on Martini. The canvas pattern is image-first: generate or upload the still you want, wire it into the Seedance 2 node, paste the recipe, and iterate the prompt while the image stays pinned. The version tray on the canvas keeps every take, which means you can A/B four recipes from the repo against the same reference image without losing any of them.

For multi-shot work, duplicate the Seedance 2 node and re-wire each duplicate to the same character or product image. Paste a different recipe into each duplicate — different camera moves, different lighting cues, different micro-actions. Drop an NLE export node downstream of all of them and the canvas assembles the takes in the order you wire them. This is the workflow the repo is optimized for: many recipes, one anchor image, one canvas, one export.

When you find a recipe that consistently produces the result you want, fork the repo and save the recipe alongside the seed and the reference image hash in a private prompt pack for your team. The public repo stays curated and small; private forks let you build a brand-specific dialect of Seedance 2 prompts that ship faster than re-iterating from scratch on every campaign.

Slow orbit hero spin (label-locked) — the signature ecommerce hero shot. The repo's recipe wires a brand-approved product still upstream and prompts only for camera and light: "Slow 360-degree orbit around the referenced product, 8 seconds, even rotation, soft front-key plus rim light, shallow depth of field, label remains crisp and centered, subtle floor reflection, locked focal length, no zoom, no cuts." Pair with Seedance 2 Pro for finished work, Lite for variant sweeps.

Slow push-in (subtle drift) — the default cinematic motion for any still. "Slow camera push-in toward subject in referenced image, 5 seconds, gentle parallax in foreground vs background, locked subject, subtle breathing, no rotation, no zoom-out, ends 1.2x closer than start." Works on portraits, products, and environments. Default to Seedance 2 Pro; switch to Kling 3 only if the image has heavy depth-of-field already baked in.

Character identity-locked turn — the recipe that justifies running Seedance 2 Omni instead of Pro. Wire the same character reference image into the Omni node and prompt: "Subject begins still facing camera, slow head turn 30 degrees to camera left, micro smile at the end, locked focal length, soft window light from frame right, 4 seconds." Repeat across multiple Omni nodes with different head turns and you have a sequence that holds identity without fine-tuning.

Open a pull request against awesome-seedance-2-prompt with a recipe you have tested in production. The repo expects four things in the PR body: the prompt text, the Seedance 2 variant you ran it on (Pro / Lite / Omni), a sample output (any video clip is fine — Twitter post, internal upload, embedded GIF), and a short note on the edge cases the prompt does not handle. PRs without a sample output are not merged, because the repo's value is exactly that every recipe has actually shipped.

Recipes that fail QA are not rejected — they are moved to graveyard/ with a note. This keeps the repo honest about which prompt shapes Seedance 2 actually rewards. If you discover a recipe that worked on Seedance 1 but no longer works on Seedance 2 (this happens often with multi-action prompts), file a graveyard PR and link the new replacement.

The repo is paired with the Martini canvas but not gated to it. You can copy any recipe into ByteDance's direct API, into BytePlus, or into any third-party tool that exposes Seedance 2. The recipes are written in plain English and do not depend on Martini-specific node syntax — only the multi-node fan-out workflow assumes a canvas.