Skip to content

Knowledgebase

Understanding unmetered bandwidth and unlimited hosting features

web-hosting, performance

Unmetered bandwidth and unlimited feature labels describe particular parts of a hosting package. They do not mean that the account has infinite computing power or that every possible workload is suitable for shared hosting. Read each label alongside the package's storage, processing, memory and other operational limits, and the applicable service terms.

01 Understand what uses account capacity

Bandwidth concerns the data transferred by your website and related services. Processing resources concern the work needed to serve that data. A heavily cached image and a request that runs many database queries can transfer similar amounts of data while placing very different demands on the server. An unmetered traffic allowance therefore does not prevent a poorly configured application from exhausting its available resources.

The same distinction applies to features such as mailboxes, databases or addon websites. Being able to create many of these does not give each one an independent hosting account. They still operate within the selected service's available capacity. A large collection of mail messages, temporary files, backups or cached objects can also create practical storage and file-count pressure even when no individual website looks especially large.

02 Plan for the workloads the package supports

Use these offers for the websites and associated services the package is designed to host. They are not permission to run unrelated high-load services or to use ordinary hosting as an unrestricted storage platform. If you expect unusually large transfers, persistent processing or a rapidly growing file collection, describe the workload to us before launch.

03 Respond to a limit warning

When a limit warning appears, review the specific measurement rather than assuming that an unlimited label makes the warning incorrect. We can help identify whether cleanup, caching, application changes or a different package will address the actual constraint. This makes capacity planning more reliable than choosing a service from one headline alone.

What should I do when an account-limit warning appears?

  1. Read the resource name, the reported value and the period covered by the measurement.
  2. Separate stored-data limits from limits on simultaneous processing. Clearing a few files will not necessarily resolve a CPU-heavy request.
  3. Check all websites, mailboxes and background jobs sharing the account before choosing cleanup or an upgrade.

Ask us for clarification if a headline allowance and an account limit appear inconsistent. Include the selected plan and the exact warning. Avoid deleting data merely to clear a chart: first identify what owns it, whether it is still needed and what recovery copy exists.

Sources and further reading

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support