Big outputs reach your bucket faster

If your jobs work with large videos, you now wait less for them, from submit to the file in your own storage. Nothing changes in your requests.

On every plan#

Big files move several times faster in both directions, so the job itself finishes sooner. Measured with a 1.08 GB file:

Delivery to your connected bucket is faster too. A 1.42 GB output landed in a bucket on another continent about 27 s after its job ended, down from 62 s at the median. A small output is copied as soon as the job finishes, about 4.7 s after it ends instead of 8.6 s.

Faster output delivery on Studio#

On the Studio plan, an output of 512 MB or more starts landing in each of your destinations while the job is still sending it, so the file is in your bucket about when the job ends. On the same 1.08 GB job, the file was in the bucket 4.5 s after the job ended on Studio and 20.9 s after on Pro.

That gap grows with the file, which is why it matters most to you if you render long videos or keep raw footage in your own storage. A smaller output is copied the same fast way on every plan.

What stays the same#

• destinations, job.delivery_succeeded and job.deliveries_settled work as before.
• Every file an output has is still delivered to your bucket, and each one is identical to the job’s output.
• GET /account/capabilities reports features.fastOutputDelivery, so your code can tell whether your plan has it.