---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/configurations/recording#article
headline: Recording configurations
description: Create, edit, and delete reusable Twilio recording configurations in the Console to control audio composition, status callbacks, and transcription features.
url: https://www.twilio.com/docs/configurations/recording
inLanguage: en
dateModified: 2026-10-19T14:07:00.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Recording configurations

## Overview

Recording configurations let you define reusable recording settings for your voice calls. Instead of specifying recording parameters on every API call, you create a reusable configuration that controls how audio is composed, which callbacks fire, and which features apply.

There are two types of Voice Recording Configurations; the [Voice Recording Account Default Configuration](/docs/configurations/recording-account-default-configuration-resource) and [Voice Recording Configurations](/docs/configurations/recording-configuration-resource).

**Recording Account Default Configuration**: Establishes default settings for all voice workflows made on an account. Once created, the settings defined in an Account Default Configuration will automatically apply to all calls without requiring code updates.

**Recording Configurations**: Defines settings that can be applied on a use-case basis. Adding a Voice Configuration to your code is functionally equivalent to passing the same parameters directly in your code or in TwiML. A voice workflow can use either a Voice Configuration or explicit programmatic parameters, but not both.

> \[!NOTE]
>
> You can create and manage recording configurations in the [Twilio Console](https://1console.twilio.com) or using the [API](/docs/configurations/recording-configuration-resource). This feature isn't available in the legacy Console.

## Create a recording configuration

To create a recording configuration using Twilio Console, follow these steps:

1. In the Console, go to **Communications** > **Voice** > **Recordings** > [**Configurations**](https://1console.twilio.com/go?to=/account/__account__/us1/voice/recordings/configurations).
2. Select **Create configuration**.
3. On the **Name configuration** step, enter a name and description for the configuration.
4. On the **Composition policy** step, choose how Twilio captures and composes audio. See [Composition policy](#composition-policy).
5. On the **Callback settings** step, configure where Twilio sends recording events. See [Callback settings](#callback-settings).
6. On the **Features** step, attach a batch transcription configuration. See [Transcription configuration](#transcription-configuration).
7. On the **Summary** step, review your settings, and then select **Create configuration**.

## Configuration settings

The following sections describe each setting you configure in the wizard.

### Composition policy

Composition policy defines how recording audio is captured, whether silence is trimmed, and which tracks are included.

To record each party on a separate channel, set **Channel** to **Dual**. To record all parties in one channel, choose **Mono**.

The **Trim silence** field controls whether Twilio keeps silence in the recording. Select **Do not trim** to keep the full audio, or **Trim silence** to remove silence from the beginning and end of the recording.

The [**Track** property](/docs/voice/tutorials/how-record-single-side-call) defines which audio track to record for the call. The  **inbound track** records the audio that is received by Twilio. The **outbound track** records the audio that is generated from Twilio. And **both** records the audio that is received and generated by Twilio.

The default composition policy uses **Dual** channels, **Do not trim**, and **Both** tracks.

### Callback settings

Configure callbacks separately for **Call recording status callback** and **Conference recording status callback**.

For each callback, provide the following:

* **Webhook URL**: The endpoint that receives recording events (up to 2,048 characters).
* **HTTP method**: `POST` or `GET`.
* **Events**: Select which recording events trigger the callback — **In-progress**, **Completed**, **Absent**, or **Failed**.

### Transcription configuration

You can attach up to three [batch transcription configurations](/docs/configurations/batch-transcriptions) to a recording configuration. This automatically transcribes your recordings after the call completes.

> \[!WARNING]
>
> The **Features** step isn't available on PCI or HIPAA accounts, on accounts that use Conversation Intelligence (classic), or on accounts that have recording encryption or external storage enabled.

To attach a transcription configuration, follow these steps:

1. On the **Features** step, select a batch transcription configuration from the list.
2. Optional: Add a description for context.
3. To attach another, select **Add another transcription configuration**. You can attach up to three.

You can attach transcription configurations at any time from the recording configuration details page.

## Edit a recording configuration

To edit an existing recording configuration using Twilio Console, follow these steps:

1. In the Console, go to **Communications** > **Voice** > **Recordings** > [**Configurations**](https://1console.twilio.com/go?to=/account/__account__/us1/voice/recordings/configurations).
2. Select a configuration from the list.
3. Select **Edit** on the section you want to update.
4. Make your changes, and then select **Save**.

## Delete a recording configuration

To delete a recording configuration using Twilio Console, follow these steps:

1. In the Console, go to **Communications** > **Voice** > **Recordings** > [**Configurations**](https://1console.twilio.com/go?to=/account/__account__/us1/voice/recordings/configurations).
2. Select a configuration from the list.
3. Select **Delete recording configuration**.

> \[!WARNING]
>
> Deleting a recording configuration is permanent. New calls that reference the deleted configuration won't apply its settings.
