Changelog
New

Verify job outputs with output.file.sha256

Check a download, or a copy delivered to your own bucket, against the SHA-256 Rendobar computed. Every output file now reports it in the job response and the completion webhook.

API SDK

You can now confirm that the file you received is the file the job produced. Each output file carries sha256, the SHA-256 of its bytes as 64 lowercase hex characters, next to size.

"file": {
  "url": "https://api.rendobar.com/dl/job_abc123?...",
  "path": "output.mp4",
  "type": "video",
  "size": 1218810,
  "sha256": "9f2c41d0b7a3e5f48c1d6e02a97b3c5f1e8d4a60b2c7f9e3d5a1b8c4e6f0a41e"
}

Hash your copy with sha256sum or any SHA-256 library and compare the strings. This works for a file fetched from file.url and for a copy delivered to connected storage, because the delivered object is the same file.

  • Computed from the whole file. A large output reports the digest of the complete file, the same value sha256sum gives you.
  • Every job type that returns a file. ffmpeg, compose, compress.target, caption.burn, captions.animate, and the three image types.
  • Same value in the webhook. job.completed carries the same output object.

The field is always present. It is null for a job that completed before this shipped, and for the individual files of a multi-file output such as an HLS ladder.

If you ran a second ffmpeg job with -f hash only to get a checksum of an output, you can drop it. Output files are covered in the ffmpeg job docs, and delivery in the storage docs.

Share