The File Storage is available in the Files section of Storage and contains all raw files uploaded to your project. It also contains files with data exported from tables. These are created when you request to export a table from Table Storage. The Files Storage serves two main purposes:
To store an arbitrary file, select the Files tab in Storage and then click Upload in the top right corner.
In the following dialog, select a file to upload along with other options:
For each uploaded file, you can enter an arbitrary number of tags in the
separating individual tags by pressing Enter. The tags can be used for filtering files later.
Important: The name of an uploaded file does not have to be unique because files are identified by their ID assigned on upload.
To avoid files being automatically deleted after 180 days (by default) and to keep them permanently, do not forget to tick the respective checkbox.
Also by default, uploaded files are marked as non-public. They are available only to the project administrators (those listed in the Users & Settings section) and users with Storage tokens who have the permission to Read all file uploads. Users without the Read all file uploads permission can access only their own files and the files they uploaded themselves. For each file in Files, you can
If you copy a link of a non-public file, you will obtain a URL in the following format:
Such a URL is valid for only one hour from the time of its generation — the time when the File upload list was shown to you, not when you clicked the link.
Important: The URL itself does not require any other authorization. That is, you can send a link to non-public files to people without access to your KBC project and they will be able to download that file via the direct link. However, they will not be able to generate or guess the link themselves.
If you copy a link to a public file, you will obtain a URL in the following format:
Such a URL is valid for the entire validity of the file itself (either 180 days or forever).
In some cases, the file may be sliced. When you encounter a sliced file, you will obtain a JSON manifest file instead of the actual file. This can happen for some exported or imported tables from Storage or files which are particularly large. Merging a sliced file requires a substantial effort.
The maximum allowed size of an uploaded file is currently 5GB (5,368,709,120 bytes exactly). This applies to both file and table uploads. The actual table size may be bigger, because it is uploaded as a compressed file. If you need to upload a larger file, you need to use sliced upload. In that case, the limit applies to the chunk size.
As stated above, unless marked as permanent, each file is automatically deleted 180 days after it has been created. This also applies to automatically generated files as a result of table imports and exports. Also, because the majority of KBC File Storage contains duplicates of your table data, the whole Files storage does not count towards your project quota.