A Netlify Alternative: Simple Hosting Without Git

You have a folder of files. Somebody told you to put it on Netlify, and every tutorial you opened starts by connecting a GitHub repository.

So you went looking for a Netlify alternative, because you do not have a repository and you do not want one.

Worth knowing before you go anywhere: you never needed git. Netlify Drop takes a dragged folder with no account at all. Vercel shipped the same route on 12 June 2026. Cloudflare Pages has accepted a zip from its dashboard for years. The "you must connect a git provider" advice is out of date, and thousands of posts repeat it anyway.

So "without git" is the wrong reason to leave. The real reasons sit after the upload: what the free plan counts, what happens when you run out of it, and whether the link you were handed is public yet. For the wider field rather than this one decision, every static host compared on what you are already holding covers it.

Everything below was checked on 9 October 2026 against Netlify's own pricing page and docs. I run a hosting service myself, so read the table with that in mind.

Do You Actually Need Git To Use Netlify?

No. Netlify Drop publishes a dragged folder without a repository, a command line, or even an account.

Netlify's own Drop quickstart, checked 9 October 2026, describes it as "the simplest way to publish a site: drag and drop a folder of files and it goes live instantly, no account required".

Three details from that same page matter more than the marketing line:

• Deploys under 50 MB work best, and Netlify warns that individual files over 10 MB may cause your deploy to get stuck.
• It only builds for you if you are signed in. Drop a project that needs npm run build while logged out and the files publish exactly as they are, build step untouched.
• Updating is the same action. Drag the revised folder onto the project's drop zone and it publishes a new production version.

The same route exists elsewhere. Vercel Drop launched on 12 June 2026 and its docs say plainly that you need no git, no CLI and no local setup, though it does require a Vercel account first. Cloudflare calls its version Direct Upload and takes a zip or a single folder from the dashboard, capped at 1,000 files by drag and drop and 25 MiB per file.

If you want to know what you are turning down, the Pro Git book on what a repository actually is is the primary source.

So the git question is settled. Now the part that actually decides this.

The Two Gates Between A Dropped Folder And A Public Link

A dropped Netlify project is not necessarily a public web page, and that catches people who expected to send the URL to a client the same afternoon.

Gate one: drop without signing in and Netlify's docs say "your project URL is protected with a temporary password until you claim it". The link exists, and a stranger cannot open it.

Gate two is newer. For Netlify teams created on or after 28 July 2026, the default project visibility is private, and that applies to every creation method including Drop. A private project needs a Netlify login to view, and someone without access gets a Netlify page telling them to request it from the owner, not your homepage.

You flip it public yourself, and the project needs one successful production deploy before you can. On Free and Personal, private projects are single seat, so only the team owner can see them.

None of that is dishonest. It is a sensible default for work in progress, and the exact opposite of what you want when the job was handing somebody a link.

What Netlify's Free Plan Actually Meters

Credits, not bandwidth. Free is $0 a month with a hard limit of 300 credits, spent across five meters. These rates come from Netlify's pricing page and credits docs, checked 9 October 2026.

Two rows there are genuinely generous. Deploy previews and form submissions both cost nothing, which is why Netlify Forms is still the easiest contact form for a site with no server. how a form works on a site with no back end covers the mechanism, which is the same everywhere.

Notice that one meter can finish the month on its own. A page with a few large images, shared somewhere busy for an afternoon, is a bandwidth event. Twenty production deploys is not many either, if you spend a Sunday on a layout.

What Happens When The 300 Credits Run Out

Every web project on your team is paused, and visitors get a "Site not available" page at each URL.

That is Netlify's own wording in its billing FAQ, checked 9 October 2026. Paused means no web requests, no form submissions and no new production deploys, and it is team-wide, so one busy project takes down the quiet ones beside it.

On a paid plan you can turn on auto recharge and keep serving. On Free there are two options: wait for the next billing cycle, or pay.

What The Free Plan Does Not Include

From Netlify's plan comparison and billing FAQ, checked 9 October 2026:

• No add-on credits. You cannot buy your way out of a pause on Free.
• No auto recharge. That is a Personal and Pro feature.
• No credit rollover. The balance resets each cycle, and rollover starts on Pro at 5,000 credits.
• No extra team members. Free and Personal cannot add team member seats at all.
• One concurrent build, and one day of retention on observability, web analytics and real user monitoring.
• No shared environment variables, role-based team access, or private organisation repositories.

One clause people expect and do not find: there is no non-commercial restriction. Netlify's Free plan page says you can deploy commercial projects on it. That beats Vercel's Hobby plan, which the Vercel docs restrict to non-commercial personal use, and it is the most common reason I tell someone to stay put.

If your account predates 4 September 2025 you may be on a legacy plan instead, where Free means 100 GB of bandwidth and 300 build minutes a month as hard limits, and going over suspends the site for the rest of the calendar month. Same outcome, different arithmetic.

Every Netlify Alternative Worth Dropping A Folder On

Four no-git routes, compared on what happens after the upload rather than before it. All cells checked 9 October 2026.

Two honest caveats. Cloudflare publishes file and build ceilings rather than a bandwidth meter, which is not the same as promising unlimited traffic forever. And Hobby is non-commercial only, so a shop or a client site belongs on Vercel Pro at $20 per user a month however little traffic it gets.

Where we are the wrong choice, plainly: OxyPages runs no build step and has no catch-all rewrite, so a single-page app whose router invents /about with no about.html behind it will 404 on a refresh. Netlify, Vercel and Cloudflare Pages all handle that properly. If that is your project, pick one of them. what a static site can and cannot do draws the line.

Who Should Stay With Netlify

Netlify is an excellent product and plenty of people reading this should not move. Stay if any of these is true.

1. You deploy from a repository on every push. That is what Netlify is built for, and a drop page is a downgrade.
2. You use Netlify Forms. Submissions cost zero credits, and rebuilding that elsewhere is work you did not plan for.
3. You need functions, edge functions or a database next to the site. Credits cover all of it in one bill.
4. Your traffic fits inside 300 credits. Moving a working site is a cost with no benefit.
5. You want deploy previews on every branch. They cost nothing on every credit plan, which is unusually fair.

Move only if the pause model is the problem. A free site that one busy afternoon can switch off team-wide is fine for a side project and wrong for a client deliverable. That is the whole decision.

What To Do Next

Fifteen minutes, in this order.

1. Open your folder. If there is an index.html and no package.json, nothing needs building, so build features are irrelevant to you.
2. If you are already on Netlify, check credits spent this cycle on your team's usage page. Nowhere near 300? Stop here.
3. Check your project's visibility. A project created after 28 July 2026 may still be private, which explains any "cannot access" message a client sent you.
4. Decide the address. A subdomain is right for anything temporary. For anything commercial, point a domain you already own at it first, because changing it later costs you every link.
5. Publish once on a free tier before you pay anybody, then open the result on your phone on mobile data.

If you have decided and just want the folder live somewhere that will not pause your other sites because one had a good week, drag your folder in and get a live link takes about a minute.

Then stop comparing. Git was never the obstacle here, and the only number worth checking is how your traffic lands against 300 credits a month.