How Devflare wires Media Transformations from config to runtime
Media Transformations bindings let Workers transform video or audio from protected sources.
Media Transformations compiles from to Wrangler , with local/test behavior called out explicitly.
Use this page when you need emitted config, preview behavior, or Cloudflare-specific limits. The overview and example pages stay focused on everyday app code.
- Normalization
- Devflare normalizes before emitting Wrangler
- Compile target
- Wrangler
- Preview note
- Cloudflare owns real codecs, output fidelity, duration handling, cache behavior, and billing.
How authored config becomes Wrangler config
The authored config stays camelCase and project-oriented. The compiler translates that into the Wrangler keys Cloudflare expects.
The emitted output is shown here so the usage pages do not have to explain compiler details.
Media Transformations config and emitted Wrangler output
Use this when you need to check how the Devflare config becomes Wrangler-compatible config.
What local runtime support covers
- Full local support through Miniflare media bindings and deterministic pure mocks for transform chains
- The default docs recipe uses or with media fixtures.
- Pure unit tests can use / when the test only needs deterministic application behavior.
Compile, preview, and cleanup behavior
- Devflare emits Wrangler from the native config surface.
- Preview and deployment lifecycle stay feature-specific; do not assume all Cloudflare products can be created, cloned, or cleaned up the same way.
- Cloudflare owns real codecs, output fidelity, duration handling, cache behavior, and billing.
Cloudflare docs vs the Devflare layer
Cloudflare Media Transformations docs is the platform reference. Use this internals page when you need to compare Cloudflare's product docs with Devflare config, generated env types, local support, and preview behavior for .
| Question | Cloudflare docs | This Devflare page |
|---|---|---|
| Primary focus | Platform reference for Media Transformations bindings, beta limits, and Workers API setup. | How to author , what the runtime surface looks like, and how Media Transformations fits a Devflare project. |
| Testing and runtime lens | Cloudflare’s docs focus on the raw binding API, product semantics, and platform limits for the binding itself. | Full local support through Miniflare media bindings and deterministic pure mocks for transform chains. Use the Devflare guidance when you need the honest local harness or the right remote gate instead of only the product API shape. |
| When to open it | When you need the platform contract, limits, APIs, or account-level product details. | When you are wiring, testing, previewing, or reviewing the binding inside a Devflare app. |
Previous
Media Transformations
Add the Media Transformations config, call from worker code, and start with the local test path Devflare supports.
Next
Testing Media Transformations
Test Media Transformations by choosing the local harness that matches the product boundary instead of reaching for Cloudflare by default.