# Batch Update Operations

**Purpose**:\
Batch operations streamline repetitive tasks, such as updating hundreds of NFTs’ metadata or transferring large volumes of tokens at once. This approach:

* Reduces transaction overhead.
* Minimizes gas costs and improves user experience.
* Ensures atomicity—either all updates succeed, or none do, maintaining data consistency.

**Examples**:

* **Batch Minting (ART20)**: Minting large sets of NFTs in a single transaction.
* **Batch Metadata Update**: Quickly change the logo URI, description, or other attributes of multiple NFTs.
* **Batch Transfer or Burn**: Efficiently redistribute or burn large quantities of NFTs without multiple transactions.

**Best Practices**:

* Use batch operations for large-scale collections or events (e.g., seasonal updates).
* Combine batch metadata updates with value sources for dynamic, time-sensitive changes.
* Test these operations extensively before running them on live collections.


---

# Agent Instructions: 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:

```
GET https://docs.artinals.com/artinals-protocol/advanced-topics/batch-update-operations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.