Skip to content

Changelog

New updates and improvements at Cloudflare.

Capture PDFs, links, scraped elements, and extracted JSON with /snapshot

Browser Run's /snapshot endpoint can now return four more formats from a single page load: pdf, links, scrape, and json. Before, /snapshot returned HTML, screenshots, Markdown, and the accessibility tree, so a workflow that also needed a PDF or structured data had to prepare the same page again in a second request.

Use the new formats when you need to:

  • PDF: print the page, with the same pdfOptions as the /pdf endpoint.
  • Links: collect the links on the page, with the same visibleLinksOnly and excludeExternalLinks options as /links.
  • Scraped elements: return the elements matched by elements, the same payload as /scrape. elements is required when you request it.
  • Extracted JSON: extract structured data from the page HTML with Workers AI, with the same prompt, response_format, and custom_ai fields as /json. prompt or response_format is required, and the request incurs Workers AI usage.

Request them through formats, the same way as the existing formats. This example returns a PDF, the page links, and the text of each paragraph:

const response = await env.BROWSER.quickAction("snapshot", {
	url: "https://example.com/",
	formats: ["pdf", "links", "scrape"],
	elements: [{ selector: "p" }],
});

const { result } = await response.json();
console.log(result.pdf);
console.log(result.links);
const response = await env.BROWSER.quickAction("snapshot", {
	url: "https://example.com/",
	formats: ["pdf", "links", "scrape"],
	elements: [{ selector: "p" }],
});

const { result } = await response.json();
console.log(result.pdf);
console.log(result.links);

Formats are captured in a fixed order rather than the order of the formats array, and the PDF is printed last because print handlers can change the page. A live page can change between captures, and any format that fails fails the whole request. For JSON snapshots, one actionTimeout budget (default 60 seconds, maximum 120 seconds) covers navigation, captures, retries, and the AI request.

You still need to request at least two distinct formats. If you only need one, use the corresponding single-format endpoint.

Refer to the /snapshot documentation for the full list of accepted values and options.

Autonomous system types on Cloudflare Radar

Cloudflare Radar now shows the type of each autonomous system (AS): Access ISP, Hosting/Cloud/Content, or Organization. AS types are inferred automatically, so an individual AS can be misclassified. They make it easier to tell, for example, whether traffic or attacks come from residential and mobile networks or from data centers.

  • Access ISP (ACCESS_ISP): networks that connect end users, such as home broadband and mobile operators, plus transit providers.
  • Hosting/Cloud/Content (HOSTING_CLOUD_CONTENT): hosting providers, cloud platforms, and content delivery networks.
  • Organization (ORGANIZATION): enterprises, universities, governments, banks, and IXP route servers.

ASes without a type are shown as Unclassified. To report a wrong AS type, email radar@cloudflare.com.

Chart of HTTP traffic from the top five ASes beside a table of the top ten, with house, cloud, and building icons before the AS numbers

Top ASes by HTTP traffic in Portugal ↗︎, with the type of each AS shown before its number.

Radar pages

  • AS pages, such as AS7922 ↗︎, show the AS type in the AS information card.
  • An icon before the AS number shows its type across Radar. Hover over the icon to see the AS type.
  • The Data Explorer ↗︎ can break down and filter HTTP, NetFlows, DNS, and layer 7 attack data by AS type.
AS information card listing the AS type as Access ISP, above a table of related ASes with house, cloud, and building icons

The AS type in the AS7922 ↗︎ information card.

Line chart of HTTP requests by AS type, scaled from zero to the maximum, where Access ISP stays well above Hosting/Cloud/Content and Organization stays near zero. A bar below shows Access ISP at 66% and Hosting/Cloud/Content at 33% of requests

Worldwide HTTP requests by AS type over the last four weeks, from the Data Explorer ↗︎.

API

  • The Get AS details, List ASes, and Get AS details by IP address endpoints return a new category field with the AS type, or null when the AS is not classified.
  • The HTTP, NetFlows, DNS, and layer 7 attacks endpoints accept a new asCategory filter, and their summary and timeseries groups endpoints support a new AS_CATEGORY dimension. Both accept ACCESS_ISP, HOSTING_CLOUD_CONTENT, ORGANIZATION, and UNCLASSIFIED, where UNCLASSIFIED also covers traffic that could not be mapped to an AS. For HTTP, they are supported for date ranges starting on or after 2023-05-01.
  • The global search endpoint returns an entity with details of the matched AS, including its category, for AS results, and of the matched region for region (adm1 and adm2) results.

For example, to get the share of HTTP requests by AS type in the last week:

Get HTTP requests summary by dimensionbash
curl "https://api.cloudflare.com/client/v4/radar/http/summary/AS_CATEGORY?dateRange=7d" \
	--request GET \
	--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"

Visit an AS page ↗︎ on Cloudflare Radar to see its type, or read the AS type definitions.

Redesigned Spectrum dashboard

The Spectrum pages in the Cloudflare dashboard have been redesigned. Your existing applications and their settings do not change.

The Spectrum Applications page lists each application's type, edge port, origin, and edge IP type, with the last minute of connections, ingress, and egress. You can search the list and sort it by column.

Creating or editing an application now opens a full page instead of a modal, with settings grouped into Application Configuration, Origin Configuration, and Advanced Options. To edit an application, select its hostname, or select the three dots next to it > Edit.

You can now create and edit applications that use static IPs or BYOIP addresses in the dashboard. Under Edge IP Type, select Dedicated IPs. Leave Subdomain blank to create an application on the zone apex.

New TCP and UDP applications created in the dashboard now have IP Access Rules turned off by default, which matches the API default. To enforce IP Access rules for an application, turn on IP Access Rules under Advanced Options. Existing applications keep their current setting.

To create your first application, refer to Get started with Spectrum.

To share feedback on the redesigned dashboard, complete this form ↗︎.

B-frame detection for Low-Latency HLS live streams

Cloudflare Stream now emits a warning when B-frames are detected in Low Latency HLS live broadcasts.

The most common cause of freezing and stuttering in LL-HLS live streams is when encoders include B-frames. These frames can reference content that has not yet been transmitted, stalling preparation for delivery. Therefore, B-Frames are not supported when LL-HLS is enabled for a live input.

Stream sends the warning ERR_LIVE_INPUT_LLHLS_INCOMPATIBLE once per live session if applicable. It is reported alongside other error and status events in:

To resolve the warning, turn off B frames in your broadcast application settings. Alternatively, turn off Low-Latency HLS in your live input settings, but playback latency will be higher.

For more information, refer to Stream live troubleshooting.

Workers and Pages now keep versions for 30 days

Cloudflare now keeps versions of your Workers and deployments of your Pages projects for 30 days. After 30 days, they are deleted, except your 100 most recent and what is currently deployed.

What is not affected:

  • Running applications: Deployed Worker versions and your current Pages production deployment are always kept
  • Rollbacks: You can still roll back to any of your 100 most recent Worker versions, and to any Pages production deployment that has not been deleted
  • Worker Previews: Worker Preview URLs always serve the latest deployment of that Preview. Use Worker Previews for branches and pull requests instead of Version URLs, which run with your production bindings

What you will notice:

  • Deleted versions and deployments no longer appear in the dashboard or API
  • The URL associated with each deleted Worker version, known as its Version URL (including any --preview-alias), stops working, as does the preview URL of each deleted Pages deployment

For more information, refer to Workers version retention, Pages deployment limits, and Compare workflows.

Automatically retrieve SAML IdP signing certificates

Cloudflare Access can retrieve signing certificates from a SAML identity provider's metadata endpoint. Your IdP can publish replacement certificates without requiring you to upload each one to Access.

In your generic SAML identity provider configuration, set Signing certificate source to Fetch certificates from IdP metadata and enter the IdP metadata URL. The endpoint must return SAML metadata XML over public HTTPS, without authentication or redirects. It must not return a JSON Web Key Set (JWKS).

For API configurations, use metadata_url instead of manual certificate fields:

{
	"type": "saml",
	"config": {
		"issuer_url": "https://idp.example.com",
		"sso_target_url": "https://idp.example.com/sso",
		"metadata_url": "https://idp.example.com/metadata.xml"
	}
}

Access caches the certificates and does not poll the endpoint.

Removing a compromised certificate from metadata does not immediately revoke the cached certificate or existing Access sessions. For setup, planned rotation, and emergency replacement guidance, refer to Discover IdP signing certificates.

Attach images, PDFs, and text files to Agent Lee

You can now attach files to a message in Agent Lee. Share a screenshot of an error, a PDF, or a log, HAR, or configuration file, and Agent Lee reads it as part of your question.

Previously, you had to describe what you were seeing or paste file contents into the chat by hand. A screenshot of a dashboard error or a long log was hard to get across that way.

How it works

  • Select the paperclip next to the message box, paste an image, or drag files onto the chat panel.
  • Each file appears as a chip above the message box. Remove any you did not mean to add, then send your message.
  • Agent Lee reads images directly, converts PDFs to text and reads them from the start, and reads text files in full or, for long files, from the start and the end.

Example requests:

  • "Here is a screenshot of the error I get when I open my site. What is wrong?"
  • "This HAR file is from a slow page load. Which requests are taking the longest?"
  • "Here is the error log from my Worker. What is causing these failures?"

Good to know

  • Supported files. PNG, JPEG, and WebP images up to 3.5 MiB, PDFs up to 5 MiB, and text files (.txt, .log, .json, .har, .csv, .yaml, .yml, .toml, .md, .xml) up to 100 MiB. You can attach up to four files per message, up to 14 MiB in total after trimming.
  • Text files are trimmed in your browser. A text file over 1 MiB (2 MiB for JSON, HAR, YAML, TOML, and XML) keeps its first and last lines. HAR files are always compacted before sending: request and response bodies and cookies are removed, and credential headers such as Authorization and Cookie are replaced with [redacted].
  • Scanned PDFs are not read. Agent Lee reads the text in a PDF. A PDF that is only scanned images, with no text layer, cannot be read.
  • Older attachments age out. Agent Lee keeps attachments from your most recent messages in view. Attach a file again to bring an older one back into the conversation.
  • Attachments are stored with the conversation. When an attachment ages out, it is removed from the stored conversation. Do not attach files that contain passwords, API tokens, or other secrets. For how Agent Lee uses your data, refer to Data usage.

Agent Lee remains in beta. Features and behaviors may change as the product evolves.

For details, refer to Agent Lee.

A new, consistent language across Images interfaces

Cloudflare Images lets you dynamically compose, manipulate, and encode images using a broad set of optimizations, including resizing, face cropping, and background removal. You can configure optimizations directly in an image URL or programmatically through the cf.image options on a Worker fetch() subrequest.

We redesigned the Images API to provide a consistent, predictable, and intuitive language for developers and AI agents to optimize and manipulate images.

Starting today, the URL interface and cf.image options in Workers use the same parameter structure to apply optimizations. A configurable optimization will have its corresponding settings nested underneath its top-level parameter. Existing syntax in URLs and Worker configurations continues to behave as before.

This release also makes adding borders and overlays available in the URL interface. For example, you can now add a logo or text watermark directly in the URL instead of writing a Worker.

What changed

Optimization parameters are now represented in one of two ways: a compact form for single values and a structured form for related settings.

For example, width=500 requests an exact width, while trim=color asks Images to automatically trim the sides of an image based on its border color. Color-based trimming already supports configuring the border color, tolerance, and retained edge; these settings were previously applied as separate top-level parameters:

Old Images interface with trim settings as separate top-level parameters

Related trim settings appeared alongside independent parameters such as width.

The new structure groups existing settings under a single top-level trim parameter:

New Images interface with trim settings as nested settings

Related trim settings are nested, while width=250 remains a top-level parameter.

In the URL interface, color-based trimming uses the following syntax:

trim=(mode=color,color=red,tolerance=10,keep=5)

The same hierarchy maps directly to cf.image in Workers, where related values that were previously separate or inferred now live in the same object. The structured object uses mode to explicitly identify the selected behavior, while the remaining properties configure that behavior:

trim: {
	mode: "color",
	color: "white",
	tolerance: 10,
	keep: 5
}

A unified parameter model

In Images, optimizations are expressed as parameters, which form the language used to describe every optimization and its intended behavior. width sets the output width, gravity identifies the area that a crop should preserve, and draw defines how image or text overlays are rendered.

Many optimization features began as scalar parameters, pairing a parameter key with one value, such as width=500. As we introduced more capabilities, some parameters gained settings to configure how the optimization worked, such as automatic width selection. We added syntax to support each use case, gradually accumulating different forms for expressing related settings.

A given optimization might follow multiple conventions for different behaviors. For example, color-based trimming relied on separate dotted parameters, while side-based trimming encoded the top, right, bottom, and left settings as four unlabeled positional values:

trim=border,trim.border.color=white,trim.border.tolerance=10,trim.border.keep=5
trim=10;20;10;20

None of these forms were especially challenging in isolation. But together, they required developers to learn several parameter models and agents to infer the relationships between parameters and their settings to produce the correct syntax for each interface.

In the new structure, the Images API distinguishes between two core concepts: A parameter identifies an optimization feature, while a setting configures how that feature behaves.

The compact form continues to assign one value directly to a parameter. When an optimization has configurable behavior, the structured form organizes named settings, lists, and nested groups beneath the parameter, making the relationship between the optimization and its configuration explicit.

The unified parameter model follows these rules:

  • A parameter that needs one value uses the compact form. When the relationship is unambiguous, existing forms like width=500, width=auto (with default settings), and gravity=auto continue to work with the same syntax.
  • A parameter with configurable behavior groups its settings beneath the top-level parameter. When a parameter supports multiple behaviors, the mode setting identifies the selected behavior. Without mode, an expression such as width=(desktop=1400) would require Images to infer auto from the presence of desktop.
  • Across interfaces, groups and lists follow the same nesting rules. A grouped URL parameter maps to an object in cf.image, while a URL list maps to an array. Previously, each feature needed a separate representation and translation rules for each interface. The shared hierarchy eliminates structural drift by using the same vocabulary and relationships in both interfaces.

For developers, a standard form for configuring parameters means fewer special-case conventions to remember and less translation between interfaces. Related settings stay together and a configuration expressed in a URL maps predictably to its cf.image object.

How this affects existing optimizations

The new structure is available for existing optimization features whose settings previously used separate top-level parameters, dotted names, or positional values. It also brings two previously Workers-only capabilities, borders and overlays, to the URL interface.

Use the new structured form to express the following optimizations and capabilities:

Optimization What it does What changed
border Adds a border around the image. Now supported in the URL interface. Previously, this was available only in Workers.
draw Adds an image or text overlay to the source image. Now supported in the transformation URL interface for remote images. Previously, this was available only in Workers.
gravity coordinates Sets the focal point using relative x and y coordinates. Uses named x and y settings in the URL interface.
quality Controls the compression quality of the output image. Groups the default quality and the quality for slow connections beneath quality.
trim Removes pixels around the sides of an image. Uses named settings beneath trim for individual sides, rectangular areas, and border-color detection.
upscale Controls the algorithm used when an image is enlarged. Configured as the upscale setting beneath fit, alongside the selected mode.
width=auto Automatically selects an appropriate output width using available information about the browser and device. Uses named settings under the width parameter for mobile, desktop, and breakpoint widths.

These structured forms are additive. Earlier forms, including gravity=0.5x0.3, dotted trim parameters, and separate top-level parameters continue to work.

Refer to Features for the complete reference of optimization features.

WAF Emergency Release - 2026-11-18

This release introduces 6 new malformed base64 Cloudflare Managed Ruleset detections for Java4Shell CVE-2026-114938. The rules are being deployed in log mode by default (in lieu of False Positive risk) and can be overridden if needed with supplementary information around the same available through blog post How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) ↗︎.

RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
Cloudflare Managed RulesetN/AJava4Shell - Malformed Base64 Header - CVE-2026-114938N/ALogThis is a new detection.
Cloudflare Managed RulesetN/AJava4Shell - Malformed Base64 Query Value - CVE-2026-114938N/ALogThis is a new detection.
Cloudflare Managed RulesetN/AJava4Shell - Malformed Base64 Body Value - CVE-2026-114938N/ALogThis is a new detection.
Cloudflare Managed RulesetN/AJava4Shell - Malformed Base64 Path Segment - CVE-2026-114938N/ALogThis is a new detection.
Cloudflare Managed RulesetN/AJava4Shell - Malformed Base64url JWT Component - CVE-2026-114938N/ALogThis is a new detection.
Cloudflare Managed RulesetN/AJava4Shell - Malformed Base64 WebAuthn Value - CVE-2026-114938N/ALogThis is a new detection.

Custom CA and client certificates (mTLS) for Workers VPC

VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with verify_ca or disabled, and origins that required client certificates were unreachable.

Upload your CA certificate and client certificate, then reference them from the TLS settings of a VPC Service:

npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca
npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client

npx wrangler vpc service create private-db \
  --type tcp \
  --tcp-port 5432 \
  --app-protocol postgresql \
  --hostname db.internal.example \
  --tunnel-id <TUNNEL_ID> \
  --certificate-authority <CA_CERTIFICATE_ID> \
  --client-certificate <CLIENT_CERTIFICATE_ID> \
  --cert-verification-mode verify_full

You can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle.

You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later.

For details, refer to Custom CA and client certificates.

AI Search can generate file summaries during indexing

AI Search can now summarize your files while it indexes them. For each text document that produces at least three chunks, AI Search uses a large language model (LLM) to generate a summary, topics, and keywords:

  • The summary and keywords are stored in the item's context metadata. A context value you already set is kept.
  • The topics are added to the context header of the file's chunks to help retrieval.

Turn on file summaries in the dashboard, or set indexing_options.file_summary to true when you create or update an instance. File summaries are off by default, and changing the setting triggers a full reindex.

indexing_options is replaced as a whole on every update. Include the current value of every option, or the options you leave out return to their defaults.

The LLM costs are billed to your account. File summaries are not part of the AI Search ingestion allotment. AI Search uses a Workers AI model suited to summarization and calls it through your instance's AI Gateway, or the default gateway if none is set, and the calls are billed as Workers AI usage. Each new or modified file is summarized once, so costs grow with the amount of content you index.

For more information, refer to File summaries.

Cloudflare CLI (cf) 1.0 release candidate

Cloudflare CLI (cf) 1.0.0-rc.1 is a release candidate for cf 1.0. cf has been in beta since late September. This is the release we recommend you try on your own projects, and we want your feedback before 1.0.

To install or update to the latest release:

npm install --global cf@latest

What is stable

We expect the following features to remain stable to cf 1.0:

  • The cloudflare.config.ts configuration format.
  • The Build Output format that cf build writes and cf deploy reads.
  • The commands that create, develop, build, and deploy projects, including cf init, cf dev, cf build, cf deploy, cf previews deploy, and cf workers versions create.
  • The large majority of commands generated from the Cloudflare API and used in the beta.

A small number of less commonly used API commands may still change before 1.0. cf generates these commands from the Cloudflare API schema, so their call path may still change before 1.0.

Upgrade from a beta

This release moves Build Output to version 1, in .cloudflare/output/v1/. cf deploy will automatically create a new build on first run in this location.

The release candidate also moves to caret (^) version ranges for its dependencies, requiring:

  • @cloudflare/vite-plugin 2.0.0-rc.0 or later, for projects that build with Vite.
  • Wrangler 4.163.0 or later, for legacy projects that build with Wrangler.

1.0.0-rc.1 renames a few generated API commands without aliases. For example, cf workers secrets bulk is now cf workers secrets bulk-edit. For the full list, refer to the release notes ↗︎.

If you last updated early in the beta, these earlier changes may also affect you:

  • Prompts, progress, and status messages are written to stderr. Stdout holds only command output, so scripts that read messages from stdout must read stderr instead.
  • Commands generated from camelCase or snake_case API names use kebab-case. For example, cf accounts billing getCredits is now cf accounts billing get-credits.
  • cf previews deploy takes the Preview name as --preview-name instead of a positional argument.
  • Commands run with --local store state in the project's .cloudflare/state directory.
  • cf no longer saves your account choice between runs. Set accountId in cloudflare.config.ts or CLOUDFLARE_ACCOUNT_ID to skip the prompt.
  • Streaming tail consumers move to experimental.streamingTailConsumers in cloudflare.config.ts.
  • Destructive commands run without a terminal exit with an error unless you pass --force.
  • cf supports the latest versions of the Node.js LTS releases and the latest active release of Node.js.

Stream live logs

cf observability tail streams live logs and other observability events as newline-delimited JSON. Select a Worker with --worker, a zone and its subdomains with --zone, or every event in the account with --all. Narrow the results with --filters, as inline JSON or from a file:

cf observability tail --worker my-worker
cf observability tail --worker my-worker --filters @filters.json

Worker events require Workers Logs to be turned on for the Worker. For filter shapes and examples, run cf observability tail --help.

What changed during the beta

Deploy

  • Deploy a directory of static assets with cf deploy ./dist. cf skips the build step and creates an assets-only Worker.
  • cf deploy --no-provision fails when a binding has no resource ID, instead of creating a new resource.
  • cf deploy --force deploys when the Worker was last deployed through the API, or when its remote configuration conflicts with your local Build Output.
  • Redeploying no longer removes secrets that you added outside cloudflare.config.ts.
  • Stack traces from deployed Workers show project paths such as src/index.ts.
  • Python Workers with vendored packages deploy correctly.
  • cf deploy applies SSH settings for Containers managed by Durable Objects.
  • cf deploy --dry-run shows the project setup changes it would make, without making them.
  • Set CLOUDFLARE_DEPENDENCIES_INSTRUMENTATION=false to stop uploading package dependency metadata with each deployment.

Develop

  • cf init creates new Worker projects with Vite+, including checks, formatting, and tests that run in the Workers runtime.
  • cf dev and cf build run the Vite or Vite+ executable installed in your project, including dependencies hoisted in a workspace.
  • cf dev passes arguments such as --port and --host to your framework's development server.
  • cf dev --profile <name> passes the selected authentication profile to your development server.
  • cf dev, cf build, and cf deploy offer to run cf migrate when they find a Wrangler configuration file.
  • On Windows, Ctrl+C exits cleanly when your framework runs through npm, Wrangler and Vite start without spawn EFTYPE errors, and cf d1 migrations create rejects names that Windows cannot store.
  • cf init approves the build scripts that pnpm 11 and later block by default, so installation succeeds.

Sign in and accounts

  • Pass --temporary-account to create a short-lived account without signing in. cf prints a URL you can use to claim the account.
  • cf auth login summarizes the scopes you granted, and cf auth scopes lists them by product.
  • cf auth whoami, also available as cf whoami, prints a short summary in a terminal and full JSON for scripts and agents.
  • cf auth login now uses the system keyring where available.
  • Long-running commands, such as cf observability tail, refresh an expired OAuth login instead of failing.
  • cf auth whoami reports the status of scoped API tokens correctly.
  • Set CLOUDFLARE_API_HEADERS to send custom headers with API requests.

API commands

  • Every command accepts --dry-run to preview what it would do and it redacts sensitive fields in request previews.
  • cf checks --body input before it asks you to sign in or confirm, and rejects array bodies larger than the API allows instead of splitting them across several requests.
  • More request fields are available as flags, including JSON objects and maps, arrays of objects, and file uploads. For example, cf pages deployments create --worker-js @./_worker.js and cf ai to-markdown --files @first.html @second.pdf.
  • Error outputs have been improved with additional messages the API returns, such as the names of missing parameters.
  • cf workers commands accept --worker to select a Worker.
  • --zone finds zones by name in accounts with many zones.
  • cf tunnels quick-start --allowed-mail limits a temporary tunnel to the email addresses and domains you allow.

Scripts and agents

  • cf --version prints only the version number.
  • Shell completions and cf tools list every flag a command accepts.
  • cf cli search has reranked cf deploy and other key commands to improve their ranking for static site and Pages deployment searches.
  • cf docs search finds Cloudflare documentation from the terminal.

Send feedback

To report a bug or tell us what is missing, open an issue in the cf repository ↗︎. For every change in each release, refer to the Cloudflare CLI release notes ↗︎.

Configure a separate WAN gateway for each appliance in a high availability site

You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway.

  • In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address.
  • In the API, set static_addressing.secondary_gateway_address when you create or update a WAN. To remove the value with a PATCH request, set it to null.

The field is optional. If you leave it blank, the secondary appliance uses the primary gateway address, which matches how HA sites worked before. You can only use this field on sites in HA mode.

curl --request PATCH \
https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id} \
--header "Authorization: Bearer <API_TOKEN>" \
--header "Content-Type: application/json" \
--data '{
	"static_addressing": {
		"address": "203.0.113.2/30",
		"gateway_address": "203.0.113.1",
		"secondary_address": "198.51.100.2/30",
		"secondary_gateway_address": "198.51.100.1"
	}
}'

For details, refer to About high availability configurations.

Optimize original TIFF files with Images

Cloudflare Images lets you optimize images for web delivery while storing only the original, high-resolution version. With Images, you can dynamically serve compressed and resized versions in the most efficient format for the requesting browser.

Starting today, Images accepts TIFF as an input format.

In publishing and e-commerce, TIFF is widely deployed as a master format for product photography, high-resolution scans, print assets, and archival collections. TIFF is a mature format, but it has limited support in modern browsers and tends to produce larger files than formats optimized for web delivery.

You can dynamically transcode original TIFF files to formats such as WebP or AVIF. These formats offer more efficient compression, which can reduce file sizes and improve page load performance. You can also resize each output without converting or modifying your original image.

For multi-page TIFF files, Images decodes only the first page. For supported formats and limits, refer to Limits and formats.

Investigate user risk events in a timeline

User Risk Scoring now groups risk behavior instances in a timeline. Each group highlights its trigger and shows later detections in time order.

User risk timeline showing a trigger, subsequent detections, and a date range selector

Customize the date range to focus on the events you want to investigate. Select a timeline marker to view its events. The sequence helps security teams follow how risk events relate during investigations.

Switch to Table to return to the existing table view whenever you prefer.

User Risk Scoring is available on Enterprise plans.

For more information, refer to User risk score.

Artifacts now supports local development

You can now develop and test Artifacts locally. Create repos, import Git repositories over HTTPS, issue repo tokens, and clone or push with Git on your machine before deploying to Cloudflare's global network. Local repos are separate from your deployed repos, so you can test changes without affecting production data.

Local repos also emit the same Artifacts events as production when a repo is created, imported, forked, or deleted, or when a repo token is created or revoked. This lets you test the Workflows that react to them before you deploy.

To use local repos when you run your Worker locally, add an Artifacts binding to your Wrangler configuration file:

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "name": "artifacts-worker",
  "main": "src/index.ts",
  // Set this to today's date
  "compatibility_date": "2026-11-19",
  "artifacts": [
    {
      "binding": "ARTIFACTS",
      "namespace": "default"
    }
  ]
}
name = "artifacts-worker"
main = "src/index.ts"
# Set this to today's date
compatibility_date = "2026-11-19"

[[artifacts]]
binding = "ARTIFACTS"
namespace = "default"

Run npx wrangler dev, then use the binding the same way you would in production:

const created = await env.ARTIFACTS.create("starter-repo");

return Response.json({
	remote: created.remote,
	token: created.token,
});
const created = await env.ARTIFACTS.create("starter-repo");

return Response.json({
	remote: created.remote,
	token: created.token,
});

The returned remote points to your local dev session, so you can use it with a standard Git client to clone and push.

Local development requires the latest version of Wrangler and Git 2.32 or later on your PATH.

When you develop with npx wrangler dev, the Cloudflare Vite plugin, or the Workers Vitest integration, Artifacts bindings use the local simulator by default. To use your deployed repos instead, set remote = true on the binding.

To learn more, refer to Local development.

Cloudflare One adds Periodic Beaconing Traffic detection

Cloudflare One now includes Periodic Beaconing Traffic as a risk behavior. It analyzes Gateway HTTP traffic for regular check-ins to the same destination.

Cloudflare flags a user after more than 30 contacts to the same destination in six hours. Contacts must be evenly spaced, from 10 seconds to about 12 minutes apart. Few other users in your organization contact that destination.

Detection uses traffic behavior only. It does not use threat intelligence, categories, or reputation. Malware can check in with a command-and-control (C2) server this way, but legitimate software also checks in regularly. Treat each event as a lead to investigate, not proof that a destination is C2.

By default, the behavior is off and its risk level is Info. To turn it on, go to Risk score > Risk behaviors. Cloudflare reports a continuing beacon once. Events usually arrive 3 to 6 hours after the six-hour window closes.

Periodic Beaconing Traffic is available on Enterprise plans.

Browser Run Quick Actions now work in local development

You can now test Browser Run Quick Actions locally. Under npx wrangler dev, the browser binding's .quickAction() method runs against a Chrome instance on your machine. Before, .quickAction() worked only in remote mode, and local calls failed with The RPC receiver does not implement the method "quickAction".

For details, refer to Test Quick Actions locally.

Manage AI Search instances in any namespace with Terraform

Starting with Cloudflare Terraform provider ↗︎ v5.29.0, you can manage AI Search instances in any namespace, not only default.

The cloudflare_ai_search_instance resource has a new namespace argument. It defaults to default, so existing configurations keep managing the same instances.

resource "cloudflare_ai_search_namespace" "support" {
  account_id = var.account_id
  name       = "support"
}

resource "cloudflare_ai_search_instance" "docs" {
  account_id = var.account_id
  id         = "docs"
  namespace  = cloudflare_ai_search_namespace.support.name
}

You can import existing instances and namespaces:

terraform import cloudflare_ai_search_instance.docs <account_id>/support/docs
terraform import cloudflare_ai_search_namespace.support <account_id>/support

The data sources read instances from the namespace you set:

data "cloudflare_ai_search_instance" "docs" {
  account_id = var.account_id
  namespace  = "support"
  id         = "docs"
}

data "cloudflare_ai_search_instances" "support" {
  account_id = var.account_id
  namespace  = "support"
}

When you upgrade to v5.29.0, review these changes:

  • The cloudflare_ai_search_instance import ID now includes the namespace: <account_id>/<namespace>/<id>. For instances in the default namespace, use <account_id>/default/<id>.
  • The cloudflare_ai_search_instance and cloudflare_ai_search_instances data sources require namespace. Set namespace = "default" for instances in the default namespace.
  • cloudflare_ai_search_instances returns the instances in one namespace. The filter.namespace argument of cloudflare_ai_search_instance is removed.
  • Changing namespace replaces the instance.

Set spending limits for Workers and Durable Objects

You can now set spending limits for Workers and Durable Objects to help control unexpected usage costs, or receive email alerts while your applications keep running. Support for more products is coming soon.

Use these controls alongside AI Gateway spend limits to manage compute and AI inference costs across your application. AI Gateway supports per-user and per-model budgets for Workers AI and other AI providers, applied to requests routed through your gateway.

Workers and Durable Objects limits apply across your account for the current subscription billing period. Each product has its own spending controls.

Set your limits and alerts

In the Cloudflare dashboard ↗︎, select your account and go to Billing > Spend limits. Choose a spending limit, notification email, and alert thresholds for Workers or Durable Objects.

For example, configure a $10 Workers spending limit with email alerts at $5 and $9. To receive alerts while your applications keep running, turn off Block usage.

Workers controls with usage blocking at $10, a notification email, and alert thresholds at $5 and $9.

See when a limit takes effect

The overview shows each product's recorded spend, alert thresholds, and pause status. Email alerts notify you without stopping usage. When a spending limit takes effect, Cloudflare blocks the product's supported operations.

Spend limits overview with Workers marked Services paused and separate spend and threshold indicators for Durable Objects.

To resume usage, raise the limit above current spend, turn it off, or remove it. Usage also resumes when the next billing period starts.

Usage reporting and blocking take time, so recorded spend can exceed a limit. Read about what counts toward a limit.

Choose alerts, limits, or both

For example, set a $50 spending limit for Workers and a $20 email alert for Durable Objects:

flowchart LR
    A["Durable Objects reaches $20"] --> B["Email alert sent"]
    B --> C["Usage continues"]
    D["Workers reaches $50"] --> E["Spending limit takes effect"]
    E --> F["New Worker invocations blocked"]

Set a spending limit with the cf CLI

Install the cf CLI and select your account, then run this command to set a $50 spending limit for Workers usage in the current billing period:

cf billing spend-policies create \
  --name 'Workers $50 spending limit' \
  --product-id workers \
  --enabled true \
  --threshold-cents 5000 \
  --action usage_block

The amount is in US cents: 5000 means $50. To set a spending limit for Durable Objects, use --product-id durable_objects and update the name. Limits count usage already recorded in the current billing period.

You can also give this prompt to your coding agent. It will ask which product you want to manage and what spending limit to set, then use the CLI to configure it.

Use spending limits alongside budget alerts

The budget alerts introduced earlier this year notify you about account-wide usage costs without stopping usage. You can keep using them alongside the new product-specific spending limits and email alerts for Workers and Durable Objects.

To configure account-wide alerts, go to Billing > Billable Usage or follow the budget alerts guide.

Read the spending limits and alerts guide to learn how spending limits work and manage limits and alerts through the dashboard or cf CLI.

AI Search supports D1 databases as a data source (beta)

AI Search can now use a D1 database as a data source. AI Search runs a read-only query that you provide and indexes each returned row as a separate document. Scheduled syncs keep the index current as rows are added, changed, or removed.

Create D1-backed instances from the dashboard, the REST API, or the Workers binding.

Selecting a D1 database as the data source when creating an AI Search instance in the dashboard
curl -X POST "https://api.cloudflare.com/client/v4/accounts/<ACCOUNT_ID>/ai-search/namespaces/default/instances" \
  -H "Authorization: Bearer <API_TOKEN>" \
  -H "Content-Type: application/json" \
  --data '{
    "id": "help-center",
    "type": "d1",
    "source": "<D1_DATABASE_ID>",
    "token_id": "<SERVICE_TOKEN_ID>",
    "source_params": {
      "d1": {
        "query": "SELECT article_id AS id, title, content, category AS meta_category\nFROM articles\nWHERE published = 1"
      }
    }
  }'

Learn more in D1 data source.

Kitesurf is now open source

Kitesurf ↗︎, Cloudflare's browser engine for AI agents, is now open source on GitHub ↗︎ under the Apache 2.0 license. You can inspect the source, run it locally, and deploy your own instance to your Cloudflare account.

Kitesurf runs entirely on Cloudflare Workers. It parses HTML, applies CSS, executes page JavaScript, and renders screenshots without a browser container. It supports the Chrome DevTools Protocol (CDP), so you can connect clients such as Puppeteer.

Kitesurf is still experimental and under heavy development. The team continues to improve web standards support, rendering fidelity, and performance.

Run locally or deploy to your account

Developers can run Kitesurf locally with Wrangler. After following the build requirements and setup instructions ↗︎, run pnpm run dev. This builds the engine and starts wrangler dev.

To run your own instance on Cloudflare, follow the deployment instructions ↗︎. Protect your deployment with Cloudflare Access or another authentication layer. Kitesurf does not provide built-in authentication.

Contribute and follow progress

Contributions and pull requests are welcome. The team remains focused on compatibility, reliability, and performance, with limited review capacity. Keep changes focused and follow the contribution guidelines ↗︎, including opening an issue and getting vouched by a maintainer before submitting a pull request.

Visit kitesurf.dev ↗︎, the main Kitesurf website and playground. Track Web Platform Tests (WPT) progress ↗︎ and performance benchmarks ↗︎ as development continues.

For background and technical details, refer to the introductory blog post ↗︎ and the Kitesurf update ↗︎. To use Kitesurf through Browser Run, refer to the Kitesurf documentation.

Export D1 databases with virtual tables

You can now export a D1 database that contains virtual tables, such as full-text search tables using SQLite's FTS5 module ↗︎ or spatial index tables using the R*Tree module. Previously, export failed for any database containing virtual tables.

To include virtual tables in the dump, set dump_options.compatibility to sqlite3_cli_only on the D1 export API. The same option is available as the --compatibility flag on wrangler d1 export.

curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/d1/database/$DATABASE_ID/export" \
	--request POST \
	--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
	--json '{
		"output_format": "polling",
		"dump_options": {
			"compatibility": "sqlite3_cli_only"
		}
	}'

For more information, refer to Export a D1 database with virtual tables.

Set custom validity windows for RealtimeKit auth tokens

RealtimeKit auth tokens now support custom validity windows, and you can revoke a single token. When your backend adds a participant to a meeting, it gets back an auth token that the participant's app uses to join.

Previously, every token was valid for 100 days from the moment it was issued. Now you can choose when a token starts and stops working, for example only during a scheduled class or interview, so a shared link stops working once the session is over. Pass not_before and expires_on in the token object when you add a participant:

Required API token permissions

At least one of the following token permissions is required:
  • Realtime Admin
  • Realtime
Add a participantbash
curl "https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/realtime/kit/$APP_ID/meetings/$MEETING_ID/participants" \
	--request POST \
	--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
	--json '{
		"name": "Mary Sue",
		"preset_name": "<preset_name>",
		"custom_participant_id": "<uuid_of_the_user_in_your_system>",
		"token": {
				"not_before": "2026-12-01T15:00:00Z",
				"expires_on": "2026-12-01T17:00:00Z"
		}
	}'

Both fields are optional, so existing integrations keep getting 100-day tokens.

You can also revoke a single token without setting the whole meeting to INACTIVE. If the participant is in the meeting, RealtimeKit removes them. A revoked token can take up to 60 seconds to stop working everywhere, so delete the participant instead if you need to block them immediately.

RealtimeKit rejects expired, not yet valid, and revoked tokens before the participant enters the meeting, so you are not billed for them.

Learn more

Add noise cancellation to web apps built on RealtimeKit

You can now add noise cancellation to RealtimeKit web apps with the new @cloudflare/realtimekit-noise-cancellation package. RealtimeKit is a high-level SDK for adding real-time audio and video components, such as video meetings, to your web or mobile app.

Install the package:

npm i @cloudflare/realtimekit-noise-cancellation

After you initialize the meeting, pass it to init():

import { RealtimeKitNoiseCancellation } from "@cloudflare/realtimekit-noise-cancellation";

// Enables automatically when the mic is available, without delaying join.
void RealtimeKitNoiseCancellation.init({ meeting }).catch(console.warn);

How it works

  • Filters background noise in the participant's browser, before their audio is sent to the meeting.
  • Turns on automatically after init(), as soon as the participant's microphone is on.
  • Keeps running through mute, unmute, and reconnects, and cleans up when the participant leaves.
  • Never unmutes the microphone.

Noise cancellation works in React, Angular, and JavaScript apps on Chrome, Edge, Firefox, and Safari, including mobile browsers. The RealtimeKit iOS and Android SDKs do not yet support it.

Learn more