Hearing "free hosting" brings two images: a gift, or a trap that pushes you to upgrade. The truth is simpler. Hosting is a service that consumes resources, and a free plan caps those resources instead of charging money. Understanding the cap is what tells you whether it fits or you are already over it.

Where the limits actually appear

Claims like "unlimited space" usually mean a higher disk quota, not infinite disk. What is really limited on most free plans: file count (inodes), CPU time, memory per process, and concurrent processes. A small article site never approaches these; a WordPress install with thirty plugins receiving huge backups may touch them within months.

Email: the most overlooked limit

Many free plans allow receiving mail but cap sending, or set a low daily ceiling. If you send newsletters or client notifications, ask specifically about the daily sending cap before building on it. Email is the first thing to break as you grow, and the hardest to move later.

What you do not get for free

  • A response-time guarantee: support exists, but its priority is below paying customers, which is fine for a personal site and not for a store.
  • Guaranteed backups: a copy may exist, but the responsibility stays yours. Read the backup plan and treat your own copy as the source of truth.
  • Stable resources: limits or servers may change, so test performance over weeks, not one day.
  • Full configuration freedom: some features (ports, scheduled jobs, PHP extensions) may be restricted.

What users actually measure

Visitors do not care that a plan says "unmetered resources"; they care that your page opens in two seconds. Measure what they feel: first load on a phone, dashboard speed when publishing, and whether a normal-sized image uploads. Those three are more honest than a resource panel, and they will change before any warning appears in a report.

An exit plan before you need one

Every host, free or paid, deserves an answer to one question: how would I leave? Prepare today: a copy of the files, a database export, and a list of current DNS records. That small bundle turns a migration into routine work at any moment and protects you from a struggling provider. Test a restore at least once, because a backup you never restored is not a backup.

Questions to ask before signing up

  • What is the daily sending cap, and does it cover receiving too?
  • How many files (inodes) are allowed, and what happens past the cap?
  • Are backups automatic, how long are they kept, and who restores them?
  • Does the free space expire, and what happens to the site if I never upgrade?
  • Are the scheduled jobs or custom ports I need actually available?

How to know you are over the limit

Three early signals: recurring slowness at peak hours, scattered 503 errors, and failed uploads of medium files. Watch your backup folder size and file count too. If the signals repeat weekly, you do not only need optimisation, you need an upgrade plan. The cost-based comparison of free and paid is in this article.

When free is the right decision

For a learning site, a portfolio, a side experiment, or a blog that is just starting. In all those cases: own your domain if possible, keep your own backup, and use mail on your own domain. Those three make a later move a matter of hours, not weeks.

When to stop postponing the upgrade

When one hour of downtime means a lost client or order, the real cost is downtime, not the plan price. Count the outages last month and how long each lasted. If the total exceeds the cost of a paid plan, the decision is already made; only the execution remains.