How to configure Cloudinary video transcoding on Webflow Cloud

Cloudinary video delivery can be integrated with a Webflow Cloud Next.js application without the Cloudinary Node.js SDK, which may fail in the Cloudflare Workers edge runtime due to unsupported Node core modules. The approach uses direct fetch requests to Cloudinary’s REST upload API, environment variables for the cloud name and unsigned upload preset, URL utilities that generate CDN delivery links, and an upload preset configured with asynchronous eager transformations for HLS via `sp_auto` and optimized MP4 fallback output. Eager transcoding prevents viewers from triggering on-demand transformation work, although delivery URLs can return HTTP 423 until asynchronous processing finishes, which can be managed through Cloudinary webhook notifications and a readiness status or by temporarily serving the original uploaded video. Videos up to 100 MB can pass through an edge Route Handler, while larger files should upload directly from the browser to Cloudinary to avoid Webflow Cloud request-size limits. HLS adaptive bitrate streams can use native browser support where reliable and hls.js elsewhere, while Cloudinary’s CDN serves all video content directly so the application only creates URLs and stores public IDs rather than proxying video files.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.