Bindings

Bindings allow your Workers to interact with resources on the Cloudflare Developer Platform.

There are multiple types of bindings available today, including environment variables (text and JSON values) as well as secrets.

To learn how to access bindings in your code, refer to Bindings in the Migrate to ES Modules guide.

​​ Configuration

Bindings can be configured in one of two ways:

• Updating your project’s wrangler.toml file.
• Logging in to the Cloudflare dashboard Open external link > Account Home > Workers & Pages > your Worker > Settings> Variables.

​​ Service bindings

Service bindings allow for communication with another Worker.

• Learn more about Service bindings.
• Configure Service bindings via your wrangler.toml file.

​​ KV namespace bindings

KV namespace bindings allow for communication between a Worker and a KV namespace.

• Learn more about KV namespace bindings.
• Configure KV namespace bindings via your wrangler.toml file.

​​ Durable Object bindings

Durable Object bindings for communication between a Worker and a Durable Object.

• Learn more about Durable Object bindings.
• Configure Durable Object bindings via your wrangler.toml file.

​​ R2 bucket bindings

R2 bucket bindings for communication between a Worker and an R2 bucket.

• Learn more about R2 bucket bindings.
• Configure R2 bucket bindings via your wrangler.toml file.

​​ Queue bindings

Queue bindings allow for communication between a Worker and a Queue.

• Configure Queue bindings via your wrangler.toml file.

​​ D1 database bindings

D1 bindings allow you to query a D1 database from your Worker.

• Create your first D1 binding.
• Configure a D1 bindings via your wrangler.toml file.
• Learn more about how to query a D1 database using the client API.

​​ Vectorize database bindings

Vectorize bindings allow you to interact with and query a Vectorize index from your Worker.

• Create your first Vectorize binding.
• Configure a Vectorize binding via your wrangler.toml file.
• Learn more about how to query a Vectorize index using the client API.

​​ Hyperdrive bindings

Hyperdrive bindings allow you to interact with and query any Postgres database from within a Worker.

• Create your first Hyperdrive binding.
• Configure a Hyperdrive binding via your wrangler.toml file.

​​ Dispatch namespace bindings (Workers for Platforms)

Dispatch namespace bindings allow for communication between a dynamic dispatch Worker and a dispatch namespace. Dispatch namespace bindings are used in Workers for Platforms. Workers for Platforms helps you deploy serverless functions programmatically on behalf of your customers.

• Create your first dispatch namespace binding.

​​ mTLS certificate bindings

mTLS certificate bindings enable Worker subrequests to present a client certificate when communicating with a service that requires client authentication.

• Learn more about mTLS certificate bindings.
• Configure mTLS certificate bindings via your wrangler.toml file.

​​ Email bindings

Email bindings allow you to send emails from your Worker. This is useful for when you want to know about certain types of events being triggered, for example.

• Learn more about email bindings.
• Configure email bindings via your wrangler.toml file.

​​ Workers AI bindings

Workers AI bindings allow for communication between a Worker and an AI/ML model.

• Learn more about Workers AI bindings.
• Create your first AI binding.
• Configure Workers AI bindings via your wrangler.toml file.

​​ Browser bindings

The Workers Browser Rendering API allows developers to programmatically control and interact with a headless browser instance and create automation flows for their applications and products.

A browser binding will provide your Worker with an authenticated endpoint to interact with a dedicated Chromium browser instance.

• Create your first browser binding.
• Configure browser bindings via your wrangler.toml file.