A simple Blender render queue from upload to final delivery

YesterdayRender keeps the public flow narrow on purpose: upload a Blender project, define the frame range, watch the queue state, and collect the finished artifact when the render is done.

Step 1

Upload a supported Blender package

Supported file types in raw v1 are .blend and .zip.

If you upload a zip archive, it should package the Blender scene and its required project files cleanly.

Uploads are private and tied to the account that created the render job.

Step 2

Choose render settings that match the job

Select the render backend available for the current public pilot.

Specify whether you need a single frame or an animation range, then confirm frame start, frame end, and frame step.

The dashboard stores those job settings so the queue state stays auditable later.

Step 3

Track the queue in your private dashboard

Each account currently gets 1 active job at a time to keep the early public queue stable.

Jobs move through uploaded, queued, rendering, completed, and failed states.

You do not need to manage object storage manually; the queue is tied to your account.

Step 4

Download the final render artifact

Raw v1 stays focused on final output delivery, but the dashboard can now show sampled rendered-frame previews with per-frame timing while the job runs.

Once the render is complete, YesterdayRender exposes one final downloadable artifact for the owning account.

This keeps the delivery path simple for the first public launch while the worker stack continues to mature.