Skip to content
Cloudflare Docs

Supported bindings per development mode

Local development

Local simulations: During local development, your Worker code always executes locally and bindings connect to locally simulated resources by default. This is supported in wrangler dev and the Cloudflare Vite plugin.

Remote binding connections:: Allows you to connect to remote, deployed resources on a per-binding basis. Supported in wrangler dev --x-remote-bindings and the Cloudflare Vite plugin.

BindingLocal simulationsRemote binding connections
AI❌✅
Assets✅❌
Analytics Engine✅❌
Browser Rendering✅✅
D1✅✅
Durable Objects✅❌
Containers✅❌
Email Bindings✅✅
Hyperdrive✅❌
Images✅✅
KV✅✅
mTLS❌✅
Queues✅✅
R2✅✅
Rate Limiting✅❌
Service Bindings (multiple Workers)✅✅ 1
Vectorize❌✅
Workflows✅❌

Remote development

During remote development, all of your Worker code is uploaded and executed on Cloudflare's infrastructure, and bindings always connect to remote resources. We recommend using local development with remote binding connections instead for faster iteration and debugging.

Supported only in wrangler dev --remote - there is no Vite plugin equivalent.

BindingRemote development
AI✅
Assets✅
Analytics Engine✅
Browser Rendering✅
D1✅
Durable Objects✅
Containers❌
Email Bindings✅
Hyperdrive✅
Images✅
KV✅
mTLS✅
Queues❌
R2✅
Rate Limiting✅
Service Bindings (multiple Workers)✅
Vectorize✅
Workflows❌

Footnotes

  1. While you can make fetch() calls on remote service bindings, you cannot currently call RPC methods on remote service bindings. ↩