Illustration for choosing a Cloudways server size: three servers of growing size under a load gauge

This article contains affiliate links. AutomateWithMNK may earn a commission if you sign up through certain links, at no additional cost to you. This does not influence our editorial assessment.

Which Cloudways server size do you need?

Start small, measure, then resize. On Cloudways Flexible a server grows without a migration, and on DigitalOcean, Vultr and Linode it can also shrink without cloning, within the limit of its storage. The right size does not follow from a visit count: it depends on how much of your traffic hits uncached pages such as carts and member areas, how many sites share the server, and how sharp your peaks are. For very spiky traffic, Cloudways Autonomous scales automatically instead.

This guide draws on Cloudways’ official pages, including its changelog, . It deliberately gives no “visits per server size” table: Cloudways does not publish one, and any such number would be made up.

Visit Cloudways and start the free trial

For what each size and add-on costs, see the Cloudways pricing guide.

Starting sizes

Cloudways Flexible, DigitalOcean Basic Standard (checked October 20, 2026)
SizeRAMvCPUStorageBandwidthMonthly
Micro1 GB125 GB1 TB$11
Small2 GB150 GB2 TB$24
Medium4 GB280 GB4 TB$46
Large8 GB4160 GB5 TB$88

Larger sizes and other server types exist; on DigitalOcean, Cloudways also offers General Purpose and CPU Optimized servers, priced on the pricing page. For stores, Cloudways’ WooCommerce page recommends a 2 GB server to start.

What actually loads a server

  • Uncached pages: a cached page is cheap; a page built on every visit (cart, account, search, member area) runs PHP and hits the database.
  • Number of sites: every app on a server shares its RAM and CPU.
  • Background jobs: imports, backups, email sends and scheduled tasks.
  • Peaks: a campaign or a sale can multiply load for a few hours.
  • Storage: media, databases and staging copies.

When to resize

Watch the server’s load graphs and alerts. According to Cloudways’ changelog, since June 2026 Cloudways Copilot monitors servers continuously, suggests a fix when a risk threshold is reached, and detects 5xx errors on WordPress and WooCommerce sites.

Signals and decisions
SignalLikely causeDecision
CPU pinned at busy hoursToo many dynamic pages for the sizeCheck caching, then resize
RAM full, random slowdownsToo many sites or processesResize, or split sites
5xx errors during peaksNot enough capacity at peak timeResize before the event, or consider Autonomous
Disk nearly fullMedia, backups, staging copiesClean up, then add storage
Slow checkout, fast elsewhereUncached pagesObject cache first, then size

Resizing up or down

Cloudways’ changelog says you can scale up or down without cloning on DigitalOcean since March 2025 and on Vultr and Linode since July 2025. One limit remains: you can only downscale to a configuration that matches your current storage, and other downsizes still require cloning. If you add storage while scaling up, that storage becomes your floor. Take an on-demand backup before resizing, and remember the billing rule: a resize on or before day 28 of the month is billed hourly.

High-traffic sites: three strategies

  1. A bigger Flexible server, resized ahead of known peaks such as sales or launches. Simple, but it needs planning.
  2. Split the sites, giving the busiest one its own server so it cannot slow the others.
  3. Cloudways Autonomous for a single WordPress or WooCommerce site with unpredictable peaks: servers are added automatically above the plan’s baseline (Growth at $99 a month, extra servers at $0.07 an hour). See Flexible vs Autonomous.

A five-step sizing method

  1. Start modest, for example Small for a standard WordPress site.
  2. Turn on one page cache and an object cache.
  3. Watch load over a representative period, peaks included.
  4. Move up one size if the signals above appear, then measure again.
  5. Review the size after every big change: a new site, a campaign, a larger catalogue.

Common sizing mistakes

  • Picking a size from a visits table found online; load depends on pages, not raw visitor counts.
  • Resizing before fixing caching.
  • Stacking every client site on one server, the busiest included.
  • Adding storage by reflex, which then blocks downsizing.

Launch a server and measure during the trial

FAQ

How many visits can each size handle?

Cloudways does not publish that figure, and it depends mostly on the share of uncached pages. Measure on your own site.

Can I downsize a Cloudways server?

Yes on DigitalOcean, Vultr and Linode, to a configuration that matches your current storage; other downsizes need cloning.

Does resizing take the site offline?

Resizing happens without a migration; take an on-demand backup first and pick a quiet moment.

When should I move to Autonomous?

When a single WordPress or WooCommerce site has sharp peaks you cannot plan for.

Sources

Official pages checked on .