---
title: "Change the orb size"
description: "Set the vCPU, memory, and disk of every orb in an install."
---

> Documentation Index
> Fetch the complete documentation index at: https://cf-orbs-site.mdick85.workers.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Change the orb size

An install has one orb size, because Amp doesn't send a size with a job. The default is 4 vCPU, 12 GiB memory, and 20 GB disk.

## Set the size at install

```sh
npx cf-orbs init --vcpu 2
```

`--vcpu` takes 1, 2, 3, or 4, and writes N vCPU, N x 3 GiB memory, and 20 GB disk to `instance`. So `--vcpu 2` gives 2 vCPU, 6 GiB, and 20 GB, for about half the memory charge of the default.

## Set any other size

Edit `instance` in `cf-orbs.config.jsonc`, then run `npx cf-orbs deploy`.

Custom size:

```jsonc
"instance": { "vcpu": 2, "memoryMib": 8192, "diskMb": 20000 }
```

Rules:

- `vcpu`: a number from 1 to 4. Fractions such as `1.5` are allowed.
- `memoryMib`: an integer, at most 12288, and at least 3072 for each vCPU.
- `diskMb`: an integer from 8000 to 20000.
- No other key. The CLI rejects any other key in the object.

Named size:

```jsonc
"instance": "standard-2"
```

The names are `standard-1`, `standard-2`, `standard-3`, and `standard-4`, with 4096, 6144, 8192, and 12288 MiB of memory. `"lite"`, `"basic"` and `"dev"` are rejected because they're too small for the orb image. Any other name is rejected as unknown.

## Check the size

`cf-orbs status <orb>` shows the `instance` of one orb, and `cf-orbs doctor` shows the size from your config on its `config` line.

## Need two sizes

Make a second install with another `name` and another Amp provider token. See [Configure cf-orbs](/docs/guides/configure/#use-a-second-install).

Source: https://cf-orbs-site.mdick85.workers.dev/docs/guides/change-orb-size/index.mdx