Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Cloudflare does both, but not for the same kind of project. For most conventional websites, Cloudflare is the DNS, CDN and security layer in front of an origin host operated by someone else. Cloudflare also provides deployment and hosting for static or JAMstack sites through Pages and Workers Static Assets, and Workers can combine frontend files with application logic. Cloudflare’s own Domains documentation says it does not offer web hosting for most websites.
What “hosting” means in this question
A web host stores your site’s files and/or runs its application so a visitor can receive a page. An origin server might run WordPress, PHP, a database-backed application or another conventional stack.
A CDN does a different job. It can cache eligible responses near visitors and forward requests to the origin. Security services can inspect traffic, block attacks and apply firewall rules. DNS publishes the records that tell browsers where to connect. Those services can all be supplied by Cloudflare without Cloudflare storing or executing your application.
Cloudflare can therefore be “in front of” a site while the site remains hosted at a separate provider. Its DNS guide explains how authoritative DNS and proxied records direct traffic through Cloudflare’s network; proxying does not transfer the origin files to Cloudflare. See Get started with Cloudflare DNS.
#1 Best Overall
How the two common architectures work
Cloudflare in front of an existing host
- You rent or operate an origin host that serves the website.
- You add the domain to Cloudflare and make Cloudflare authoritative for DNS, usually by changing the domain’s nameservers.
- For proxied records, a visitor connects to Cloudflare first. Cloudflare applies CDN, DDoS and web-application protections, then retrieves content from the origin when needed.
- The origin remains responsible for the application, files, runtime and database. Removing the proxy does not delete that host.
This is the normal arrangement for a site that needs a general-purpose server environment. Cloudflare’s domain guidance explicitly separates a web host from CDN onboarding and says most websites still need hosting elsewhere.
Cloudflare deploys and serves the site
For a static or JAMstack project, you can deploy the generated HTML, CSS, JavaScript and images to Cloudflare Pages. Workers Static Assets can also serve project files directly from Cloudflare. In that model, Cloudflare is not merely a traffic filter; it is serving the deployed site.
Workers can add request handling and backend logic to those assets. Cloudflare’s web-app guidance describes Workers as a way to serve frontend assets and application code, with data and storage services available for full-stack applications. Read the current product descriptions in Static Assets and Web sites and web apps.
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 →Which Cloudflare product fits your site?
| Your situation | Cloudflare capability | What it means in practice |
|---|---|---|
| An existing WordPress, PHP or other server-based site | DNS, proxy/CDN and security | Cloudflare can sit in front of the origin. It does not automatically replace the provider running the server or application. |
| A static or JAMstack site produced by a build step | Pages or Workers Static Assets | Project files can be deployed and served on Cloudflare without a traditional web host. |
| A new frontend that also needs server-side logic | Workers with static assets and application code | Frontend delivery and request-handling logic can be deployed together; confirm that your framework and runtime fit the current Workers model. |
| An existing Pages project | Pages and Pages Functions | Pages remains available. Cloudflare’s current web-app guidance recommends Workers for new projects, so evaluate Workers when starting a new build. |
The documentation does not provide a universal compatibility matrix for every framework or server application. Do not assume that a site requiring PHP, a particular Apache module or unrestricted server access can move unchanged to Pages or Workers.
Does using Cloudflare DNS count as hosting?
No. DNS is the directory service that publishes records such as the address for your website. Cloudflare can manage those records even when another company stores every file and runs every process. A DNS-only record sends the browser toward the origin; a proxied record sends HTTP traffic through Cloudflare first. Neither option, by itself, creates an application runtime or moves your files.
This distinction matters during troubleshooting. If Cloudflare DNS is working but the origin server is down, visitors can still receive an origin error. If the origin is healthy but a DNS record points to the wrong address, the application may be unreachable. Treat DNS, the proxy and the origin as separate layers.
Can Cloudflare host a normal business website?
It depends on how the site is built, not on its branding or domain name.
Static marketing, documentation or portfolio site
If a build process produces files and the site does not require a long-running server process, Pages or Workers Static Assets may be sufficient. Your deployment pipeline uploads the output; Cloudflare serves it to visitors. Functions or Workers can handle selected dynamic requests when your design fits their supported runtime.
Full-stack application
Workers can combine static delivery with application logic and Cloudflare’s associated data and storage products. You still need to check framework adapters, runtime APIs, background work, database connectivity, file handling and any server features your application expects. “Full-stack” does not mean every server stack runs unchanged.
WordPress, PHP or another conventional server application
The usual design is to keep the application at a compatible origin host and put Cloudflare in front of it. The Pages and Workers documentation cited above does not establish that all such applications can be migrated without modification, so plan a platform-specific migration rather than treating Cloudflare as a drop-in shared host.
What you still need when Cloudflare is only the front door
- An origin host: a server or hosting account that stores files and runs the application.
- Application services: databases, queues, email delivery and other dependencies required by your software.
- Deployment and backups: a way to publish code and recover the origin independently of Cloudflare.
- DNS records: correct records for the website and any mail or verification services. Proxy only the records intended for web traffic.
Cloudflare can reduce exposure of the origin and add caching or filtering, but it does not remove the operational responsibilities of the origin provider.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How to choose between an origin host, Pages and Workers
- Describe the workload. List required runtimes, server-side modules, databases, file writes, scheduled jobs and long-running processes.
- Separate build-time from request-time work. If pages are generated during a build and requests only read assets, a static deployment is a candidate. If requests execute application logic, assess Workers APIs and limits.
- Check framework support. Review the current Pages and Workers documentation for your framework’s adapter, deployment command and runtime assumptions.
- Decide whether an origin is acceptable. If the application needs a conventional server environment or an unsupported module, retain a suitable host and use Cloudflare as DNS/proxy/CDN/security.
- Test non-page dependencies. Verify forms, authentication, webhooks, uploads, redirects, cookies, APIs and email after deployment or proxying.
Cloudflare’s current guidance favors Workers for new web-app projects, while Pages remains a usable deployment option. That is a product recommendation, not a guarantee that Workers is the correct runtime for every application.
Common misunderstandings and failure modes
“I changed nameservers, so my site moved to Cloudflare.”
Changing nameservers changes DNS authority. Unless you also deployed the project to Pages or Workers Static Assets, the files and application are still at the previous origin. Confirm the A, AAAA and CNAME records in Cloudflare DNS and verify which records are proxied.
“The Cloudflare dashboard shows my domain, but the page is blank.”
Adding a domain does not publish site content. For an origin setup, check that the origin serves the correct hostname and that the DNS record points to it. For Pages or Workers, confirm that a deployment completed and that the assigned project domain serves the expected output.
“A server feature stopped working after enabling the proxy.”
Inspect the request path, hostname and record type. Some services are not ordinary HTTP website origins and may require DNS-only records or a separate configuration. Check the origin logs and Cloudflare request details, then test the origin directly in a controlled way.
“Can I move every site to Workers because it says full-stack?”
No universal migration is established by the product pages. Workers supports frontend and backend logic, but compatibility depends on the framework, APIs and data services your application uses. Prototype the critical paths before retiring the existing host.
Performance, reliability and cost considerations
Using Cloudflare in front of an origin can change where requests are handled and which responses are cached, but the cited documentation does not provide a universal speed, uptime or cost figure. Performance depends on cacheability, asset size, origin latency, code execution and configuration. Measure your own routes and keep an independent origin recovery plan.
With Pages or Workers Static Assets, deployment and serving are part of the Cloudflare platform. You still need source control, build reproducibility, secrets management, data backups and a rollback process. A platform deployment is not a substitute for those controls.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A practical way to document either setup
When explaining an architecture to teammates or customers, capture the public result after DNS and deployment changes. A screenshot can show whether the expected hostname, redirects and UI are present, while logs and configuration prove which layer served the request.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstallOr skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP or PDF. It removes cookie-consent banners, newsletter popups and chat widgets before capture; bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing result. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
Use the ScreenshotNeo documentation for all options, including full-page and element captures, device and retina settings, waits, custom headers and cookies, request blocking, geolocation, PDFs, signed links, asynchronous jobs and bulk capture.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://developers.cloudflare.com/pages/ -o cloudflare-pages.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://developers.cloudflare.com/pages/"}, timeout=90)
open("cloudflare-pages.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://developers.cloudflare.com/pages/' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 shots each month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is included on every plan. Create a free ScreenshotNeo account.
Bottom line for your architecture
Cloudflare is not “only a CDN,” and it is not a general-purpose host for most websites. Keep a separate origin when your site needs a conventional server stack. Use Pages or Workers Static Assets for suitable static projects, and evaluate Workers for new applications that can run on its supported model. DNS, proxying and hosting are separate decisions; identify which one you are using before planning a migration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently Asked Questions
Can I use Cloudflare without changing my web host?
Yes. You can use Cloudflare DNS and proxy services while leaving the application and files at the existing origin, provided the DNS records and origin configuration are correct.
Is Cloudflare Pages the same product as Workers?
No. Pages is a deployment product that remains available, while Cloudflare’s current guidance recommends Workers for new web-app projects. Their deployment and runtime workflows should be evaluated separately.
Does Cloudflare host databases for my application automatically?
The documentation describes Workers integrations with data and storage services, but database requirements depend on your application. Selecting Workers does not automatically migrate or provision every database your site may need.
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.
Recommended Free Tools
