Higgsfield Joins Video Lab — Cinematic Camera Moves Runway Can't Quite Do

May 18, 2026

Video Lab now talks to two providers: the existing Runway path, and Higgsfield. You pick which one runs each clip — Runway when you want broad style coverage and the model menu you already know, Higgsfield when you want one of those slow cinematic camera arcs around a portrait or a sweeping pan across a landscape that Runway has to be coaxed into via prompt language. Same video_lab tool, new provider knob.

What you can do

• Pick the provider per call. provider: "auto" keeps today's behaviour (Runway). provider: "runway" pins Runway. provider: "higgsfield" routes to Higgsfield for cinematic image-to-video.
• Four Higgsfield models, each with a job:
  • DOP Lite — fastest tier. Use it for previews and A/B-testing camera moves before committing.
  • DOP Turbo — middle tier. Faster than Standard, still high fidelity. Default for working drafts.
  • DOP Standard — slowest, highest fidelity. Reserve it for the keeper / hero shot, not for every iteration.
  • Kling 2.1 Pro — cinematic camera arcs across landscapes and product shots. Length is locked to 5 or 10 seconds (the model's hard rule).
• A "when to pick which provider" playbook lives in the agent (video_provider_routing). It walks Alfred through IP-safe prompt translation (e.g. how to ask for "Matrix bullet-time in a Ghibli look" without naming the franchises), and a worked example that generates a still on Image Lab and animates it on Higgsfield DOP.
• Honest failure surfacing. If Higgsfield refuses or the render fails, you see the reason plus retry suggestions — Alfrada never silently swaps to Runway behind your back. You decide whether to rerun on the other provider.

Where this shows up

• You want a slow orbit around a portrait with cinematic depth-of-field. Before, you'd nudge Runway with prompt language and hope. Now you upload the still, pick Higgsfield, choose DOP Standard, and the camera move comes out native.
• You want a sweeping camera pan across a landscape. Pin Higgsfield + Kling 2.1 Pro, set duration to 5 or 10 seconds, done. The model is built for those arcs.
• You want a Matrix-style bullet-dodge in a Ghibli look. The new routing playbook walks Alfred through (a) translating "Matrix bullet-time in Ghibli" into descriptive visual language without naming either franchise, (b) generating a character still on Image Lab, (c) animating it on Higgsfield DOP. You get the shot without fighting moderation.
• A render fails. Alfrada surfaces the specific reason — model busy, content blocked, capability not supported on Higgsfield — and offers retry suggestions. You stay in control of the next move.

Try it

• "Animate this portrait with a slow orbit, cinematic golden hour, 6 seconds — use Higgsfield DOP."
• "Give me a cinematic camera pan across this landscape, 10 seconds, on Higgsfield Kling 2.1 Pro."
• "Create a 6-second clip from this character still: slow-motion bullet-dodge, hand-painted anime look, on Higgsfield."
• "Run a quick draft on Higgsfield DOP Lite first, then re-render the keeper on DOP Standard."
• "Higgsfield DOP doesn't support text-to-video — what should I use instead?" — Alfred reads the capability map and tells you to drop input_image or stay on Runway for pure text-to-video.

Heads up

• Higgsfield is image-to-video only, for now. Pure text-to-video and prompt-enhancement still go through Runway. If you ask for provider: "higgsfield" on a create (text-to-video) call, Image Lab returns a clear capability error with retry suggestions — no silent fallback.
• First+last keyframe morphs are still Runway-only. Use Runway's veo3.1, veo3.1_fast, seedance2, or gen3a_turbo when you need to lock both ends of a clip.
• Kling 2.1 Pro durations snap to 5 or 10 seconds. The model's API rejects anything else; the runtime quietly snaps your value so the call doesn't fail.
• Set up the API keys once. Add HF_KEY (or HIGGSFIELD_API_KEY) in the API environment as a single "<api_key>:<api_secret>" string, or split into HF_API_KEY + HF_API_SECRET. Runway keeps working unchanged when these are unset.
• Higgsfield needs your reference image hosted at a public URL. Alfrada handles this for you: it temporarily uploads the still to a public GitHub repo, hands the raw URL to Higgsfield, and deletes the upload as soon as the render finishes (success, failure, NSFW, cancel — all paths clean up). You configure it once with HIGGSFIELD_GITHUB_TOKEN, HIGGSFIELD_GITHUB_REPO (must be public), and optionally HIGGSFIELD_GITHUB_BRANCH / HIGGSFIELD_GITHUB_PATH_PREFIX.
• Some Higgsfield models on the public docs aren't available on this account. A handful of variants Higgsfield lists publicly (DOP Preview, Seedance v1 Pro) aren't reachable on the current plan; the runtime rejects those slugs with a clear capability error rather than failing mid-render. Re-add them once the plan exposes them.
• Sora 2 Pro, Veo 3.1, Kling 2.6 Pro, Soul T2V, and DOP motion presets are documented future targets. They're referenced in the routing playbook but not yet wired to live submit endpoints. Coming in a follow-up release.