> ## Documentation Index
> Fetch the complete documentation index at: https://docs.suji.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# Resize

> Change VM size after it's running. Storage can grow; CPU/RAM can go either way.

You can change the size of a running VM without re-provisioning. From the instance detail page → **Resize**:

1. Pick the new size (Small / Medium / Large / XL).
2. Confirm.
3. The VM reboots into the new shape. Downtime: typically 30–90 seconds.

## What changes

| Resource    | Up                                    | Down                                                           |
| ----------- | ------------------------------------- | -------------------------------------------------------------- |
| **vCPU**    | ✅ Reboots into more cores             | ✅ Reboots into fewer cores                                     |
| **RAM**     | ✅ Reboots with more RAM               | ✅ Reboots with less RAM                                        |
| **Storage** | ✅ Disk expands, filesystem auto-grows | ❌ **Not supported** — cloud provider doesn't allow disk shrink |

The resize-down case for storage is the only hard restriction. If you need a smaller disk, snapshot → restore into a fresh smaller VM → destroy the old.

## Before you resize

Resize doesn't take a snapshot for you. If you want a rollback point, take a [manual snapshot](/manage-vm/snapshots) first — then you can restore in one click if anything goes wrong (very rare).

## Billing during resize

* The reboot itself is billed at the **new** rate as soon as the resize commits.
* Hourly billing is pro-rated to the minute.

## When to resize

* **Up**: you're seeing OOM kills in `dmesg`, CPU sitting at 100%, or response times creeping up under load.
* **Down**: idle CPU for weeks, RAM usage well below the size's cap, and storage isn't the bottleneck.

The dashboard's Metrics tab (CPU / memory / network / disk over time) helps you decide.

## Edge cases

<AccordionGroup>
  <Accordion title="What if my disk is already full?">
    Resize up if you need more storage. Resize-down for storage is unsupported.
  </Accordion>

  <Accordion title="Will my apps lose state?">
    No — resize is a reboot, not a rebuild. Volumes, containers, system config all persist.
  </Accordion>

  <Accordion title="What if the resize fails?">
    A failed resize degrades to "still on the old plan, still up" — the VM is best-effort restarted on its previous size. If you took a [manual snapshot](/manage-vm/snapshots) first, you can restore from it in one click.
  </Accordion>

  <Accordion title="Can I schedule a resize?">
    Not yet — resizes run immediately. Plan your maintenance window manually.
  </Accordion>
</AccordionGroup>

## Next

<CardGroup cols={2}>
  <Card title="Snapshots" icon="camera" href="/manage-vm/snapshots">
    The safety net behind resizes.
  </Card>

  <Card title="Billing & credits" icon="credit-card" href="/concepts/billing-credits">
    How resize affects your hourly rate.
  </Card>
</CardGroup>