Local development
Last updated Jun 25, 2026 Test changes to your dynamic dispatch Worker by running the dynamic dispatch Worker locally but connecting it to user Workers that have been deployed to Cloudflare.
Note
Consider using a staging namespace to test changes safely before deploying to production.
This is helpful when:
- Testing routing changes and validating that updates continue to work with deployed User Workers
- Adding new middleware like authentication, rate limiting, or logging to the dynamic dispatch Worker
- Debugging issues in the dynamic dispatcher that may be impacting deployed User Workers
How to use remote dispatch namespaces
In the dynamic dispatch Worker's Wrangler file, configure the dispatch namespace binding to connect to the remote namespace by setting remote = true:
{
"dispatch_namespaces": [
{
"binding": "DISPATCH_NAMESPACE",
"namespace": "production",
"remote": true
}
]
}
[[dispatch_namespaces]]
binding = "DISPATCH_NAMESPACE"
namespace = "production"
remote = true
This tells your dispatch Worker that's running locally to connect to the remote production namespace. When you run wrangler dev, your Dispatch Worker will route requests to the User Workers deployed in that namespace.
For more information about remote bindings during local development, refer to remote bindings documentation.
Was this helpful?
YesNo
On this page
{"@context":"https://schema.org","@type":"TechArticle","@id":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/local-development/#page","headline":"Local development","description":"Test your dynamic dispatch Worker locally while connecting to deployed user Workers in a Workers for Platforms namespace.","url":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/local-development/","inLanguage":"en","image":"https://developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/local-development/og.png?v=e7fa5fdc4378e7e8","dateModified":"2026-06-25","publisher":{"@type":"Organization","name":"Cloudflare","description":"One platform for your apps, agents, and workforce. Build, secure, and scale without managing infrastructure","url":"https://www.cloudflare.com/","sameAs":["https://github.com/cloudflare","https://www.linkedin.com/company/cloudflare","https://x.com/cloudflare"],"logo":{"@type":"ImageObject","url":"https://developers.cloudflare.com/logo.svg"},"address":{"@type":"PostalAddress","streetAddress":"101 Townsend St","addressLocality":"San Francisco","addressRegion":"CA","postalCode":"94107","addressCountry":"US"},"contactPoint":[{"@type":"ContactPoint","contactType":"Customer Support","url":"https://support.cloudflare.com/","availableLanguage":["English"]},{"@type":"ContactPoint","contactType":"Sales","url":"https://www.cloudflare.com/contact/","availableLanguage":["English"]}]},"isPartOf":{"@type":"WebSite","@id":"https://developers.cloudflare.com/#website","name":"Cloudflare Docs","url":"https://developers.cloudflare.com/"}}
description: Define Workers configuration in JSON metadata for multipart form-data script uploads. title: Multipart upload metadata image: https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/og.png?v=e03a6759be39ccfb
Documentation Index
Fetch the complete documentation index at: https://developers.cloudflare.com/workers/llms.txt
Use this file to discover all available pages before exploring further.
Docs