---
title: Manage indexing pipeline extensions
slug: '1645'
canonical_url: https://docs.coveo.com/en/1645/
collection: index-content
source_format: adoc
---
# Manage indexing pipeline extensions
An [indexing pipeline extension (IPE)](https://docs.coveo.com/en/206/) is a Python script used to customize the way one or more [sources](https://docs.coveo.com/en/246/) [index](https://docs.coveo.com/en/204/) content.
For details on how IPEs work, see [Indexing pipeline extension overview](https://docs.coveo.com/en/1556/).
This article explains how to use the [**Extensions**](https://platform.cloud.coveo.com/admin/#/orgid/content/extensions/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/extensions/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/extensions/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/extensions/)) page to manage your IPEs.
## Add an indexing pipeline extension
Coveo provides [script samples](https://docs.coveo.com/en/111/) to help you get started with extensions.
You'll most likely need developer skills to adapt a sample script to your needs, and then test it.
> **Note**
>
> Avoid including a `sys.exit` in your script, as this can cause issues at the [processing stage](https://docs.coveo.com/en/1893#processing) of the Coveo indexing pipeline.
Once you're satisfied with your script, follow these steps to add it to your organization, and then apply it to a source.
. On the [**Extensions**](https://platform.cloud.coveo.com/admin/#/orgid/content/extensions/) ([platform-ca](https://platform-ca.cloud.coveo.com/admin/#/orgid/content/extensions/) | [platform-eu](https://platform-eu.cloud.coveo.com/admin/#/orgid/content/extensions/) | [platform-au](https://platform-au.cloud.coveo.com/admin/#/orgid/content/extensions/)) page, click **Add extension**.
. In the **Add an extension** panel, enter a name for your extension.
> **Leading practice**
>
> * Use a short, descriptive name.
>
> * Use a developer-friendly name, as it may be used in the extension script to specify a metadata or [data stream](https://docs.coveo.com/en/2891/) indexing pipeline stage `origin`.
>
> * Prefix your extension name with `pre-` or `post-` to indicate at which [stage of the pipeline](https://docs.coveo.com/en/1556#PreVsPost) the script will apply.
. Optionally, enter a description of the extension's purpose.
For example, explain what it does to [metadata](https://docs.coveo.com/en/218/) or a [data stream](https://docs.coveo.com/en/2891/), and to which sources it applies.
. If applicable, select the types of item data that your extension script needs to access.
Select only those you intend to use with [`document.get_data_stream(...)`](https://docs.coveo.com/en/34#get-data-stream-method) to avoid adding overhead to the execution.
**Body text**
Details
The _body text_ contains all the text found in an item.
It's formatted to be used at the pipeline's [indexing stage](https://docs.coveo.com/en/1893#indexing), which makes the content searchable.
Since the body text is created at the [processing stage](https://docs.coveo.com/en/1893#processing), it's available to post-conversion extension scripts only.
Select **Body text** when your extension script needs to process the text extracted from your content items.
Selecting this option when it's not necessary may degrade indexing performances.
[NOTE]
**Note**
Details
The _body HTML_ of an item is an HTML version of the item.
It's used by the [quickview](https://docs.coveo.com/en/3311/) component of a search interface.
Since the body HTML is created at the [processing stage](https://docs.coveo.com/en/1893#processing), it's available to post-conversion extension scripts only.
Select **Body HTML** only if your script needs the item's quickview content.
Selecting this option when it's not necessary may degrade indexing performances.
[NOTE]
**Notes**
Details
The _body Markdown_ of an item is a Markdown version of the item.
It uses Markdown format and contains all the body text found in an item.
The Markdown data stream is used only by a [CPR model to create chunks](https://docs.coveo.com/en/p9ub0044#chunking-data-stream) for the [embeddings](https://docs.coveo.com/en/ncc87383/) that are used for semantic content retrieval.
The body Markdown [data stream](https://docs.coveo.com/en/2891/) preserves an item's formatting and structure during ingestion, which allows the model to create more coherent and semantically focused chunks.
The Markdown is also preserved in the chunk itself, which improves the reasoning capabilities of a large language model (LLMs).
Since the body Markdown data stream is created at the [processing stage](https://docs.coveo.com/en/1893#processing), it's available to post-conversion extension scripts only.
Select **Body Markdown** when your extension script needs to process the Markdown text that's used to create chunks for embeddings.
[NOTE]
**Notes**
Details
A _thumbnail_ is a small image that typically represents the content of the item, such as a miniature image of the first page of a document.
When available, the thumbnail can be included in search results templates to help search users identify the item.
Select **Thumbnail** only if your post-conversion extension script needs the thumbnail generated by Coveo.
Selecting this option when it's not necessary may degrade indexing performances.
Details
The _original file_ is the actual binary data, or content, of the item.
For example, if the item is a PDF file, then the item data is the actual content of this file.
Select **Original file** only if your pre-conversion extension script needs the binary data of the item.
There's generally no point in feeding the original file to a post-conversion extension, because the [indexing stage](https://docs.coveo.com/en/1893#indexing) doesn't process it.
[NOTE]
**Note**