What is the compatibility_date in wrangler.toml?

The compatibility_date pins your Worker to a specific snapshot of the runtime's behaviour. Cloudflare uses it to apply or withhold breaking runtime changes, so setting a recent date keeps behaviour stable across deploys.

Do I need to include account_id?

Not always. If you run wrangler login, the CLI resolves your account interactively. Setting account_id is useful in CI or when your token has access to multiple accounts and you need to disambiguate.

How do KV, R2, and D1 bindings work?

Each binding maps a variable name your code uses (like MY_KV) to a real Cloudflare resource by its ID or name. At runtime the binding appears on the env object passed to your Worker, giving you typed access to storage and databases.

What does the [env.staging] block do?

Named environments let one wrangler.toml describe multiple deploy targets. wrangler deploy --env staging uses the [env.staging] overrides — typically a different name and variables — while sharing the rest of the base config.

Where do I put wrangler.toml?

Place wrangler.toml in the root of your Worker project next to package.json. The Wrangler CLI reads it automatically for deploy, dev, and tail commands.

wrangler.toml Builder (Cloudflare Workers)

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

A ready-to-deploy wrangler.toml

Cloudflare Workers read their entire deploy configuration from wrangler.toml: the entry point, the runtime compatibility date, routes, and resource bindings. Getting the TOML syntax and binding shapes right by hand is error-prone, so this builder generates a valid file from simple inputs.

How it works

The tool writes top-level keys — name, main, optional account_id, and compatibility_date — then appends TOML table arrays for anything you enable. A route becomes a [[routes]] table with a pattern and optional zone_name. KV, R2, and D1 each get their correct array-of-tables form: [[kv_namespaces]] with binding + id, [[r2_buckets]] with binding + bucket_name, and [[d1_databases]] with binding, database_name, and database_id. String values are TOML-quoted and escaped so special characters do not break parsing. An optional [env.staging] block adds a named environment with its own name and a vars table.

Example and notes

A minimal Worker needs only name, main, and compatibility_date. Add a route like example.com/api/* to serve a path on your own domain, and add bindings as you adopt storage. Binding variable names are what you reference in code via env.MY_KV, so keep them descriptive. After copying the file, run wrangler deploy (or wrangler deploy --env staging) to ship.