# Creating Templates

Users with the `Template Administrator` role or above can create templates
within Coder.

## From a starter template

In most cases, it is best to start with a starter template.

<Tabs items="[&#x22;Web UI&#x22;, &#x22;CLI&#x22;, &#x22;CI/CD&#x22;]" groupId="coder-docs-tab:ci-cd-cli-web-ui" persist="true">
  <Tab value="Web UI" id="web-ui">
    After navigating to the Templates page in the Coder dashboard, choose
    `Create Template > Choose a starter template`.

    ![Create a template](/docs/images/admin/templates/create-template.png)

    From there, select a starter template for desired underlying infrastructure for
    workspaces.

    ![Starter templates](/docs/images/admin/templates/starter-templates.png)

    Give your template a name, description, and icon and press `Create template`.

    ![Name and icon](/docs/images/admin/templates/import-template.png)

    If template creation fails, it's likely that Coder is not authorized to deploy infrastructure in the given location.
    Learn how to configure [provisioner authentication](/docs/@v2.34.3/admin/templates/extending-templates/provider-authentication/).
  </Tab>

  <Tab value="CLI" id="cli">
    You can the [Coder CLI](/docs/@v2.34.3/install/cli/) to manage templates for Coder.
    After [logging in](/docs/@v2.34.3/reference/cli/login/) to your deployment, create a
    folder to store your templates:

    ```sh
    # This snippet applies to macOS and Linux only
    mkdir $HOME/coder-templates
    cd $HOME/coder-templates
    ```

    Use the [`templates init`](/docs/@v2.34.3/reference/cli/templates_init/) command to
    pull a starter template:

    ```sh
    coder templates init
    ```

    After pulling the template to your local machine (e.g. `aws-linux`), you can
    rename it:

    ```sh
    # This snippet applies to macOS and Linux only
    mv aws-linux universal-template
    cd universal-template
    ```

    Next, push it to Coder with the
    [`templates push`](/docs/@v2.34.3/reference/cli/templates_push/) command:

    ```sh
    coder templates push
    ```

    If `template push` fails, it's likely that Coder is not authorized to deploy infrastructure in the given location.
    Learn how to configure [provisioner authentication](/docs/@v2.34.3/admin/provisioners/).

    You can edit the metadata of the template such as the display name with the
    [`templates edit`](/docs/@v2.34.3/reference/cli/templates_edit/) command:

    ```sh
    coder templates edit universal-template \
      --display-name "Universal Template" \
      --description "Virtual machine configured with Java, Python, Typescript, IntelliJ IDEA, and Ruby. Use this for starter projects. " \
      --icon "/emojis/2b50.png"
    ```
  </Tab>

  <Tab value="CI/CD" id="cicd">
    Follow the [change management](/docs/@v2.34.3/admin/templates/managing-templates/change-management/) guide
    to manage templates via GitOps.
  </Tab>
</Tabs>

## From an existing template

You can duplicate an existing template in your Coder deployment. This will copy
the template code and metadata, allowing you to make changes without affecting
the original template.

<Tabs items="[&#x22;Web UI&#x22;, &#x22;CLI&#x22;]" groupId="coder-docs-tab:cli-web-ui" persist="true">
  <Tab value="Web UI" id="web-ui-1">
    After navigating to the page for a template, use the dropdown menu on the right
    to `Duplicate`.

    ![Duplicate menu](/docs/images/admin/templates/duplicate-menu.png)

    Give the new template a name, icon, and description.

    ![Duplicate page](/docs/images/admin/templates/duplicate-page.png)

    Press `Create template`. After the build, you will be taken to the new template
    page.

    ![New template](/docs/images/admin/templates/new-duplicate-template.png)
  </Tab>

  <Tab value="CLI" id="cli-1">
    First, ensure you are logged in to the control plane as a user with permissions
    to read and write permissions.

    ```console
    coder login
    ```

    You can list the available templates with the following CLI invocation.

    ```console
    coder templates list
    ```

    After identified the template you'd like to work from, clone it into a directory
    with a name you'd like to assign to the new modified template.

    ```console
    coder templates pull <template-name> ./<new-template-name>
    ```

    Then, you can make modifications to the existing template in this directory and
    push them to the control plane using the `-d` flag to specify the directory.

    ```console
    coder templates push <new-template-name> -d ./<new-template-name>
    ```

    You will then see your new template in the dashboard.
  </Tab>
</Tabs>

## From scratch (advanced)

There may be cases where you want to create a template from scratch. You can use
[any Terraform provider](https://registry.terraform.io) with Coder to create
templates for additional clouds (e.g. Hetzner, Alibaba) or orchestrators
(VMware, Proxmox) that we do not provide example templates for.

Refer to the following resources:

* [Tutorial: Create a template from scratch](/docs/@v2.34.3/tutorials/template-from-scratch/)
* [Extending templates](/docs/@v2.34.3/admin/templates/extending-templates/): Features and concepts
  around templates (agents, parameters, variables, etc)
* [Coder Registry](https://registry.coder.com/templates): Official and community
  templates for Coder
* [Coder Terraform Provider Reference](https://registry.terraform.io/providers/coder/coder)

### Next steps

* [Extending templates](/docs/@v2.34.3/admin/templates/extending-templates/)
* [Managing templates](/docs/@v2.34.3/admin/templates/managing-templates/)