What does the FARPY calculator estimate?
It estimates render time from a verified benchmark baseline, frame count, resolution scale, and GPU count. The separate cost estimate is the expected completed frame count multiplied by $0.01.
Choose a known GPU, then enter frames and scaling choices.
Loading verified calculator data...
FARPY charges $0.01 per successfully completed Blender Cycles frame. Multiply the number of frames you expect to complete by one cent: expected frames × $0.01 = estimated cost.
This is a pay-per-frame rendering estimate, not a binding quote. The example assumes every entered frame completes. Failed work and work cancelled before completion are not charged as completed output; the final wallet debit follows completed billable frames.
The calculator keeps its existing formula: verified baseline seconds × resolution multiplier ÷ GPU count × frame count. It reports seconds to two decimal places and also shows a readable duration.
Choose a published GPU benchmark and engine, enter a whole-number frame count of at least one, then select resolution scaling and 1, 2, 4, or 8 GPUs. Defaults are one frame, 1× resolution, one GPU, and the first available verified result.
Resolution and multi-GPU scaling are planning models. Scene complexity, samples, effects, memory pressure, uneven frames, queue time, and available capacity can make a real project faster or slower. The calculator does not predict taxes, refunds, or a guaranteed completion time.
The time calculator accepts whole-number frame counts of one or more and does not impose the API maximum in its input control. When you submit actual work, the public API contract permits frame requests from 1 through 10,000, Blender .blend uploads up to 100 MiB, and the Cycles render engine.
The public $0.01 completed-frame rate is the same for browser and authenticated API rendering. Resolution, samples, scene complexity, GPU count, and queue time do not change this calculator's per-frame cost formula.
It estimates render time from a verified benchmark baseline, frame count, resolution scale, and GPU count. The separate cost estimate is the expected completed frame count multiplied by $0.01.
Multiply the number of successfully completed Blender Cycles frames by $0.01. For example, 120 completed frames cost $1.20.
No. The time result is a planning estimate, not a completion-time promise. The cost example assumes every entered frame completes; the final charge follows completed billable output.
The selected verified GPU result, engine, whole-number frame count, resolution multiplier, and GPU count affect the time estimate. They do not change FARPY's public per-frame price.
The public render API accepts Blender .blend files up to 100 MiB, requires Cycles, and supports frame requests from 1 through 10,000.