Free Web Hosting Limits Explained (2026)

Every free web host has limits, including the ones advertising "unlimited" — the limits are just written in the fine print rather than the headline. They fall into three groups: resource caps on how much you can store and serve, feature locks on what the account can do, and reliability gaps in uptime and support. Understanding each one tells you in advance where a free host will stop working for you, so you are never surprised after you have built the site. Here is every common limit, in plain English.

Storage and file-count limits (inodes)

Free hosts limit both how much you store and how many files you store. The disk cap is the obvious one — InfinityFree, for example, gives 5 GB. The sneaky one is the inode limit: an inode is one file or folder, and free hosts cap the total count, often around 30,000 on a classic free host. This matters because a WordPress site with plugins can contain tens of thousands of small files and hit the inode ceiling long before it fills the disk. When you read "unlimited storage" on a free host, look for the inode limit underneath — that is the real cap, and it is the one people trip over.

Traffic limits: bandwidth, hits and CPU

Free hosts limit traffic in up to three ways, and "unlimited bandwidth" only addresses one of them. Bandwidth is the total data served. A daily hit limit is different and more restrictive: a "hit" is any single request — one page with ten images and two scripts is thirteen hits, not one. A classic free host capping you at 50,000 hits a day sounds generous until you realise a media-heavy page can spend dozens of hits per visitor, which is why the same host can advertise unlimited bandwidth yet suspend a site getting only a few hundred visitors. CPU and memory limits are the third lever, throttling database-driven sites that do real work per request. On the static free hosts, the equivalent limits are bandwidth (100 GB a month on Netlify and Vercel) or genuinely unlimited (Cloudflare Pages).

File-size and upload limits

Many free hosts cap the size of a single file, often around 10 MB. That sounds harmless until it blocks something ordinary: a large image, a PDF, a backup archive, or a WordPress or plugin update package that arrives as one file. The limit also complicates restoring a site, because a full backup is usually a single large file that will not upload. When you evaluate a free host, check the per-file size limit alongside the storage cap — the two together decide what you can actually put on the site.

Feature locks: email, cron, SSH and databases

Beyond raw resources, free hosts lock away features. Almost none give you email at your domain, so you cannot send or receive mail as [email protected] — a genuine problem for anything that looks like a business. Scheduled tasks (cron), shell access (SSH) and background jobs are commonly disabled. Database counts and sizes are capped on the PHP hosts, and the static hosts have no database at all. Custom domains are sometimes reserved for paid plans, though the best free hosts include them — a distinction we cover in using a custom domain on free hosting. Each lock is a place the free plan is nudging you toward paying.

Reliability limits: uptime and support

The limits that do not appear as numbers are often the most important. Free plans rarely carry an uptime guarantee, so a slow or down day is simply something you absorb. Support is a community forum, not a person with a deadline, which means a broken site can stay broken while you wait for a reply. And free accounts are the first to be suspended when a server is under strain or a limit is exceeded, sometimes with little warning. None of this makes free hosting unusable — it makes it unsuitable for anything that has to stay up, which is the single most useful thing to know about it.

How to live within the limits

You can stretch a free host a long way with a few habits. Keep the site as static as possible, because static files barely touch the limits that throttle database sites. Optimise images so each page spends fewer hits and less bandwidth. Prune unused files and plugins to stay under the inode cap. And keep a full backup off the host, so a suspension is an inconvenience rather than a loss. Match the host to the job using our best free web hosting guide, and the limits stop being surprises and become a spec you designed around.

How free-host limits compare to cheap paid

A cheap paid plan does not just raise these limits a little — it removes most of them as a category. There is no daily hit limit on a normal shared plan, so a busy day is fine rather than a suspension. Inode caps are far higher or effectively irrelevant for a typical site. File-size limits are generous enough that updates and media are not a problem. Email at your domain is usually included, cron and databases are available, and there is an uptime commitment with support behind it. That is why the honest framing is not "free is bad" but "free is a fixed budget of resources." You design within that budget while it fits, and the day your site needs more than the budget allows, a few dollars a month buys a much larger one. Our guide to when to upgrade from free hosting maps the limits to the exact moment it is worth paying.

The limit you'll hit first

Different sites meet different walls first, and knowing which one is coming for you saves a lot of frustration. A media-heavy site — lots of images, a gallery, big downloads — usually hits the daily hits limit or the bandwidth cap before anything else, because every asset is a request. A plugin-heavy WordPress site tends to hit the inode cap first, since each plugin adds hundreds or thousands of small files. A site that publishes large files runs into the per-file size limit. And any site that needs to email its visitors — order confirmations, password resets, newsletters — hits the no-email wall immediately, regardless of traffic. Look at your own site and ask which of these it leans on hardest; that is the limit that will define your experience of a free host, and the one to weigh most heavily when you choose.