Application example Bindings

Use Media Transformations in a real application path

Media Transformations bindings let Workers transform video or audio from protected sources.

A compact Media Transformations recipe with config and worker usage in one application path.

Use this as the copyable starter before threading the feature into a larger application.

Config focus: bindings.media
Runtime shape
Best use: video/audio transformation paths where the Worker calls Cloudflare Media Transformations

Start by wiring the binding clearly in config

Smallest Media Transformations config

import { defineConfig } from 'devflare/config'

export default defineConfig({

name: 'media-worker',

bindings: {

media: {

MEDIA: true

}

})

Build the application flow around the binding

Treat this as the app-level Media Transformations path: the route, event handler, or service module receives a real request and uses the binding to do useful work.

Keep product limits, remote ownership, and fallback behavior visible in the code around the binding instead of hiding everything behind a vague utility too early.

Keep the first example short enough to paste into a new Worker.
Cloudflare owns real codecs, output fidelity, duration handling, cache behavior, and billing.

Run one media transformation chain

import { env } from 'devflare/runtime'

export async function fetch(request: Request): Promise<Response> {

if (!request.body) {

return new Response('missing media', { status: 400 })

}

return env.MEDIA

.input(request.body)

.transform({ width: 640 })

.output({ format: 'video/mp4' })

}

Keep production boundaries visible

Config focus: bindings.media.
Runtime shape: .
Best use: video/audio transformation paths where the Worker calls Cloudflare Media Transformations.

Thread this into the next recipe

Once this smallest path works, add routing, generated types, and feature-specific abstraction in that order.

Testing Media Transformations

Test Media Transformations by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.

Artifacts

Add the Artifacts config, call from worker code, and start with the local test path Devflare supports.