> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/plugins/first-party-ango-plugins/duplicate-detection.md).
# Duplicate Detection
## Overview
The Duplicate Detection plugin is an export plugin that scans the assets in a project and returns a CSV report of duplicated assets.
Use this plugin when you want to find assets that share the same external ID or the same asset URL.
## Plugin Functionality
The Duplicate Detection plugin checks the assets in the project and creates a ZIP file containing a CSV report of matching duplicates.
The report includes:
* Batch
* Asset ID
* External ID
* URL
The plugin can detect duplicates in two ways:
* By **External ID**, to find assets with the same external ID.
* By **Asset URL**, to find assets that point to the same source file.
## Plugin Configuration
From the **Config JSON** field, choose which value the plugin should use for duplicate detection.
```json
{
"duplicate_type": "external_id"
}
```
* **"duplicate\_type":** Defines which asset field should be checked for duplicates.
* Options:
* "external\_id"
* "asset\_url"
* Example:
* "duplicate\_type": "external\_id"
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.imerit.net/plugins/first-party-ango-plugins/duplicate-detection.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
