# Install Kirby CMS locally

Source: https://docs.fortrabbit.com/guides/kirby/install
Reviewed: 2026-07-04


## Get ready

To install Kirby locally, you need a local development environment and access to the official Kirby documentation.

- Have a [local development environment](/integrations/local-development/intro).
- See the [official Kirby quick start install guide](https://getkirby.com/docs/guide/quickstart#installing-kirby) as well.

If you already have a local Kirby project, continue with [deployment options](/guides/kirby/deployment-options).

### Kirby starter kits

Kirby has different starting points for new projects:

- [Plainkit](https://github.com/getkirby/plainkit): with no content at all (used here).
- [Starterkit](https://github.com/getkirby/starterkit): with demo content and a theme with templates.
- [Composerkit](https://github.com/getkirby/composerkit): best for Git/Composer workflows. Adjust [root path](/platform/settings/root-path) to `public`.

Our instructions will use Plainkit. Composerkit is the future (we think).

## A: Install Kirby locally with Composer (recommended)



```shell
# 1. Create a local Kirby project folder with Composer:
$ composer create-project getkirby/plainkit {{app-env-id}}
```

## B: Install Kirby locally without Composer



```shell
# Make a directory and move into it
$ mkdir {{app-env-id}} && cd {{app-env-id}}

# Get the plainkit
$ wget https://github.com/getkirby/plainkit/archive/main.zip

# Unzip the plainkit
$ unzip main.zip

# Move all contents from the folder one level up
$ mv plainkit-main/* .

# Remove artifacts
$ rm -rf main.zip plainkit-main
```

---

- [Why host Kirby on fortrabbit](/software/kirby)
