BlitzFrames

STAY ON REMOTION LAMBDA, THE MOST EXPENSIVE PART OUTSOURCED TO ACCELERATED SERVERS

Remotion Lambda at a flat US$0.00001 per frame.
Renders up to 11× faster and up to 5× cheaper

BlitzFrames does not replace Remotion Lambda. Your infrastructure, configuration, logs and behaviour stay exactly the same, because only the rendering itself is outsourced, to servers built for that one job.

npx blitzframes

Try out the free trial: 500,000 frames, no credit card. Your email is all it takes.

Idea ↓Deployment ↓Pricing ↓Subscribe ↓

IDEA

Same Lambda. Faster rendering. Predictable price.

The BlitzFrames deploy has the effect of a single configuration change: your Lambda forwards rendering work to dedicated BlitzFrames servers instead of render Lambdas. The rest of your infrastructure stays as it is. Your AWS bill for rendering drops to almost zero, and you pay a predictable US$0.00001 per rendered frame instead.

Initial design

Remotion Lambda

Lambda function Your infrastructure
stays unchanged
  • Render Lambda
  • Render Lambda
  • Render Lambda
  • Render Lambda

New design

With BlitzFrames

Lambda function Your infrastructure
stays unchanged
  • Render server
  • Render server
  • Render server
  • Render server

Your existing logs and workflow stay in place. Start, launch and combine stay on your Lambda.

DEPLOYMENT

Only the deploy changes.

Swap Remotion’s deploy for ours, from the command line or from Node. The render call stays exactly as it is, and so do the region, the bucket, the serve URL, the codec and the progress polling.

From the command line

Before

Deploy

$ npx remotion lambda functions deploy

Render

$ npx remotion lambda render <serve-url> MyVideo

After

Deploy

$ npx blitzframes lambda functions deploy

Render

$ npx remotion lambda render <serve-url> MyVideo

The deploy adds a BlitzFrames function next to any function you already have. How the deploy picks and names functions ↗

From Node

Before

Deploy

import {deployFunction} from "@remotion/lambda";

const {functionName} = await deployFunction({
  region: "eu-central-1",
  memorySizeInMb: 2048,
});

Render

await renderMediaOnLambda({
  functionName,
  region: "eu-central-1",
  serveUrl,
  composition: "MyVideo",
  codec: "h264",
});

After

Deploy

import {deployFunctionBlitzFrames} from "blitzframes";

const {functionName} = await deployFunctionBlitzFrames({
  region: "eu-central-1",
  memorySizeInMb: 2048,
});

Render

await renderMediaOnLambda({
  functionName,
  region: "eu-central-1",
  serveUrl,
  composition: "MyVideo",
  codec: "h264",
});

PRICING

One price per frame.

US$0.00001 per rendered frame, billed monthly. No platform fee. A 30-minute video at 30 fps is 54,000 frames, US$0.54.

  • You stop paying AWS for the renderer invocations and pay us for the same work instead. The rest of the bill is untouched: the start, launch and combine steps stay on your Lambda, and so do storage, data transfer and your Remotion licence. What remains on your AWS bill is close to zero, around US$0.0001 per render.
  • Each render is billed once for the frames it asks for: its frame range, every nth frame where set. Only completed renders count; a render that fails or is cancelled, for any reason, is not billed, and retried chunks cost nothing extra.
  • The same price for every resolution, frame rate and composition. Where rendering is unusually expensive, we may offer a custom rate.
  • Prices are in USD, excluding applicable taxes.

For example: a 400-frame render costs US$0.004 before tax, however long it takes and however many chunks it uses.

Subscribe

Keep rendering after the trial. Stripe collects a payment method for monthly usage invoices; there is no fixed fee.

RSites GmbH provides the rendering service and issues your invoices; payment is collected by Stripe. See our privacy notice.

Questions before you start? Contact us ↗

A FEW DETAILS

Before you render.

Is there any risk?

Your renders keep running on your own Lambda function, with your own configuration, so nothing about your setup changes. The output is the same video: same composition, same frames, same codec, apart from tiny pixel differences from browser rasterization. We are responsible for our uptime and have many technical measures.

How is a render counted?

Each render is billed once, for the frames it renders: your frame range, or every nth frame if you set one. Every frame costs the same, whatever the resolution.

  • Billed: the render completes and your video is written to your bucket.
  • Not billed: the render fails or is cancelled, whatever the cause: your composition, its assets, a timeout, or our servers.
  • Retries of failed chunks are never billed again.
Which Remotion versions are supported?

Stable Remotion 4.0 releases starting at 4.0.293. Newly published stable 4.0 releases become available shortly after release. Both npx blitzframes lambda functions deploy and deployFunctionBlitzFrames check your project’s version before they touch anything, and refuse one below 4.0.293 with a message to upgrade first.

What else do I need?

Your own Remotion Lambda setup, AWS account and any required Remotion licence. AWS, storage, data transfer and Remotion costs are separate from BlitzFrames usage.

How do I cancel?

Open Manage billing on your account page, sign in to the billing portal with your checkout email, or email [email protected]. Cancellation takes effect at the end of the current billing period: until then your renders keep going to BlitzFrames, and you can undo the cancellation in the billing portal. There is no fixed fee, so a period without renders costs nothing. Afterwards your token is no longer accepted: use your stock Remotion function as functionName again, because renders on the BlitzFrames function can fail. The usage up to the end of the period appears on the regular invoice.