Cloudflare Takes Python Workers Out of Beta After Two Years

Cloudflare made Python a fully supported language on its Workers platform Monday, software engineer Dominik Picheta wrote, ending a beta that ran for two years and removing the JavaScript conversion code Python developers previously had to write by hand.

Until now, a Python Worker that wanted to send a message to a Cloudflare queue had to convert its data through a JavaScript bridge, calling something like to_js({"key": "value"}, dict_converter=js.Object.fromEntries). Picheta's post says that call now works directly as self.env.QUEUE.send({"key": "value"}), without a JavaScript layer in between.

What actually changed on Monday

Python Workers now support the FastAPI, Django and Flask frameworks natively, and Python code can call Cloudflare's D1 database, R2 storage, Workers AI, Durable Objects, Queues and Workflows bindings directly. New TCP socket support lets Python connect to Postgres and MySQL through ordinary drivers such as asyncpg and aiomysql via Cloudflare's Hyperdrive service, rather than through a bespoke Cloudflare client. Popular AI libraries including openai, langchain and mcp now work without modification because their HTTP calls route through Workers' fetch implementation.

Cloudflare also says it proposed and won acceptance of PEP 783, a Python packaging standard for compiling native code to WebAssembly, and has added support for it in the cibuildwheel tool that package maintainers use to build wheels for multiple platforms.

The limit that was quietly the real story

RuntimeWire reported that on Sept. 4, ahead of the general-availability announcement, Cloudflare replaced a compressed bundle cap of 3 MB on free plans and 10 MB on paid plans with a single 64 MiB uncompressed limit across both tiers. The outlet cited a GitHub issue filed in July showing that dependencies alone, pandas, NumPy and Pillow among them, could consume most or all of the old compressed allowance before a developer's own application code was added.

Bundle limit	Before Sept. 4	After Sept. 4
Free plan	3 MB compressed	64 MiB uncompressed
Paid plans	10 MB compressed	64 MiB uncompressed

RuntimeWire's coverage frames Python Workers as suited to APIs, agents and event-driven jobs rather than to applications that need local disks or native threads, since pure Python packages run natively but native C, C++ or Rust extensions still need a WebAssembly-compatible build. The shift toward native language support without a translation layer mirrors a broader pattern in developer tooling in 2026, including GitHub's decision to rewrite its own Copilot runtime in Rust to cut process overhead, and the expanding ecosystem of tools built around the Jujutsu version control system.

What Cloudflare isn't saying

Neither Cloudflare's post nor RuntimeWire's gives a price for Python Workers specifically; Cloudflare has not published Python-specific CPU time or per-request limits distinct from the JavaScript Workers runtime it has offered since 2017. The company also has not said how many of the roughly two years of beta users have moved to production traffic on the GA runtime.

Cloudflare's own recent infrastructure work has focused on squeezing overhead out of the same platform: RuntimeWire separately reported on Sept. 18 that four Cloudflare engineers reclaimed more than 100 terabytes of RAM across the network by shrinking a consistent-hashing data structure from eight bytes to six. The next milestone to watch is whether Cloudflare publishes Python-specific pricing or keeps billing identical to JavaScript Workers, which it has not yet addressed.