Script → video

The script-to-video workflow is the lowest-friction path: you bring the words, Revid brings the visuals + voice + captions + edit.

When to use this skill

• The user pastes a finished script (or generates one in-conversation).
• They want full creative control over the words.
• They are happy with stock visuals (otherwise see revid-script-with-custom-media).
• For an idea-to-video flow, use revid-prompt-to-video.

Inputs

Step-by-step

1. Validate text is non-trivial (>30 words) and within practical limits (~1500 words for a 5-min video).
2. POST /render.
3. Poll /status.

API call template

POST /api/public/v3/render
Host: www.revid.ai
Content-Type: application/json
key: $REVID_API_KEY

{
  "workflow": "script-to-video",
  "source":   { "text": "{SCRIPT}" },
  "aspectRatio": "9:16",
  "voice":    { "enabled": true, "voiceId": "aria-en-us", "stability": 0.6, "speed": 1.0, "language": "en-US" },
  "captions": { "enabled": true, "position": "middle", "autoCrop": true },
  "music":    { "enabled": true, "syncWith": "beats" },
  "media": {
    "type": "stock-video",
    "density": "medium",
    "animation": "soft",
    "quality": "pro",
    "imageModel": "good",
    "videoModel": "pro"
  },
  "options": {
    "summarizationPreference": "no-summarization",
    "soundEffects": true,
    "hasToGenerateCover": true
  },
  "render": { "resolution": "1080p", "frameRate": 30 }
}

summarizationPreference: "no-summarization" — the user wrote the script for a reason. Don't paraphrase it.

Examples

• examples/honey-script.json
• examples/run.sh

Failure modes

See also

• revid-script-with-custom-media for full visual control.
• revid-prompt-to-video when you want Revid to write the script too.
• revid-tweet-to-talking-head for short scripts with an avatar.