Video-by-code tools, actually run and measured.
videobycode tests tools that generate video from code, and publishes what the runs actually produced
Comparisons, render costs, and working implementations for tools that generate video from code. Every number here comes from a run we performed, with tool version, operating system, and wall-clock render time recorded.
What we publish
Comparisons
Tools placed side by side on one fixed set of criteria. The criteria, the scoring, and the version of each tool are stated before the first result.
Pricing
What a render costs in practice. Figures come from jobs we ran, with the machine, the output settings, and the wall-clock time recorded next to the price.
Tutorials
One task, implemented end to end. Each article lists the versions used, shows the code that produced the output, and reports how long the run took.
Stacks
How the pieces fit together: renderers, encoders, queues, and the glue between them. Written for people choosing what to build on.
Recorded on every test
Editorial policyTool and version
The exact release we installed, so a result can be checked against the same build later.
Machine and OS
CPU, memory, and operating system. Render numbers mean nothing without the machine they came from.
Wall-clock render time
Measured end to end on the stated output settings, not the figure printed by the tool.
Attempts, including failures
How many runs it took and what broke on the way. Runs that never finished are reported too.
Article types
How we testNumbers produced by running the tool ourselves, with the setup written down.
A task implemented step by step, with the code and the run time included.
Tools scored on one fixed set of criteria, stated before the results.