> For the complete documentation index, see [llms.txt](https://help.brieftech.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brieftech.ai/how-to-guides/organise/find-remove-duplicates.md).

# Find and remove duplicate documents

Detect duplicate documents and remove the copies you don't need.

1. In the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-8f18f06a78c4d0bf6e51eac54ec7d3e5d2cdb8a2%2Ftab-review.svg?alt=media" alt="Review tab" data-size="line"> tab (or the Files view), click the **Tools** menu and choose **Duplicate Document Finder**.
2. The first time you use the finder in a matter, click **Activate** when prompted ("Activate duplicate document agent feature? This is currently in BETA so being offered for FREE"). Only the matter's owner can activate the agent; if you have shared (non-owner) access, ask the owner to activate it once for the matter.
3. In the dialog, set the **Similarity Threshold** (default **70%**) and click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-a7334d46a688625c80515a9fb058c9a1c65bc6b9%2Fbtn-run-duplicate-check.svg?alt=media" alt="Run Duplicate Check" data-size="line">. The finder returns document pairs at roughly 70% similarity or higher; raise the threshold to narrow the results to closer matches. BriefTech lists candidate **pairs** in a table: Document A, Document B, and a similarity score. (Use **Export to CSV** if you want the full list.)
4. For any pair, click **Compare** to see the two documents side by side, then click <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-7c32cf50191395f2f657f404ff2ff195611317dc%2Fbtn-move-to-bin-compare.svg?alt=media" alt="Move to bin" data-size="line"> on the copy you want to remove. Repeat for each pair you want to resolve.

Binned documents are excluded from the check, so once you move a copy to the bin its pair no longer appears in the results.

You don't have to open **Compare** to remove a copy. Back in the matter's document list (the **Review** tab or **Files** view), you can tick a copy's row — or several rows — and choose <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-1be3df96ec310ea3302e70fd81129f7dcb9378ef%2Fbtn-move-to-bin.svg?alt=media" alt="Move to bin" data-size="line"> from the right-click menu, which confirms before binning. (The finder's own results table doesn't offer row-ticking, so bin from **Compare** while you're inside it.)

Binned documents can be restored from the <img src="https://2262431129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlnHu06wl3NH457iwjBmr%2Fuploads%2Fgit-blob-23382f24f3c775db713bb068c3beb9d306e24974%2Fview-bin.svg?alt=media" alt="Bin" data-size="line"> view — open it, select the documents, and click **Restore**. To remove them for good, select them in the Bin and click **Delete**.

You now have the matter's duplicate pairs reviewed, and the copies you didn't need moved to the bin.

## Same-filename warning at upload

If some files in an upload batch share a filename with a document already in the **same folder** of the matter, the Upload Manager shows a **Duplicate Files Detected** warning before the batch lands. You can:

* **Exclude Documents with the same filename** — drop the same-named files from this batch, or
* **Upload them anyways** — keep them; this creates additional copies alongside the existing documents.

This warning only compares file names within the same folder. To catch duplicates that have different names, run the **Duplicate Document Finder** after upload (above).

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Folders, labels, and collections</strong></td><td>How folders, labels, and collections organise documents in a matter.</td><td><a href="/reference/folders-labels-and-collections.md">Folders, labels, and collections</a></td></tr><tr><td><strong>Organise documents into folders</strong></td><td>Create folders and move documents between them.</td><td><a href="/how-to-guides/organise/organise-documents-into-folders.md">Organise documents into folders</a></td></tr><tr><td><strong>Apply labels to documents</strong></td><td>Create labels and apply them to documents in bulk.</td><td><a href="/how-to-guides/organise/apply-labels-to-documents.md">Apply labels to documents</a></td></tr><tr><td><strong>Group documents into a collection</strong></td><td>Segment your document set into collections.</td><td><a href="/how-to-guides/organise/group-documents-into-collection.md">Group documents into a collection</a></td></tr></tbody></table>


---

# 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://help.brieftech.ai/how-to-guides/organise/find-remove-duplicates.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.
