Cloudflare Resource Tagging Hits Public Beta: Tag and Query Your Resources

Hey there, it's me, Shii-chan! Today I found a happy little update that makes tidying up your infrastructure a whole lot easier, so let me tell you about it.

Cloudflare Changelog developers.cloudflare.com

What was announced?

On the Cloudflare Changelog, they announced that Resource Tagging has entered public beta! It's rolling out to all Cloudflare accounts over the coming days. You can attach your own key-value metadata (tags) to your Cloudflare resources and query across your entire account to find exactly what you need.

The story so far

As you add more services — Zones, Workers, D1, R2, KV, and on and on — it gets harder to answer "whose team owns this?" or "is this production or staging?" Until now, you had to keep track of all that in your head or a spreadsheet.

What changes

From now on, you can put tags like team:web or env:production on your resources and search for them together later. That makes inventory cleanups and cost attribution a lot easier to prep for.

Dive Deep

• Broad resource support: Zones, custom hostnames, Cloudflare Tunnels, Workers, D1, R2, KV, Durable Objects, Queues, Stream, Images, Access applications, Gateway rules, AI Gateways, and more. Check the full list of supported resource types.
• Powerful filtering: it supports AND/OR logic, negation, and key-only matching, and you can combine up to 20 filters in a single query to build precise views.
• Full CRUD across both account and zone scopes, with authentication via Account Owned Tokens. Since they aren't tied to an individual user, your automation keeps running even when team members change.
• On the roles side, Super Administrators, Workers Admins, and Tag Admins can all manage tags.

It's API-first by design, and that's the recommended path for scripting, CI/CD pipelines, or your infrastructure-as-code toolchain. Of course, you can also head to Manage Account then Resource Tagging in the dashboard to filter by name or tag and edit tags inline.

There are a few beta caveats too. PUT replaces all tags on a resource (no partial update), so to add just one tag safely, use the GET, merge, then PUT workflow. DELETE removes all tags at once. And querying a resource that has never been tagged returns 500 instead of 404 — a known beta limitation.

Wrap-up

• Cloudflare's Resource Tagging is now in public beta, rolling out to all accounts over the coming days
• Attach key-value tags to resources and search across them with AND/OR, negation, and up to 20 filters
• Broad resource coverage, plus Account Owned Tokens that are great for automation
• API-first design, but you can edit tags from the dashboard too
• Tag-based access control, cost attribution, and Terraform support are planned next

This one really lands for ops folks and DevOps teams who tend to lose track of where everything lives. Start by peeking at the Resource Tagging documentation!