The workflow builder chains online video tools — readiness, 9:16 fit, compress, loudness, and Shorts or Reels packs — in one sequential job (up to four encodes), then you download and upload the MP4 yourself.
What is a video processing pipeline builder?
A video processing pipeline builder orders publish-prep tools — readiness, 9:16 fit, Shorts/Reels packs, compress, loudness, captions — then encodes process steps in sequence on one FFmpeg worker.
Analyze and report tools (readiness, loudness report) open on their own pages. Process tools (crop, pack, compress, subtitle burn, audio replace) run in one job, max four encodes, with MAX_CONCURRENT_JOBS=1 on the VPS. Mid-chain GIF, still, or audio-extract steps are skipped unless they are last.
Which tools can creators add to a pipeline?
Creators can add any live catalog tool with a public landing — Platform Readiness, Fit to Aspect, Shorts and Reels packs, Compress, loudness normalize, captions, Pinterest pack, and the rest of the published toolkit.
Where do pipeline recipes save?
Pipeline recipes save in browser localStorage on this device (steps plus knobs); checklist progress saves in sessionStorage; shareable step lists and knobs live in the URL query — no account sync and no Redis queue.
Clearing site data removes saved recipes. Sequential encode uses the existing Mongo job worker. A multi-job cloud queue stays out of scope while the VPS runs one FFmpeg job at a time.
How does this differ from the check-then-pack workflow guide?
The check-then-pack workflow guide teaches a recommended readiness-then-pack path; this page is an interactive builder where you pick a template, open reports, set encode knobs, and run process steps in one sequential job.
Pick a template, open reports if needed, attach sidecars, set knobs, and run up to four process encodes in one VPS job under the 50 MB and two-hour file limits.