How much VPS memory and storage does your site need?

Your current server is the best starting point for choosing its replacement. Check what it uses during a busy period, including scheduled jobs, rather than ordering from a quiet-hour screenshot.

For a new site, collect the software’s requirements and allow room for the database, uploads and maintenance work. An empty installation is rarely the full workload.

Put the published plans beside your measurements

xUID plan	Resources	Monthly USD price
VPS 1	1 vCore, 2 GB RAM, 50 GB SSD	$400
VPS 2	2 vCores, 4 GB RAM, 100 GB SSD	$500
VPS 3	4 vCores, 8 GB RAM, 150 GB disk	$600

Each plan includes one IPv4 address and a minimum 100 Mbps network. The step from VPS 1 to VPS 2 adds a vCore, 2 GB RAM and 50 GB SSD for $100/month. VPS 3 adds two more vCores, 4 GB RAM and 50 GB disk for another $100/month.

Check more than the website folder

Memory supports the operating system, application processes and database. Record its use during traffic peaks and background work such as search indexing or an import. If you already see memory-related failures, include those symptoms in the enquiry.

Storage needs to cover uploads and the database as well as the application. Logs, temporary files and any local backup copies take space too. Record current use and recent growth so a new plan doesn’t begin nearly full.

Suppose your site already uses 42 GB of disk. Moving it to a 50 GB plan would leave 8 GB before accounting for growth and differences in the new setup. That is a reason to discuss more capacity, not a claim that every 42 GB site needs the same server.

CPU and network numbers need context

Tell the team when the application gets busy and what it does at those times. Serving cached pages, processing images and searching a large forum database can place different demands on a server.

The minimum network speed in the plan is not a statement of monthly transfer allowance or an end-to-end speed guarantee. Include your expected transfer, visitor locations and any special network requirement so the service can be confirmed around them.

Avoid sizing solely by registered users or page views. A mostly static archive and an interactive community can have similar audience numbers but very different workloads.

Send enough detail to make the choice

Send your software and versions, current server specification, busy-period resource use and expected storage growth. Add any setup or management work you need.

Compare the VPS plans once those details are together. For resources outside the published plans, use a VDS enquiry or the dedicated-server checklist. Forum owners can also use the community hosting page to plan database, mail and migration requirements together.