Cloudflare / Cloudflare

Cloudflare Wrangler dev EMFILE Too Many Open Files with Static Assets

Fix wrangler dev crashing with EMFILE too many open files when Workers Static Assets directory has many subdirectories Includes evidence for Cloudflare troubleshooting demand.

Source-backed Last updated May 11, 2026 1 source Needs local verification

Category: Cloudflare
Error signature: EMFILE: too many open files, watch at FSWatcher._handle.onchange
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 11, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Cloudflare, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

EMFILE: too many open files, watch at FSWatcher._handle.onchange is a Cloudflare failure pattern reported for developers trying to fix wrangler dev crashing with emfile too many open files when workers static assets directory has many subdirectories. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Open issue. wrangler 4.86.0, Node 20.19.2, macOS. Cutoff exact at 4,096 directories regardless of file count. .assetsignore does not prevent the crash. System rlimit is 1,048,576, so this is a Wrangler/libuv watcher cap, not an OS limit.

Common causes

Cloudflare Wrangler dev crashes with EMFILE error when the Workers Static Assets directory contains more than 4,095 subdirectories. The crash happens at watcher setup before the local server is ready. The threshold is exact at 4,096 directories (power-of-two suggests hardcoded watcher cap). .assetsignore does not help because it filters deploy/upload but not the dev watcher. This is a significant limitation for developers with large static asset structures.
Open issue. wrangler 4.86.0, Node 20.19.2, macOS. Cutoff exact at 4,096 directories regardless of file count. .assetsignore does not prevent the crash. System rlimit is 1,048,576, so this is a Wrangler/libuv watcher cap, not an OS limit.

Quick fixes

Confirm the exact error signature matches EMFILE: too many open files, watch at FSWatcher._handle.onchange.
Check the Cloudflare account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match EMFILE: too many open files, watch at FSWatcher._handle.onchange exactly before applying the quick fix.
Compare the failing environment with Cloudflare versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does EMFILE: too many open files, watch at FSWatcher._handle.onchange mean in Cloudflare?

EMFILE: too many open files, watch at FSWatcher._handle.onchange indicates the workflow described by "Cloudflare Wrangler dev EMFILE Too Many Open Files with Static Assets" failed in a Cloudflare context. Start by confirming the exact signature and the component that emitted it.

What should I check first for EMFILE: too many open files, watch at FSWatcher._handle.onchange?

Check whether this cause matches your environment: Cloudflare Wrangler dev crashes with EMFILE error when the Workers Static Assets directory contains more than 4,095 subdirectories. The crash happens at watcher setup before the local server is ready. The threshold is exact at 4,096 directories (power-of-two suggests hardcoded watcher cap). .assetsignore does not help because it filters deploy/upload but not the dev watcher. This is a significant limitation for developers with large static asset structures.

Is the EMFILE: too many open files, watch at FSWatcher._handle.onchange guidance source-backed?

The "Cloudflare Wrangler dev EMFILE Too Many Open Files with Static Assets" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for EMFILE: too many open files, watch at FSWatcher._handle.onchange?

For "Cloudflare Wrangler dev EMFILE Too Many Open Files with Static Assets", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging EMFILE: too many open files, watch at FSWatcher._handle.onchange?

For "Cloudflare Wrangler dev EMFILE Too Many Open Files with Static Assets", collect the failing Cloudflare command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.