Confirm the origin can handle direct request load and choose a limited testing period. Note any application cache plugin, server cache or browser cache that must be inspected separately.

1. Open the domain’s caching Configuration page and locate Development Mode.
2. Enable it for the planned test and record the start time. Cloudflare automatically turns the mode off after its temporary window.
3. Request the changed page or asset and confirm the origin serves the intended version. Use a fresh browser request when local caching might hide it.
4. Fix the content or application issue, then disable Development Mode when the test is complete rather than leaving a long maintenance session unmanaged.
5. Purge specific stale objects if needed and verify ordinary cache behaviour after the mode ends.

During the active window, requests should bypass the normal Cloudflare cache path. The website should still use the configured proxy and security features unless separately changed.

Development Mode does not purge existing cached objects, and it does not disable an origin cache or browser cache. If the old content persists, check those layers and verify you changed the correct origin files.

No. Pausing changes how traffic reaches the origin and bypasses the reverse proxy. Development Mode is a temporary cache-related diagnostic while the site remains proxied.

• Purging one changed asset from Cloudflare cache
• Interpreting CF-Cache-Status during performance testing
• Temporarily pausing Cloudflare for a controlled diagnosis
• Checking why cookies prevent or alter Cloudflare caching

• Cloudflare: Development Mode