Cloudflare can host some websites, but it is not a general-purpose web-hosting provider for most sites. In the common setup, Cloudflare supplies authoritative DNS, CDN caching, DDoS protection and web-application security while your files and application remain on a separate origin host. For static or JAMstack projects, Cloudflare Pages and Workers Static Assets can deploy and serve the site; Workers can also run application logic.
The important question is therefore not whether Cloudflare “hosts” in the abstract, but which Cloudflare product matches your architecture. Cloudflare’s own Domains documentation says it does not offer web hosting for most websites while identifying Pages for JAMstack deployments.
What “hosting” means in a Cloudflare setup
Web hosting is the service that stores or runs what your visitors request: HTML, CSS, JavaScript, images, uploaded files, databases and server-side code. A conventional host might run WordPress, PHP, a control panel, an email service or a database on your behalf.
Cloudflare’s DNS, proxy and security products perform different jobs. DNS publishes the records that tell browsers where to connect. When a record is proxied, the request first reaches Cloudflare’s network, where Cloudflare can cache eligible responses, absorb attacks and apply firewall rules before forwarding a request to the origin. The origin still stores the application unless you have deployed it to a Cloudflare hosting product. Cloudflare explains this separation in its DNS getting-started guide.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
Cloudflare in front of another host
Suppose your site runs on a conventional provider. You can move the domain’s authoritative DNS to Cloudflare and enable the orange-cloud proxy for supported records. Visitors see Cloudflare’s edge, but uncached or dynamic requests continue to your existing origin. You have changed the traffic and security layer, not necessarily the place where the site is hosted.
- Origin: stores files and runs application code.
- Cloudflare DNS: publishes and manages domain records.
- Cloudflare proxy/CDN: handles traffic, caching and edge security.
- Cloudflare hosting products: deploy and serve projects directly on Cloudflare.
Which Cloudflare products can host a site?
Pages for static and JAMstack deployments
Cloudflare Pages is designed for deploying websites built from static files or a framework build process. A typical workflow connects a repository or uploads a build output; Pages then serves the generated HTML, stylesheets, scripts and assets. Cloudflare’s domain guidance specifically identifies Pages as a way to deploy and host JAMstack sites.
Pages can also use Pages Functions for server-side behavior. Pages remains available, although Cloudflare’s current web-application guidance recommends Workers for new projects. Do not interpret that recommendation as Pages being discontinued; the Pages documentation continues to describe its deployment model and functions.
Workers Static Assets
Workers Static Assets lets a Worker serve project files such as HTML, CSS and images. This is useful when the same deployment needs edge code, routing or request handling alongside static content.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteWorkers for full-stack applications
Workers can serve frontend assets and execute backend logic at the edge. Cloudflare’s web-app guidance describes Workers combined with data and storage services for full-stack applications. That can remove the need for a separate traditional origin, provided your framework, runtime and data requirements fit the Workers platform.
“Hosted on Cloudflare” in this context means your deployment is running on Pages or Workers. It does not mean every server-based application can be copied to Cloudflare unchanged.
Do you still need a separate web host?
| Your situation | Likely arrangement | Separate origin required? |
|---|---|---|
| WordPress, PHP or another conventional server application | Keep the application at a compatible host; use Cloudflare DNS, proxy and security in front of it. | Usually, unless you redesign or migrate to a supported Cloudflare architecture. |
| Static HTML/CSS/JavaScript site | Deploy to Pages or Workers Static Assets, or keep an existing host behind Cloudflare. | No if deployed directly to Cloudflare. |
| JAMstack site built by a repository workflow | Use Pages, with functions where appropriate. | No for the deployed site. |
| Frontend plus edge API logic | Use Workers and Static Assets, with Cloudflare data or storage services as needed. | No separate origin may be needed, subject to compatibility. |
The documentation does not establish that every WordPress, PHP or other server-based site can move without modification. Check your framework, runtime, filesystem, database, background-job and third-party-service requirements before treating Workers as a replacement for a conventional host.
How to choose the right architecture
Keep your existing host and add Cloudflare
Choose this path when your application already depends on a conventional server environment, a managed database, WordPress plugins, persistent local storage or host-level controls. Change the domain’s authoritative nameservers to Cloudflare, recreate the DNS records accurately, and proxy only the records that should pass through Cloudflare. Keep the origin available and verify TLS, redirects, webhooks and administrative access after the change.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Deploy a static site to Pages
Pages is a natural fit when a build produces deployable files and the site does not need a general-purpose server. Confirm the build command, output directory, environment variables and custom-domain settings for your framework. Dynamic features may require Pages Functions or an external API.
Build a new application with Workers
Workers is the current recommendation for new Cloudflare web applications. Use it when you want edge request handling, backend logic and static assets in one deployment. Map each required capability—database access, object storage, authentication, scheduled work and queues—to a supported Cloudflare service or an external provider before migrating.
What Cloudflare DNS does—and does not do
Authoritative DNS answers queries for records such as A, AAAA, CNAME, MX and TXT. It can direct a hostname to your origin or to a Cloudflare deployment. DNS management by itself does not store your HTML, execute PHP, run a database or replace the origin server.
Proxying is also not the same as hosting. A proxied request can receive a cached response at Cloudflare’s edge, but a cache miss or dynamic request still needs an origin unless the hostname is backed by Pages, Workers or another Cloudflare service that serves the response directly.
Migration and setup checklist
- Classify the site: static files, framework build, server-rendered application, API, database-backed application or a mixture.
- Choose the product: existing origin plus Cloudflare proxy, Pages, Workers Static Assets or Workers.
- Inventory dependencies: runtime version, filesystem writes, database drivers, cron jobs, queues, uploads, authentication and third-party callbacks.
- Recreate DNS carefully: include mail, verification and service records; changing nameservers without them can interrupt email or integrations.
- Test a preview or staging deployment: check navigation, forms, cookies, redirects, canonical URLs, assets, APIs and error handling.
- Cut over gradually: lower DNS TTL before a planned change, monitor the origin and retain a rollback plan.
- Verify operational behavior: inspect logs, cache headers, TLS mode, firewall events and webhook delivery after launch.
Common misconceptions and failure modes
“I pointed DNS to Cloudflare, so Cloudflare now hosts my site.”
DNS only determines where names resolve. Confirm where the application files and runtime actually live. If the record points to your old provider, that provider remains the origin.
“The CDN should cache my logged-in pages.”
Personalized or authenticated responses generally need careful cache rules. Caching them incorrectly can expose one user’s content to another. Start with static assets and explicitly define behavior for cookies, authorization and dynamic routes.
“Any server application can be uploaded to Workers.”
Workers is not a drop-in virtual machine or unrestricted PHP host. Identify incompatible APIs, persistent-process assumptions, native dependencies and filesystem behavior. Adapt the application or retain a conventional origin.
“Pages has been replaced.”
Pages remains documented and usable. The narrower, current guidance is that Workers is recommended for new projects; select Pages when its deployment model fits your project.
Recommended Free Tools
Mail stopped working after a DNS move.
Review MX, SPF, DKIM, DMARC and provider verification records. Web proxying does not proxy ordinary mail delivery, and mail records normally should not be orange-cloud proxied.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Performance, reliability and cost considerations
Cloudflare’s edge can reduce origin requests for cacheable content and add security controls, but no generic speed or uptime figure follows from using Cloudflare. Results depend on cacheability, geography, origin performance, configuration and traffic patterns. Test your own routes, especially uncached and authenticated ones.
A Cloudflare-hosted deployment also changes operational responsibilities. You may no longer manage an operating system, but you must manage deployments, environment variables, data durability, observability, limits and vendor-specific APIs. Keep backups and an export or rebuild path for critical content.
Product availability, framework support and plan terms can change. Use the current product documentation linked above when making a production decision.
Or skip the browser setup: ScreenshotNeo for automated captures
If you need screenshots of a Cloudflare-hosted site for documentation, visual checks or release records, ScreenshotNeo provides a website screenshot API and MCP server. A single request returns PNG, JPEG, WebP or PDF. Before capture it accepts consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status.
Example using the documented API (full documentation):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpIt also offers custom CSS and JavaScript, device presets, full-page and element captures, dark mode, PDF controls, request blocking, headers and cookies, geolocation, signed links, asynchronous jobs, bulk capture and an MCP server with take_screenshot, get_page_info and capture_pdf. 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.
Bottom line
Cloudflare is both a delivery/security layer and, for suitable architectures, a hosting and deployment platform. Most conventional sites still keep an origin host and place Cloudflare in front of it. Static and JAMstack projects can deploy to Pages or Workers Static Assets, while new full-stack projects can use Workers. Decide based on your runtime and application dependencies—not on the fact that your DNS is managed by Cloudflare.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFrequently Asked Questions
Can Cloudflare host a static HTML website without another provider?
Yes. You can deploy static files with Cloudflare Pages or Workers Static Assets, so a separate origin host is not required for that deployment.
Is Cloudflare a replacement for cPanel hosting?
Usually no. Cloudflare’s DNS, proxy and security services do not provide the general-purpose server, control panel and runtime commonly supplied by cPanel hosts.
Should a new Cloudflare project use Pages or Workers?
Cloudflare’s current web-application guidance recommends Workers for new projects, while Pages remains available for deployments that fit its model.
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.
