> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/create-and-publish/production/episodes/edit-episode-details.md).

# Edit episode details

Edit the title, texts, type, number, permalink, cover, and keywords of an episode.

Use this task to change the information that describes an episode in players, directories, and on the podcast website. The same page explains how to find an episode in the episode list.

## Before you start

* You are the podcast owner, or you have permission to create and edit episodes in the podcast. Without this permission the **General** tab is read-only.
* The episode exists. See [Create and publish an episode](/documentation/create-and-publish/production/episodes/create-and-publish-an-episode.md).

{% tabs %}
{% tab title="Classic view" %}

### Find the episode

1. Open the podcast. The episode list shows 20 episodes per page.
2. Sort the list by publication date or by title.
3. Enter part of the title or the numeric episode ID in the search field.
4. Select **Edit** on the episode row. **Analytics** opens the episode analytics instead.

The status label of each row shows the publication state. A published episode has a green label with the local publication time. A scheduled episode has a blue label with a calendar icon. A draft has a gray label with **Not published**. An encoding indicator shows when Podigee processes the audio.

![Episode list of a podcast in the classic view with the Title and Status sort columns, the search field, and the Edit button](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e1daa8157117a47a61db1f0893759f5b81a5de29%2Fdoc-production-002-classic-episode-list.png?alt=media)

Sort the list by Title or Status, search for the episode, and select Edit on its row.

An AI agent can also find episodes for you. See [Find and filter episodes](/documentation/start-here/ai-agents/manage-episodes/find-and-filter-episodes.md).

### Edit the details

1. Open the **General** tab of the episode.
2. Change the fields that you need. The form saves each change automatically and shows **Autosaved** in the footer. When the footer offers **Save**, select it.

| Field                    | Rule                                                                                             |
| ------------------------ | ------------------------------------------------------------------------------------------------ |
| **Title**                | Required. Up to 120 characters in the form. A blank title is saved as "New episode".             |
| **Subtitle**             | Up to 255 characters.                                                                            |
| **Description**          | Up to 4000 characters. Supports text snippet placeholders (snippet name in double curly braces). |
| **Show notes**           | Markdown editor without a length limit. Supports text snippet placeholders.                      |
| **Episode type**         | **Full**, **Trailer**, or **Bonus**. Directories use this value as the episode type.             |
| **Season**               | Shown for serial podcasts only.                                                                  |
| **Number**               | Required, numeric, greater than 0. Unique per podcast, season, and episode type.                 |
| **External episode URL** | Shown only when the podcast uses an external website. Must be a URL.                             |
| **Episode permalink**    | Lowercase letters, digits, and hyphens. Up to 255 characters.                                    |
| **Cover image**          | Less than 2 MB. Use a square image between 1400x1400 and 3000x3000 pixels.                       |
| **Keywords**             | Up to 10 keywords. Each keyword up to 255 characters.                                            |
| **Authors**              | Up to 255 characters.                                                                            |
| **Explicit language**    | When the episode contains explicit content, check the box.                                       |

Tips:

* Select **Generate from title** to build the permalink from the title. The **Resulting URL** field shows the public address of the episode when the podcast uses the Podigee website.
* A new episode copies the explicit setting from the podcast.
* The AI buttons next to the text fields belong to Content Hub. See [Get started with Content Hub](/documentation/create-and-publish/production/content-hub/get-started-with-content-hub.md).

### Expected result

The footer shows **Autosaved** or the notice "Successfully saved". Podigee writes changed metadata into the audio files of an encoded episode in the background. This applies to the title, subtitle, description, permalink, keywords, chapter marks, and cover image. You do not need to update the audio file.

### If you cannot complete the task

* The form shows "Update failed": check the field rules in the table above and save again.
* "A tag is too long (max 255 characters)": shorten the keyword.
* The fields are read-only: ask the podcast owner or an admin for the permission to edit episodes.
  {% endtab %}

{% tab title="Podigee workspace" %}
In the Podigee workspace you open the episode first and then its editor. The editor saves with one button.

1. Open the podcast and select **Episodes** in the sidebar.
2. Find the episode. You can switch between **Tiles** and **List**, or filter by **All statuses**, **Draft**, **Scheduled**, or **Published**. You can also use the search field **Search title, description or number**, or change the sort order.
3. Select the episode title. The episode preview opens.
4. Select **Edit details**.
5. Change the fields under **Title & description**, **Show notes**, and **Keywords**. Open **Expert fields** for **URL slug**, **External URL**, **Episode number**, **Season**, **Episode type** (**Full episode**, **Trailer**, **Bonus**), **Author override**, **Contains explicit content**, and **Use a custom episode cover**.
6. Select **Save changes**. Podigee shows "Episode saved."

![Episode editor of the Podigee workspace with the Title, Subtitle, and Description fields under Title & description and the Variants buttons](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-2ed0c8fe3e7739e22adee9102e9bbff7f0ebf1d3%2Fdoc-production-002-episode-editor.png?alt=media)

The Title & description panel holds the fields that the classic General tab shows.

What is different:

* The editor does not save automatically. Select **Save changes**.
* The episode list has no **Edit** or **Analytics** action on the row. Open the episode, then select **Edit details**. The episode analytics open from **Analytics** in the sidebar.
* There is no **Generate from title** and no **Resulting URL**. The permalink field is **URL slug**.
* The field counters show 255 characters for the **Title** and 4000 characters for the **Subtitle**.
  {% endtab %}
  {% endtabs %}

## Next step

[Upload audio or video](/documentation/create-and-publish/production/episodes/upload-audio-or-video.md) to add the media file for the episode.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/create-and-publish/production/episodes/edit-episode-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
