Engines & hardware

Your engines. Your accounts. Your call.

SP Studio routes each job to an engine that’s strong at it, behind one provider interface, so any engine can be swapped without touching your project. On set you choose quality and run location; engine names live in Settings and the shot log.

Engine policy

Bring your own keys

Connect your own provider accounts. Usage is billed by each provider directly to you; SeriousPixel never resells model access. Keys live in the OS keychain.

Open weights: free, never bundled

Open-weights engines are downloaded from their publishers at your request, under your own acceptance of their license. SP Studio records the license you accepted.

Video engines must do audio

The default registry lists only video engines with native synchronized audio, so scratch dialogue and room tone arrive with every take.

License-aware routing

Every registry entry carries license flags. SP Studio checks your organization profile — country, revenue, headcount, use — and warns or blocks before a job runs.

Constraints first

Require Local only, a cost cap, a region or no-training API settings per project. The router drops any engine that breaks a constraint.

Failover with a record

If a provider is down or retires a model, SP Studio offers the next engine and records the change in the take’s provenance.

Registry defaults · as of November 2026

What runs each job by default.

The engine market moves monthly, so defaults live in an updatable registry, not in the app. Power users can override any choice in Pro mode.

JobDefaultAlternativesRuns
Writing
Spark, logline, treatment, adaptationYour selected language model — Claude recommendedOpenAI flagship; local Qwen, Gemma or Llama-class modelsCloud or local
Screenplay, dialogue polish, continuity notesYour selected language modelA second model for “writers’ room” A/B draftsCloud or local
Shot direction for image and video enginesYour selected language model, tuned per engine—Cloud or local
Design & boards
Concept art, key art, boards with textOpenAI gpt-image-2Grok Imagine image, FLUX.2Hosted
Character sheets, recurring identityGoogle Nano Banana 2 / Progpt-image-2, Seedream 5.0, FLUX.2Hosted
Fast draft boards and thumbnailsFLUX.2 [klein] 4B (Apache 2.0)Other open image modelsLocal
Shoot
Shots — local defaultLTX-2.5 (open weights, video and audio together)LTX-2.3Local or API
Shots — hosted enginesLTX-2.5 Pro API, Grok Imagine Video 1.5, MiniMax H3 API, Wan 3.0 APISeedance 2.5, Veo 3.1, Kling 3.0Hosted
Take review and continuity QAClaude vision on sampled framesGemini visionHosted
Sound & delivery
Dialogue and narrationElevenLabs Eleven v4Native audio from the take, for scratchHosted
Voice consistency across shotsElevenLabs Voice Changer—Hosted
Sound effectsElevenLabs Sound EffectsNative audio from the takeHosted
MusicYour own tracks — WAV, MP3 or stemsElevenLabs Music (optional, off by default)Imported
Transcription and captionsElevenLabs Speech to TextLocal Whisper-class modelHosted or local
Engine availability, versions and pricing change often. The in-app registry is the source of truth; this table is a snapshot.

Language models

Cloud or local. Tested on your own pages.

Pick a cloud model with your own key or the best local model your machine can run — globally or per project.

  • Writing Check. A blind A/B that runs the same scene or treatment through two or more models, cloud and local. You pick the better page; the result sets the default for that task.
  • Capability routing. Long adaptations and whole-bible continuity default to cloud; short rewrites, loglines and captions can stay local.
  • GPU memory manager. A local language model and a local video engine share memory, so the queue swaps them automatically on smaller machines.
  • Runtimes managed for you. Ollama, llama.cpp or MLX as optional components, fetched on request.
Local candidates · November 2026

Running locally

Qwen3.6 27B and Qwen3.8-27B (about 18 GB of weights at 4-bit), Gemma 4 31B, and Llama 3.3 70B on 48 GB-class machines and above.

Local quality for long-form screenwriting varies. Treat local models as drafting and editing tools until they pass the Writing Check on your own material. A Local-only project shows a note wherever long-form quality may drop.

License notes

The fine print, surfaced before you shoot.

SP Studio checks these for you, but you should know them. This is a summary, not legal advice — confirm terms with each provider and your counsel.

LTX-2.5 open weights are free for commercial use by organizations under $10M in annual revenue, measured across the entity and its affiliates. Larger studios need their own agreement with Lightricks. Distributing fine-tunes may require a paid license.
MiniMax H3 open weights list the United States as an excluded territory. US organizations use H3 through MiniMax’s hosted API only.
ElevenLabs Music self-serve plans exclude film, TV, radio and games; only the Enterprise music tier covers that work. That’s why music is user-supplied by default and hosted music is off.
Imported music — from a composer, a library or another tool — is logged in the License Ledger with its source and terms, and checked against each delivery. SP Studio imports files; it doesn’t call unofficial APIs.

Compute profiles

Recommended at first run, changeable any time.

The first-run doctor checks your GPU, drivers, memory and disk, benchmarks the machine, and walks you through engine downloads — including gated models that need a publisher sign-in and license acceptance.

Profile

Local

Video, local images and local audio run on this machine. Language models follow your Language Models setting. Voice services remain cloud.

Profile · studio default

Hybrid

Drafts run locally; finals and long or high-resolution shots go to hosted engines.

Profile

Cloud

Everything runs through your API accounts. Suits laptops, editing seats and trial use.

Profile

Remote GPU Roadmap

A headless SP Studio Core on a workstation or rented GPU, with the desktop app as the client.

Hardware

Local generation wants a workstation. Editing doesn’t.

Apple Silicon Macs and Windows or Linux with NVIDIA GPUs are both supported from the first release. Minimums follow published engine requirements; Recommended and Studio-class are planning figures confirmed during the beta.

Windows & Linux · NVIDIA

ComponentMinimumRecommendedStudio-class
OSWindows 10/11 64-bit, or Ubuntu 22.04+Windows 11 or Ubuntu 22.04+Windows 11 Pro, or Linux for long unattended jobs
GPUNVIDIA, 24 GB VRAM (e.g. RTX 3090 / 4090)RTX 5090, 32 GBRTX PRO 6000 Blackwell, 96 GB ECC
Memory32 GB64 GB128 GB+
CPU8 cores, recent generation12–16 cores24+ cores
Storage1 TB NVMe2 TB NVMe plus a fast media drive4 TB NVMe plus RAID or NAS
RunsLTX-2.5 at reduced speed; language model swaps in and outLTX-2.5 with a 27B language model (swapped), 4K editingLTX-2.5 and a 70B-class language model loaded together

macOS · Apple Silicon

ComponentMinimumRecommendedStudio-class
OSmacOS 26 or later for local generationmacOS 26 or latermacOS 26 or later
ChipApple Silicon (e.g. M5 Pro)M5 Max, 40-core GPUM5 Ultra
Unified memory48 GB128 GB256 GB, or 512 GB for the largest local models
Storage1 TB SSD2 TB SSD plus a fast external drive4–8 TB SSD plus Thunderbolt 5 storage
RunsLTX-2.5 at full local settings; language model swapsLTX-2.5 and a 27B language model together, 4K editingLTX-2.5 and a 70B-class model, with room for parallel jobs
Below the minimum? A 16 GB card or a smaller Mac runs SP Studio in the Hybrid or Cloud profile. On a 32 GB Mac, local video is limited to short, lower-resolution takes.
Editing and review seats need far less — the target floor is in line with professional editors: 16 GB RAM and a modest GPU, more for 4K timelines.
Disk. Local video engines need 100 GB or more (up to 160 GB with LoRAs). A local language model adds 18–37 GB. Project media comes on top.

Not sure what your machines can run?

Tell us what’s in your edit bays and render boxes when you apply, and we’ll recommend a profile.