Free tools Windows power users keep installed
One-click scans. No signup required.
Usually, no. Cloudflare normally sits in front of a website hosted elsewhere, providing authoritative DNS, CDN caching, reverse-proxy security and traffic controls. It does directly host static or JAMstack sites with Cloudflare Pages, and it runs edge code and APIs with Cloudflare Workers. The right answer depends on where your files, application runtime and data actually execute.
What “hosting” means in a Cloudflare setup
A web host stores and serves your site’s files and, for dynamic applications, runs the application server and connects to databases. Cloudflare’s most common role is different: it publishes DNS records and reverse-proxies requests to an origin server operated by another hosting company.
When a DNS record is Proxied, visitors connect to Cloudflare’s network first. Cloudflare can cache eligible responses, apply security rules and optimize the request before forwarding it to your origin. When a record is DNS only, the record resolves directly to the origin and Cloudflare’s HTTP proxy is bypassed.
That means adding a domain to Cloudflare does not, by itself, move your WordPress files, PHP runtime, database or virtual machine to Cloudflare. Your existing host continues to provide the underlying website.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Three ways a website can run with Cloudflare
1. A separate origin behind Cloudflare
This is the conventional arrangement for WordPress, PHP, Ruby, Python, Node.js applications and database-backed systems. Your host supplies a persistent server or platform. Cloudflare supplies DNS, the reverse proxy, caching, TLS controls and edge security in front of it.
- Content location: your other provider’s server.
- Runtime: the origin’s web server and application stack.
- Cloudflare role: authoritative DNS plus optional proxy, caching and protection.
- Origin requirement: yes, unless another service supplies the application.
2. Cloudflare Pages
Pages is Cloudflare’s native deployment and hosting product for static and JAMstack sites. You connect a repository or deploy generated assets; Pages builds the project and serves the resulting frontend from Cloudflare’s network. A custom domain can be attached to the project.
Pages is a good fit for documentation, portfolios, marketing sites, blogs generated at build time and frontends that call APIs elsewhere. It is not a drop-in replacement for a server that must keep PHP processes, a local filesystem, or a continuously running database connection.
3. Cloudflare Workers
Workers executes JavaScript, TypeScript or other supported edge logic on Cloudflare’s network. A route maps a URL pattern to a Worker script. The script can handle a request itself, call an API, transform a response or fetch an application server behind Cloudflare.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWorkers is programmable edge infrastructure, not traditional shared hosting. You design the runtime, deployment and data architecture. It can provide API endpoints and dynamic behavior, but you should identify where persistent data and any origin application will live.
Does Cloudflare host a static website?
Yes, when you deploy it to Cloudflare Pages. The deployed HTML, CSS, JavaScript and other frontend assets are served by Pages, so a separate conventional web host is not required for those assets.
Pages prerequisites
- A static-site generator output or other deployable frontend files.
- A Pages project and a deployment workflow, such as a connected source repository or direct deployment.
- A custom domain configured on the project if you want to use your own domain.
For an apex domain such as example.com, Cloudflare’s documented full setup requires adding the domain as a Cloudflare zone and pointing the domain’s nameservers to Cloudflare. A subdomain can use the project’s assigned hostname or a configured DNS record, subject to Pages’ domain instructions.
What Pages does not provide automatically
- A general-purpose PHP hosting environment.
- A built-in replacement for every database or background worker.
- Automatic migration of an existing site’s server-side code.
A Pages frontend can still call an external API, and Workers can add edge endpoints, but those are separate architectural pieces.
Can Cloudflare host WordPress?
Cloudflare can protect and accelerate a WordPress site, but ordinary WordPress still needs a host that runs PHP and provides a database. The common design is:
- Keep WordPress files, PHP and the database at your WordPress or VPS provider.
- Add the domain to Cloudflare and use Cloudflare as the authoritative DNS provider in a full setup.
- Set the web records that should pass through Cloudflare to Proxied.
- Leave records for services that must be reached directly as DNS only, where appropriate.
Cloudflare then sits between visitors and the WordPress origin. It does not become the PHP runtime or database host. Moving an existing WordPress installation to Pages would require converting it to a static or headless architecture rather than simply changing DNS.
Do you need separate hosting if you use Cloudflare?
| Architecture | Separate origin host? | Best suited to |
|---|---|---|
| Cloudflare DNS and proxy in front of another provider | Yes | WordPress, PHP, database-backed apps and conventional servers |
| Cloudflare Pages | No for the deployed static frontend | Static sites and JAMstack frontends |
| Cloudflare Workers | Sometimes; a Worker may call an origin | Edge logic, request handling, APIs and serverless-style applications |
“No separate host” is therefore accurate for a Pages deployment of static assets, but not for a proxied traditional website. Workers may remove the need for a conventional origin for some workloads, while still requiring a deliberate solution for storage, databases or external services.
What happens to DNS and nameservers?
Full DNS setup
In a full setup, Cloudflare becomes authoritative for the zone. You change the domain’s nameservers at the registrar to the Cloudflare nameservers assigned during onboarding. Cloudflare then answers DNS queries for the domain.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For proxied A, AAAA and CNAME records, DNS responses use Cloudflare anycast addresses and HTTP or HTTPS traffic is routed through Cloudflare to the origin. DNS-only records return the origin record and do not use the HTTP proxy.
Partial (CNAME) setup
Cloudflare also documents a partial CNAME setup through a certified hosting partner. This is intended for situations where you cannot change nameservers. Availability and eligibility depend on the partner and hosting arrangement, so it should not be assumed for every account.
Registrar versus host
Cloudflare can sell or transfer domain registrations without markup fees, according to its domains documentation. Registration gives you control of the domain name; it does not supply a website origin. You still need Pages, Workers, or another hosting provider to serve the site.
Choosing the right Cloudflare option
Choose Pages when
- Your site can be produced as static files during a build.
- You want a managed build-and-deploy workflow and Cloudflare-served frontend assets.
- Dynamic functionality can live in an external API or separate edge code.
Keep an origin behind Cloudflare when
- Your application needs PHP, WordPress, a persistent server process or a conventional database connection.
- You already have a functioning host and want DNS, caching or reverse-proxy security.
- Your deployment depends on server-side files or software that Pages does not run.
Choose Workers when
- Request routing, authentication, API responses or transformations should execute at the edge.
- You are comfortable designing deployment, runtime limits and data connections.
- A Worker can serve the request directly or intentionally fetch an origin.
Practical setup checklist
- Classify the application. List static assets, server-side code, APIs, databases, scheduled jobs and file uploads.
- Select the execution location. Use Pages for a static frontend, Workers for edge logic, or an external host for a conventional application.
- Choose DNS mode. Use full Cloudflare DNS when you can change nameservers; investigate a certified-partner partial setup only when that constraint applies.
- Record the origin. For a proxied site, keep the origin hostname or IP, ports, certificates and firewall rules documented.
- Set proxy status deliberately. Proxy public web records that should pass through Cloudflare; use DNS-only status for records that must resolve directly.
- Test before switching traffic. Verify the custom domain, redirects, TLS, API calls, forms, uploads, webhooks and administrative login after DNS changes propagate.
Common mistakes and fixes
“I changed nameservers, but the site is still down.”
Changing nameservers only changes DNS authority; it does not create an origin. Confirm that the required A, AAAA or CNAME records point to a running host, or deploy the site to Pages.
“The domain works on DNS-only but fails when proxied.”
Check that the origin accepts Cloudflare’s connection, listens on a supported HTTP or HTTPS port, presents a suitable certificate and allows the expected Host header. Temporarily compare DNS-only behavior to isolate an origin-versus-proxy problem.
“My WordPress site shows errors after enabling the proxy.”
Verify the origin protocol and redirect rules, then check WordPress’s configured site URL, caching rules and any firewall restrictions. Do not treat Cloudflare DNS as a substitute for the PHP and database services WordPress requires.
“My Pages domain will not attach.”
Confirm that the domain is in the expected Cloudflare account and zone, that DNS is using the required Cloudflare setup for the domain type, and that conflicting records are removed or corrected according to Pages’ domain configuration.
“A Worker route does nothing.”
Check that the URL pattern matches the request, the route is enabled for the intended zone and the request is reaching the zone. A route maps a pattern to a Worker; it does not automatically migrate an existing application or database.
Performance, reliability and cost considerations
With an external origin, every uncached or dynamic request still depends on that host’s capacity and availability. Cloudflare can reduce origin traffic for cacheable responses and apply edge controls, but it cannot repair an unavailable application or a failed database.
Pages changes the operational model: deployment and frontend delivery are managed as a Pages project rather than as a manually maintained server. Workers adds programmable edge execution, which can reduce round trips for suitable logic but requires you to design storage and origin interactions.
Cloudflare’s documentation does not establish a universal uptime figure, a single free-hosting quota or a standard price that applies to every Pages or Workers use case. Check the current plan and product terms for your account and workload before committing to a cost estimate.
Or skip the browser setup
When you need a repeatable image of a Cloudflare Pages site, Worker response or any public URL, ScreenshotNeo provides a website screenshot API. A single request returns PNG, JPEG, WebP or PDF. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be disabled. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status.
cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for the complete options. It also has an MCP server with take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
The bottom line
Cloudflare is usually the DNS and reverse-proxy layer in front of a separate host. It directly hosts static and JAMstack deployments through Pages, and it runs programmable edge code through Workers. Decide first where your application and data must run; then choose Cloudflare’s product and DNS arrangement that matches that architecture.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
