• Docs
  • Changelog
Sign in
Get started
    • Home
    • Your first deploy
    • Free instances
    • Platform features by plan
    • Use with coding agents
    • FAQ
    • Templates
      • Migrate from…
        • Heroku
        • Railway
    • Compute plans
    • SandboxesBeta
      • Service types
        • Which to use?
        • Static sites
        • Web services
        • Private services
        • Background workers
        • Cron jobs
        • Workflows
        • Multi-service architectures
      • Data storage
        • Render Postgres
        • Render Key Value (Redis®-compatible)
        • Persistent disks
    • How deploys work
    • Supported languages
    • Git providers (GitHub, etc.)
    • Build pipeline
    • Deploy hooks
    • Monorepo support
    • Troubleshooting deploys
      • Previewing changes
        • Single-service previews
        • Preview environments (multi-service)
      • Docker deploys
        • Overview
        • Deploy a registered image
        • Using secrets
      • Runtime
        • Native runtimes
        • Environment variables & secrets
        • Default environment variables
    • Intro to sandboxes
    • Limits
      • How to…
        • Create & configure sandboxes
        • Execute commands
        • Manage files
        • Manage snapshots
      • Use with…
        • Claude Managed Agents
        • Cursor Cloud Agents
        • OpenAI Agents API
      • SDK/CLI reference
        • TypeScript SDK
        • Python SDK
        • CLI commands
    • Intro to workflows
    • Tutorial
    • Limits & pricing
      • How to…
        • Define tasks
        • Define flowsNew
        • Trigger runs
        • Develop locally
      • SDK reference
        • TypeScript SDK
        • Python SDK
      • Example workflows
        • TypeScript examples
        • Python examples
    • Overview
    • Create & connect
    • Database credentials
    • Extensions
    • Version upgrades
    • Logical replication
    • Legacy instance types
      • Database recovery
        • Recovery & backups
        • High availability
      • Database performance
        • Read replicas
        • Connection pooling
        • Admin apps
        • Repacking tables
        • Troubleshooting performance
    • Regions
    • Inbound IP rules
    • Edge caching
    • WebSockets
    • TLS certificates
      • Custom domains
        • Overview
        • Cloudflare
        • Namecheap
        • Other DNS providers
      • Internal traffic
        • Private network
        • Private links
      • Outbound traffic
        • Default IP ranges
        • Dedicated IP addresses
        • Outbound bandwidth
        • Handling network changes
      • Static site config
        • Custom response headers
        • Redirects & rewrites
    • The Render Dashboard
    • SSH / Shell access
    • Projects & environments
      • Service actions
        • Scaling
        • Rollbacks
        • Maintenance mode
        • One-off jobs
      • Infrastructure as code
        • Blueprints overview
        • render.yaml reference
        • Terraform provider
    • In-dashboard metrics
    • Health checks
    • Uptime best practices
      • Logging
        • In-dashboard logs
        • Log streams (syslog/HTTPS)
      • OpenTelemetry (OTel) metrics
        • Provider setup
        • Metrics reference
      • Notifications
        • Webhooks
        • Email / Slack
    • MCP Server
      • Render CLI
        • Overview
        • Command reference
      • REST API
        • Overview
        • API reference
      • Third-party connections
        • OIDC support
        • Datadog
    • Workspaces, members, & roles
    • Login settings
    • Audit logs
      • Organizations
        • Overview
        • SAML SSO
    • DDoS protection
    • Platform maintenance
      • Compliance
        • Overview
        • HIPAA (US health data)
        • HIPAA best practices
        • Shared responsibility model
        • Pentest policy
    • Heroku vs Render
    • Vercel vs Render

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:

SpecsLegacy Plan NameNew 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 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 and the Render 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:

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 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 and the Render API) supports the new set of plan IDs and also continues to support legacy plan names.

View all compute plans

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.

Web service / Private service / Background worker

CPURAMPlan ID
2 CPU8 GB

2c-8g

2 CPU16 GB

2c-16g

4 CPU32 GB

4c-32g

8 CPU16 GB

8c-16g

8 CPU64 GB

8c-64g

12 CPU24 GB

12c-24g

12 CPU48 GB

12c-48g

12 CPU96 GB

12c-96g

Cron job

CPURAMPlan ID
2 CPU8 GB

2c-8g

2 CPU16 GB

2c-16g

4 CPU16 GB

4c-16g

4 CPU32 GB

4c-32g

8 CPU16 GB

8c-16g

8 CPU32 GB

8c-32g

8 CPU64 GB

8c-64g

Render Postgres

CPURAMPlan ID
1 CPU2 GB

1c-2g

View all compute plans

FAQ

Are there any changes to pricing?

No. All compute plans keep their existing pricing.

For pricing details on the new plan options, see the pricing page.

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 do not have a corresponding legacy plan name.

Updates to Render Compute Plans
  • New plan ID format
  • New plan options
  • FAQ
All Systems Operational
© Render Inc. All rights reserved.