> 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/restrict-uploads-using-file-extensions.md).
# Restrict Uploads Using File Extensions
This article demonstrates how to restrict file uploads based on file extensions.
Uploads can be restricted as follows:
* [Using a SharinPix Permission record to specify the list of accepted file extensions.](#using-sharinpix-permission-records)
* [Using an Apex method to generate an online token with a list of accepted file extensions.](#using-the-upload_accept-parameter-in-apex-method)
## Using SharinPix Permission Records
SharinPix Permission records consist of the **Accepted file types** parameter used to specify the type of files that can be uploaded to an album.
The **Accepted file types** parameter takes as a value the list of accepted file extensions separated by a semi-colon.
For example, to restrict uploads to .jpeg, and PDF files, the value will be as follows: `.jpeg;application/pdf`
{% hint style="success" %}
**Tips:**
* The **application/pdf** extension is used in the **Accepted file types** parameter to enable the upload of PDF files.
* For more information on how to create and assign SharinPix Permission, refer to this article: [SharinPix Permission object](/documentation/access-and-security/sharinpix-permission-object-how-to-create-and-assign-custom-permission.md)
{% endhint %}
## Using the upload\_accept parameter in Apex Method
Online tokens can be used to restrict uploads based on file extensions using the `upload_accept` parameter that specifies the type of files that can be uploaded to an album.
For example, to restrict uploads to .png and .jpeg files, the value will be as follows:
`'upload_accept' => new List { '.png', '.jpeg' }`
The following code snippet demonstrates how to generate an online token with the `upload_accept` parameter.
```
public String generateToken(Id recordID) {
sharinpix.Client clientInstance = sharinpix.Client.getInstance();
String token = clientInstance.token(
new Map {
'Id' => recordID,
'upload_accept' => new List { '.png', '.jpeg' },
'path' => '/pagelayout/' + recordID,
'abilities' => new Map {
recordID => new Map {
'Access' => new Map {
'see' => true,
'image_list' => true,
'image_upload' => true
}
}
}
}
);
return token;
}
```
{% hint style="success" %}
**Tip:**
For more information on the common uses of online tokens and how they can be generated, refer to this article: [Online token generation methods](/documentation/access-and-security/online-token-generation-methods.md).
{% 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/restrict-uploads-using-file-extensions.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.