---
title: Changelogs
image: https://edgetunnel-b2h.pages.dev/cf-twitter-card.png
---

> Documentation Index  
> Fetch the complete documentation index at: https://edgetunnel-b2h.pages.dev/changelog/llms.txt  
> Use this file to discover all available pages before exploring further. 

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

All products

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

Apr 11, 2025
1. ### [Signed URLs and Infrastructure Improvements on Stream Live WebRTC Beta](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-14-webrtc-beta-signed-urls/)  
[ Stream ](https://edgetunnel-b2h.pages.dev/stream/)  
Cloudflare [Stream](https://edgetunnel-b2h.pages.dev/stream/) has completed an infrastructure upgrade for our [Live WebRTC beta](https://edgetunnel-b2h.pages.dev/stream/webrtc-beta/) support which brings increased scalability and improved playback performance to all customers. WebRTC allows broadcasting directly from a browser (or supported WHIP client) with ultra-low latency to tens of thousands of concurrent viewers across the globe.  
Additionally, as part of this upgrade, the WebRTC beta now supports Signed URLs to protect playback, just like our standard live stream options (HLS/DASH).  
For more information, learn about the [Stream Live WebRTC beta](https://edgetunnel-b2h.pages.dev/stream/webrtc-beta/).

Apr 11, 2025
1. ### [Workers AI for Developer Week - faster inference, new models, async batch API, expanded LoRA support](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-11-new-models-faster-inference/)  
[ Workers AI ](https://edgetunnel-b2h.pages.dev/workers-ai/)  
Happy Developer Week 2025! Workers AI is excited to announce a couple of new features and improvements available today. Check out our [blog ↗](https://blog.cloudflare.com/workers-ai-improvements) for all the announcement details.  
#### Faster inference + New models  
We’re rolling out some in-place improvements to our models that can help speed up inference by 2-4x! Users of the models below will enjoy an automatic speed boost starting today:

  * [@cf/meta/llama-3.3-70b-instruct-fp8-fast](https://edgetunnel-b2h.pages.dev/workers-ai/models/llama-3.3-70b-instruct-fp8-fast/) gets a speed boost of 2-4x, leveraging techniques like speculative decoding, prefix caching, and an updated inference backend.
  * [@cf/baai/bge-small-en-v1.5](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-small-en-v1.5/), [@cf/baai/bge-base-en-v1.5](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-base-en-v1.5/), [@cf/baai/bge-large-en-v1.5](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-large-en-v1.5/) get an updated back end, which should improve inference times by 2x.  
    * With the `bge` models, we’re also announcing a new parameter called `pooling` which can take `cls` or `mean` as options. We highly recommend using `pooling: cls` which will help generate more accurate embeddings. However, embeddings generated with cls pooling are not backwards compatible with mean pooling. For this to not be a breaking change, the default remains as mean pooling. Please specify `pooling: cls` to enjoy more accurate embeddings going forward.  
We’re also excited to launch a few new models in our catalog to help round out your experience with Workers AI. We’ll be deprecating some older models in the future, so stay tuned for a deprecation announcement. Today’s new models include:

  * [@cf/mistralai/mistral-small-3.1-24b-instruct](https://edgetunnel-b2h.pages.dev/workers-ai/models/mistral-small-3.1-24b-instruct/): a 24B parameter model achieving state-of-the-art capabilities comparable to larger models, with support for vision and tool calling.
  * [@cf/google/gemma-3-12b-it](https://edgetunnel-b2h.pages.dev/workers-ai/models/gemma-3-12b-it/): well-suited for a variety of text generation and image understanding tasks, including question answering, summarization and reasoning, with a 128K context window, and multilingual support in over 140 languages.
  * [@cf/qwen/qwq-32b](https://edgetunnel-b2h.pages.dev/workers-ai/models/qwq-32b/): a medium-sized reasoning model, which is capable of achieving competitive performance against state-of-the-art reasoning models, e.g., DeepSeek-R1, o1-mini.
  * [@cf/qwen/qwen2.5-coder-32b-instruct](https://edgetunnel-b2h.pages.dev/workers-ai/models/qwen2.5-coder-32b-instruct/): the current state-of-the-art open-source code LLM, with its coding abilities matching those of GPT-4o.  
#### Batch Inference  
Introducing a new batch inference feature that allows you to send us an array of requests, which we will fulfill as fast as possible and send them back as an array. This is really helpful for large workloads such as summarization, embeddings, etc. where you don’t have a human-in-the-loop. Using the batch API will guarantee that your requests are fulfilled eventually, rather than erroring out if we don’t have enough capacity at a given time.  
Check out the [tutorial](https://edgetunnel-b2h.pages.dev/workers-ai/features/batch-api/) to get started! Models that support batch inference today include:

  * [@cf/meta/llama-3.3-70b-instruct-fp8-fast](https://edgetunnel-b2h.pages.dev/workers-ai/models/llama-3.3-70b-instruct-fp8-fast/)
  * [@cf/baai/bge-small-en-v1.5](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-small-en-v1.5/)
  * [@cf/baai/bge-base-en-v1.5](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-base-en-v1.5/)
  * [@cf/baai/bge-large-en-v1.5](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-large-en-v1.5/)
  * [@cf/baai/bge-m3](https://edgetunnel-b2h.pages.dev/workers-ai/models/bge-m3/)
  * [@cf/meta/m2m100-1.2b](https://edgetunnel-b2h.pages.dev/workers-ai/models/m2m100-1.2b/)  
#### Expanded LoRA support  
We’ve upgraded our LoRA experience to include 8 newer models, and can support ranks of up to 32 with a 300MB safetensors file limit (previously limited to rank of 8 and 100MB safetensors) Check out our [LoRAs page](https://edgetunnel-b2h.pages.dev/workers-ai/features/fine-tunes/loras/) to get started. Models that support LoRAs now include:

  * [@cf/meta/llama-3.2-11b-vision-instruct](https://edgetunnel-b2h.pages.dev/workers-ai/models/llama-3.2-11b-vision-instruct/)
  * [@cf/meta/llama-3.3-70b-instruct-fp8-fast](https://edgetunnel-b2h.pages.dev/workers-ai/models/llama-3.3-70b-instruct-fp8-fast/)
  * [@cf/meta/llama-guard-3-8b](https://edgetunnel-b2h.pages.dev/workers-ai/models/llama-guard-3-8b/)
  * [@cf/meta/llama-3.1-8b-instruct-fast](https://edgetunnel-b2h.pages.dev/workers-ai/models/llama-3.1-8b-instruct-fast/) (coming soon)
  * [@cf/deepseek-ai/deepseek-r1-distill-qwen-32b](https://edgetunnel-b2h.pages.dev/workers-ai/models/deepseek-r1-distill-qwen-32b/) (coming soon)
  * [@cf/qwen/qwen2.5-coder-32b-instruct](https://edgetunnel-b2h.pages.dev/workers-ai/models/qwen2.5-coder-32b-instruct/)
  * [@cf/qwen/qwq-32b](https://edgetunnel-b2h.pages.dev/workers-ai/models/qwq-32b/)
  * [@cf/mistralai/mistral-small-3.1-24b-instruct](https://edgetunnel-b2h.pages.dev/workers-ai/models/mistral-small-3.1-24b-instruct/)
  * [@cf/google/gemma-3-12b-it](https://edgetunnel-b2h.pages.dev/workers-ai/models/gemma-3-12b-it/)

Apr 10, 2025
1. ### [D1 Read Replication Public Beta](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-10-d1-read-replication-beta/)  
[ D1 ](https://edgetunnel-b2h.pages.dev/d1/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
D1 read replication is available in public beta to help lower average latency and increase overall throughput for read-heavy applications like e-commerce websites or content management tools.  
Workers can leverage read-only database copies, called read replicas, by using D1 [Sessions API](https://edgetunnel-b2h.pages.dev/d1/best-practices/read-replication). A session encapsulates all the queries from one logical session for your application. For example, a session may correspond to all queries coming from a particular web browser session. With Sessions API, D1 queries in a session are guaranteed to be [sequentially consistent](https://edgetunnel-b2h.pages.dev/d1/best-practices/read-replication/#replica-lag-and-consistency-model) to avoid data consistency pitfalls. D1 [bookmarks](https://edgetunnel-b2h.pages.dev/d1/reference/time-travel/#bookmarks) can be used from a previous session to ensure logical consistency between sessions.

**TypeScript**  
```ts  
// retrieve bookmark from previous session stored in HTTP header  
const bookmark = request.headers.get("x-d1-bookmark") ?? "first-unconstrained";  
const session = env.DB.withSession(bookmark);  
const result = await session  
  .prepare(`SELECT * FROM Customers WHERE CompanyName = 'Bs Beverages'`)  
  .run();  
// store bookmark for a future session  
response.headers.set("x-d1-bookmark", session.getBookmark() ?? "");  
```  
Read replicas are automatically created by Cloudflare (currently one in each supported [D1 region](https://edgetunnel-b2h.pages.dev/d1/best-practices/read-replication/#read-replica-locations)), are active/inactive based on query traffic, and are transparently routed to by Cloudflare at no additional cost.  
To checkout D1 read replication, deploy the following Worker code using Sessions API, which will prompt you to create a D1 database and enable read replication on said database.  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/d1-starter-sessions-api)  
To learn more about how read replication was implemented, go to our [blog post ↗](https://blog.cloudflare.com/d1-read-replication-beta).

Apr 10, 2025
1. ### [Cloudflare Pipelines now available in beta](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-10-launching-pipelines/)  
[ Pipelines ](https://edgetunnel-b2h.pages.dev/pipelines/)[ R2 ](https://edgetunnel-b2h.pages.dev/r2/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
[Cloudflare Pipelines](https://edgetunnel-b2h.pages.dev/pipelines) is now available in beta, to all users with a [Workers Paid](https://edgetunnel-b2h.pages.dev/workers/platform/pricing) plan.  
Pipelines let you ingest high volumes of real time data, without managing the underlying infrastructure. A single pipeline can ingest up to 100 MB of data per second, via HTTP or from a [Worker](https://edgetunnel-b2h.pages.dev/workers). Ingested data is automatically batched, written to output files, and delivered to an [R2 bucket](https://edgetunnel-b2h.pages.dev/r2) in your account. You can use Pipelines to build a data lake of clickstream data, or to store events from a Worker.  
Create your first pipeline with a single command:

**Create a pipeline**  
```bash  
$ npx wrangler@latest pipelines create my-clickstream-pipeline --r2-bucket my-bucket  
🌀 Authorizing R2 bucket "my-bucket"  
🌀 Creating pipeline named "my-clickstream-pipeline"  
✅ Successfully created pipeline my-clickstream-pipeline  
Id:    0e00c5ff09b34d018152af98d06f5a1xvc  
Name:  my-clickstream-pipeline  
Sources:  
  HTTP:  
    Endpoint:        https://0e00c5ff09b34d018152af98d06f5a1xvc.pipelines.cloudflare.com/  
    Authentication:  off  
    Format:          JSON  
  Worker:  
    Format:  JSON  
Destination:  
  Type:         R2  
  Bucket:       my-bucket  
  Format:       newline-delimited JSON  
  Compression:  GZIP  
Batch hints:  
  Max bytes:     100 MB  
  Max duration:  300 seconds  
  Max records:   100,000  
🎉 You can now send data to your pipeline!  
Send data to your pipeline's HTTP endpoint:  
curl "https://0e00c5ff09b34d018152af98d06f5a1xvc.pipelines.cloudflare.com/" -d '[{ ...JSON_DATA... }]'  
To send data to your pipeline from a Worker, add the following configuration to your config file:  
{  
  "pipelines": [  
    {  
      "pipeline": "my-clickstream-pipeline",  
      "binding": "PIPELINE"  
    }  
  ]  
}  
```  
Head over to our [getting started guide](https://edgetunnel-b2h.pages.dev/pipelines/getting-started) for an in-depth tutorial to building with Pipelines.

Apr 10, 2025
1. ### [R2 Data Catalog is a managed Apache Iceberg data catalog built directly into R2 buckets](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-10-r2-data-catalog-beta/)  
[ R2 ](https://edgetunnel-b2h.pages.dev/r2/)  
Today, we're launching [R2 Data Catalog](https://edgetunnel-b2h.pages.dev/r2/data-catalog/) in open beta, a managed Apache Iceberg catalog built directly into your [Cloudflare R2](https://edgetunnel-b2h.pages.dev/r2/) bucket.  
If you're not already familiar with it, [Apache Iceberg ↗](https://iceberg.apache.org/) is an open table format designed to handle large-scale analytics datasets stored in object storage, offering ACID transactions and schema evolution. R2 Data Catalog exposes a standard Iceberg REST catalog interface, so you can connect engines like [Spark](https://edgetunnel-b2h.pages.dev/r2/data-catalog/config-examples/spark-scala/), [Snowflake](https://edgetunnel-b2h.pages.dev/r2/data-catalog/config-examples/snowflake/), and [PyIceberg](https://edgetunnel-b2h.pages.dev/r2/data-catalog/config-examples/pyiceberg/) to start querying your tables using the tools you already know.  
To enable a data catalog on your R2 bucket, find **R2 Data Catalog** in your buckets settings in the dashboard, or run:  
```bash  
npx wrangler r2 bucket catalog enable my-bucket  
```  
And that's it. You'll get a catalog URI and warehouse you can plug into your favorite Iceberg engines.  
Visit our [getting started guide](https://edgetunnel-b2h.pages.dev/r2/data-catalog/get-started/) for step-by-step instructions on enabling R2 Data Catalog, creating tables, and running your first queries.

Apr 09, 2025
1. ### [Cloudflare Zero Trust SCIM User and Group Provisioning Logs](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-09-scim-provisioning-logs/)  
[ Access ](https://edgetunnel-b2h.pages.dev/cloudflare-one/access-controls/policies/)  
[Cloudflare Zero Trust SCIM provisioning](https://edgetunnel-b2h.pages.dev/cloudflare-one/team-and-resources/users/scim) now has a full audit log of all create, update and delete event from any SCIM Enabled IdP. The [SCIM logs](https://edgetunnel-b2h.pages.dev/cloudflare-one/insights/logs/dashboard-logs/scim-logs/) support filtering by IdP, Event type, Result and many more fields. This will help with debugging user and group update issues and questions.  
SCIM logs can be found on the Zero Trust Dashboard under **Logs** \-> **SCIM provisioning**.  
![Example SCIM Logs](https://edgetunnel-b2h.pages.dev/_astro/example-scim-log.Bv5Zqckh_BY26C.webp)

Apr 09, 2025
1. ### [Hyperdrive now supports custom TLS/SSL certificates](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-09-hyperdrive-custom-certificate-support/)  
[ Hyperdrive ](https://edgetunnel-b2h.pages.dev/hyperdrive/)  
Hyperdrive now supports more SSL/TLS security options for your database connections:

  * Configure Hyperdrive to verify server certificates with `verify-ca` or `verify-full` SSL modes and protect against man-in-the-middle attacks
  * Configure Hyperdrive to provide client certificates to the database server to authenticate itself (mTLS) for stronger security beyond username and password  
Use the new `wrangler cert` commands to create certificate authority (CA) certificate bundles or client certificate pairs:  
```bash  
# Create CA certificate bundle  
npx wrangler cert upload certificate-authority --ca-cert your-ca-cert.pem --name your-custom-ca-name  
# Create client certificate pair  
npx wrangler cert upload mtls-certificate --cert client-cert.pem --key client-key.pem --name your-client-cert-name  
```  
Then create a Hyperdrive configuration with the certificates and desired SSL mode:  
```bash  
npx wrangler hyperdrive create your-hyperdrive-config \
  --connection-string="postgres://user:password@hostname:port/database" \
  --ca-certificate-id <CA_CERT_ID> \
  --mtls-certificate-id <CLIENT_CERT_ID>
  --sslmode verify-full  
```  
Learn more about [configuring SSL/TLS certificates for Hyperdrive](https://edgetunnel-b2h.pages.dev/hyperdrive/configuration/tls-ssl-certificates-for-hyperdrive/) to enhance your database security posture.

Apr 09, 2025
1. ### [Cloudflare Snippets are now Generally Available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-09-snippets-ga/)  
[ Rules ](https://edgetunnel-b2h.pages.dev/rules/)  
![Cloudflare Snippets are now GA](https://edgetunnel-b2h.pages.dev/_astro/snippets-ga.BJr3csvv_Z2q49jT.webp)  
[Cloudflare Snippets](https://edgetunnel-b2h.pages.dev/rules/snippets/) are now generally available at no extra cost across all paid plans — giving you a fast, flexible way to programmatically control HTTP traffic using lightweight JavaScript.  
You can now use Snippets to modify HTTP requests and responses with confidence, reliability, and scale. Snippets are production-ready and deeply integrated with Cloudflare Rules, making them ideal for everything from quick dynamic header rewrites to advanced routing logic.  
What's new:

  * **Snippets are now GA** – Available at no extra cost on all Pro, Business, and Enterprise plans.
  * **Ready for production** – Snippets deliver a production-grade experience built for scale.
  * **Part of the Cloudflare Rules platform** – Snippets inherit request modifications from other Cloudflare products and support sequential execution, allowing you to run multiple Snippets on the same request and apply custom modifications step by step.
  * **Trace integration** – Use [Cloudflare Trace](https://edgetunnel-b2h.pages.dev/rules/trace-request/) to see which Snippets were triggered on a request — helping you understand traffic flow and debug more effectively.  
  ![Snippets shown in Cloudflare Trace results](https://edgetunnel-b2h.pages.dev/_astro/snippets-ga-trace.WlCshaFo_1WNo07.webp)  
Learn more in the [launch blog post ↗](https://blog.cloudflare.com/snippets/).

Apr 09, 2025
1. ### [Cloudflare Secrets Store now available in Beta](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-09-secrets-store-beta/)  
[ Secrets Store ](https://edgetunnel-b2h.pages.dev/secrets-store/)[ SSL/TLS ](https://edgetunnel-b2h.pages.dev/ssl/)  
Cloudflare Secrets Store is available today in Beta. You can now store, manage, and deploy account level secrets from a secure, centralized platform to your Workers.  
![Import repo or choose template](https://edgetunnel-b2h.pages.dev/_astro/secrets-store-landing-page.BQoEWsq8_ZUrGq1.webp)  
To spin up your Cloudflare Secrets Store, simply click the new Secrets Store tab [in the dashboard ↗](http://dash.cloudflare.com/?to=/:account/secrets-store) or use this Wrangler command:  
```sh  
wrangler secrets-store store create <name> --remote  
```  
The following are supported in the Secrets Store beta:

  * Secrets Store UI & API: create your store & create, duplicate, update, scope, and delete a secret
  * Workers UI: bind a new or existing account level secret to a Worker and deploy in code
  * Wrangler: create your store & create, duplicate, update, scope, and delete a secret
  * Account Management UI & API: assign Secrets Store permissions roles & view audit logs for actions taken in Secrets Store core platform  
For instructions on how to get started, visit our [developer documentation](https://edgetunnel-b2h.pages.dev/secrets-store/).

Apr 09, 2025
1. ### [Investigate your Workers with the Query Builder in the new Observability dashboard](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-09-qb-workers-logs-ga/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The [Workers Observability dashboard ↗](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/) offers a single place to investigate and explore your [Workers Logs](https://edgetunnel-b2h.pages.dev/workers/observability/logs/workers-logs).  
The **Overview** tab shows logs from all your Workers in one place. The **Invocations** view groups logs together by invocation, which refers to the specific trigger that started the execution of the Worker (i.e. fetch). The **Events** view shows logs in the order they were produced, based on timestamp. Previously, you could only view logs for a single Worker.  
![Workers Observability Overview Tab](https://edgetunnel-b2h.pages.dev/_astro/2025-04-09-workers-observability-overview.BKVvdscp_Z2bR5zE.webp)  
The **Investigate** tab presents a Query Builder, which helps you write structured queries to investigate and visualize your logs. The Query Builder can help answer questions such as:

  * Which paths are experiencing the most 5XX errors?
  * What is the wall time distribution by status code for my Worker?
  * What are the slowest requests, and where are they coming from?
  * Who are my top N users?  
![Workers Observability Overview Tab](https://edgetunnel-b2h.pages.dev/_astro/2025-04-09-query-builder.CaW9IZza_ZBBKf9.webp)  
The Query Builder can use any field that you store in your logs as a key to visualize, filter, and group by. Use the Query Builder to quickly access your data, build visualizations, save queries, and share them with your team.  
#### Workers Logs is now Generally Available  
[Workers Logs](https://edgetunnel-b2h.pages.dev/workers/observability/logs/workers-logs) is now Generally Available. With a [small change](https://edgetunnel-b2h.pages.dev/workers/observability/logs/workers-logs/#enable-workers-logs) to your Wrangler configuration, Workers Logs ingests, indexes, and stores all logs emitted from your Workers for up to 7 days.  
We've introduced a number of changes during our beta period, including:

  * Dashboard enhancements with customizable fields as columns in the Logs view and support for invocation-based grouping
  * Performance improvements to ensure no adverse impact
  * Public [API endpoints ↗](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/observability/) for broader consumption  
The API documents three endpoints: list the keys in the telemetry dataset, run a query, and list the unique values for a key. For more, visit our [REST API documentation ↗](https://edgetunnel-b2h.pages.dev/api/resources/workers/subresources/observability/).  
Visit the [docs](https://edgetunnel-b2h.pages.dev/workers/observability/query-builder) to learn more about the capabilities and methods exposed by the Query Builder. Start using Workers Logs and the Query Builder today by enabling observability for your Workers:

  * [  wrangler.jsonc ](#tab-panel-5163)
  * [  wrangler.toml ](#tab-panel-5164)

**JSONC**  
```jsonc  
{  
  "observability": {  
    "enabled": true,  
    "logs": {  
      "invocation_logs": true,  
      "head_sampling_rate": 1 // optional. default = 1.  
    }  
  }  
}  
```

**TOML**  
```toml  
[observability]  
enabled = true  
  [observability.logs]  
  invocation_logs = true  
  head_sampling_rate = 1  
```

Apr 09, 2025
1. ### [CPU time and Wall time now published for Workers Invocations](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-09-workers-timing/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now observe and investigate the CPU time and Wall time for every Workers Invocations.

  * For [Workers Logs](https://edgetunnel-b2h.pages.dev/workers/observability/logs/workers-logs), CPU time and Wall time are surfaced in the [Invocation Log](https://edgetunnel-b2h.pages.dev/workers/observability/logs/workers-logs/#invocation-logs)..
  * For [Tail Workers](https://edgetunnel-b2h.pages.dev/workers/observability/logs/tail-workers), CPU time and Wall time are surfaced at the top level of the [Workers Trace Events object](https://edgetunnel-b2h.pages.dev/logs/logpush/logpush-job/datasets/account/workers%5Ftrace%5Fevents).
  * For [Workers Logpush](https://edgetunnel-b2h.pages.dev/workers/observability/logs/logpush), CPU and Wall time are surfaced at the top level of the [Workers Trace Events object](https://edgetunnel-b2h.pages.dev/logs/logpush/logpush-job/datasets/account/workers%5Ftrace%5Fevents). All new jobs will have these new fields included by default. Existing jobs need to be updated to include CPU time and Wall time.  
You can use a Workers Logs filter to search for logs where Wall time exceeds 100ms.  
![Workers Logs Wall Time Filter](https://edgetunnel-b2h.pages.dev/_astro/2025-04-09-wall-time-filter.CT-VQyTS_Z97Aoe.webp)  
You can also use the Workers Observability [Query Builder ↗](https://dash.cloudflare.com/?to=/:account/workers-and-pages/observability/investigate) to find the median CPU time and median Wall time for all of your Workers.  
![Query Builder filter](https://edgetunnel-b2h.pages.dev/_astro/2025-04-09-query-builder.CaW9IZza_ZBBKf9.webp)

Apr 08, 2025
1. ### [Local development support for Email Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-local-development/)  
[ Email Service ](https://edgetunnel-b2h.pages.dev/email-service/)  
Email Workers enables developers to programmatically take action on anything that hits their email inbox. If you're building with Email Workers, you can now test the behavior of an Email Worker script, receiving, replying and sending emails in your local environment using `wrangler dev`.  
Below is an example that shows you how you can receive messages using the `email()` handler and parse them using [postal-mime ↗](https://www.npmjs.com/package/postal-mime):

**TypeScript**  
```ts  
import * as PostalMime from "postal-mime";  
export default {  
  async email(message, env, ctx) {  
    const parser = new PostalMime.default();  
    const rawEmail = new Response(message.raw);  
    const email = await parser.parse(await rawEmail.arrayBuffer());  
    console.log(email);  
  },  
};  
```  
Now when you run `npx wrangler dev`, wrangler will expose a local `/cdn-cgi/handler/email` endpoint that you can `POST` email messages to and trigger your Worker's `email()` handler:  
```bash  
curl -X POST 'http://localhost:8787/cdn-cgi/handler/email' \
  --url-query 'from=sender@example.com' \
  --url-query 'to=recipient@example.com' \
  --header 'Content-Type: application/json' \
  --data-raw 'Received: from smtp.example.com (127.0.0.1)  
        by cloudflare-email.com (unknown) id 4fwwffRXOpyR  
        for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000  
From: "John" <sender@example.com>  
Reply-To: sender@example.com  
To: recipient@example.com  
Subject: Testing Email Workers Local Dev  
Content-Type: text/html; charset="windows-1252"  
X-Mailer: Curl  
Date: Tue, 27 Aug 2024 08:49:44 -0700  
Message-ID: <6114391943504294873000@ZSH-GHOSTTY>  
Hi there'  
```  
This is what you get in the console:  
```json  
{  
  "headers": [  
    {  
      "key": "received",  
      "value": "from smtp.example.com (127.0.0.1) by cloudflare-email.com (unknown) id 4fwwffRXOpyR for <recipient@example.com>; Tue, 27 Aug 2024 15:50:20 +0000"  
    },  
    { "key": "from", "value": "\"John\" <sender@example.com>" },  
    { "key": "reply-to", "value": "sender@example.com" },  
    { "key": "to", "value": "recipient@example.com" },  
    { "key": "subject", "value": "Testing Email Workers Local Dev" },  
    { "key": "content-type", "value": "text/html; charset=\"windows-1252\"" },  
    { "key": "x-mailer", "value": "Curl" },  
    { "key": "date", "value": "Tue, 27 Aug 2024 08:49:44 -0700" },  
    {  
      "key": "message-id",  
      "value": "<6114391943504294873000@ZSH-GHOSTTY>"  
    }  
  ],  
  "from": { "address": "sender@example.com", "name": "John" },  
  "to": [{ "address": "recipient@example.com", "name": "" }],  
  "replyTo": [{ "address": "sender@example.com", "name": "" }],  
  "subject": "Testing Email Workers Local Dev",  
  "messageId": "<6114391943504294873000@ZSH-GHOSTTY>",  
  "date": "2024-08-27T15:49:44.000Z",  
  "html": "Hi there\n",  
  "attachments": []  
}  
```  
Local development is a critical part of the development flow, and also works for sending, replying and forwarding emails. See [our documentation](https://edgetunnel-b2h.pages.dev/email-service/local-development/routing/) for more information.

Apr 08, 2025
1. ### [Hyperdrive Free plan makes fast, global database access available to all](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-hyperdrive-free-plan/)  
[ Hyperdrive ](https://edgetunnel-b2h.pages.dev/hyperdrive/)  
Hyperdrive is now available on the Free plan of Cloudflare Workers, enabling you to build Workers that connect to PostgreSQL or MySQL databases without compromise.  
Low-latency access to SQL databases is critical to building full-stack Workers applications. We want you to be able to build on fast, global apps on Workers, regardless of the tools you use. So we made Hyperdrive available for all, to make it easier to build Workers that connect to PostgreSQL and MySQL.  
If you want to learn more about how Hyperdrive works, read the [deep dive ↗](https://blog.cloudflare.com/how-hyperdrive-speeds-up-database-access) on how Hyperdrive can make your database queries up to 4x faster.  
![Hyperdrive provides edge connection setup and global connection pooling for optimal latencies.](https://edgetunnel-b2h.pages.dev/_astro/hyperdrive-global-placement.DHxlaFbz_1MNCXL.webp)  
Visit the docs to [get started](https://edgetunnel-b2h.pages.dev/hyperdrive/get-started/) with Hyperdrive for PostgreSQL or MySQL.

Apr 08, 2025
1. ### [Hyperdrive introduces support for MySQL and MySQL-compatible databases](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-hyperdrive-mysql-support/)  
[ Hyperdrive ](https://edgetunnel-b2h.pages.dev/hyperdrive/)  
Hyperdrive now supports connecting to MySQL and MySQL-compatible databases, including Amazon RDS and Aurora MySQL, Google Cloud SQL for MySQL, Azure Database for MySQL, PlanetScale and MariaDB.  
Hyperdrive makes your regional, MySQL databases fast when connecting from Cloudflare Workers. It eliminates unnecessary network roundtrips during connection setup, pools database connections globally, and can cache query results to provide the fastest possible response times.  
Best of all, you can connect using your existing drivers, ORMs, and query builders with Hyperdrive's secure credentials, no code changes required.

**TypeScript**  
```ts  
import { createConnection } from "mysql2/promise";  
export interface Env {  
  HYPERDRIVE: Hyperdrive;  
}  
export default {  
  async fetch(request, env, ctx): Promise<Response> {  
    const connection = await createConnection({  
      host: env.HYPERDRIVE.host,  
      user: env.HYPERDRIVE.user,  
      password: env.HYPERDRIVE.password,  
      database: env.HYPERDRIVE.database,  
      port: env.HYPERDRIVE.port,  
      disableEval: true, // Required for Workers compatibility  
    });  
    const [results, fields] = await connection.query("SHOW tables;");  
    ctx.waitUntil(connection.end());  
    return new Response(JSON.stringify({ results, fields }), {  
      headers: {  
        "Content-Type": "application/json",  
        "Access-Control-Allow-Origin": "*",  
      },  
    });  
  },  
} satisfies ExportedHandler<Env>;  
```  
Learn more about [how Hyperdrive works](https://edgetunnel-b2h.pages.dev/hyperdrive/concepts/how-hyperdrive-works/) and [get started building Workers that connect to MySQL with Hyperdrive](https://edgetunnel-b2h.pages.dev/hyperdrive/get-started/).

Apr 08, 2025
1. ### [Deploy a Workers application in seconds with one-click](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-deploy-to-cloudflare-button/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now add a [Deploy to Cloudflare](https://edgetunnel-b2h.pages.dev/workers/platform/deploy-buttons/) button to the README of your Git repository containing a Workers application — making it simple for other developers to quickly set up and deploy your project!  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/saas-admin-template)  
The Deploy to Cloudflare button:

  1. **Creates a new Git repository on your GitHub/ GitLab account**: Cloudflare will automatically clone and create a new repository on your account, so you can continue developing.
  2. **Automatically provisions resources the app needs**: If your repository requires Cloudflare primitives like a [Workers KV namespace](https://edgetunnel-b2h.pages.dev/kv/), a [D1 database](https://edgetunnel-b2h.pages.dev/d1/), or an [R2 bucket](https://edgetunnel-b2h.pages.dev/r2/), Cloudflare will automatically provision them on your account and bind them to your Worker upon deployment.
  3. **Configures Workers Builds (CI/CD)**: Every new push to your production branch on your newly created repository will automatically build and deploy courtesy of [Workers Builds](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/).
  4. **Adds preview URLs to each pull request**: If you'd like to test your changes before deploying, you can push changes to a [non-production branch](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/build-branches/#configure-non-production-branch-builds) and [preview URLs](https://edgetunnel-b2h.pages.dev/workers/versions-and-deployments/preview-urls/) will be generated and [posted back to GitHub as a comment](https://edgetunnel-b2h.pages.dev/workers/ci-cd/builds/git-integration/github-integration/#pull-request-comment).  
![Import repo or choose template](https://edgetunnel-b2h.pages.dev/_astro/dtw-user-flow.zgS3Y8iK_Z1r8gDo.webp)  
To create a Deploy to Cloudflare button in your README, you can add the following snippet, including your Git repository URL:  
```md  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=<YOUR_GIT_REPO_URL>)  
```  
Check out our [documentation](https://edgetunnel-b2h.pages.dev/workers/platform/deploy-buttons/) for more information on how to set up a deploy button for your application and best practices to ensure a successful deployment for other developers.

Apr 08, 2025
1. ### [Full-stack frameworks are now Generally Available on Cloudflare Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-fullstack-on-workers/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)[ Workers for Platforms ](https://edgetunnel-b2h.pages.dev/cloudflare-for-platforms/workers-for-platforms/)  
![Full-stack on Cloudflare Workers](https://edgetunnel-b2h.pages.dev/_astro/fullstack-on-workers.D7fotYu2_ZMwDKf.webp)  
The following full-stack frameworks now have Generally Available ("GA") adapters for Cloudflare Workers, and are ready for you to use in production:

  * [React Router v7 (Remix)](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/react-router/)
  * [Astro](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/astro/)
  * [Hono](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/more-web-frameworks/hono/)
  * [Vue.js](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/vue/)
  * [Nuxt](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/more-web-frameworks/nuxt/)
  * [Svelte (SvelteKit)](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/sveltekit/)
  * And [more](https://edgetunnel-b2h.pages.dev/workers/framework-guides/).  
The following frameworks are now in **beta**, with GA support coming very soon:

  * [Next.js](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/nextjs/), supported through [@opennextjs/cloudflare ↗](https://opennext.js.org/cloudflare) is now `v1.0-beta`.
  * [Angular](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/more-web-frameworks/angular/)
  * [SolidJS (SolidStart)](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/more-web-frameworks/solid/)  
You can also build complete full-stack apps on Workers **without a framework**:

  * You can [“just use Vite" ↗](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and React together, and build a back-end API in the same Worker. Follow our [React SPA with an API tutorial](https://edgetunnel-b2h.pages.dev/workers/vite-plugin/tutorial/) to learn how.

**Get started building today with our [framework guides](https://edgetunnel-b2h.pages.dev/workers/framework-guides/)**, or read our [Developer Week 2025 blog post ↗](https://blog.cloudflare.com/full-stack-development-on-cloudflare-workers) about all the updates to building full-stack applications on Workers.

Apr 08, 2025
1. ### [Improved support for Node.js Crypto and TLS APIs in Workers](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-nodejs-crypto-and-tls/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
When using a Worker with the [nodejs\_compat](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/nodejs/) compatibility flag enabled, the following Node.js APIs are now available:

  * [node:crypto](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/nodejs/crypto/)
  * [node:tls](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/nodejs/tls/)  
This make it easier to reuse existing Node.js code in Workers or use npm packages that depend on these APIs.  
#### node:crypto  
The full [node:crypto ↗](https://nodejs.org/api/crypto.html) API is now available in Workers.  
You can use it to verify and sign data:

**JavaScript**  
```js  
import { sign, verify } from "node:crypto";  
const signature = sign("sha256", "-data to sign-", env.PRIVATE_KEY);  
const verified = verify("sha256", "-data to sign-", env.PUBLIC_KEY, signature);  
```  
Or, to encrypt and decrypt data:

**JavaScript**  
```js  
import { publicEncrypt, privateDecrypt } from "node:crypto";  
const encrypted = publicEncrypt(env.PUBLIC_KEY, "some data");  
const plaintext = privateDecrypt(env.PRIVATE_KEY, encrypted);  
```  
See the [node:crypto documentation](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/nodejs/crypto/) for more information.  
#### node:tls  
The following APIs from `node:tls` are now available:

  * [connect ↗](https://nodejs.org/api/tls.html#tlsconnectoptions-callback)
  * [TLSSocket ↗](https://nodejs.org/api/tls.html#class-tlstlssocket)
  * [checkServerIdentity ↗](https://nodejs.org/api/tls.html#tlscheckserveridentityhostname-cert)
  * [createSecureContext ↗](https://nodejs.org/api/tls.html#tlscreatesecurecontextoptions)  
This enables secure connections over TLS (Transport Layer Security) to external services.

**JavaScript**  
```js  
import { connect } from "node:tls";  
// ... in a request handler ...  
const connectionOptions = { key: env.KEY, cert: env.CERT };  
const socket = connect(url, connectionOptions, () => {  
  if (socket.authorized) {  
    console.log("Connection authorized");  
  }  
});  
socket.on("data", (data) => {  
  console.log(data);  
});  
socket.on("end", () => {  
  console.log("server ends connection");  
});  
```  
See the [node:tls documentation](https://edgetunnel-b2h.pages.dev/workers/runtime-apis/nodejs/tls/) for more information.

Apr 08, 2025
1. ### [The Cloudflare Vite plugin is now Generally Available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-08-vite-plugin/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The [Cloudflare Vite plugin](https://edgetunnel-b2h.pages.dev/workers/vite-plugin/) has [reached v1.0 ↗](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and is now Generally Available ("GA").  
When you use `@cloudflare/vite-plugin`, you can use Vite's local development server and build tooling, while ensuring that while developing, your code runs in [workerd ↗](https://github.com/cloudflare/workerd), the open-source Workers runtime.  
This lets you get the best of both worlds for a full-stack app — you can use [Hot Module Replacement ↗](https://vite.dev/guide/features.html#hot-module-replacement) from Vite right alongside [Durable Objects](https://edgetunnel-b2h.pages.dev/durable-objects/) and other runtime APIs and bindings that are unique to Cloudflare Workers.  
`@cloudflare/vite-plugin` is made possible by the new [environment API ↗](https://vite.dev/guide/api-environment) in Vite, and was built [in partnership with the Vite team ↗](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin).  
#### Framework support  
You can build any type of application with `@cloudflare/vite-plugin`, using any rendering mode, from single page applications (SPA) and static sites to server-side rendered (SSR) pages and API routes.  
[React Router v7 (Remix)](https://edgetunnel-b2h.pages.dev/workers/framework-guides/web-apps/react-router/) is the first full-stack framework to provide full support for Cloudflare Vite plugin, allowing you to use all parts of Cloudflare's developer platform, without additional build steps.  
You can also build complete full-stack apps on Workers **without a framework** — ["just use Vite" ↗](https://blog.cloudflare.com/introducing-the-cloudflare-vite-plugin) and React together, and build a back-end API in the same Worker. Follow our [React SPA with an API tutorial](https://edgetunnel-b2h.pages.dev/workers/vite-plugin/tutorial/) to learn how.  
#### Configuration  
If you're already using [Vite ↗](https://vite.dev/) in your build and development toolchain, you can start using our plugin with minimal changes to your `vite.config.ts`:

**vite.config.ts**  
```ts  
import { defineConfig } from "vite";  
import { cloudflare } from "@cloudflare/vite-plugin";  
export default defineConfig({  
  plugins: [cloudflare()],  
});  
```  
Take a look at the [documentation for our Cloudflare Vite plugin](https://edgetunnel-b2h.pages.dev/workers/vite-plugin/) for more information!

Apr 07, 2025
1. ### [Build MCP servers with the Agents SDK](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-mcp-servers-agents-sdk-updates/)  
[ Agents ](https://edgetunnel-b2h.pages.dev/agents/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
The Agents SDK now includes built-in support for building remote MCP (Model Context Protocol) servers directly as part of your Agent. This allows you to easily create and manage MCP servers, without the need for additional infrastructure or configuration.  
The SDK includes a new `MCPAgent` class that extends the `Agent` class and allows you to expose resources and tools over the MCP protocol, as well as authorization and authentication to enable remote MCP servers.

  * [  JavaScript ](#tab-panel-5167)
  * [  TypeScript ](#tab-panel-5168)

**JavaScript**  
```js  
export class MyMCP extends McpAgent {  
  server = new McpServer({  
    name: "Demo",  
    version: "1.0.0",  
  });  
  async init() {  
    this.server.resource(`counter`, `mcp://resource/counter`, (uri) => {  
      // ...  
    });  
    this.server.tool(  
      "add",  
      "Add two numbers together",  
      { a: z.number(), b: z.number() },  
      async ({ a, b }) => {  
        // ...  
      },  
    );  
  }  
}  
```

**TypeScript**  
```ts  
export class MyMCP extends McpAgent<Env> {  
  server = new McpServer({  
    name: "Demo",  
    version: "1.0.0",  
  });  
  async init() {  
    this.server.resource(`counter`, `mcp://resource/counter`, (uri) => {  
      // ...  
    });  
    this.server.tool(  
      "add",  
      "Add two numbers together",  
      { a: z.number(), b: z.number() },  
      async ({ a, b }) => {  
        // ...  
      },  
    );  
  }  
}  
```  
See [the example ↗](https://github.com/cloudflare/agents/tree/main/examples/mcp) for the full code and as the basis for building your own MCP servers, and the [client example ↗](https://github.com/cloudflare/agents/tree/main/examples/mcp-client) for how to build an Agent that acts as an MCP client.  
To learn more, review the [announcement blog ↗](https://blog.cloudflare.com/building-ai-agents-with-mcp-authn-authz-and-durable-objects) as part of Developer Week 2025.  
#### Agents SDK updates  
We've made a number of improvements to the [Agents SDK](https://edgetunnel-b2h.pages.dev/agents/), including:

  * Support for building MCP servers with the new `MCPAgent` class.
  * The ability to export the current agent, request and WebSocket connection context using `import { context } from "agents"`, allowing you to minimize or avoid direct dependency injection when calling tools.
  * Fixed a bug that prevented query parameters from being sent to the Agent server from the `useAgent` React hook.
  * Automatically converting the `agent` name in `useAgent` or `useAgentChat` to kebab-case to ensure it matches the naming convention expected by [routeAgentRequest](https://edgetunnel-b2h.pages.dev/agents/runtime/communication/routing/).  
To install or update the Agents SDK, run `npm i agents@latest` in an existing project, or explore the `agents-starter` project:  
```sh  
npm create cloudflare@latest -- --template cloudflare/agents-starter  
```  
See the full release notes and changelog [on the Agents SDK repository ↗](https://github.com/cloudflare/agents/blob/main/packages/agents/CHANGELOG.md) and

Apr 07, 2025
1. ### [Create fully-managed RAG pipelines for your AI applications with AutoRAG](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-autorag-open-beta/)  
[ AI Search ](https://edgetunnel-b2h.pages.dev/ai-search/)[ Vectorize ](https://edgetunnel-b2h.pages.dev/vectorize/)  
[AutoRAG](https://edgetunnel-b2h.pages.dev/ai-search/) is now in open beta, making it easy for you to build fully-managed retrieval-augmented generation (RAG) pipelines without managing infrastructure. Just upload your docs to [R2](https://edgetunnel-b2h.pages.dev/r2/get-started/), and AutoRAG handles the rest: embeddings, indexing, retrieval, and response generation via API.  
With AutoRAG, you can:

  * **Customize your pipeline:** Choose from [Workers AI](https://edgetunnel-b2h.pages.dev/workers-ai) models, configure chunking strategies, edit system prompts, and more.
  * **Instant setup:** AutoRAG provisions everything you need from [Vectorize](https://edgetunnel-b2h.pages.dev/vectorize), [AI gateway](https://edgetunnel-b2h.pages.dev/ai-gateway), to pipeline logic for you, so you can go from zero to a working RAG pipeline in seconds.
  * **Keep your index fresh:** AutoRAG continuously syncs your index with your data source to ensure responses stay accurate and up to date.
  * **Ask questions:** Query your data and receive grounded responses via a [Workers binding](https://edgetunnel-b2h.pages.dev/ai-search/api/search/workers-binding/) or [API](https://edgetunnel-b2h.pages.dev/ai-search/api/search/rest-api/).  
Whether you're building internal tools, AI-powered search, or a support assistant, AutoRAG gets you from idea to deployment in minutes.  
Get started in the [Cloudflare dashboard ↗](https://dash.cloudflare.com/?to=/:account/ai/autorag) or check out the [guide](https://edgetunnel-b2h.pages.dev/ai-search/get-started/) for instructions on how to build your RAG pipeline today.

Apr 07, 2025
1. ### [Browser Rendering REST API is Generally Available, with new endpoints and a free tier](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-br-free-ga-playwright/)  
[ Browser Run ](https://edgetunnel-b2h.pages.dev/browser-run/)  
We’re excited to announce Browser Rendering is now available on the [Workers Free plan ↗](https://www.cloudflare.com/plans/developer-platform/), making it even easier to prototype and experiment with web search and headless browser use-cases when building applications on Workers.  
The Browser Rendering **[REST API](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/) is now Generally Available**, allowing you to control browser instances from outside of Workers applications. We've added three new endpoints to help automate more browser tasks:

  * **Extract structured data** – Use `/json` to retrieve structured data from a webpage.
  * **Retrieve links** – Use `/links` to pull all links from a webpage.
  * **Convert to Markdown** – Use `/markdown` to convert webpage content into Markdown format.  
For example, to fetch the Markdown representation of a webpage:

**Markdown example**  
```bash  
curl -X 'POST' 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-rendering/markdown' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <apiToken>' \
  -d '{  
    "url": "https://example.com"  
  }'  
```  
For the full list of endpoints, check out our [REST API documentation](https://edgetunnel-b2h.pages.dev/browser-run/quick-actions/). You can also interact with Browser Rendering via the [Cloudflare TypeScript SDK ↗](https://github.com/cloudflare/cloudflare-typescript).  
We also recently landed support for [Playwright](https://edgetunnel-b2h.pages.dev/browser-run/playwright/) in Browser Rendering for browser automation from Cloudflare [Workers](https://edgetunnel-b2h.pages.dev/workers/), in addition to [Puppeteer](https://edgetunnel-b2h.pages.dev/browser-run/puppeteer/), giving you more flexibility to test across different browser environments.  
Visit the [Browser Rendering docs](https://edgetunnel-b2h.pages.dev/browser-run/) to learn more about how to use headless browsers in your applications.

Apr 07, 2025
1. ### [Durable Objects on Workers Free plan](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-durable-objects-free-tier/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
Durable Objects can now be used with zero commitment on the [Workers Free plan](https://edgetunnel-b2h.pages.dev/workers/platform/pricing/) allowing you to build AI agents with [Agents SDK](https://edgetunnel-b2h.pages.dev/agents/), collaboration tools, and real-time applications like chat or multiplayer games.  
Durable Objects let you build stateful, serverless applications with millions of tiny coordination instances that run your application code alongside (in the same thread!) your durable storage. Each Durable Object can access its own SQLite database through a [Storage API](https://edgetunnel-b2h.pages.dev/durable-objects/best-practices/access-durable-objects-storage/). A Durable Object class is defined in a Worker script encapsulating the Durable Object's behavior when accessed from a Worker. To try the code below, click the button:  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/hello-world-do-template)

**JavaScript**  
```js  
import { DurableObject } from "cloudflare:workers";  
// Durable Object  
export class MyDurableObject extends DurableObject {  
  ...  
  async sayHello(name) {  
    return `Hello, ${name}!`;  
  }  
}  
// Worker  
export default {  
  async fetch(request, env) {  
    // Every unique ID refers to an individual instance of the Durable Object class  
    const id = env.MY_DURABLE_OBJECT.idFromName("foo");  
    // A stub is a client used to invoke methods on the Durable Object  
    const stub = env.MY_DURABLE_OBJECT.get(id);  
    // Methods on the Durable Object are invoked via the stub  
    const response = await stub.sayHello("world");  
    return response;  
  },  
};  
```  
Free plan [limits](https://edgetunnel-b2h.pages.dev/durable-objects/platform/pricing/) apply to Durable Objects compute and storage usage. Limits allow developers to build real-world applications, with every Worker request able to call a Durable Object on the free plan.  
For more information, checkout:

  * [Documentation](https://edgetunnel-b2h.pages.dev/durable-objects/concepts/what-are-durable-objects/)
  * [Zero-latency SQLite storage in every Durable Object blog ↗](https://blog.cloudflare.com/sqlite-in-durable-objects/)

Apr 07, 2025
1. ### [SQLite in Durable Objects GA with 10GB storage per object](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-sqlite-in-durable-objects-ga/)  
[ Durable Objects ](https://edgetunnel-b2h.pages.dev/durable-objects/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
SQLite in Durable Objects is now generally available (GA) with 10GB SQLite database per Durable Object. Since the [public beta ↗](https://blog.cloudflare.com/sqlite-in-durable-objects/) in September 2024, we've added feature parity and robustness for the SQLite storage backend compared to the preexisting key-value (KV) storage backend for Durable Objects.  
SQLite-backed Durable Objects are recommended for all new Durable Object classes, using `new_sqlite_classes` [Wrangler configuration](https://edgetunnel-b2h.pages.dev/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class). Only SQLite-backed Durable Objects have access to Storage API's [SQL](https://edgetunnel-b2h.pages.dev/durable-objects/api/sqlite-storage-api/#sql-api) and [point-in-time recovery](https://edgetunnel-b2h.pages.dev/durable-objects/api/sqlite-storage-api/#pitr-point-in-time-recovery-api) methods, which provide relational data modeling, SQL querying, and better data management.

**JavaScript**  
```js  
export class MyDurableObject extends DurableObject {  
  sql: SqlStorage  
  constructor(ctx: DurableObjectState, env: Env) {  
    super(ctx, env);  
    this.sql = ctx.storage.sql;  
  }  
  async sayHello() {  
    let result = this.sql  
      .exec("SELECT 'Hello, World!' AS greeting")  
      .one();  
    return result.greeting;  
  }  
}  
```  
KV-backed Durable Objects remain for backwards compatibility, and a migration path from key-value storage to SQL storage for existing Durable Object classes will be offered in the future.  
For more details on SQLite storage, checkout [Zero-latency SQLite storage in every Durable Object blog ↗](https://blog.cloudflare.com/sqlite-in-durable-objects/).

Apr 07, 2025
1. ### [Capture up to 256 KB of log events in each Workers Invocation](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-increase-trace-events-limit/)  
[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
You can now capture a maximum of 256 KB of log events per Workers invocation, helping you gain better visibility into application behavior.  
All console.log() statements, exceptions, request metadata, and headers are automatically captured during the Worker invocation and emitted as [JSON object](https://edgetunnel-b2h.pages.dev/logs/logpush/logpush-job/datasets/account/workers%5Ftrace%5Fevents). [Workers Logs](https://edgetunnel-b2h.pages.dev/workers/observability/logs/workers-logs) deserializes this object before indexing the fields and storing them. You can also capture, transform, and export the JSON object in a [Tail Worker](https://edgetunnel-b2h.pages.dev/workers/observability/logs/tail-workers).  
256 KB is a 2x increase from the previous 128 KB limit. After you exceed this limit, further context associated with the request will not be recorded in your logs.  
This limit is automatically applied to all Workers.

Apr 07, 2025
1. ### [Workflows is now Generally Available](https://edgetunnel-b2h.pages.dev/changelog/post/2025-04-07-workflows-ga/)  
[ Workflows ](https://edgetunnel-b2h.pages.dev/workflows/)[ Workers ](https://edgetunnel-b2h.pages.dev/workers/)  
[Workflows](https://edgetunnel-b2h.pages.dev/workflows/) is now _Generally Available_ (or "GA"): in short, it's ready for production workloads. Alongside marking Workflows as GA, we've introduced a number of changes during the beta period, including:

  * A new `waitForEvent` API that allows a Workflow to wait for an event to occur before continuing execution.
  * Increased concurrency: you can [run up to 4,500 Workflow instances](https://edgetunnel-b2h.pages.dev/changelog/2025-02-25-workflows-concurrency-increased/) concurrently — and this will continue to grow.
  * Improved observability, including new CPU time metrics that allow you to better understand which Workflow instances are consuming the most resources and/or contributing to your bill.
  * Support for `vitest` for testing Workflows locally and in CI/CD pipelines.  
Workflows also supports the new [increased CPU limits](https://edgetunnel-b2h.pages.dev/changelog/2025-03-25-higher-cpu-limits/) that apply to Workers, allowing you to run more CPU-intensive tasks (up to 5 minutes of CPU time per instance), not including the time spent waiting on network calls, AI models, or other I/O bound tasks.  
#### Human-in-the-loop  
The new `step.waitForEvent` API allows a Workflow instance to wait on events and data, enabling human-in-the-the-loop interactions, such as approving or rejecting a request, directly handling webhooks from other systems, or pushing event data to a Workflow while it's running.  
Because Workflows are just code, you can conditionally execute code based on the result of a `waitForEvent` call, and/or call `waitForEvent` multiple times in a single Workflow based on what the Workflow needs.  
For example, if you wanted to implement a human-in-the-loop approval process, you could use `waitForEvent` to wait for a user to approve or reject a request, and then conditionally execute code based on the result.

  * [  JavaScript ](#tab-panel-5165)
  * [  TypeScript ](#tab-panel-5166)

**JavaScript**  
```js  
import {  
  WorkflowEntrypoint,  
  WorkflowStep,  
  WorkflowEvent,  
} from "cloudflare:workers";  
export class MyWorkflow extends WorkflowEntrypoint {  
  async run(event, step) {  
    // Other steps in your Workflow  
    let stripeEvent = await step.waitForEvent(  
      "receive invoice paid webhook from Stripe",  
      { type: "stripe-webhook", timeout: "1 hour" },  
    );  
    // Rest of your Workflow  
  }  
}  
```

**TypeScript**  
```ts  
import { WorkflowEntrypoint, WorkflowStep, WorkflowEvent } from "cloudflare:workers";  
export class MyWorkflow extends WorkflowEntrypoint<Env, Params> {  
  async run(event: WorkflowEvent<Params>, step: WorkflowStep) {  
    // Other steps in your Workflow  
    let stripeEvent = await step.waitForEvent<IncomingStripeWebhook>("receive invoice paid webhook from Stripe", { type: "stripe-webhook", timeout: "1 hour" })  
    // Rest of your Workflow  
  }  
}  
```  
You can then send a Workflow an event from an external service via HTTP or from within a Worker using the [Workers API](https://edgetunnel-b2h.pages.dev/workflows/build/workers-api/) for Workflows:

  * [  JavaScript ](#tab-panel-5169)
  * [  TypeScript ](#tab-panel-5170)

**JavaScript**  
```js  
export default {  
  async fetch(req, env) {  
    const instanceId = new URL(req.url).searchParams.get("instanceId");  
    const webhookPayload = await req.json();  
    let instance = await env.MY_WORKFLOW.get(instanceId);  
    // Send our event, with `type` matching the event type defined in  
    // our step.waitForEvent call  
    await instance.sendEvent({  
      type: "stripe-webhook",  
      payload: webhookPayload,  
    });  
    return Response.json({  
      status: await instance.status(),  
    });  
  },  
};  
```

**TypeScript**  
```ts  
export default {  
  async fetch(req: Request, env: Env) {  
    const instanceId = new URL(req.url).searchParams.get("instanceId")  
    const webhookPayload = await req.json<Payload>()  
    let instance = await env.MY_WORKFLOW.get(instanceId);  
    // Send our event, with `type` matching the event type defined in  
    // our step.waitForEvent call  
    await instance.sendEvent({type: "stripe-webhook", payload: webhookPayload})  
    return Response.json({  
      status: await instance.status(),  
    });  
  },  
};  
```  
Read the [GA announcement blog ↗](https://blog.cloudflare.com/workflows-is-now-generally-available/) to learn more about what landed as part of the Workflows GA.

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/37/#page","headline":"Changelogs | Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/changelog/37/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/cf-twitter-card.png","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```