Free tools Windows power users keep installed
One-click scans. No signup required.
Usually, no. Cloudflare normally sits in front of a website hosted somewhere else. It provides authoritative DNS, a reverse proxy, CDN delivery, and security services, while your files, application runtime, and database remain on an origin server. Cloudflare does directly host static and JAMstack projects with Cloudflare Pages, and it can run edge code and APIs with Workers. The right answer therefore depends on what you are building.
What Cloudflare normally does
A traditional web host keeps your website online on a server. Cloudflare’s usual role is different: it publishes DNS for your domain and proxies web traffic to your origin. DNS records identify the server that holds your content. When an HTTP record is proxied, visitors connect to Cloudflare’s anycast network first; Cloudflare can cache eligible responses, apply security rules and forward requests to the origin.
Your origin might be a shared-hosting account, virtual private server, managed WordPress host, cloud load balancer or an internal application server. Cloudflare does not replace that server in this arrangement.
Proxied versus DNS-only records
| Record mode | What visitors receive from DNS | Traffic path | Typical use |
|---|---|---|---|
| Proxied (orange cloud) | Cloudflare anycast addresses | Visitor → Cloudflare → origin | Web traffic that should use caching, TLS termination and Cloudflare protection |
| DNS-only (gray cloud) | Your origin address | Visitor → origin directly | Services that cannot use the HTTP proxy, or records you intentionally want exposed |
Changing a record to DNS-only bypasses the Cloudflare proxy for that hostname. It does not move your files to Cloudflare, and it can expose the origin address or remove proxy-layer protections.
#1 Best Overall
Does Cloudflare host a website directly?
Cloudflare has two products that can serve code without a conventional web-hosting account: Pages and Workers. They are hosting options, but they are not the same thing as a general-purpose shared host.
Cloudflare Pages: static and JAMstack hosting
Pages is the closest Cloudflare equivalent to ordinary website hosting. You connect a repository or deployment workflow, Cloudflare builds the project and serves the resulting frontend assets from its network. It suits static HTML, CSS and JavaScript sites, documentation, blogs generated at build time, and JAMstack frontends.
You can attach a custom domain to a Pages project. For an apex domain such as example.com, Cloudflare requires the domain to be added as a Cloudflare zone and its nameservers pointed to Cloudflare. A subdomain can be connected through DNS after the project is configured.
Pages can serve the deployed frontend directly, so a separate origin host is not required for those assets. If the application needs a database, long-running server process or a framework runtime that Pages does not provide, keep that backend on a suitable service and connect to it from the frontend.
Workers: programmable edge execution
Workers runs JavaScript, TypeScript or other supported edge code on Cloudflare’s network. A route maps a URL pattern to a Worker script; matching requests execute that script. The Worker can return a response itself, implement an API, rewrite requests or fetch an application server behind Cloudflare.
That makes Workers useful for request handling, authentication layers, API endpoints, personalization and edge-side logic. It is not a drop-in replacement for a cPanel-style account with PHP, a filesystem and a database. You design the runtime and data architecture explicitly, and a Worker may still depend on an origin or external storage.
Cloudflare Pages versus a regular host
| Question | Cloudflare Pages | Conventional host behind Cloudflare | Workers |
|---|---|---|---|
| Where content runs | Deployed static/JAMstack assets on Cloudflare | Another provider’s origin server | Worker code at the edge; it may call an origin |
| Best fit | Static sites and build-based frontends | WordPress, PHP, databases and persistent application servers | Edge logic, APIs, routing and serverless behavior |
| Separate origin required? | Not for the deployed frontend | Yes | Only if your design fetches one |
| Deployment model | Managed build and deploy workflow | You manage the host and application | You deploy scripts and configure routes |
Do you need separate hosting when using Cloudflare?
Use this rule: if Cloudflare is only providing DNS and proxying, yes, you need an origin host. If you deploy a static project to Pages, Pages can be the host for that frontend. If you build around Workers, the Worker is the execution layer, but you may still need storage, a database or an origin API.
WordPress, PHP and database-backed applications
Keep WordPress on a WordPress or PHP-capable host. WordPress requires an application runtime, writable files and a database; Cloudflare’s DNS and proxy do not supply those components. Point the site’s DNS records at the WordPress origin and proxy the web hostnames. Configure the origin to accept traffic from Cloudflare and keep administrative or non-HTTP services on the mode those services require.
Recommended Free Tools
Static marketing sites and documentation
Choose Pages when your build produces the files the browser needs and dynamic operations are handled through an API or other service. A separate shared host is unnecessary for the Pages-served frontend.
Dynamic applications and APIs
Choose a conventional origin for a long-running framework, database-backed application or background process. Choose Workers when moving request logic to the edge is a deliberate architectural choice. Many production systems combine Workers with an origin rather than choosing one exclusively.
Can you host a website on Cloudflare for free?
Cloudflare Pages has a free availability tier, but the exact limits and included capabilities can change; check the current Pages plan documentation before committing a workload. “Free Cloudflare” does not mean every application is hosted at no cost: a WordPress origin, database, email service or external API can still charge separately. Workers also has plan-specific limits and billing, so evaluate invocation, CPU, storage and data-transfer requirements against the current Workers terms.
Do you have to change nameservers?
Full setup
In the standard setup, add the domain as a Cloudflare zone and replace the registrar’s nameservers with the Cloudflare nameservers assigned to that zone. Cloudflare then becomes authoritative for DNS. You copy or recreate the required records, verify them, and decide which records should be proxied.
Nameserver changes affect the entire DNS zone, not only the website. Review mail (MX), verification, VPN and other service records before switching, and do not proxy records for services that are not compatible with Cloudflare’s HTTP proxy.
Partial CNAME setup
Cloudflare also documents a partial CNAME arrangement through a certified hosting partner. This is for cases where you cannot delegate the zone’s nameservers. Availability depends on the partner and the domain setup, so it is not a universal substitute for full DNS delegation.
Cloudflare Registrar is not web hosting
Cloudflare can sell and manage domain registrations without markup fees under its registrar offering. Registration gives you control of a domain name; it does not provide the server, application runtime or database that makes a website operate. You can register a domain with Cloudflare and host the site on Pages, Workers, or an entirely different provider.
Choosing the right architecture
- Identify the application type. If a build outputs static assets, start with Pages. If you need PHP, WordPress, a persistent process or a database, select an origin host.
- Decide where dynamic logic belongs. Keep it on the origin, move selected request logic to Workers, or expose an API that the Pages frontend calls.
- Plan DNS ownership. Use full Cloudflare nameserver delegation when you want Cloudflare authoritative DNS. Investigate partial CNAME only when delegation is impossible and a supported partner is available.
- Separate web and non-web records. Proxy compatible HTTP/HTTPS hostnames; leave mail and other incompatible services DNS-only as required.
- Test before cutover. Verify the origin directly, confirm TLS settings, test redirects and forms, check cache behavior, and validate email and third-party verification records after DNS changes.
Common problems and fixes
The site shows a Cloudflare error instead of the page
Check that the proxied A or CNAME record points to the current origin, that the origin is listening on the selected port, and that the origin firewall permits Cloudflare traffic. Temporarily using DNS-only can isolate whether the failure is at the origin or proxy layer, but it removes proxy protection while enabled.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →The domain works at the old host but not after onboarding
Confirm that the registrar lists the exact Cloudflare nameservers assigned to the zone. Then review every DNS record, especially the apex, www, MX and verification records. Nameserver changes can take time to propagate according to resolver caching.
HTTPS redirects loop
Ensure the origin’s protocol and Cloudflare’s SSL/TLS mode agree. A redirect loop commonly occurs when Cloudflare accepts HTTPS from the visitor but the origin believes the connection is HTTP and redirects repeatedly. Configure the origin to honor the forwarded protocol and use a certificate appropriate for the connection Cloudflare makes to it.
Pages custom-domain validation fails
Check that the Pages project is deployed, the hostname is entered exactly, and the required DNS record exists in the correct Cloudflare zone. Apex domains require the zone’s nameservers to be on Cloudflare.
Workers route does not run
Verify that the request hostname and path match the route pattern, the Worker is deployed to the expected environment, and a more specific route or another configuration is not taking precedence. Confirm that the script returns a response for every intended method and path.
Validate the finished site with clean screenshots
If you need visual checks of a Cloudflare-hosted site—for release approvals, documentation or regression review—ScreenshotNeo can capture the public URL without requiring you to maintain a browser worker. It removes cookie-consent banners, newsletter popups and chat widgets before capture, and failed loads, bot checks, blank pages and cache hits are not billed. It also offers an MCP server for AI clients with take_screenshot, get_page_info and capture_pdf tools.
A single request is enough:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for options such as full-page capture, device presets, dark mode, CSS selectors, waits, custom headers, caching and PDF output. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo.
Bottom line
Cloudflare is usually the DNS and reverse-proxy layer in front of a separate host, not that host itself. Use Pages for a static or JAMstack frontend, Workers for edge-executed logic and APIs, and a conventional origin for WordPress, PHP, databases and persistent application servers. Domain registration is separate from all three.
Frequently Asked Questions
Can Cloudflare host WordPress without another provider?
No. WordPress needs PHP, writable application files and a database, so keep it on a compatible origin host and use Cloudflare for DNS and proxying.
Is Cloudflare a CDN or a web host?
It is both in different products: the standard service is DNS plus CDN/reverse proxy, Pages directly serves deployed static projects, and Workers executes edge code.
Will changing nameservers move my website files?
No. Nameserver delegation changes who answers DNS queries. Your files remain wherever the origin or Pages deployment is located.
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.
