Cloudflare Pages Deployment Checker

Check Cloudflare Pages deployment settings, output directory, build command, static files, redirects, headers, robots.txt, sitemap, and duplicate content risks.

Output:A ready-to-use configuration file for Cloudflare Pages Deployment Checker with best practices applied.

What framework are you using?

Next.js Output Mode

Static Export (out)SSR / OpenNext

Cloudflare Dashboard Settings

Build Command

Build Output Directory

NODE_VERSION (Env Var)

Estimated Static Files Count (HTML, JS, CSS, Images)

Included Files

Which files are you currently generating in your build?

_headers (Security & Caching)_redirects (Routing & SPA)robots.txt (SEO Crawling)sitemap.xml (SEO Indexing)

Deployment Analysis

Run the checker to see results

Cloudflare Pages Limits Reminder

Max 20,000 files per deployment (excluding _headers/_redirects)
Max 25 MiB file size for individual assets
Max 2,000 redirect rules in _redirects
Max 100 header rules in _headers

Quick Summary

Use the Cloudflare Pages Deployment Checker to validate your build command, output directory, Node version, and SEO/Security file locations before you push code, helping you avoid broken builds or indexed staging domains.

What is this tool?

Deploying to Cloudflare Pages is fast, but misconfiguring the build settings (like the output directory or build command) is a very common source of frustration.

This checker acts as a pre-flight checklist. By telling it your framework and current settings, it will flag common mistakes (like deploying the whole repo instead of the build folder) and remind you of essential SEO files.

How to Use This Tool

Select your framework (Next.js, Astro, Hugo, etc.).
Enter the build command and output directory you plan to use in the Cloudflare dashboard.
Check off which SEO/Security files you have currently implemented.
Review the generated checklist and fix any flagged issues before pushing your code.

What This Tool Generates

A pass/fail checklist of your Cloudflare Pages configuration.
Actionable recommendations to fix misconfigurations.

Best Practices

Always explicitly set your Node version in Cloudflare Pages via the NODE_VERSION environment variable or a .nvmrc file.
Ensure your _headers and _redirects files are correctly placed so they end up in the final output directory.
If you are using Next.js without a custom SSR adapter, always set 'output: export' in your next.config.js.

Common Mistakes

Leaving the output directory blank, which causes Cloudflare to try and deploy your source code (including package.json) as a static website.
Deploying the .next folder instead of the out folder for Next.js static sites.
Forgetting to add a robots.txt or sitemap.xml to the final build output.

Security Notes

Be careful not to deploy your root directory if it contains .env files with sensitive secrets. Always build to a dist/out folder and only deploy that folder.

Frequently Asked Questions

What output directory should I use for Cloudflare Pages?

It depends heavily on your framework. For Next.js static export it is 'out', for React/Vite it is usually 'dist', and for Hugo it is 'public'.

Why is Cloudflare deploying too many files?

Cloudflare Pages has a limit of 20,000 files per deployment. If you are hitting this, you might be accidentally deploying your 'node_modules' folder, the entire project root, or you have an enormous static site (like a dictionary with 50,000 pages).

Should I deploy .next to Cloudflare Pages?

No. The '.next' folder is an intermediate build cache for Next.js. You should either be deploying the 'out' folder (for static exports) or using @cloudflare/next-on-pages for full SSR.

How do I fix Cloudflare Pages build errors?

Common fixes include checking your Node.js version (Cloudflare defaults might be older than your local setup), ensuring your build command is correct (like 'npm run build'), and verifying your output directory matches what your framework actually generates.

How do I check _headers and _redirects?

Make sure they are placed in the correct source directory before the build runs (usually 'public') so that they get copied to the final output directory. If they don't end up in the root of the output directory, Cloudflare will ignore them.

How We Keep Your Configs Safe & Valid

Built-in Error Checking

Every file is checked against official rules. We catch missing fields and bad syntax. YAML indentation errors are flagged right away. Kubernetes, Terraform, and Docker specs are all covered. API versions and labels are verified too. You get valid output every time you generate.

100% Private & Local

All tools run in your browser only. Your API keys never leave your machine. We do not use any tracking scripts. No data is sent to any server. Passwords and secrets stay on your device. Crypto operations use the Web Crypto API. Your privacy is fully protected at all times.

Secure Settings by Default

Configs use safe defaults out of the box. Containers run as non-root users. Root filesystems are set to read-only. Dangerous Linux capabilities are dropped. Network policies limit pod-to-pod traffic. TLS 1.3 is enabled for web servers. Security headers are added where needed.

Ready for CI/CD & Git

Output files are ready for your Git repo. Use them with ArgoCD, Flux, or GitHub Actions. Files use clear formatting and comments. Code review is easy for your team. Indentation and key order are consistent. Test in staging before going to production. Every file is clean and well-structured.

Infrastructure as Code

Store configs in Git alongside your code. Terraform modules include typed variables. Backend configs support remote state locking. Outputs work across multiple modules. Ansible playbooks use clear task steps. Chef and Puppet configs are also supported. Every file works with version control tools.

Monitoring & Tracing

Set up Prometheus with auto-discovery rules. Create Grafana dashboards with template variables. Add alerting rules with severity labels. Use OpenTelemetry for trace collection. Forward logs to Loki or Elasticsearch. Connect to Jaeger or Tempo for tracing. Monitor metrics, logs, and traces together.

Container & Docker Safety

Dockerfiles use multi-stage builds for small images. Base images are pinned to exact versions. Dev files are excluded from final images. Health checks are added for orchestrator use. Containers switch to non-root users. Docker Compose uses named volumes and networks. Resource limits are set in deploy configs.

Multiple Output Formats

Export as YAML, JSON, HCL, or TOML. Kubernetes uses YAML with proper separators. Terraform uses HCL with correct escaping. JSON output has consistent indentation. Copy to clipboard with one click. Preview output with syntax highlighting. Line numbers help you review quickly.