> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/features/upload-images/upload-large-files-to-sharinpix.md).

# Upload Large Files To SharinPix

## Overview

In this article, we will demonstrate how to use a multipart image upload on a SharinPix Album or SharinPix Single Image. To do so, we will:

* [Create a SharinPix Permission to set Multipart Upload](#creation-of-sharinpix-permission)
* [Assign the Permission to a SharinPix Component](#assign-the-sharinpix-permission-to-the-album-component)

SharinPix uses a feature called **Multipart Upload** for large file transfers: breaking a large file into smaller parts, uploading them in parallel for speed, and reassembling them in Amazon S3.

The key benefits include:

* Improved Throughput/Speed when uploading large files
* Enhanced Reliability and Fault Tolerance
* Efficient Memory Usage

{% hint style="warning" %}
**Note:** 

* If you do not frequently upload files larger than **100 MB**, do not activate this, as it will affect performance
* **Before using this feature, ensure you have the latest SharinPix package installed.** [*How to upgrade SharinPix package*](/faqs/how-to-update-sharinpix-package-from-the-appexchange.md)
  {% endhint %}

## Creation of SharinPix Permission

* In [SharinPix Permissions](/documentation/access-and-security/sharinpix-permission-object-how-to-create-and-assign-custom-permission.md), create a new record or edit an existing permission.
* Open the Upload section and check Multipart Upload.

![](https://2221230591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5EvYRrLbUyvRh8o1jmMG%2Fuploads%2Fgit-blob-c658a9971e26308c71f54d1bbe554090488f204c%2FUpload%20Multipart%20Doc.png?alt=media)

## Assign the SharinPix Permission to the Album component

* On a [SharinPix Album](/documentation/lightning-web-component/sharinpix-album-lwc.md), add the **ID** or **Name** of the SharinPix Permission record, which includes the maximum file size.
* In this example, the custom permission was named **Upload Multipart**. It has been set in the **Custom Permissions ID or Name** parameter of a *SharinPix Album* component.

![](https://2221230591-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5EvYRrLbUyvRh8o1jmMG%2Fuploads%2Fgit-blob-f42dec0b6686db780962afe979f04b51030ed297%2FUpload%20Multipart%20Doc%20\(1\).png?alt=media)

{% hint style="success" %}
**Tip:**\
\
The above will also work for a [SharinPix Single Image](/documentation/lightning-web-component/sharinpix-single-image.md). The custom permission created should then be defined as a Single Image Permission.
{% endhint %}


---

# 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.sharinpix.com/documentation/features/upload-images/upload-large-files-to-sharinpix.md?ask=<question>&goal=<user_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.