# Updates to Render Compute Plans

On *August 26, 2026*, Render introduced a new naming convention for compute plans (previously called "instance types").

The new plan IDs more helpfully reflect each plan's specifications. Here are three examples for web service compute plans:

| Specs | Legacy Plan Name | New Plan ID |
| --- | --- | --- |
| 0.5 CPU 512 MB RAM | *`starter`* | *`0.5c-512mb`* |
| 1 CPU 2 GB RAM | *`standard`* | *`1c-2g`* |
| 2 CPU 4 GB RAM | *`pro`* | *`2c-4g`* |

Additionally, Render added [new plan options](compute-plans-update#new-plan-options) with commonly requested combinations of CPU and RAM.

*Here are the most important details:*

- There are no changes to pricing.
- Legacy plan names (`standard`, `pro`, etc.) remain supported across all Render tooling, including [Blueprints](infrastructure-as-code) and the [Render API](api).
- Each legacy plan name has a corresponding _new_ plan with identical specs and pricing.

The rest of this article provides additional details about these updates.

## New plan ID format

Compute plans now use an identifier that reflects their specs. Most plan IDs use the following format:

```
{CPU_COUNT}c-{RAM_GB}g
```

For example, the *`1c-2g`* compute plan provides 1 CPU and 2 GB of RAM (the same as the legacy *`standard`* plan).

*Exceptions include:*

- The [*`free`*](free) plan, which retains its name
- Paid compute plans with less than 1 GB of RAM
    - These end in `mb` instead of `g` (such as *`0.5c-512mb`*)
- Plan IDs for Render Key Value
    - Key Value plan IDs only reflect memory (`256mb`, `1g`, and so on)

All Render tooling (including [Blueprints](infrastructure-as-code) and the [Render API](api)) supports the new set of plan IDs and also continues to support legacy plan names.

## New plan options

Render has introduced new compute plans for the service types listed below. Many of these new plans provide a higher ratio of RAM to CPU to support memory-intensive workloads.

> *For pricing details on these and all other compute plans, see the [pricing page](/pricing#compute).*

**Tab: Web service / Private service / Background worker**

#### Web service / Private service / Background worker

| CPU | RAM | Plan ID |
| --- | --- | --- |
| 2 CPU | 8 GB | *`2c-8g`* |
| 2 CPU | 16 GB | *`2c-16g`* |
| 4 CPU | 32 GB | *`4c-32g`* |
| 8 CPU | 16 GB | *`8c-16g`* |
| 8 CPU | 64 GB | *`8c-64g`* |
| 12 CPU | 24 GB | *`12c-24g`* |
| 12 CPU | 48 GB | *`12c-48g`* |
| 12 CPU | 96 GB | *`12c-96g`* |

**Tab: Cron job**

#### Cron job

| CPU | RAM | Plan ID |
| --- | --- | --- |
| 2 CPU | 8 GB | *`2c-8g`* |
| 2 CPU | 16 GB | *`2c-16g`* |
| 4 CPU | 16 GB | *`4c-16g`* |
| 4 CPU | 32 GB | *`4c-32g`* |
| 8 CPU | 16 GB | *`8c-16g`* |
| 8 CPU | 32 GB | *`8c-32g`* |
| 8 CPU | 64 GB | *`8c-64g`* |

**Tab: Render Postgres**

#### Render Postgres

| CPU | RAM | Plan ID |
| --- | --- | --- |
| 1 CPU | 2 GB | *`1c-2g`* |

## FAQ

###### Are there any changes to pricing?

No. All compute plans keep their existing pricing.

For pricing details on the [new plan options](#new-plan-options), see the [pricing page](/pricing#compute).

###### Can I continue to use legacy plan names, such as standard and pro?

Yes. Legacy plan names remain supported. There is no difference in specs or pricing between a legacy plan and its corresponding new plan, such as between *`standard`* and *`1c-2g`*.

Note that the [new plan options](#new-plan-options) do not have a corresponding legacy plan name.


---

##### Appendix: Glossary definitions

###### compute plan

Specifies the CPU and RAM available to your service's *instances*.

Common compute plans for a new web service include:

- *`free`*: 0.1 CPU / 512 MB RAM
- *`0.5c-512mb`*: 0.5 CPU / 512 MB RAM
- *`1c-2g`*: 1 CPU / 2 GB RAM

Compute plans were previously known as *instance types*.

Related article: https://render.com/docs/compute-plans.md