Limits and Instance Types

The memory, vCPU, and disk space for Containers are set through instance types. You can use one of six predefined instance types or configure a custom instance type.

For an application that uses the default scheduling policy, specify the size with the instance_type property in your Worker's Wrangler configuration file. For the durable_object policy, pass the named size to ctx.container.start() with the runtime instance property.

In addition to the predefined instance types, you can configure custom instance types. Field names depend on where you configure the size. Wrangler configuration for the default policy uses vcpu, memory_mib, and disk_mb. A ctx.container.start() call for the durable_object policy uses vcpu, memoryMib, and diskMb.

Refer to the Wrangler configuration documentation or scheduling policy documentation for examples.

Custom instance types have the following constraints:

For workloads requiring less than 1 vCPU, use the predefined instance types such as lite or basic.

If you need larger instance sizes or higher account-level limits, contact your account team, file a support ticket, or fill out this form ↗︎.

The following limits apply per account:

The following limits apply to Container snapshots:

Restoring a snapshot refreshes its 30-day time-to-live.