Create Video’s fps sets the playback rate for the image sequence; Save Video’s options choose how the resulting video is packaged and, where selected, encoded. The Save Video documentation does not list an fps input, so do not look to its container or codec settings to set the sequence’s playback rate. Decide the frame rate where the VIDEO is created, then choose the save configuration that fits the intended delivery.
Assign each setting to its node
Create Video takes images and a required fps value, with a documented default of 30 and a range of 1–120. It outputs a VIDEO. Its optional codec setting is an advanced choice: none keeps the output in tensor form, while selecting a codec encodes it immediately. The node also has optional audio, bit depth, and color-space inputs; those are separate from the frame-rate setting. See the Create Video node documentation.
Save Video takes a VIDEO and saves it using a selected container and codec. Its documented formats include Auto, MP4, MKV, and WebM, while codec options depend on the chosen format. See the Save Video node documentation.
| Decision | Node and control | What the documentation says |
|---|---|---|
| Image-sequence playback rate | Create Video: fps | Required; 1–120 fps; default 30 |
| Container | Save Video: format | Auto, MP4, MKV, or WebM; format affects available codecs |
| Output codec | Save Video: codec | Options depend on the chosen format; verify the installed selector because the cited page conflicts about WebM/AV1 |
| Preserve or re-encode | Save Video: encoding for H.264 or AV1 | Auto preserves a compatible source stream; re-encode applies custom encoding options |
| Quality and size tradeoff | Save Video: crf, when shown | Appears for re-encoding; lower values mean higher quality and larger files |
Set the playback rate first
Use this sequence when turning generated or otherwise prepared stills into a clip:
- Decide the intended playback rate from the delivery brief or the rate required by the downstream timeline. Do not infer it from the desired file extension or codec.
- In Create Video, enter that rate in
fps. Check that the input is within the documented 1–120 range. If you leave it at the documented default, the value is 30 fps. - Connect the resulting
VIDEOto Save Video. Choose a container and codec combination that is actually available in the selected format. - Choose
codec: autoif preserving a compatible source stream is the intended behavior. Choose H.264 or AV1 and inspect the conditionalencodingcontrol if you intend to re-encode. CRF is available only when re-encoding is selected. - Save, then inspect the produced file in a media-information tool or the intended playback or editing application. Check the reported frame rate and the codec/container fields separately; do not treat one as evidence for the other.
If Create Video’s immediate encoding option is used, note that this is a separate encoding decision from Save Video’s settings. The documentation describes both nodes’ roles but does not specify every interaction between an already encoded input and all Save Video combinations. Confirm the actual output rather than assuming a particular path.
Hypothetical acceptance check
Suppose a creator wants a 24 fps sequence and an MP4 H.264 delivery. The figures below are an illustrative target, not a test result or a guarantee that every workflow will report metadata identically.
| Check | Hypothetical setting or observation | Pass condition |
|---|---|---|
| Create Video | fps set to 24 | The created sequence is intended to play at 24 fps |
| Save Video | format: mp4, codec: h264 | The saved file is an MP4 with an H.264 video stream |
| Encoding mode | For this MP4/H.264 example, select codec: h264, then set encoding: re-encode | crf appears; its value is recorded as an encoding choice |
| Independent inspection | File information reports 24 fps, MP4, H.264 | Each field matches its own target; a codec match alone is not enough |
If the inspection reports the wrong rate, revisit the Create Video fps setting and the actual workflow input rather than changing CRF. If the rate is right but the container or codec is wrong, revisit Save Video’s selected format and its nested codec options. If an expected control is absent, first check the conditions: encoding and crf are conditional on choosing H.264 or AV1, and CRF appears only for re-encoding.
Understand Auto and CRF limits
In Save Video, codec: auto is documented as preserving a compatible source stream rather than re-encoding it. The cited page has an internal contradiction: its codec row excludes AV1 with WebM, while its AV1 section and final note include that combination. This guide therefore does not certify WebM/AV1 selector availability. Check the installed version’s actual options and inspect the resulting file; the worksheet above uses the separately documented MP4/H.264 path.
When re-encoding, the documented CRF ranges are 0–51 for H.264 and 0–63 for AV1. Lower values trade larger files for higher quality according to the node documentation; they do not set frame rate or guarantee recovery of detail that was not present in the source. Treat CRF as an encoding-quality choice, not a timing correction. Detailed codec tuning is outside this guide’s scope.
Common questions
Can I set the frame rate in Save Video? The cited Save Video input list does not include an fps control. Set the sequence playback rate in Create Video and inspect the saved file’s reported rate.
Does choosing H.264 or AV1 change the intended fps? The documentation describes those controls as codec and encoding choices, not playback-rate controls. Verify the output rate independently; do not assume codec selection sets it.
Why can’t I see CRF? CRF appears when H.264 or AV1 is selected and encoding is set to re-encode. If the input uses Auto or is preserved as a compatible stream, a CRF value is not shown by the documented controls. The sources describe the node inputs, not every runtime edge case, so use the saved file’s metadata to confirm the result.
Sources and next step
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the film workspace. The external software controls discussed above belong to their respective products.