Three months ago we announced the public beta of remote bindings for local development. Now, we’re excited to say that it’s available for everyone in Wrangler, Vite, and Vitest without using an experimental flag!
With remote bindings, you can now connect to deployed resources like R2 buckets and D1 databases while running Worker code on your local machine. This means you can test your local code changes against real data and services, without the overhead of deploying for each iteration.
Example configuration
To enable remote bindings, add "remote" : true to each binding that you want to rely on a remote resource running on Cloudflare:
wrangler.jsonc
{"name": "my-worker","compatibility_date": "2025-09-16","r2_buckets": [{"bucket_name": "screenshots-bucket","binding": "screenshots_bucket","remote": true,},],}wrangler.toml
name = "my-worker"compatibility_date = "2025-09-16"[[r2_buckets]]bucket_name = "screenshots-bucket"binding = "screenshots_bucket"remote = true
When remote bindings are configured, your Worker still executes locally, but all binding calls are proxied to the deployed resource that runs on Cloudflare’s network.
You can try out remote bindings for local development today with:
Source: Cloudflare
Latest Posts
- GCP Release Notes: October 30, 2025
- Updates available for Microsoft 365 Apps for Current Channel [MC1181780]
- Microsoft Teams: File attachment control now enabled by default in external 1:1 and group chats [MC1181772]
- Microsoft Purview: eDiscovery admin content access restrictions when not in compliance with Entra policies [MC1181768]
