A Cloudflare Pages Alternative Without The Setup

You opened the Cloudflare dashboard and the sidebar has about thirty things in it. DNS. WAF. Workers. R2. Turnstile. Zero Trust. Tunnels. Pages is in there somewhere, because Pages is what somebody told you to use, and what you were trying to do was put four files online.

That mismatch is the honest reason most people go looking for a Cloudflare Pages alternative. It is almost never the price.

Cloudflare's free tier is the most generous one in this comparison by a distance, and I will show you the numbers. Cloudflare is also not a hosting company. It is an infrastructure company, and Pages is a door into a platform rather than a place to put a file.

Every number below was checked on 9 October 2026 against Cloudflare's own documentation, because this product moved recently and most posts have not caught up. I run a hosting service myself, so read the tables with that in mind. For the wider field, the static hosting comparison has it.

What Opening Cloudflare Pages Actually Puts In Front Of You

A network console, with your folder as one small item inside it. Pages sits in the same dashboard as DNS records, firewall rules, Workers, R2 buckets and Zero Trust policies, and inherits its assumptions.

You can see it in the vocabulary. The create screen asks whether you want Direct Upload or a git connection, and then there is a production branch, a build command, an output directory, bindings, a compatibility date, and a tool called Wrangler. Every one of those words is useful to the reader it was written for. None mean anything to someone holding an index.html.

You do not have a production branch. You have a file.

That is the trade. Cloudflare gives you the network that serves some of the largest sites online, certificates included, and asks you to learn its model first. If certificates brought you here, what a certificate costs now is worth two minutes.

So the platform is not the problem. Here is what is.

Cloudflare Pages Free Limits, Checked October 2026

From Cloudflare's Pages limits page on 9 October 2026, the Free plan gives you:

• 20,000 files per site, rising to 100,000 on a paid plan.
• 25 MiB maximum per file, the same on free and paid.
• 500 builds a month, against 5,000 on Pro.
• 1 concurrent build, against 5 on Pro.
• 100 custom domains per project and 100 projects per account.
• Unlimited preview deployments and an unlimited number of users.

Notice what is missing. No bandwidth number, no request number, no visitor number, because there is no meter.

The sentence that confirms it is not on the limits page, which is why people miss it. It is on the Pages Functions pricing page: "on both free and paid plans, requests to static assets are free and unlimited. A request is considered static when it does not invoke Functions."

Nothing else here matches that. Netlify meters a free project in credits and pauses it when they run out; GitHub Pages carries a soft 100 GB a month. Cloudflare just serves the file.

The Upload Choice You Cannot Take Back

The route with no git is called Direct Upload, and choosing it is permanent. Cloudflare's documentation, checked 9 October 2026, says it in one line: "if you choose Direct Upload, you cannot switch to Git integration later."

That decision happens on the create screen, in the first thirty seconds, before you know what the project will become. It is documented, and the docs are not where you are when you click.

Six months later you learn git, or hand the site to a developer, and the fix is not a setting. You create a second project, upload again, move the custom domain across and delete the first. Not a disaster. Just an afternoon you did not budget, over a radio button nobody explained.

Three more details, same source and date:

• Drag and drop takes a zip file or a single folder of assets, capped at 1,000 files and 25 MiB each.
• Wrangler, the command line tool, takes a single folder and zip files are not supported. The two routes accept opposite inputs.
• No build runs for you. You build locally, then upload the output.

If your project has no build at all, the short way to get one HTML file online is what you need.

Where Free And Unlimited Gets An Edge

The moment anything on your site stops being a static file. That is when the free plan starts counting.

Cloudflare's Pages Functions pricing page is explicit: "requests to your Pages Functions count towards your quota for the Workers Free plan." That plan, on Cloudflare's pricing page the same day, allows 100,000 requests a day, resetting at midnight UTC, with 10 milliseconds of CPU time per invocation. Workers Paid starts at a $5 minimum per month.

So "free and unlimited" is true, and it covers exactly the part of your site that is a file. Add one function for a contact form and it sits on a different meter, with a daily reset and a CPU ceiling.

This only matters if you reached for Pages Functions assuming the whole project sat on the unlimited side. A form needs no function at all on any host: how a form works with no back end covers the ways that work.

Cloudflare Now Says To Start New Projects On Workers

This changes the question, and most comparison posts predate it. The Cloudflare Pages documentation, checked 9 October 2026, opens with a banner:

Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare's primary platform for building applications. Start new projects with Workers.

Pages is not deprecated and nothing I found says it is going away. But when a vendor tells you to start new projects somewhere else, that belongs in your decision.

The awkward result: there are three ways to get a folder onto Cloudflare and they disagree about setup.

Read down that table. The only route with no setup is a one hour preview. The only permanent route with no command line is the product Cloudflare just told you not to start new projects on. The one it recommends begins with a terminal.

None of that makes Cloudflare wrong. It makes it an infrastructure company behaving like one.

A Cloudflare Pages Alternative With No Console To Learn

If the console is the cost, compare on setup, not features. All cells checked 9 October 2026.

Netlify Drop is what I point people at when they need a link in five minutes, because it hands over a URL before asking who you are. Tiiny Host has the gentlest interface and the tightest free tier, so check that 3 MB figure against your images folder first.

What OxyPages adds is the part Pages leaves to you after the upload. A contact form works with no code: submissions land in your dashboard and arrive by email, where on Pages a form means writing a Pages Function. A shared password is one switch on a paid plan, where Pages offers Cloudflare Access sign-ins or a Worker you write yourself. And you can paste HTML instead of uploading a file, then change the live site in the browser, with an AI editor if you want one, instead of uploading again.

Where we are the wrong answer, plainly. OxyPages runs no build step and no server-side code, so a Next.js project that needs rendering, or anything that wanted Pages Functions, belongs on Cloudflare or Netlify. We hold the output. We do not build it.

Who Should Stay With Cloudflare Pages

Most people reading this should stay. Stay if any of these is true.

1. Your DNS is already at Cloudflare. Domain, records and certificate in one place. Splitting them across two vendors to save nothing is a bad trade.
2. You need a firewall in front of the site. A WAF filters HTTP requests against a rule set before they reach your pages, and almost no plain upload host has one. OWASP on what a web application firewall does
3. You are expecting a traffic spike. Static asset requests are free and unlimited on both plans, which is the strongest position here and not close.
4. You already push to git and run a build. The setup cost is paid, and Pages does the rest for nothing.
5. You want Workers, KV or R2 beside the site. One account, one bill, and the bindings that looked like jargon become the reason you are there.

Leave only if the setup is what you are paying for. A permanent choice made in the first thirty seconds, in a console built for engineers, is a steep price for four files that will not change again.

What To Do Next

Ten minutes, in this order.

1. Look in your folder for a package.json or a build script. If there is one, Cloudflare is a reasonable home and the console is worth learning.
2. If there is no build, count the files and check the largest. Under 1,000 files and nothing over 25 MiB means Direct Upload will take it today.
3. Decide whether anything on the page needs to run code. If yes, that part is on the Workers meter.
4. Ask whether the project might ever move to git. If it might, do not pick Direct Upload, because that door closes behind you.
5. Publish on a free tier before paying anybody, then open the result on your phone on mobile data.

If step one found no build and step four made you hesitate, you do not need a better platform. You need an upload box, and drag your folder in and get a live link is about a minute of work.

Cloudflare's free tier is excellent and the network is genuinely the best here. None of that helps if the first screen asks you a question you cannot answer yet.