How can I increase my web storage space?
- Select “Products” in the menu on the left.
- In the “Products” menu, choose “Web Hosting”.
- Under “Web Space”, click on “Show details”.
- Go to the “Storage” section and click on “Reserve additional storage space”.
- Click on “Edit”.
- Select the desired extension in GB increments using the “+” symbol; the resulting annual costs will be displayed directly to you. Please note that the first payment may be lower, as the extension duration is adjusted to the duration of your reserved web hosting package and is prorated when you order for the first time.
- Confirm the paid reservation by checking the corresponding box and complete the order by clicking “Save”.
Understanding quota vs. actual usage
“Webspace” refers to the storage allocated to your hosting package for website-related data. In practice, this includes the files you upload to your web directory (for example, HTML, PHP, images, and downloads) and any additional data stored within the webspace structure generated by your applications. Many users assume webspace is only the visible website files. Still, real usage often grows due to system- and application-generated content, such as caches, log files, backups created in the web directory, and media uploads from a CMS.
Usage reporting may not always feel intuitive because the webspace total is the sum of many folders and file types. That is why you can hit quota limits even when you believe “the website didn’t change.” A quota increase expands your allowed maximum, but it does not automatically reduce existing consumption. The most effective approach is to treat webspace as a capacity budget: increase it when you expect sustained growth, and periodically review what is consuming it so you can avoid sudden outages when it reaches its limit.
How to identify what is using the most space (top offenders)
Before increasing webspace, or immediately after, identify what is consuming the most storage. This helps you decide whether you genuinely need more quota or whether a cleanup will solve the problem faster and at lower cost. In webhosting environments, the biggest offenders are usually not core website files, but generated content.
Common storage drivers include:
- Media uploads (especially large images and videos in CMS libraries)
- Backups stored inside the web directory (manual backups, plugin backups, full-site exports)
- Cache directories (page cache, image optimization cache, staging caches)
- Log files created by applications or scripts
- Old staging or test installations that were never removed
A practical method is to review directory sizes and look for unexpectedly large folders, then confirm whether those files are still needed. If your setup allows file manager or SSH access, check folder-level usage first and focus on the most significant directories. Start with typical hotspots such as uploads, cache, backup, and any plugin-generated storage. This targeted approach often frees meaningful space without impacting the site.
Cost and billing impact of increasing webspace
Increasing your webspace quota is typically tied to the commercial limits of your web hosting package. Depending on the product model, raising storage may be part of an upgrade path, a configurable add-on, or a change that affects recurring fees. Users often expect storage to be “just a slider,” but in billing terms, more allocated resources usually mean a higher monthly or yearly cost.
Best practice before saving a higher quota:
- Confirm whether the portal indicates a pricing change as part of the update process.
- Make the change intentionally (avoid repeated edits) so you can track what you selected and when it takes effect.
- If you are increasing storage for a short-term spike (for example, a one-time import), consider whether cleanup or offloading large files is a better long-term approach than permanently growing quota.
After increasing the quota, monitor the next invoice and confirm it reflects the expected billing adjustment. This prevents surprises and helps you align resource needs with your budget.
Troubleshooting: quota increased but issues remain
If you increased webspace but you still see errors, the problem is usually one of three things: the change has not yet fully reflected everywhere, the site is still at or near the limit, or the underlying issue is not webspace-related.
Work through this sequence:
- Verify the new quota is visible in the portal and refresh after a short interval if needed. Some systems take time to synchronize the updated value.
- Confirm actual usage vs new quota. If usage remains exceptionally high, you may continue to experience failures (uploads, updates, cache writes) until you free up space.
- Check for large temporary growth drivers. Backup plugins or logging can immediately consume newly added space, making it seem like the increase “did nothing.”
- Consider other limits. Some errors are caused by database size limits, mail storage limits, or application-level restrictions, not webspace quota. If a CMS update still fails after increasing webspace, check whether the failure is due to permissions, PHP limits, or database issues rather than disk capacity.
This structured troubleshooting approach prevents repeated quota changes and helps you quickly resolve the actual bottleneck.