# Upload
Thanks to the plugin Upload
, you can upload any kind of file on your server or external providers such as AWS S3.
# Configuration
Currently the strapi middleware in charge of parsing request needs to be configured to support bigger file sizes if you need to upload file with a size greater than 200MB.
The library we use is koa-body
, and itself uses the node-formidable
library to process files.
You can pass configuration to the middleware directly by setting it in the parser
middleware configuration:
{
"parser": {
"enabled": true,
"multipart": true,
"formidable": {
"maxFileSize": 20000000 // defaults to 200mb
}
}
}
# Endpoints
Method | Path | Description |
---|---|---|
GET | /upload/files | Get a list of files |
GET | /upload/files/:id | Get a specific file |
POST | /upload | Upload files |
DELETE | /upload/files/:id | Delete a file |
# Upload files
To upload files into your application.
# Parameters
files
: The file(s) to upload. The value(s) can be a Buffer or Stream.
# Code example
<form>
<!-- Can be multiple files -->
<input type="file" name="files" />
<input type="submit" value="Submit" />
</form>
<script type="text/javascript">
const formElement = document.querySelector('form');
formElement.addEventListener('submit', e => {
e.preventDefault();
const request = new XMLHttpRequest();
request.open('POST', '/upload');
request.send(new FormData(formElement));
});
</script>
WARNING
You have to send FormData in your request body
# Upload files related to an entry
To upload files that will be linked to a specific entry.
# Request parameters
files
: The file(s) to upload. The value(s) can be a Buffer or Stream.path
(optional): The folder where the file(s) will be uploaded to (only supported on strapi-provider-upload-aws-s3).refId
: The ID of the entry which the file(s) will be linked to.ref
: The name of the model which the file(s) will be linked to (see more below).source
(optional): The name of the plugin where the model is located.field
: The field of the entry which the file(s) will be precisely linked to.
# Examples
The Restaurant
model attributes:
"attributes": {
"name": {
"type": "string"
},
"cover": {
"model": "file",
"via": "related",
"plugin": "upload"
}
}
Code
<form>
<!-- Can be multiple files if you setup "collection" instead of "model" -->
<input type="file" name="files" />
<input type="text" name="ref" value="restaurant" />
<input type="text" name="refId" value="5c126648c7415f0c0ef1bccd" />
<input type="text" name="field" value="cover" />
<input type="submit" value="Submit" />
</form>
<script type="text/javascript">
const formElement = document.querySelector('form');
formElement.addEventListener('submit', e => {
e.preventDefault();
const request = new XMLHttpRequest();
request.open('POST', '/upload');
request.send(new FormData(formElement));
});
</script>
WARNING
You have to send FormData in your request body
# Upload file during entry creation
You can also add files during your entry creation.
# Examples
The Restaurant
model attributes:
"attributes": {
"name": {
"type": "string"
},
"cover": {
"model": "file",
"via": "related",
"plugin": "upload"
}
}
Code
<form>
<!-- Can be multiple files if you setup "collection" instead of "model" -->
<input type="text" name="name" />
<input type="file" name="cover" />
<input type="submit" value="Submit" />
</form>
<script type="text/javascript">
const formElement = document.querySelector('form');
formElement.addEventListener('submit', e => {
e.preventDefault();
const request = new XMLHttpRequest();
const formData = new FormData();
const formElements = formElement.elements;
const data = {};
for (let i = 0; i < formElements.length; i++) {
const currentElement = formElements[i];
if (!['submit', 'file'].includes(currentElement.type)) {
data[currentElement.name] = currentElement.value;
} else if (currentElement.type === 'file') {
if (currentElement.files.length === 1) {
const file = currentElement.files[0];
formData.append(`files.${currentElement.name}`, file, file.name);
} else {
for (let i = 0; i < currentElement.files.length; i++) {
const file = currentElement.files[i];
formData.append(`files.${currentElement.name}`, file, file.name);
}
}
}
}
formData.append('data', JSON.stringify(data));
request.open('POST', `${HOST}/restaurants`);
request.send(formData);
});
</script>
Your entry data has to be contained in a data
key. You have to JSON.stringify
your data object.
And for your files, they have to be prefixed by files
.
Example here with cover attribute files.cover
.
TIP
If you want to upload files for a component, you will have to specify the index of the item you want to add the file to.
Example files.my_component_name[the_index].attribute_name
WARNING
You have to send FormData in your request body
# Models definition
Adding a file attribute to a model (or the model of another plugin) is like adding a new association.
In the first example below, you will be able to upload and attach one file to the avatar attribute.
Path — User.settings.json
.
{
"connection": "default",
"attributes": {
"pseudo": {
"type": "string",
"required": true
},
"email": {
"type": "email",
"required": true,
"unique": true
},
"avatar": {
"model": "file",
"via": "related",
"plugin": "upload"
}
}
}
In our second example, you can upload and attach multiple pictures to the restaurant.
Path — Restaurant.settings.json
.
{
"connection": "default",
"attributes": {
"name": {
"type": "string",
"required": true
},
"convers": {
"collection": "file",
"via": "related",
"plugin": "upload"
}
}
}
# Using a provider
By default Strapi provides a provider that uploads files to a local directory. You might want to upload your files to another provider like AWS S3.
You can check all the available providers developed by the community on npmjs.org - Providers list
To install a new provider run:
$ npm install strapi-provider-upload-aws-s3 --save
or
$ yarn add strapi-provider-upload-aws-s3
To enable the provider, create or edit the file at ./extensions/upload/config/settings.json
{
"provider": "aws-s3",
"providerOptions": {
"accessKeyId": "dev-key",
"secretAccessKey": "dev-secret",
"region": "aws-region",
"params": {
"Bucket": "my-bucket"
}
}
}
Make sure to read the provider's README
to know what are the possible parameters.
# Configuration per environment
When configuring your upload provider you might want to change the configuration based on the NODE_ENV
environment variable or use environment specific credentials.
You can do so using a settings.js
file:
if (process.env.NODE_ENV === 'production') {
module.exports = {
provider: 'providerName',
providerOptions: {
cloud_name: process.env.PROVIDER_CLOUD_NAME,
api_key: process.env.PROVIDER_API_KEY,
api_secret: process.env.PROVIDER_API_SECRET,
},
};
} else {
// to use the default local provider you can return an empty configuration
module.exports = {};
}
# Create providers
You can create a Node.js module to implement a custom provider. Read the official documentation here.
To work with strapi, your provider name must match the pattern strapi-provider-upload-{provider-name}
.
Your provider need to export the following interface:
module.exports = {
init(providerOptions) {
// init your provider if necessary
return {
upload(file) {
// upload the file in the provider
},
delete(file) {
// delete the file in the provider
},
};
},
};
You can then publish it to make it available to the community.
# Create a local provider
If you want to create your own provider without publishing it on npm you can follow these steps:
- Create a
./providers/strapi-provider-upload-{provider-name}
folder in your root application folder. - Create your provider as explained in the documentation above.
- Then update your
package.json
to link yourstrapi-provider-upload-{provider-name}
dependency to point to the local path of your provider.
{
...
"dependencies": {
...
"strapi-provider-upload-{provider-name}": "file:providers/strapi-provider-upload-{provider-name}"
...
}
}
- Finally, run
yarn install
ornpm install
to install your new custom provider.