payless.host
How shared hosting works, and where its limits are
Updated Nov 22, 2026
What shared hosting is
Shared hosting puts hundreds of websites on a single server, each with a fraction of the processor, memory and storage. When you upload files or a visitor loads a page, the server handles your request alongside everyone else's. The provider sets limits on how much each account can use, and enforces them when load crosses a threshold.
The trade-off: low cost in exchange for limits you will eventually meet.
How files reach the server
You connect through FTP, SFTP or a file manager inside the control panel. The credentials arrive in the welcome email after signup. Point your FTP client at the hostname, username and password provided. The connection drops you into a directory, usually `public_html` or `www`, where anything you upload becomes visible at your domain.
What can go wrong: wrong credentials, firewall blocking port 21 or 22, or uploading to the wrong directory. Check by putting a single `index.html` file in `public_html` and visiting your domain — if it loads, the path is correct.
How the server identifies your site
A domain points to the server's IP address through DNS. The server reads the domain name in each incoming request and serves files from the matching account. One IP address handles thousands of domains this way, which is why shared hosting costs what it does.
What can go wrong: DNS not updated, or updated but not yet propagated. Propagation takes minutes to hours. Check by visiting the IP address directly if the provider gives you one, or by pinging your domain from a terminal — if it resolves to the provider's IP, DNS is set.
How databases are shared
MySQL or MariaDB runs on the same server or a dedicated database server, with each account allowed a set number of databases and a storage cap. WordPress, for instance, creates tables inside one database to hold posts, users and settings. The database server handles queries from hundreds of sites at once, and slow queries from one account can stall others.
What can go wrong: hitting the database limit, or a query timing out under load. Check database count and size in the control panel under MySQL or Database Management. If queries fail, check the error log for timeout messages.
Resource limits and how they are enforced
Every shared plan rations CPU time, memory, simultaneous processes and disk I/O. Cross the limit and the provider throttles the account or suspends the site temporarily. Limits are usually invisible until you hit them, and what counts as excessive varies by provider and plan.
DreamHost lists limits in its hosting documentation. HostGator enforces them through CPU and memory caps in cPanel. Hostinger documents thresholds in its knowledge base. Namecheap and InterServer state limits in terms of inodes, entry processes and CPU seconds. SherlockHost advertises unlimited everything, which makes the actual boundary impossible to judge.
What causes you to hit limits
Traffic spikes, unoptimised images, plugins running background tasks, database queries without indexes, or another site on the same server monopolising resources. Shared hosting assumes your site idles most of the time. A site that stays busy will be asked to move.
What can go wrong: the site loads slowly, returns 503 errors, or the provider sends a warning email. Check server load and process count in the control panel if available, or ask support for a resource usage report.
When to move off shared hosting
When you receive multiple resource warnings, when load times degrade despite optimisation, or when you need a fixed resource guarantee. Shared hosting works until your site's demand becomes incompatible with a shared environment.
The next step is VPS, which gives you dedicated CPU and memory in exchange for managing more of the software yourself, or managed WordPress hosting, which raises the resource ceiling while keeping the interface simple.
