---
title: "Deployment mode"
url: https://docs.corefinity.com/guides/sites/code-and-deployments/deployment-modes
type: guide
last_updated: 2026-11-13
feature: deployments
related:
  - https://docs.corefinity.com/api/reference/deployments/get-site-deployments.md
  - https://docs.corefinity.com/api/reference/deployments/create-site-deployment.md
  - https://docs.corefinity.com/api/reference/deployments/list-site-deployment-branches.md
  - https://docs.corefinity.com/api/reference/deployments/update-site-deployment-mode.md
  - https://docs.corefinity.com/api/reference/deployments/list-site-deployment-repositories.md
  - https://docs.corefinity.com/api/reference/deployments/update-site-deployment-repository.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_get.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_mode_set.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_repositories_list.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_branches_list.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployments_repository_set.md
  - https://docs.corefinity.com/mcp/tools/corestack_deployment_trigger.md
---
# Deployment mode

See whether a site takes manual uploads or deploys from Git, and switch it back to manual uploads.

## Before you start

- You can open the site in **Managed Websites**. Anyone who can open a site can see its deployment mode.
- To switch the mode you are an owner, or your role has **Manage Deployment Source**.
- To move a site to Git, follow [Connect a repository](/guides/sites/code-and-deployments/connect-a-repository).

## What each mode does

| Mode                 | How changes reach the site                                                                                                                                            | Roll back                |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| **Manual uploads**   | Files you change over SFTP or in the terminal are live at once, in `htdocs`.                                                                                          | Nothing to roll back.    |
| **Deploys from Git** | **Deploy**, or a push to the branch, builds the repository into a new release in `releases/`. Uploads and configuration live in `shared/`, linked into every release. | To the previous release. |

On a site that deploys from Git, files changed over SFTP inside a release are overwritten by the next deployment. Put uploads in `shared/`, or commit the change.

## See how a site deploys

1. **Open the site's deployments**

   Go to **Managed Websites**, choose the site, then **Deployments** under **Code & backups**. The **Deployment mode** card describes the environment chosen in the site header.

2. **Open How it works**

   Choose **How it works**. **This site today** lists the releases kept, the shared folders, the repository, the branch and whether **Deploy on push** is on.

   _Screenshot: The How deployments work here dialog on a site that deploys from Git: Git deployments marked Current beside Manual uploads, This site today with the releases kept and the repository, and the site's folders now and after switching to manual._

The site's other environments keep their own branch and **Deploy on push** setting.

## Switch back to manual uploads

1. **Open the card's menu**

   On the **Deployment mode** card, open the **…** menu and choose **Switch to manual uploads…**. **What switching to manual does** shows the site's folders now and afterwards.

   _Screenshot: The Deployment mode card of a site that deploys from Git, with its menu open on Switch to manual uploads._

2. **Confirm the switch**

   In the dialog, choose **Switch to manual uploads…** again, then **Switch to manual uploads** to confirm.

   _Screenshot: The dialog that confirms the switch to manual uploads: htdocs becomes a plain folder, the other releases are removed, pushes no longer deploy, and the buttons Cancel and Switch to manual._

   > **Warning:** The other releases are removed, so there is nothing to roll back to afterwards.

**Deployment mode** reads **Manual uploads**. The repository stays connected but unused, and the deployment history stays readable.

The site keeps serving while the current release is copied into `htdocs`. A Laravel site rebuilds once at the end, and visitors may see an error page until it finishes.

## Automate this

**API:** [Update how a site deploys](https://docs.corefinity.com/api/reference/deployments/update-site-deployment-mode.md), scope `write`

```bash
curl -X PUT https://manage.corefinity.com/api/corestack/sites/1042/deployments/mode \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "mode": "git"
  }'
```

**MCP:** [`corestack_deployments_mode_set`](https://docs.corefinity.com/mcp/tools/corestack_deployments_mode_set.md), scope `write`

```json
{
  "name": "corestack_deployments_mode_set",
  "arguments": {
    "site_id": 4211,
    "mode": "manual"
  }
}
```

**Control Panel:** Managed Websites › your site › Code & backups › Deployments ([https://manage.corefinity.com/go/deployments](https://manage.corefinity.com/go/deployments))

## Related

- [Connect a repository](/guides/sites/code-and-deployments/connect-a-repository): Switch a site to Git deployments.
- [Deploy, stop, retry and roll back](/guides/sites/code-and-deployments/deploy-stop-retry-roll-back): Deploy, stop, retry or roll back.
- [SSH keys](/guides/sites/access-and-security/ssh-keys): Add a key to log in over SSH.
