# Clone an environment

Cloning copies an environment's shape into a new environment in the same project — the fastest way to stand up a staging twin of production. This page covers what a clone copies, what it never copies, and the steps.

## What a clone copies

- 
- 
-

Databases are created before the services that consume them, so a connection variable pointing at a cloned database resolves on the clone from the start.

## What a clone never copies

- 
- 
-

## Clone from the console

1. 
2. 
3. 
4. 
5.

## Requirements

Cloning requires the admin role, because it creates a new environment — see [Teams & roles](/docs/collaboration/teams-and-roles). The clone also counts against your plan's environment limit — see [Usage & limits](/docs/account/usage-and-limits).

> **Note:**
>
> A clone is a one-time copy: the two environments share nothing afterwards. To repeatedly push configuration from one existing environment onto another, use [Promote an environment](/docs/projects/promote-an-environment) instead.

You can also clone via the [Environments API](/api/environments).