Cloudflare Pages is a deployment target. Most websites need a home.
Pages is free, unmetered and genuinely fast, and it is superb at the job it was built for: shipping a developer’s build output to the edge. The friction starts when the person maintaining the site is not a developer, when the images and fonts are the reason the page is slow, or when Cloudflare’s own roadmap moves on.
It is a developer console, not a site dashboard
You need a Cloudflare account and either wrangler or a build command. Direct Upload exists, but a deployment is immutable: there is no file editor, so changing a phone number means rebuilding or re-dragging the whole folder from your computer, and the drag-and-drop box caps at 1,000 files. The same dashboard manages DNS, WAF and Workers, which is a lot of surface for one landing page.
Files go out exactly as they were uploaded
Pages serves the build output as-is. Cloudflare retired Auto Minify in 2024; Polish and Image Transformations are separate, separately billed products configured on your domain’s zone, not on the Pages project. Font subsetting, lazy loading and LCP preloads are yours to wire up in the build. A 2 MB hero JPEG on a fast edge is still a 2 MB download on 4G.
The platform has moved on to Workers
Cloudflare’s documentation now points new projects at Workers with static assets and publishes a Pages-to-Workers migration guide; new platform features ship for Workers first. Existing Pages projects keep working and there is no deadline, but for a business owner it is a second platform to learn, with the same wrangler workflow, to stay on the recommended path.
Cloudflare Pages details as published in Cloudflare Docs (500 builds/month, 20,000 files per deployment, 1,000 files via drag-and-drop, 25 MiB per file, immutable deployments, Auto Minify retirement, Workers recommended for new projects). Check developers.cloudflare.com for the current wording.
Side by side, for a finished static site
Netlify and GitHub Pages are in the table because they are the other names on every “static hosting” list. All four are good products; they are built for different people.
| What you need | Fylo.Host | Cloudflare Pages | Netlify | GitHub Pages |
|---|---|---|---|---|
| Upload a finished folder as a ZIPNo account, no CLI | ✓ | Drag & drop, 1,000 files | Netlify Drop | Git push only |
| Edit a file in the browser and go liveNo redeploy to wait for | ✓ | Redeploy the folder | ✗ | Commit, then rebuild |
| Source files stay private on the free plan | ✓ | ✓ | ✓ | Public repo required |
| Business and client sites allowed on freePer each provider’s terms | ✓ | ✓ | ✓ | Restricted by terms |
| Built-in blog: posts, pages, categories, RSS, sitemapWritten in the dashboard, no build | ✓ | Bring a CMS | Bring a CMS | Jekyll, Markdown in git |
| Images converted to WebP / AVIF for youWithout changing your HTML | ✓ | Paid, on your zone | URL rewrite / adapter | ✗ |
| Font subsetting, minification, lazy loadingApplied by the host | ✓ | Auto Minify retired | Build plugins | ✗ |
| Responsive srcset and LCP preload injected | ✓ | ✗ | ✗ | ✗ |
| Contact form without a backend | Pro plans | Write a Function | ✓ | Third-party service |
| Visitor analytics in the dashboard | ✓ | Web Analytics | Paid add-on | Third-party service |
| Custom domain with automatic SSL | Paid plans | ✓ | ✓ | ✓ |
| Free-plan traffic allowance | 1,000 visits / mo | Unmetered | Credit-metered | Soft 100 GB / mo |
| Git-connected builds and deploy previews | ✗ | ✓ | ✓ | Builds, no previews |
| Server-side code (functions, SSR) | ✗ | Functions, Workers rates | ✓ | ✗ |
Keep Cloudflare Pages for the app. Move the website to Fylo.
A switch that costs you something you rely on is a bad switch. Here is the honest split.
Cloudflare Pages is still the right pick when
- You are a developer with a repository, a build command and wrangler already installed, and push-to-deploy with previews is how you work.
- The site needs server-side code: Pages Functions, KV, D1 or Durable Objects bindings, or a framework rendering on the server.
- You need a custom domain on a free plan, or many of them. Pages includes them; Fylo’s custom domains start on Starter.
- Traffic or media is heavy. Pages does not meter static bandwidth; Fylo’s free plan is sized for 1,000 visits a month, with paid plans from 25,000 up.
- Your DNS, WAF and Workers already live in one Cloudflare account and you want the site in the same place.
Fylo is the better fit when
- The person who maintains the site is not a developer, and “change the opening hours” should take one minute in a browser, not a redeploy.
- The images and fonts are the reason the page is slow, and you want them fixed by the host rather than by a build step and a paid image product.
- The upload is a Webflow or Framer export, an AI-generated page, a bought template or a Hugo, Astro or Eleventy build.
- Your visitors are on phones and mobile data, and Core Web Vitals decide whether the page ranks.
- The site needs a blog, a contact form and analytics from one dashboard, in English, Hindi, Tamil, Bengali or whatever your readers speak, without a CMS, a Function or three third-party services.
Cloudflare Pages to Fylo in four steps, no downtime
Around ten minutes for a plain HTML site. Keep the Pages deployment live until your DNS change lands; nothing in the Cloudflare account needs deleting. If the site needs a blog, open the Blog tab afterwards.
Get the built site
Direct Upload project: it is the folder you dragged in. Git-connected: run the build locally (npm run build) and use the output folder, usually dist or public, which is what Pages actually serves.
dist/about/index.html
dist/assets/main.css
dist/img/hero.jpg ← 2.1 MB
Zip it and upload
Compress the folder so index.html sits at the top level of the ZIP, then drop it on the homepage. Live on a fylo.dev address in seconds. No account, no wrangler, no build settings to fill in.
Switch on the optimizations
In the performance tab, turn on the toggles you want. Fylo rebuilds an optimized copy; your uploaded files stay exactly as they were.
Point your domain
On a paid plan, add the domain in the Fylo dashboard. In your DNS, change the CNAME target from the pages.dev address to the Fylo address, then remove the custom domain from the Pages project. SSL is issued automatically.
www CNAME my-site.pages.dev
www CNAME your-site.fylo.dev
; SSL issued automatically
The performance work Cloudflare Pages leaves to your build
Every item below is a toggle in the dashboard. Turn one on and Fylo rebuilds the optimized copy at the edge; turn it off and the original is back. No build plugin, no wrangler, no Images subscription on your zone.
Nothing is applied silently. You choose what runs, and you can check the result on the speed checker before pointing a domain.
Add a blog to the site without a build pipeline
A Cloudflare Pages blog is a static site generator, a headless CMS or Markdown in git, a build command and a deploy on every post. On Fylo every site gets a Blog tab: write a post, pick a category, add an image and publish. Fylo writes the static post page, the archive pages, the RSS feed and the sitemap, and serves them from the same edge as the rest of the site.
- Posts and pages in a rich-text editor, with a Code view when you want the HTML
- Categories, tags and a navigation menu; a media library for images
- Three themes, or “match my site” to inherit your own header and footer
- Draft preview link, RSS feed, sitemap with lastmod, SEO checklist on every post
- Hindi, Bengali, Tamil, Telugu, Urdu and a dozen more scripts, with the right fonts loaded
- Lives on your custom domain at
/blog/; 10 published posts on the free plan, more on paid plans
The rest of the shortlist, and who each one suits
If Fylo is not the fit, one of these probably is. The one-line verdicts are ours; the products are all solid.
Cloudflare’s own recommended path for new projects: the same edge and wrangler workflow as Pages, plus Durable Objects, cron triggers and the newest features first. Still a developer tool, still served as uploaded.
Repository, build command, deploy previews, forms and functions in one place. A credit-metered free plan that pauses the site when credits run out. Fylo vs Netlify
Free hosting straight from a public repository, with a free custom domain. Git push only, and GitHub’s terms rule out using it for a business site. Fylo vs GitHub Pages
Drag a ZIP or a single HTML file and get a link. Simple and friendly; no optimization pipeline, and the free plan is meant for one small site. Fylo vs Tiiny Host
Upload a folder, a PDF or a gallery and get a link, with an online editor. Served as uploaded; free sites need a login every 90 days. Fylo vs Static.run
Upload a ZIP, toggle the optimizations, add a blog, serve from the same 330+ cities as Pages. Built for sites whose visitors are on phones and whose owners are not running wrangler.
Sites that leave Cloudflare Pages for Fylo
Questions people ask before switching
index.html in it. Zip it, drop it on the homepage and the site is live. Changes are made by uploading again or by opening the file in the dashboard’s code editor, editing it and saving.Same edge you deployed to with wrangler.
Faster site, no wrangler.
Drop your ZIP. We handle the milliseconds, and the blog.
Upload your site free No signup. No account on Cloudflare. Live in seconds.