How Vootkit Workflow Works
A workflow is a reusable path through several compatible Vootkit tools. The builder uses the same processing functions as the individual tool pages, so if a tool cannot be called by the workflow engine yet, it is not offered as a step.
58 tools can currently be workflow steps. Every chain is checked before it runs, and your files stay in your browser while one step hands its output to the next. That means you can prepare a whole batch without repeatedly downloading a file, opening another page, and choosing the same file again.
Workflow-ready tools
The current workflow engine focuses on file-processing tools with callable browser engines. These include image tools such as Image Resizer, Image Compressor, Image Converter, Crop Image, JPG to WebP and PNG to WebP. The website image optimizer template uses that exact family of tools so the canvas is not a fake demo: resize, compress and convert all stay editable after the template loads.
PDF workflows can combine real PDF tools including Merge PDFs, Compress PDF, Split PDF, Rotate PDF, PDF Watermark, Protect PDF, Extract PDF Pages, Add Page Numbers, Images to PDF, PNG to PDF and WebP to PDF. If a requested document conversion is not workflow-ready yet, it is kept out of the builder instead of being shown and failing later.
Video workflows use the same in-browser media engine as the individual pages, with steps such as Video Trimmer, Video Compressor, Video to GIF, Video Resizer, Mute Video, Extract Audio, Video Converter and Frame Grabber. The first video run may load the video engine, then processing happens locally in the browser.
Why templates matter
The template marketplace is there for people who know the result they want but do not want to design a chain from zero. A template clones a real definition into the builder, preserves its starting settings, and leaves every node editable. You can open Website Image Optimizer, inspect the resize/compress/convert chain, adjust the compression level, add another image step, remove a step, save the workflow locally, then run it on your own files.
The preview panel shows what the template is meant to do before you use it: accepted inputs, output format, privacy status and a simple before/after visual. It does not run anything by itself and it does not imply the stock-photo subjects or image sources are Vootkit customers. The photographs are local template artwork, while the workflow itself still depends on the real tool definitions available in the registry.
Running safely
Before a workflow runs, Vootkit checks the chain from input to output. A PDF step cannot receive an image unless a compatible conversion step appears before it. A video step cannot receive a PDF. If the chain is incompatible, the builder marks the step and, where possible, suggests a real bridge tool. During a run, each node reports its own status. If one step fails, the run stops at that step, keeps the last successful output when possible, and tells you what happened in the tool's own words.
Do my files get uploaded when I run a workflow?
No. Every workflow-compatible step runs in your browser on your own machine, including the handover between steps.
How is this different from using the tools one at a time?
A workflow is one file selection and one run through a reusable chain, instead of opening several pages manually.
Which tools can be workflow steps?
58 tools today - the runnable PDF, image, audio and video sets.