Recipes

Recipes are templated build configurations that generate build and sync steps. They reduce boilerplate and encode best practices for common patterns.

How Recipes Work

A recipe is a Handlebars template that takes configuration parameters and expands into full canister configuration.

Recipe Template + Configuration → Expanded Build/Sync Steps

Example

Given this recipe usage:

canisters:
  - name: backend
    recipe:
      type: "@dfinity/rust"
      configuration:
        package: my-backend

The recipe expands to something like:

canisters:
  - name: backend
    build:
      steps:
        - type: script
          commands:
            - cargo build --package my-backend --target wasm32-unknown-unknown --release
            - cp target/wasm32-unknown-unknown/release/my_backend.wasm "$ICP_WASM_OUTPUT_PATH"

Recipe Sources

Recipes can come from three sources:

Registry (Recommended)

Official recipes from the DFINITY registry:

recipe:
  type: "@dfinity/rust"
  configuration:
    package: my-crate

Version pinning:

recipe:
  type: "@dfinity/rust@v1.0.0"

The @dfinity prefix resolves to github.com/dfinity/icp-cli-recipes.

Local Files

Project-specific recipes:

recipe:
  type: ./recipes/my-template.hb.yaml
  configuration:
    param: value

Remote URLs

Recipes hosted anywhere:

recipe:
  type: https://example.com/recipes/custom.hb.yaml
  sha256: 17a05e36278cd04c7ae6d3d3226c136267b9df7525a0657521405e22ec96be7a
  configuration:
    param: value

Always include sha256 for remote recipes.

Available Official Recipes

Recipe	Purpose
@dfinity/rust	Rust canisters with Cargo
@dfinity/motoko	Motoko canisters
@dfinity/asset-canister	Asset canisters for static files
@dfinity/prebuilt	Pre-compiled WASM files

Recipe Template Syntax

Recipes use Handlebars templating:

recipes/example.hb.yaml

build:
  steps:
    - type: script
      commands:
        {{#if optimize}}
        - cargo build --release
        {{else}}
        - cargo build
        {{/if}}
        - cp target/{{configuration.package}}.wasm "$ICP_WASM_OUTPUT_PATH"

Template Variables

icp-cli will essentially render the handlebar template with all the parameters passed in the configuration section of the recipe.

Viewing Expanded Configuration

See what recipes expand to:

icp project show

This displays the effective configuration after all recipes are rendered.

When to Use Recipes

Use recipes when:

• Building standard canister types (Rust, Motoko, Asset Canister)
• Sharing configurations across multiple canisters
• Encoding team-specific build conventions

Use direct build steps when:

• Your build process is unique
• You need fine-grained control
• The overhead of a recipe isn’t justified

Next Steps

• Using Recipes — Apply recipes in your projects
• Creating Recipes — Build custom recipes

Browse all documentation →