Viral Studio (under Produce → Viral Studio, /viral) packages the effects filling your feed — clone yourself, invisible-cut teleports, text behind you, sky swaps, beat-synced zooms, AI object morphs — as guided recipes. Each recipe teaches the shoot, collects your takes, and runs the whole edit pipeline for you. No keyframes, no tutorials.
Gating: Creator and up (viral_studio entitlement). Recipe cards carry an extra plan badge when they also use the Pro compositing suite (vfx), Agency AI matting (vfx_ai) or tracking (vfx_tracking). AI-morph recipes spend credits.
Recipes are cards grouped by family — Clone, Transition, AI Magic, Rhythm, Tracking — each with:
  • a hover sample of the finished effect (operator-curated),
  • a difficulty rating (⭐ one take, ⭐⭐⭐ trickier shoots),
  • a 🔥 Viral / ↗ Rising badge (operator-curated trending flags),
  • a plan badge when the recipe needs a higher tier than yours.

​
The 4-step wizard

1

Watch

See the finished effect, the hook, and exactly what you’ll film.
2

Shoot

Take-by-take shoot cards: tripod flag, instructions, timing hints, and pro tips (“lock exposure”, “don’t cross the centre line”). Tap Open Shoot Mode for a phone-friendly fullscreen checklist with a countdown timer and beep cues — prop the phone up and film hands-free.
3

Drop your takes

Typed inputs, one card each: video takes and images open the full media picker; mask inputs open the mask editor over your take’s poster (“draw around where your clone will stand”); captions are plain text; morph transformations are one-tap chips.
4

Make it

One tracked job runs the whole pipeline (watch it in the Activity dock — the steps narrate the recipe: “Compositing your clone…”). The result plays inline with download, popup player, Regenerate, and a one-click VEditor hand-off.
Every result lands in your Library with a “Made with …” provenance badge (gen_meta.recipe_key), so you always know which recipe produced what.

​
The launch recipes

Operators curate this list live (rename, re-badge, publish/hide, edit shoot cards and even the step pipelines) from the ops console — no deploy.

​
Credits (Pop Morph)

Generative morphs run on hosted video models and spend the same monthly credits budget as SonicBliss/ClipForge (≈60 credits per morph; 1 credit = $0.01). Everything else in Viral Studio is engine-rendered and costs no credits.

​
Under the hood (why results are editable)

Recipes don’t produce black boxes: every step is a normal MediaBliss job — the same VFX compositing, EDL rendering, chain ops, and ClipForge generation you can drive by hand. The final asset is a regular Library video, so Open in VEditor gives you the full editor for polish, and the “post-ready” chains (tighten / reframe / auto-zoom) apply as usual.

​
Troubleshooting

  • “Viral Studio needs the Creator plan” — upgrade in Settings → Billing; recipe cards with a plan badge additionally need that tier.
  • A matting recipe fails with no_provider_key — the instance operator hasn’t configured the AI-matting provider (ops console → Credentials).
  • Pop Morph fails or is locked — check your credits balance (Settings → Billing) and that an fx model is enabled in ops → AI Models.
  • The clone looks wrong — nine times out of ten the camera moved between takes. Re-shoot on a tripod with locked exposure; keep each “you” on their own side of the mask.

​
Over the API

Routes appear in the API Reference tab under the viral tag:
  • GET /viral/recipes — the published catalog (+ per-recipe locked state for your plan).
  • POST /viral/recipes/{key}/run → 202 {job_id} — body {inputs: {…}, project_id?}; input values are Library asset ids (take/image/media), mask docs ({shapes:[{type:"polygon"|"ellipse", …, feather}]}, coords normalized 0–1), text, or a choice value. Follow progress on GET /jobs/{id}/events (SSE).
  • GET /viral/runs/{job_id} — run state + output_asset once succeeded.
Operators: GET/POST/PUT/DELETE /ops/viral/recipes[/{key}] (audited), sample media via POST /ops/vfx-samples/viral_<key>/upload.