Storage Engine: Local Storage

Uploaded files will be saved in a local directory on the server's hard drive. This is suitable for scenarios with a small total volume of uploaded files managed by the system or for experimental purposes.

:::warning Note

Local Storage does not support private access. After a file is uploaded, NocoBase generates a directly accessible URL, and anyone who has that URL can access the file.

If you need to store contracts, identity documents, internal materials, or other files that should not be public, use S3 Pro. If historical files already exist, see Migrate to S3 Pro.

If you are not using Docker or the official nginx configuration and access local uploaded files through a custom proxy, make sure the /storage/uploads/ path sets X-Content-Type-Options: nosniff and returns active content files such as html, svg, xhtml, and pdf as attachments. For details, see Security guide: File storage.

:::

Configuration Parameters

:::info{title=Note} This section only introduces parameters specific to the local storage engine. For general parameters, please refer to General Engine Parameters. :::

Path

Represents both the relative path for file storage on the server and the URL access path. For example, "user/avatar" (without leading or trailing slashes) represents:

1. The relative path on the server where uploaded files are stored: /path/to/nocobase-app/storage/uploads/user/avatar.
2. The URL prefix for accessing the files: http://localhost:13000/storage/uploads/user/avatar.