Upload Field

Shows an upload field in the Payload Admin Panel
Admin Panel screenshot of an Upload field

Example uses:

  • To provide a Page with a featured image
  • To allow for a Product to deliver a downloadable asset like PDF or MP3
  • To give a layout building block the ability to feature a background image

Config

OptionDescription
name *To be used as the property name when stored and retrieved from the database. More
*relationTo *Provide a single collection slug to allow this field to accept a relation to. Note: the related collection must be configured to support Uploads.
filterOptionsA query to filter which options appear in the UI and validate against. More.
maxDepthSets a number limit on iterations of related documents to populate when queried. Depth
labelText used as a field label in the Admin Panel or an object with keys for each language.
uniqueEnforce that each entry in the Collection has a unique value for this field.
validateProvide a custom validation function that will be executed on both the Admin Panel and the backend. More
indexBuild an index for this field to produce faster queries. Set this field to true if your users will perform queries on this field's data often.
saveToJWTIf this field is top-level and nested in a config supporting Authentication, include its data in the user JWT.
hooksProvide Field Hooks to control logic for this field. More details.
accessProvide Field Access Control to denote what users can see and do with this field's data. More details.
hiddenRestrict this field's visibility from all APIs entirely. Will still be saved to the database, but will not appear in any API or the Admin Panel.
defaultValueProvide data to be used for this field's default value. More
localizedEnable localization for this field. Requires localization to be enabled in the Base config.
requiredRequire this field to have a value.
adminAdmin-specific configuration. See the default field admin config for more details.
customExtension point for adding custom data (e.g. for plugins)
typescriptSchemaOverride field type generation with providing a JSON schema

* An asterisk denotes that a property is required.

Example

collections/ExampleCollection.ts

1
import { CollectionConfig } from 'payload'
2
3
export const ExampleCollection: CollectionConfig = {
4
slug: 'example-collection',
5
fields: [
6
{
7
name: 'backgroundImage', // required
8
type: 'upload', // required
9
relationTo: 'media', // required
10
required: true,
11
},
12
],
13
}

Filtering upload options

Options can be dynamically limited by supplying a query constraint, which will be used both for validating input and filtering available uploads in the UI.

The filterOptions property can either be a Where query, or a function returning true to not filter, false to prevent all, or a Where query. When using a function, it will be called with an argument object with the following properties:

PropertyDescription
relationToThe collection slug to filter against, limited to this field's relationTo property
dataAn object containing the full collection or global document currently being edited
siblingDataAn object containing document data that is scoped to only fields within the same parent of this field
idThe id of the current document being edited. id is undefined during the create operation
userAn object containing the currently authenticated user

Example

1
const uploadField = {
2
name: 'image',
3
type: 'upload',
4
relationTo: 'media',
5
filterOptions: {
6
mimeType: { contains: 'image' },
7
},
8
}

You can learn more about writing queries here.

Next

The Admin Panel